Trust and security
This platform holds the financial record. It has to be defensible.
The books we keep have to stand up to an auditor, a tax authority and a court, years after the person who created the entry has left the company.
The ledger
How the ledger protects itself
Correctness is enforced by the lowest layer that can enforce it, because guarantees placed in application code eventually get bypassed by application code.
Balance is a database constraint
Debits equal credits by a deferrable trigger in PostgreSQL. An unbalanced journal cannot be committed by any code path, including a future one written in a hurry.
Corrections are reversals
Nothing is edited in place. A mistake is corrected by posting an opposing entry, so the original and the correction both remain visible and the history stays answerable.
Tenant isolation is asserted
Each business and each firm is isolated at the database schema level, and the application refuses to start if any table is found outside that scope. Isolation is verified, not assumed.
Audit rows are immutable
Every write records the actor, the time, the source document and the preceding state. Audit rows are append only and export in open formats.
Reconciliation runs as a health check
A standing set of consistency checks runs against live data and fails loudly. Silent drift in a system of record is worse than an outage, because nobody notices it.
Documents are verified before they are trusted
Where a source document carries a digital signature, it is verified against the issuing authority before its contents are used in a posting.
The AI
How the AI is constrained
A language model is used where language is the problem. It is kept away from anything where being confidently wrong would be expensive.
The model never supplies an amount
Every figure originates in the user's own words or their own documents. The model determines meaning and structure. It does not produce values.
Confidence is carried, not discarded
Extraction and matching results keep their confidence score through the pipeline, and low scores route to a human queue rather than into the ledger.
Reasoning is retained
The processing trail records what was decided and on what evidence, in terms an auditor can follow without reading code.
Confirmation gates every write
Proposals are shown in full and posted only on an explicit yes. There is no automatic mode and no setting that removes the gate.
Providers are swappable
Model access sits behind an internal interface with a configured fallback and per-provider circuit breakers, so a vendor incident degrades the service rather than stopping it.
Filing stays with the professional
Submission to a tax authority requires the taxpayer's or the accountant's own credentials. The platform prepares; a person files.
Platform controls
Platform and data handling
Standard controls, stated plainly, with the current state described rather than dressed up.
Data residency
Customer data is stored and processed in the region you select, and does not leave it for routine processing.
Encryption
Transport is TLS terminated at the gateway. Data at rest and stored documents are encrypted, and credentials are held in managed secret storage rather than in configuration files.
Authentication
Sign in is one-time password based on a verified phone number, with short-lived server-issued sessions. Single sign-on is available on enterprise terms. The sign-in endpoint returns identical responses for registered and unregistered numbers so it cannot be used to test who is a customer.
Access control
People see only the entities and engagements assigned to them. Role assignment and every access are recorded in the audit log.
Backups
Point-in-time recovery on the primary database, with restores exercised rather than assumed to work.
Monitoring
Distributed tracing, metrics and error tracking across services, so an incident can be reconstructed rather than guessed at.
Subprocessors
The current list of subprocessors, and the categories of data each one handles, is provided on request and updated with notice.
Certification status
Formal certification is on the roadmap and is not yet in place. We would rather say so here than imply otherwise. Our current controls are documented and available to review under a mutual non-disclosure agreement.
Reporting a vulnerability
Write to admin@aawazai.com. We acknowledge within two working days, and we do not pursue researchers who report in good faith.
Send us your security questionnaire
We answer them directly, including the questions where the honest answer is that we are not there yet.