A bookkeeping tool holds the most sensitive paper in a business. Here is how Pakka Books looks after it.
Kept apart
Two locks between your books and everyone else's.
Every business on Pakka Books has its own address and its own data. The app keeps each request to one business, and the database checks it again, row by row.
Every request
Your request
Signed in at your business's own address
Lock 1: the app
Adds your business to every read and write
Lock 2: the database
Row-level security in Postgres checks each row
Only your rows
Invoices, bills, staff: yours and nobody else's
If the app ever made a mistake
A query with a bug
Forgets to say which business it is for
Lock 1 missed it
The kind of slip code can make
Lock 2 still holds
With no business named, the database returns nothing
Nothing leaks
Another business's rows are never returned
Many businesses share one database, each kept apart by both locks. The database also refuses a record that points at another business's record. These locks protect against mistakes in our code; like any system, they assume our servers themselves are not taken over.
Signing in
What stands between a stranger and your books.
Step 1InvitedNo public sign-up into your books: people join by invitation, with a role.
Step 2Password, hashedStored with a slow hash, never as text. Or Google, for existing members only.
Step 32-step codeTurn on an authenticator app; backup codes for a lost phone.
Step 4Guesses slowedRepeated wrong tries are rate-limited automatically.
Step 5One addressA sign-in works only at your business's own address.
Step 6LoggedEach sign-in and failed try is recorded for the owner, with device and time.
Every protection
Ten things that keep your data yours.
Invite-only access, with roles
There is no public way into your books. People join when you invite them, and each role (Owner, Admin, Staff, Accountant, or your own) decides exactly what they can see and change. Nobody can give themselves more access than they have.
Staff see only their own HR
An employee's login opens their own payslips, leave, attendance and claims, and nothing else. Your books stay closed to them until you give that person a role that includes them, and the Employee role itself can never be widened. When someone leaves, their login is switched off and they are signed out everywhere.
Sign-in you can trust
Sign in with email and password, or with Google. Turn on 2-step verification with an authenticator app, and a stolen password alone is not enough. Repeated wrong guesses are slowed down automatically.
Passwords are never stored as text
Passwords are hashed with a strong, slow algorithm. We cannot read yours, and neither can anyone who might get at the database.
Encrypted connections
Everything between your phone or computer and Pakka Books travels over HTTPS.
Private files
Supplier bills, logos and signatures live in private storage. They are only handed to people who are signed in and allowed to see them. There are no public file links.
Kept in India
Your data is held in managed Postgres in Mumbai, with the app running in the same region.
Your data, yours to take
Download your GST reports as CSV and print or save any invoice as a PDF, whenever you like.
A record of every sign-in
Owners can see each sign-in and each failed attempt, with the time, address and device, next to the record of who changed what. Entries can't be edited or deleted, and the whole log can be downloaded.
Control of your sessions
See where you are signed in, and sign out all your other devices in one tap. Signing out of the Android app also clears the pages it saved on the phone.
Reading bills with AI
Read on our servers first. You always confirm.
Most supplier bills are read entirely on our own servers. Only when a photo or scan is too hard for that, and only on the Enterprise plan, a copy can be sent to Google's Gemini to double-check it. You always see the result before anything is saved.