Your business records, kept pakka.

Your data is only yours

No other business on Pakka can see your items, customers or bills.

On the server, every business's records are separated by database row-level security — enforced by the database itself on every query, not only by application code.

• On a device, each business gets its own local database. Two businesses signed in on the same browser never see each other's items, customers or bills.
• Tested by signing up a second business in the same browser and checking it sees nothing of the first.

Staff see only their job

Owner, manager, counter staff and stock staff each get what their work needs.

Four roles — owner (admin), manager, counter staff and stock — checked on the server for every action, never only hidden on screen.

• Purchase cost is hidden from counter staff on screen, in exports and in the data kept on the device.
• Approvals can never be decided by the person who asked for them.
• Only the owner can change the UPI ID printed on bills, and every change is logged.

Nothing can be secretly edited

Bills, payments and stock movements can't be edited or deleted — only corrected, with a reason.

Financial records are append-only: the database refuses edits and deletes on bills, payments, stock movements and change logs.

• A mistake is corrected by a reversing entry that records who, when and why.
• The customer's details are frozen onto each invoice, so editing a customer later never rewrites a past bill.

Closed days can't be changed quietly

Each closed day is locked with a digital seal linked to the day before, so any change shows.

Each closed day is sealed with a SHA-256 hash that includes the previous day's seal, forming a chain.

• If a sealed record is changed, it no longer matches its seal — and the seal can be checked.
• The database refuses new entries dated into a closed day. An owner's correction needs a written reason and is shown on that day.

Passwords kept safe

Nobody — including us — can read your password.

Passwords are stored only as argon2id hashes, never in readable form, and must be at least 12 characters.

• Common passwords are refused.
• Long-lived sign-in (refresh) tokens are stored on the server only as hashes.

Photos checked, not trusted

Uploaded photos are checked by what is actually inside them.

Uploads are validated by their actual content, not by the file type they claim.

• Supplier bill scan (Beta) sends only the image and a fixed instruction to an AI service to read it. The image isn't stored, and nothing is saved until you review the draft.

Encrypted connections

Data between your device and our servers will be encrypted.

In production, Pakka will be served only over HTTPS.

Data stays in India

We plan to keep your data in India.

Hosting, including sealed daily records, planned in India-region data centres.