Tenant & entity boundaries
Data is scoped to a tenant and legal entity. Operations and the API enforce that scope.
Hiding a button in the UI doesn't complete access control. Authorization has to apply all the way to data access — so the security design lives in the backend, not the interface.
These describe the security design of the Reconciliation Engine. They are product design — not a certification, audit result, or compliance claim.
Data is scoped to a tenant and legal entity. Operations and the API enforce that scope.
Role- and permission-based access, enforced from the API down to data — with PostgreSQL row-level security.
Maker-checker: the person who prepares a decision and the person who approves it are different.
Sensitive values are masked where appropriate across the console and exports.
Review and decision steps are recorded and tied to the run and result digest.
Multi-tenant SaaS, dedicated cloud, customer's own cloud, or on-prem — data residency, retention, and key location set per profile.
The controls above are technical design. We don't publish PCI, GDPR, KVKK, or other regulatory-compliance claims, specific retention guarantees, or certifications we can't show evidence for. Security is discussed directly, against your environment and deployment profile, as part of a technical evaluation.
Design description — not a certification, audit, or compliance claim
We address security against your actual environment and deployment profile — not generic claims.