Deny by default
The data layer ships closed, not open. Reading or writing a record requires proof of an active membership and the right role. Adding a new screen doesn’t open a new permission.
CashEye/Security
This page isn’t a marketing list; it’s an audit list: every control running in production, and how it’s implemented.
Design principles
The data layer ships closed, not open. Reading or writing a record requires proof of an active membership and the right role. Adding a new screen doesn’t open a new permission.
The browser can’t write financial records. Every operation is validated on the server, applied in one atomic transaction, and a repeated request never creates a second record.
Financial records are never physically deleted. Corrections are made with a traceable reversing entry. History isn’t rewritten; it’s only added to.
Control matrix
Every control below is running in production today.
Active membership document and per-tenant sub-collections.
Owner, CEO, CFO, finance manager, finance specialist, accounting, viewer.
Client writes are closed; a server command is required.
The requester can’t approve their own payment.
Unique command keys and duplicate-record prevention.
Who, what, when, before and after, IP and browser details.
Tenant tagging, PDF/image types and a 15 MB limit; client-side deletion closed.
CSP, HSTS, framing, MIME and referrer policies.
Daily backups (30-day retention), point-in-time recovery, delete protection.
For your audit team: we walk through the technical detail and evidence for every control, item by item, on a call.
Permission matrix
Hiding a menu isn’t a permission. Authorisation is enforced in the data layer and in server commands; the interface is only a convenience.
| Role | Scope |
|---|---|
| Owner | Read everything; manage workspace, users and policies |
| CEO | Read everything; summary, intelligence and risk screens |
| CFO | Full finance read/write, scenarios, approvals and part of settings |
| Finance manager | Finance operations and first-level approval |
| Finance specialist | Operational records, tasks and documents; no destructive admin actions |
| Accounting | Records, reconciliation and reporting; limited planning writes |
| Viewer | Read-only access to permitted modules |
Resilience
Recovery is the feature you only notice the day you don’t have it. The targets are written down.
Data is stored in the European region; workspaces are kept isolated from each other.
Daily managed backups, 30-day retention, point-in-time recovery and delete protection.
Assess impact, pause writes while keeping reads open if needed, reconstruct the sequence from the audit trail, correct with reversing entries.
FAQ
In the European data region. Every record belongs to a workspace; access isn’t granted without a verified active membership and role.
Operational access is role-based and written to the audit trail. The access policy and confidentiality commitment are shared in writing at contract stage.
Financial records are never physically deleted; corrections are made with a reversing entry. That’s what accounting discipline and auditability require. Who corrected what, and when, is recorded.
Today, sign-in is by email and password. We plan enterprise SSO and multi-factor authentication with you during onboarding.
Yes. Reports and saved views can be exported, and if you leave you get a complete export. Your data is yours.
If your information security team has a checklist, we’ll answer it item by item.