Leave whenever you like
Bills, stock and the khata export to CSV, free, with no tier and no support request. Anti-lock-in costs us nothing and it is the fear worth answering first.
Not adjectives — a table. For each thing in your shop, who sees it: you, the boy at the counter, and us. Every “no” below is enforced by the server, which is the only kind of no that holds.
Support can tell whether your bills are syncing. They cannot open your khata, read a customer's name, or see a single rupee figure for your shop. It is not a policy we ask staff to follow — the endpoints do not return it.
A support conversation is “my bill did not sync” or “this product is flagged”. It is never “how much did you make”. A capability nobody needs only has a downside.
The middle column is the one worth reading twice — it is the reason you can hand the phone to someone else during a rush.
| In your shop | You, the owner | Your staff | Us |
|---|---|---|---|
| The day's takings | Yes — it is the first thing on the home screen. | No. There is no setting that turns this on. | No. Not per shop, not ever. |
| Individual bills | All of them. | Only the ones they made themselves. | No. |
| The udhaar book | Yes. | No. Staff cannot open it at all. | No. Customer names and balances are off limits to support by design. |
| Prices, and changing them | Yes. | Reads them. Changing one needs a permission you grant per person, off by default. | No. |
| Which phones are signed in | Their own. Every person sees only their own devices. | Their own, and they can sign a lost phone out themselves. | No. |
| Whether the shop is syncing | Yes. | Yes — it is on the screen while they bill. | Yes. This is how a stuck sync gets noticed before you have to report it. |
Bills, stock and the khata export to CSV, free, with no tier and no support request. Anti-lock-in costs us nothing and it is the fear worth answering first.
One request removes the account and its data. The page that describes it is linked from inside the app, and it is a real process rather than a form that opens a ticket.
The app writes to the phone first and syncs after. If our servers vanished tomorrow, the bills you made today would still be on your handset.
No logo, no watermark, no 'sent via'. The receipt is the shop's signboard, not our billboard, so there is no de-branding to sell back to you later.
Today it mostly doesn't need to. The app works offline, so it barely touches a server; the running cost of a pilot shop is close to nothing. That is a real answer and it only works at this size, which is why the pilot is small.
Later, money comes from places where the value is already obvious — listing placement for shops that want it, ordering between businesses, analytics for people who ask for analytics. Never from the till.
Billing, stock, the udhaar book and sync do not become paid, get row limits, get a device count, or start charging to restore a backup. Those are the five ways this category usually monetises, and each one works by removing something that already worked.
A paid listing will also never be allowed to outrank a real search result. If we ever sell placement it is a separate, labelled, capped slot — not a thumb on the scale.
No, and the sharpest version of that promise is about the khata specifically: the udhaar book is never sold, never shared, and never monetised. It is the record of a relationship that existed before this app and will outlast it.
Lending against your transaction history is the obvious way to make money here. It is also the obvious way to lose the trust the whole thing depends on, and it is written down internally as a decision that cannot be made quietly.
A small team building this in India, in the open, with a pilot you can talk to a human in. There is no growth team and no ad budget — which is also why you found this page rather than an advertisement.
Every security page on the internet says “bank-grade” and “encrypted”. Here is where those words would be doing more work than they deserve.
Nobody worries about a shop app until the network drops mid-sale. That is a separate page, and it is the one that shows the actual mechanism.