Privacy Policy
Last updated: 16 November 2026
Splitbook is an expense tracker, bill splitter and debt ledger (Khata) published by NexCode Labs ("we", "us"). This policy explains what the app collects, why, who can see it, where it is kept, and how to get rid of it.
Splitbook records who owes what. It never moves money. It is not a bank, a wallet or a payment service, it has no access to any payment rail, and it never asks for or stores card numbers, bank logins or any other banking credentials. A payment you record in the app is a note that money changed hands outside it.
1. What we collect, and why
We only collect what the app needs to work. The app shows ads through Google AdMob, which collects some device data of its own, counts installs and usage with Google Firebase Analytics, and sends crash reports through Google Firebase Crashlytics; see “Ads”, “Usage analytics” and “Crash reports” below.
Usage analytics
To understand how many people install and use Splitbook, the app uses Google Firebase Analytics. It records when the app is first opened, when you open it and for how long, which version you run, and your device model, Android version, language and approximate country (worked out from your IP address). Each installation gets a random app instance ID, and Firebase may also read your phone's advertising ID. We see this only as totals and trends: it is not linked to your name, email or account, and it never includes anything you record in the app.
Crash reports
If the app crashes or freezes, Google Firebase Crashlytics sends us a report so we can fix it: which part of the app's code failed, your device model, Android version, app version, free memory and storage, whether the phone is rooted, and the time of the crash, with a random ID for this installation. Reports are not linked to your name, email or account, and never include anything you record in the app.
Ads
Splitbook is free and shows ads served by Google AdMob: a banner at the bottom of the main screens and, at most once every few hours, a full-screen ad when you come back to the app, and now and then a full-screen ad after you save a new expense (never more than one every few minutes). To choose, show and measure ads, Google's ad SDK collects from your device the advertising ID, IP address, device and app information, and how you interact with ads (views and taps). Google may use this to show you personalised ads.
Ads never receive anything you record in the app: no expenses, amounts, names, receipts, balances or anything else from your ledger.
If you are in the European Economic Area or the UK, the app asks for your consent before ads are personalised, and you can change your choice later. Anywhere, you can reset or delete your advertising ID in your phone's settings (Settings → Privacy → Ads, or Settings → Google → Ads).
Your account
Email address, and a password that is hashed before storage — we never see or keep the password itself. If you sign in with Google we receive your name, email address and profile picture from Google. Used to identify you, keep you signed in, and recover your account.
What you record
Expenses and income you enter: amount, currency, date, merchant, note, category and account. Budgets, your expected monthly income, your chosen financial-month start day, what you measure spending against, and whether earlier expenses count against income you add later. This is the content of the app; it exists because you typed it.
Receipt photos
Photos you choose to attach to an expense or a payment. Picked through the Android photo picker, which hands the app one image at a time. Splitbook never reads your photo library.
Split and Khata (shared records)
When you connect with another Splitbook user, by invite code, for splitting bills or for a Khata / Debit ledger: the connection between your accounts and which list it belongs to; the bills, each person's share and any loans; every “You gave” / “You got” entry and payment recorded between you, with its amount, date and note; and, for groups, the group's name and icon, its members, and the payments recorded between members. Invite codes are single-purpose and stop working once used or withdrawn. These records are necessarily visible to the other people on them — see section 3.
People who are not on the app
Names you type for people who have no Splitbook account, and the shares, loans, ledger entries and payments you attach to them. See section 4.
Notification token
If notifications are enabled, a Firebase Cloud Messaging registration token identifying this installation. Used only to tell you when someone adds or settles an expense, a payment or a ledger entry that involves you, or connects with you. Deleted when you sign out.
Security settings
Your recovery question, and a one-way hash of its answer. If you use the private-expenses feature, a one-way hash of your PIN. We cannot read either back — they can only be checked against something you type. Fingerprint and face unlock are handled entirely by Android; the app is told only whether the check passed and never receives biometric data.
Your country (on the device only)
To suggest a default currency and choose the wording of the ledger (“Khata” or “Debit”), the app reads the country code of your SIM card or mobile network, or failing that your phone's language setting. This is a two-letter country code, not your location. It is used on the device and never uploaded. The currency you then pick is saved with your preferences.
Apart from what Google AdMob collects for ads and the usage counts described under “Usage analytics” above, we do not collect your precise location, contacts, call logs, SMS, installed-app list, or any behavioural profile tied to you.
2. Guest mode and offline use
If you use Splitbook without an account, everything you enter stays on your device and is never uploaded. We receive none of it. (The ads and usage analytics described in section 1 still run in guest mode and collect their device data.) If you later create an account, that local data is uploaded so it can sync — that upload is the point at which this policy begins to apply to it.
When you are signed in, the app keeps a copy of your records on the device so it works without a connection. Entries you make offline are queued on the phone and uploaded when you are back online. The device copy of your Split and Khata records is encrypted with a key held in the Android Keystore. Signing out removes the signed-in copy from the device.
While the app is open and online it keeps a live connection to our database, so balances update the moment someone you share records with changes one. That connection only carries changes to records you are already allowed to see; it collects nothing new.
3. What other people can see
Splitting and ledgers are shared by nature.
- A person you are connected with sees your display name and profile picture, and the bills, shares, loans, ledger entries and payments between the two of you.
- Members of a group see the group, its members (including people without the app — see section 4), every bill in it with each person's share, every payment recorded in it, and who owes whom within it.
- Notifications sent to the other people on a record include your name and what was recorded, such as the expense name and the amount.
Nobody can see anything else: not your other expenses, your income, your budgets, your balances with people they are not connected to, groups they are not in, or anything in your private ledger.
Statements you export as a PDF or image are made on your phone and contain whatever the screen contains. Once you have shared one, where it goes is outside our control and outside this policy.
4. People who do not have an account
Splitbook lets you record a name for someone who is not a user, so you can keep a split or a Khata for them.
- A person you add for yourself, for one-on-one splitting or a Khata, is visible to you alone.
- A person added to a group is visible by name to every member of that group, together with their shares and the payments recorded for them, so everyone sees the same balances. Only the group's creator can record payments on their behalf.
The person named is not notified and has no access, unless you send them a statement.
You are responsible for what you record about other people. Only enter what you need, keep it accurate, and remove it when it no longer serves a purpose. Removing a person from the app deletes their shares, entries and payments permanently.
5. Who processes your data
- Supabase — hosts the database, live updates and receipt storage. Data is held in Seoul, South Korea (ap-northeast-2).
- Google Firebase Cloud Messaging — delivers notifications. Receives the device token and the text of the notification, nothing else.
- Google Firebase Analytics — counts installs and usage. Receives the device and usage data described under “Usage analytics” in section 1, never your ledger. How Google uses it: policies.google.com/technologies/partner-sites.
- Google Firebase Crashlytics — collects crash reports. Receives the crash data described under “Crash reports” in section 1, never your ledger.
- Google Sign-In — only if you choose it, and only to verify who you are.
- Google Play — installs and updates the app under Google's own policy. The app uses Play to check whether an update is available, and for the optional one-time “Remove ads” purchase: payment happens entirely inside Google Play, and the app is told only whether your Google account owns it. We never see your card or payment details, and nothing about the purchase is stored on our servers.
- Google AdMob — shows the ads. Receives the device data described under “Ads” in section 1, never your ledger. How Google uses it: policies.google.com/technologies/partner-sites.
We do not sell your data or rent it. Nothing you record in the app is shared for advertising; the only data that reaches an ad network is what Google AdMob collects from the device, described in section 1. We give your data to no one else except where the law requires it.
6. Keeping and deleting
Your data is kept while your account exists. Delete anything from inside the app at any time — an expense, a receipt, a payment, a ledger entry, a group, a person — and it is removed from our systems.
To delete your account and everything in it, open Settings in the app and tap Delete my account. It is erased immediately. If you no longer have the app, email labsnexcode@gmail.com from your registered address and we will erase it within 30 days. Records that belong to other people as well — their copy of a bill or ledger you both shared — stay with them. Full details are on the account deletion page.
7. Security
Every connection is HTTPS, and the app refuses unencrypted traffic outright. Access is enforced per-row in the database, so a request can only ever return records the signed-in account is allowed to see. Device backups are disabled, so the local copy of your data cannot be lifted off the phone through Android's backup system.
You can add a biometric or PIN lock, and keep selected expenses in a PIN-protected private ledger that is hidden from every other screen.
No system is perfect, and we do not claim otherwise.
8. Children
Splitbook is not intended for children under 13 (or the minimum age in your country). We do not knowingly collect their data. If you believe a child has given us data, contact us and we will remove it.
9. Your rights
Depending on where you live, you may have the right to see a copy of your data, correct it, delete it, export it, or object to how it is used. Most of this is already available inside the app — export your history from Settings, and edit or delete anything at any time. For anything else, contact us.
10. Changes
We will update this page if the app changes what it collects, and update the date at the top. Material changes will be announced in the app.
11. Contact
labsnexcode@gmail.com
NexCode Labs, Pakistan