Cookie Policy
Last updated: September 29, 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
Instead of cookies, the app keeps the following on your device:
Sign-in: a session token in the iOS Keychain, to keep you signed in.
Settings and working data: your settings, such as language, currency and App Lock, and working data, such as the amounts on bills you take part in and copies of receipt photos so they open quickly. Reset and Delete Account in Settings clear this data; signing out removes the photo copies.
Crash reporting (Sentry): a small store of its own and a random identifier per installation, sent with crash reports and app starts so we can find and fix problems.
Usage statistics (PostHog): an identifier and a small store of its own for the usage statistics, only after you switch them on.
If you turn on notifications, we store your device's push token with your account so we can alert you about your bills. You can turn notifications off in iOS Settings.
2. The iOS app uses no cookies
Instead of cookies, the app keeps the following on your device:
Sign-in: a session token in the iOS Keychain, to keep you signed in.
Settings and working data: your settings, such as language, currency and App Lock, and working data, such as the amounts on bills you take part in and copies of receipt photos so they open quickly. Reset and Delete Account in Settings clear this data; signing out removes the photo copies.
Crash reporting (Sentry): a small store of its own and a random identifier per installation, sent with crash reports and app starts so we can find and fix problems.
Usage statistics (PostHog): an identifier and a small store of its own for the usage statistics, only after you switch them on.
If you turn on notifications, we store your device's push token with your account so we can alert you about your bills. You can turn notifications off in iOS Settings.
3. The website sets no cookies
Our web pages, tabsnap.app, split.tabsnap.app and pay.tabsnap.app, set no cookies. Our website host Framer counts visits to tabsnap.app for us without cookies, using the page you open, the site you came from, your browser's language, time zone and connection type, and, for daily unique visitors, your IP address and browser type. Nothing is stored on your device for this, and you are not recognised on another day.
The split page (split.tabsnap.app) keeps three things in your browser's local storage:
A random claim token, so you can return to the items you claimed. We also use it to count when the link was opened and whether the App Store banner was tapped, without your IP address or name.
A record of any extra items the host assigned to you after the bill was shared, so you still see what you owe.
The name you typed, so you do not have to type it again on the next bill.
The payment page (pay.tabsnap.app) stores nothing in your browser.
3. The website sets no cookies
Our web pages, tabsnap.app, split.tabsnap.app and pay.tabsnap.app, set no cookies. Our website host Framer counts visits to tabsnap.app for us without cookies, using the page you open, the site you came from, your browser's language, time zone and connection type, and, for daily unique visitors, your IP address and browser type. Nothing is stored on your device for this, and you are not recognised on another day.
The split page (split.tabsnap.app) keeps three things in your browser's local storage:
A random claim token, so you can return to the items you claimed. We also use it to count when the link was opened and whether the App Store banner was tapped, without your IP address or name.
A record of any extra items the host assigned to you after the bill was shared, so you still see what you owe.
The name you typed, so you do not have to type it again on the next bill.
The payment page (pay.tabsnap.app) stores nothing in your browser.
4. Similar technologies
Our website tabsnap.app loads one typeface from Google Fonts, so your browser contacts Google and sends it your IP address. Google states that it sets no cookies for this.
4. Similar technologies
Our website tabsnap.app loads one typeface from Google Fonts, so your browser contacts Google and sends it your IP address. Google states that it sets no cookies for this.
5. Consent
Under the ePrivacy Directive and the Dutch Telecommunicatiewet, storage that is strictly necessary to deliver what you asked for, such as the claim token and the record of extra items on the split page, needs no consent. Neither do visit statistics with little or no impact on your privacy, such as the cookieless counts on tabsnap.app and the link counts on the split page. That is why our web pages show no cookie banner. The remembered name only saves you typing, and everything the split page stores stays in your browser until you clear your site data.
In the app, the crash reporting library keeps a random identifier on your device without asking, because it only serves to keep the app working and has little impact on your privacy. Usage statistics only start after you switch them on, and you can switch them on or off at any time under Settings > Security & Privacy > Security > Usage statistics.
5. Consent
Under the ePrivacy Directive and the Dutch Telecommunicatiewet, storage that is strictly necessary to deliver what you asked for, such as the claim token and the record of extra items on the split page, needs no consent. Neither do visit statistics with little or no impact on your privacy, such as the cookieless counts on tabsnap.app and the link counts on the split page. That is why our web pages show no cookie banner. The remembered name only saves you typing, and everything the split page stores stays in your browser until you clear your site data.
In the app, the crash reporting library keeps a random identifier on your device without asking, because it only serves to keep the app working and has little impact on your privacy. Usage statistics only start after you switch them on, and you can switch them on or off at any time under Settings > Security & Privacy > Security > Usage statistics.
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