Cookie Policy
Last updated: August 25, 2026
Content
1. Introduction
This Cookie Policy explains what cookies and similar technologies Tabsnap uses, and what we do not use. Tabsnap is operated by Tabsnap B.V., Berkenweg 11, 3941 JA Doorn, the Netherlands.
This policy covers the Tabsnap iOS app and our web pages: tabsnap.app, split.tabsnap.app, and pay.tabsnap.app. Our internal admin and investor dashboard sits on a separate address, is not open to the public, and uses only the strictly necessary sign-in cookies needed to keep the people we invited signed in.
We believe in being blunt about this. Read on for the short version.
1. Introduction
This Cookie Policy explains what cookies and similar technologies Tabsnap uses, and what we do not use. Tabsnap is operated by Tabsnap B.V., Berkenweg 11, 3941 JA Doorn, the Netherlands.
This policy covers the Tabsnap iOS app and our web pages: tabsnap.app, split.tabsnap.app, and pay.tabsnap.app. Our internal admin and investor dashboard sits on a separate address, is not open to the public, and uses only the strictly necessary sign-in cookies needed to keep the people we invited signed in.
We believe in being blunt about this. Read on for the short version.
2. The iOS app uses no cookies
The Tabsnap iOS app does not use cookies. Cookies are a web technology, and the app is a native iOS app, so there are no cookies to set.
The app does store a local session token on your device to keep you signed in. That token is not a cookie. It stays on your device, in the iOS Keychain, and is used to talk to our Supabase backend. The app also stores a small number of preferences (such as your chosen language, currency, appearance, and whether App Lock with Face ID is enabled) in iOS UserDefaults on your device. None of these leave the device for tracking purposes.
The app uses a small number of native SDKs that are libraries, not browser trackers, so they set no cookies:
Crash reporting (Sentry): a native library used to capture crash and error reports so we can fix bugs. It does not set browser cookies.
Product analytics (PostHog): EU-hosted product analytics, off until you switch it on. Events are recorded per action and tied to a one-way hashed id, which under the GDPR makes them pseudonymous rather than anonymous. We do not send your name, phone number, email, or exact bill amounts to PostHog. We ask once during sign-up, and before you say yes the SDK is never started. You can change your answer at any time under Settings > Security & Privacy > Security > Anonymous analytics.
If you turn on notifications, the app registers for Apple Push Notifications and stores a device push token linked to your account so we can alert you about your bills, for example when someone pays their share. You can turn notifications off anytime in iOS Settings.
2. The iOS app uses no cookies
The Tabsnap iOS app does not use cookies. Cookies are a web technology, and the app is a native iOS app, so there are no cookies to set.
The app does store a local session token on your device to keep you signed in. That token is not a cookie. It stays on your device, in the iOS Keychain, and is used to talk to our Supabase backend. The app also stores a small number of preferences (such as your chosen language, currency, appearance, and whether App Lock with Face ID is enabled) in iOS UserDefaults on your device. None of these leave the device for tracking purposes.
The app uses a small number of native SDKs that are libraries, not browser trackers, so they set no cookies:
Crash reporting (Sentry): a native library used to capture crash and error reports so we can fix bugs. It does not set browser cookies.
Product analytics (PostHog): EU-hosted product analytics, off until you switch it on. Events are recorded per action and tied to a one-way hashed id, which under the GDPR makes them pseudonymous rather than anonymous. We do not send your name, phone number, email, or exact bill amounts to PostHog. We ask once during sign-up, and before you say yes the SDK is never started. You can change your answer at any time under Settings > Security & Privacy > Security > Anonymous analytics.
If you turn on notifications, the app registers for Apple Push Notifications and stores a device push token linked to your account so we can alert you about your bills, for example when someone pays their share. You can turn notifications off anytime in iOS Settings.
3. The website uses only essential cookies
The tabsnap.app website sets no cookies at all. What our split and payment pages (split.tabsnap.app and pay.tabsnap.app) do use is first-party browser storage, which never travels to a server on its own:
A random claim token, so you can return to the items you claimed.
The display name you type in yourself, so you do not have to type it again on the next bill.
A local record of any extra items the host assigned to you after the bill was shared.
That is the full list, and all three are strictly necessary to deliver the page you asked for.
On the website we do not use, and we do not set:
Google Analytics (_ga, _gid, _gat)
Facebook Pixel (_fbp, fr)
Any advertising or retargeting cookies
Any marketing or attribution cookies
We do use product analytics (PostHog) in the Tabsnap iOS app, described in section 2. This is anonymous, EU-hosted, and uses no browser cookies. It is a native SDK in the app, not a website cookie..
3. The website uses only essential cookies
The tabsnap.app website sets no cookies at all. What our split and payment pages (split.tabsnap.app and pay.tabsnap.app) do use is first-party browser storage, which never travels to a server on its own:
A random claim token, so you can return to the items you claimed.
The display name you type in yourself, so you do not have to type it again on the next bill.
A local record of any extra items the host assigned to you after the bill was shared.
That is the full list, and all three are strictly necessary to deliver the page you asked for.
On the website we do not use, and we do not set:
Google Analytics (_ga, _gid, _gat)
Facebook Pixel (_fbp, fr)
Any advertising or retargeting cookies
Any marketing or attribution cookies
We do use product analytics (PostHog) in the Tabsnap iOS app, described in section 2. This is anonymous, EU-hosted, and uses no browser cookies. It is a native SDK in the app, not a website cookie..
4. Similar technologies
We do not use tracking pixels, web beacons, fingerprinting scripts, or session replay tools on the website or in the app. The only usage data we collect is the EU-hosted, pseudonymous product analytics in the iOS app described in section 2. It is off until you switch it on, and you can switch it off again under Settings > Security & Privacy > Security > Anonymous analytics.
4. Similar technologies
We do not use tracking pixels, web beacons, fingerprinting scripts, or session replay tools on the website or in the app. The only usage data we collect is the EU-hosted, pseudonymous product analytics in the iOS app described in section 2. It is off until you switch it on, and you can switch it off again under Settings > Security & Privacy > Security > Anonymous analytics.
5. Consent
Our web pages use only strictly necessary, first-party storage, and all of it stays in your own browser. On split.tabsnap.app that is three things: a random token so you can return to your own claim, the name you type in yourself so you do not have to type it again, and a local record of any extra items the host assigned to you, so you still see what you owe when you come back. None of it is used for tracking or advertising. It stays in your browser until you clear your site data. The link itself expires on our side after 14 days. Under the ePrivacy Directive and the Dutch Telecommunicatiewet, storage that is strictly necessary to deliver a service you asked for does not require prior consent, so there is no cookie banner on tabsnap.app and none is required.
If we ever add anything that is not strictly necessary, for example website analytics, we will show a proper consent banner before setting it, and you will be able to accept, reject, or configure your choice, with rejecting just as easy as accepting.
The Tabsnap app uses no advertising and no cross-app tracking. Its product analytics are optional and off by default, and you can switch them on or off at any time under Settings > Security & Privacy > Security > Anonymous analytics.
5. Consent
Our web pages use only strictly necessary, first-party storage, and all of it stays in your own browser. On split.tabsnap.app that is three things: a random token so you can return to your own claim, the name you type in yourself so you do not have to type it again, and a local record of any extra items the host assigned to you, so you still see what you owe when you come back. None of it is used for tracking or advertising. It stays in your browser until you clear your site data. The link itself expires on our side after 14 days. Under the ePrivacy Directive and the Dutch Telecommunicatiewet, storage that is strictly necessary to deliver a service you asked for does not require prior consent, so there is no cookie banner on tabsnap.app and none is required.
If we ever add anything that is not strictly necessary, for example website analytics, we will show a proper consent banner before setting it, and you will be able to accept, reject, or configure your choice, with rejecting just as easy as accepting.
The Tabsnap app uses no advertising and no cross-app tracking. Its product analytics are optional and off by default, and you can switch them on or off at any time under Settings > Security & Privacy > Security > Anonymous analytics.
6. Managing cookies in your browser
You can control cookies through your browser settings. You can block all cookies, block third-party cookies only, or delete existing cookies. Because our pages rely on browser storage rather than cookies, blocking cookies does not break them, but clearing your site data does remove your claim token and saved name, so a shared bill may no longer recognise you.
Short guides:
Safari: Settings > Safari > Privacy & Security.
Chrome: Settings > Privacy and security > Cookies and other site data.
Firefox: Settings > Privacy & Security > Cookies and Site Data.
Edge: Settings > Cookies and site permissions > Manage and delete cookies and site data.
6. Managing cookies in your browser
You can control cookies through your browser settings. You can block all cookies, block third-party cookies only, or delete existing cookies. Because our pages rely on browser storage rather than cookies, blocking cookies does not break them, but clearing your site data does remove your claim token and saved name, so a shared bill may no longer recognise you.
Short guides:
Safari: Settings > Safari > Privacy & Security.
Chrome: Settings > Privacy and security > Cookies and other site data.
Firefox: Settings > Privacy & Security > Cookies and Site Data.
Edge: Settings > Cookies and site permissions > Manage and delete cookies and site data.
7. Changes to this policy
If we change the cookies we use, we will update this policy and the "Last updated" date at the top. For any addition of non-essential cookies, we will also show a consent banner before the new cookies are set.
7. Changes to this policy
If we change the cookies we use, we will update this policy and the "Last updated" date at the top. For any addition of non-essential cookies, we will also show a consent banner before the new cookies are set.
8. Contact
Questions about this policy:
Email: contact@tabsnap.app
Tabsnap B.V., Berkenweg 11, 3941 JA Doorn, the Netherlands
8. Contact
Questions about this policy:
Email: contact@tabsnap.app
Tabsnap B.V., Berkenweg 11, 3941 JA Doorn, the Netherlands