Data safety
Google Play asks every app to declare what it collects. This page is that declaration in plain English, so you can read it without going through the Play Store — and so it can be checked against what the software actually does.
Last reviewed
The short version
- We collect what running a shop's till requires: who you are, and what you sold.
- We share none of it. Nothing is sold, and nothing is passed on for anyone else's purposes.
- No analytics, no ads, no tracking, no crash reporting. Not "off by default" — not present.
- All of it is encrypted in transit.
- You can ask us to delete your account, from inside the app or from this website.
What we collect, item by item
"Shared" has Play's specific meaning here: passed to another company for their purposes. Our service providers — the database, sign-in and hosting companies listed in the privacy policy — process data on our instructions only, which Play does not count as sharing, and neither do we.
| Data type | Collected | Shared | Why | Required |
|---|---|---|---|---|
| Name | Yes | No | Account management, and showing who rang up a sale | Optional |
| Email address | Yes | No | Account management — it is how an owner signs in | Required |
| Phone number | Yes | No | Staff sign-in by SMS code, and customer records a shop chooses to keep | Optional |
| User IDs | Yes | No | Account management | Required |
| Photos | Yes | No | Product images and a business logo, uploaded by the owner | Optional |
| Purchase history | Yes | No | The shop's own sales records, reports and receipts | Required |
| Crash logs and diagnostics | No | No | Crash reporting ships switched off — see below | — |
| Device or other IDs | No | No | No advertising ID, no analytics ID, no push token | — |
| Location | No | No | Never requested, at any precision | — |
| Payment information | No | No | Entered on Razorpay's own page — it never reaches our apps or servers | — |
| Contacts, messages, calendar, audio, files | No | No | No permission is requested for any of these | — |
Two answers worth explaining
Crash reporting is off, and that is not a default we forgot to change
The apps include a crash-reporting library, and it is never switched on. Initialising it requires a key to be supplied when the app is built, and no build supplies one — so the reporter is never started and no diagnostic data leaves your device. That is why the table above says no rather than optional.
If we ever start collecting crash reports, this page and the Play declaration change together, and we will say so here.
Payment details never reach us
Paying for a subscription opens Razorpay's own hosted checkout. Your card number, UPI ID or bank details are typed on Razorpay's page and handled by Razorpay, who are a regulated payment processor. Our apps never display a card field and our servers never receive one. What we store is the fact that a payment succeeded, its amount, and when the next one is due.
Deletion
Yes — you can request deletion of your account and its data. There are two ways, and they reach the same place:
- In the admin app: Settings → Delete account.
- On the web, including after you have uninstalled the app: the deletion request page.
Requests are actioned within 30 days. Completed sales are an exception and are retained — they are your business's statutory books, and tax law requires them to be kept. The deletion page spells out exactly what goes and what stays.
Security
- Encrypted in transit end to end, over HTTPS.
- Which business a request may read is decided by our own server from your signed-in identity, never from anything the app sends — so no request can ask for another business's data.
- Staff accounts are limited to what their role allows.
Audience
These are business tools for shop owners and their staff, intended for people aged 18 and over. They are not directed at children.