Your khata, locked the way a khata should be.
The books of a business are the most sensitive thing it owns. This page describes the controls that are actually built into E-Khata, in plain language, without claiming a badge we do not hold.
What is built in
Your data is yours, and it is separated
Every record in E-Khata carries the business it belongs to, and every request is scoped to that business before it reaches the database. A branch user's request is scoped again to their branch. There is no shared table a query can wander out of.
Permissions are per action, not per job title
Access is granted key by key. Who can see purchase prices, who can edit a posted invoice's tax, who can approve a stock movement, who can file to FBR. Roles bundle those keys for convenience, and a branch can narrow them further.
Nothing is silently deleted
Documents are cancelled and reversed, not erased. Cancelling an invoice reverses its accounting entries and stock movements and leaves both the original and the reversal on the record.
Every change is recorded with a before and after
The amendment log stores what the document looked like before the edit, what it looks like now, which user made the change, and when. There is a separate user activity log for actions that are not document edits.
Devices can be controlled
You can see which devices a user has signed in from and cut off access to one without disturbing the rest of the team.
Integration credentials are encrypted, and write-only
FBR tokens, WhatsApp credentials and API secrets are stored encrypted in a vault. Once saved, the interface will let you replace a credential but never read it back, so a screen-share or a support session cannot leak it.
API access is scoped and rate limited
Every API token carries a scope, requests are rate limited, and write calls accept an idempotency key so a retried request cannot post the same document twice.
Hosted on Microsoft Azure
The application and database run on managed Azure infrastructure with automated backups and encryption at rest and in transit. Passwords are hashed, and sessions are stored as hashes, never as recoverable tokens.
The questions buyers actually ask
- Can your staff see my data?
- Access to production data is limited to the engineers who operate the system, is used only to investigate a problem you have reported, and is logged. We do not read customer books for any other reason.
- What happens to my data if I leave?
- It stays yours. Every list and report exports, and we will produce a full export on request. Deletion is covered by our data deletion policy.
- Is my data kept in Pakistan?
- The production environment runs in a Microsoft Azure region selected for latency to Pakistan. If your business has a specific data residency requirement, raise it on the call and we will tell you plainly whether we can meet it.
- Do you have SOC 2 or ISO 27001?
- Not today. We describe the controls we actually operate rather than implying an audit we have not completed. If a certification matters to your purchase, tell us and we will give you a straight answer about timelines.
Found something, or need detail we have not published?
Report a vulnerability or ask a security question at support@ekhata.ai. We answer security mail before anything else in the queue.
See also our Privacy Policy, Terms of Service, and data deletion policy.