>_ SAJIBU LABS
  • Services
  • Solutions
  • Approach
  • Why Us
  • Contact

legal / privacy policy

Privacy policy

Effective date: 25 September 2026 Applies to: the Tab Keeper mobile app for Android and iOS, and the Tab Keeper API it connects to.

The short version

Question Answer
What do you collect? The identity your sign-in provider gives us, and the contacts and transactions you type in. Nothing else.
Why? To run the ledger. That is the whole purpose.
Who else sees it? Google, Apple or Facebook — whichever you sign in with — and whoever hosts the database. No analytics, no advertisers, no data brokers.
Is it sold? No. It is never sold, rented, or shared for advertising, and there is no advertising or analytics code in the app.
Where is it? Your device holds only your login token and your theme choice. Everything else is in the database behind the API.
How do I delete it? Settings → Delete account, in the app. It is immediate and cannot be undone. See the account deletion page.
Who do I ask? support@sajibulabs.com

1. Who we are

Tab Keeper is developed and operated by Sajibu Labs (India) — "we". That makes us the data controller for the personal data described here: we decide what is collected and why.

For anything in this policy, including to exercise any of the rights in section 9, write to support@sajibulabs.com.

2. What we collect

2.1 What you give us

What Where it comes from Why we need it
Email address Your sign-in provider Identifies your ledger, and links your ledger if you later sign in with a different provider using the same address
Display name Your sign-in provider Shown as your account name inside the app
Profile picture URL Your sign-in provider Shown on your profile card. It is a link to the provider's own image, not a copy we store
Provider and provider account ID Your sign-in provider The identifier that says "this login is this ledger". We store Google's, Apple's or Facebook's ID for you, never your password — we never see a password at all

If you use Sign in with Apple and choose to hide your address, the only email we ever receive is the private relay address Apple generates for you. We store that and never learn your real one.

2.2 What you record

The contents of your ledger, which is the point of the app:

  • Contacts — the name you give someone, and an optional note about them.
  • Transactions — for each one: whether it was lent or borrowed; whether it was money or a physical item; the amount and its currency, or the item's name; an optional description; its status (active, settled, returned, or written off as a gift); the date the loan happened; and an optional reminder date.
  • Preferences — your chosen currency and symbol.

That is the complete list. It is also in the data inventory, field by field, if you want to check it against the database schema (available from us on request).

2.3 What the app never collects

This is the part most policies leave vague, so here it is explicitly. Tab Keeper has no:

  • analytics, telemetry, or usage tracking of any kind;
  • crash reporting;
  • advertising, ad identifiers, or attribution SDKs (see the note below);
  • access to your device's address book;
  • access to your camera, microphone, photos, location, or files;
  • push notifications;
  • cookies or any other tracking technology — authentication is a token sent in a request header, so there is nothing to consent to and nothing to clear;
  • automated decision-making or profiling;
  • any processing of your data to train machine learning models.

About the advertising-ID permission. The Android build declares com.google.android.gms.permission.AD_ID. That declaration is added automatically by the libraries that implement the sign-in buttons; it is not something Tab Keeper asks for or uses. The app contains no advertising code and never reads the advertising identifier. We intend to remove the declaration outright, and this page will be updated when we do.

About your contacts. When you use "Import from phone", Tab Keeper opens the system contact picker — the same screen the operating system shows other apps — and receives only the name of the single contact you tap. The app never asks for, and does not have, permission to read your address book, and it never uploads a list of your contacts. If you never use that button, no contact data from your device is ever read.

3. Why we process it, and on what legal basis

Purpose Data Legal basis (GDPR Art. 6)
Creating and running your account; storing and displaying your ledger All of section 2.1 and 2.2 Performance of a contract — 6(1)(b). The app cannot work without them
Keeping the service secure: authenticating requests, preventing abuse Your login token, and the access logs described in section 6 Legitimate interests — 6(1)(f). We have a genuine interest in keeping accounts and the service safe, and this processing is minimal and expected

We do not process your data on the basis of consent, which is why there is nothing to opt out of and no consent banner: nothing beyond running the ledger happens at all. We do not use your data for marketing, and we do not create profiles of you.

4. Who else is involved

We do not sell your personal data, share it for advertising, or hand it to data brokers. There are exactly two kinds of third party that touch it:

4.1 Your sign-in provider

Whichever you choose — Google, Apple, or Facebook (Meta). When you sign in, the provider authenticates you and returns a token, which our backend verifies directly with that provider. The provider also sees your IP address and the fact that you are using Tab Keeper; their handling of that is governed by their own privacy policy, not this one.

We receive only the fields in section 2.1. We do not receive, and cannot read, your password, your friends list, your mail, or anything else in your account with them.

4.2 Our infrastructure provider

The API and the database run on infrastructure provided by Hostinger International Limited (Mumbai, India), who process the data on our instructions as a processor. The data is stored in a PostgreSQL database that only this application can reach, in a dedicated schema rather than a shared one.

If you would like a current list of sub-processors, ask us at support@sajibulabs.com.

5. Your profile picture

Your provider gives us a URL for your profile picture, and the app loads it directly from the provider's servers when it shows your profile. That request goes to Google, Apple or Facebook, not to us, and it reveals your IP address to them. If you would rather that did not happen, the picture is cosmetic: the app falls back to showing your initial.

6. Logs

The web server in front of the API keeps standard access logs — the kind any web server keeps: IP address, the path requested, the response code, the time. These are used for security and debugging, are never used to build a profile, and are not combined with your ledger.

Request bodies are not logged, so the amounts, item names and notes you record do not appear in logs. Your token is not logged either. The API also deliberately logs nothing about you at application level — the only log lines in the code are "started" and "shutdown".

7. How long we keep it

Data Kept for
Account, contacts, transactions, preferences Until you delete your account. There is no expiry and no archival: if you keep using the app, the ledger stays
Login tokens on your device Until you sign out, or the refresh token expires (30 days of no use), or you delete the app
Access logs At our hosting provider's standard log retention
Backups 30 days — see the note below

About backups. Deleting your account removes your data from the live database immediately (see the account deletion page). If Hostinger takes database backups, deleted records can survive inside those backups until they age out — 30 days. They are not restored except to recover from a failure, and they are never used for anything else.

8. Security

  • Sign-in happens entirely through your provider; no password is ever sent to or stored by Tab Keeper.
  • Access is authorised on every request by a signed token that contains only an opaque account ID and an expiry — your email, name and ledger contents are not inside the token.
  • The API scopes every single query to the signed-in account. There is no way to reach another account's data; requests for it are answered with "not found" rather than leaking whether it exists.
  • Your tokens are stored on your device in the platform's secure storage — the iOS Keychain and the Android Keystore-backed encrypted store — never in plain preferences.
  • All traffic between the app and the API goes over HTTPS in the published app. The API address is fixed when the app is built, so there is no way for it to be pointed somewhere else at runtime.

No system is perfectly secure, and we cannot promise otherwise. If we ever became aware of a breach affecting your personal data, we would notify affected users and the relevant supervisory authority as the law requires.

9. Your rights

You have the rights listed in the data rights summary (available from us on request), which also says how to exercise each one and how quickly. In short: access, correction, deletion, portability, restriction, and objection. To use any of them, write to support@sajibulabs.com. Deletion you can also do yourself, instantly, in the app.

If you are in the EU, the UK, or another jurisdiction with a data protection authority, you have the right to complain to that authority. We would rather you came to us first.

10. Where your data goes

Our infrastructure is in Mumbai, India (Hostinger International Limited).

Your sign-in provider may be in the United States. That means verifying your login involves a transfer of your identity data outside your country — to Google, Apple or Facebook, under the safeguards those companies provide for international transfers (Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework). We send them only the token needed to answer the question "is this login genuine?".

11. Children

Tab Keeper is not for children. It is a record-keeping tool for adults, and it is not directed at anyone under 16 in the European Economic Area or the United Kingdom, or under 13 elsewhere. We do not knowingly collect data from children; if you believe a child has used the app, write to support@sajibulabs.com and we will delete the account.

12. Changes

If this policy changes in a way that matters — a new kind of data, or a new purpose — we will say so in the app before the change takes effect, and update the effective date at the top of this page. Continuing to use Tab Keeper after a change means you accept it. Earlier versions are available from us on request.

13. Contact

Sajibu Labs

India

support@sajibulabs.com

Published at https://sajibulabs.com/privacy-policy.

← Back to Sajibu Labs

SAJIBU LABS

© 2026 Sajibu Labs · Imphal-01 · contact@sajibulabs.com

Services Solutions Approach Why Us Contact
Privacy Policy Terms of Service Account Deletion