Trust & safety
Security & trust
Your firm holds trade licences, Emirates IDs, bank statements, and the books of every client you serve. That is exactly the kind of data that deserves engineering discipline, not marketing adjectives.
This page lists what PocketLedger actually does to protect it — every claim here describes a control built into the product today.
Why it matters
Your practice answers for its clients. We answer to you.
An accounting firm is itself a regulated business. When you put client records, ledgers, and filings into a platform, you are extending your professional responsibility onto it — so the platform has to be built like the systems your clients trust you to run.
PocketLedger's controls follow that chain of accountability: isolation between firms, precise permissions within a firm, and a record of every sensitive action taken.
What's built in
The controls, in plain language
Grouped by what they protect. No certifications implied, no vague assurances — just what the product enforces.
Isolation
Every record belongs to your firm
PocketLedger is multi-tenant by design: every record is scoped to the firm that owns it, and that scoping is enforced in the data layer on every query — not left to individual screens to remember.
Super-admin separation
Platform administration is a separate principal from firm staff. Day-to-day roles in your practice never carry platform-level rights.
Access control
Granular, per-action permissions
Access is governed by a permission registry keyed by resource and action — for example, accounting:journal:post. Each staff member holds roles, and roles hold exactly the permissions they need.
Short-lived sessions, no tokens in the browser
Sign-in issues short-lived access tokens with refresh rotation, delivered in httpOnly secure cookies. Nothing is stored in browser storage for scripts to steal, and every cookie-authenticated write requires a CSRF protection header.
Passwordless client portal
Your clients log in with a one-time code sent to them — there are no client passwords in the system, so there are no client passwords to leak.
Data integrity
Full audit trail
Sensitive actions are logged with who did what, and when. When a regulator or a partner asks how a number got there, the answer is on record.
Filed periods lock
Once a tax period is filed, it locks. Nothing changes the underlying figures silently — corrections happen in the open, in later periods.
No double-posting
Background work runs with retries and idempotency keys, so a retried job posts once — a network hiccup never becomes a duplicate journal entry.
Communications
Encrypted in transit
All traffic between your browser, the client portal, and our servers is encrypted with TLS, with HSTS ensuring browsers never fall back to an insecure connection.
Verified inbound webhooks
Messages arriving from WhatsApp are signature-verified before they are processed — spoofed payloads are rejected at the door.
Where we're headed
Honest about today, working on tomorrow
We don't yet hold formal certifications such as SOC 2 or ISO 27001 — they are on our roadmap as the platform and the team grow. We would rather say that plainly than decorate this page with badges.
What we can do today is walk you through our current posture in detail — how isolation, access control, and auditing work in practice. Ask us in a demo; it's a conversation we enjoy having.
Common questions
What firms ask us about security
No. Every record in the system is scoped to the firm that owns it, and that scoping is enforced in the data layer on every query. Isolation isn't a per-screen convention — it's how data access works throughout the platform.
Ask us the hard questions
Bring your security checklist to a demo — we'll show you how each control works in the real product.