Security & data protection

Who approved it, at what rate, on what day — kept whether or not anyone asks.

Approvals, payment status, exchange rates and role changes are recorded by the server as they happen — not reconstructed from a group chat six weeks later.

Audit log
Winter Beats
  • Expense approved · €3,450.00
    A. Silva · 2m ago · over threshold
  • Member role changed · M. Lopes → Accounts
    A. Silva · 14m ago
  • Expense submitted · $500 → €462.20 @ 0.9244
    J. Costa · 1h ago
  • Budget line edited · Production +€2,000
    A. Silva · yesterday

For your security review

Everything a reviewer usually asks for, in one place.

What is in place today, the agreements, and what happens to your data. If something is missing, ask us directly.

Ask for a security walkthrough
Pillar 01 // Audit trail

Financial changes leave a trail

Every financial change carries the person who made it and the moment they did it. Creating the event, approving an expense, moving a budget line — each one lands in that event's own history.


  • Actor and timestamp on every change
  • Written by the server, not the browser
Pillar 02 // Access

Access that matches the job

A stage manager filing receipts and an accountant marking invoices paid do not need the same powers. Four roles, and every endpoint checks the caller's before it acts.


  • Four roles, checked server-side
  • Membership checked on every request
Pillar 03 // History

Historical numbers stay historical

A supplier billed in dollars keeps the dollar amount and the rate on the day you entered it. A report pulled months later shows what the show cost, not what today's rate says it cost.


  • FX rate stored at entry
  • Tax treatment frozen per line
Pillar 04 // Payments

Card details never touch Cashbox

Subscription payments go through Stripe’s hosted checkout. Cashbox keeps your plan and billing status, never the card number.


  • Card data stays with Stripe
  • Only plan and status on our side
How a request is checked

Four boundaries every write passes.

These are the layers a request crosses before it can change a number. They are the same layers in every environment.

Perimeter 01Sign-in

Signed-in session

Every request starts by establishing who is asking. Sign-in is by email and password, or with Google.


  • Email and Google sign-in
  • Session established before anything else
Perimeter 02Checked per request

Membership checked on every request

Every request is checked against your current workspace membership and role, not against a token that could be out of date. Every record belongs to one organisation, and the database refuses access across organisations.


  • Membership read on every request
  • Every record scoped to one organisation
Perimeter 03On every action

Role checked on the server

Every action checks the person’s role on the server before it runs. Hiding a button is not the control; the check on the server is.


  • Role checked before every change
  • A hidden button is not a control
Perimeter 04Database-enforced

Every change goes through the server

Browsers never write to the database directly. Every change goes through the server and database commands that enforce the rules, so tax and FX snapshots cannot be forged from the browser.


  • Client writes refused
  • Snapshots cannot be forged
A worked example

Four lines from one event's record.

Every line here is written by the server. The client cannot author an audit entry or a rate snapshot.

What the record keeps
Winter Beats · event ledger
  • Expense approved · €3,450.00
    A. Silva · threshold route · recorded with actor and timestamp
  • Tax rate snapshotted · IVA 23% stored on the line
    Renaming the catalog rate later will not change this line
  • FX rate captured at entry · $500 → €462.20 @ 0.9244
    Stored on the record, never re-derived at report time
  • Role changed · M. Lopes → Accounts
    Takes effect on the next request
Diligence

What we can put in writing.

The honest version of a security page: what is implemented today, and where you can verify it yourself. We will say so plainly when something is not in place.

AreaWhere it standsHow to verify
Data residencySupabase (Ireland, eu-west-1) for the database, sign-in and file storage; Vercel (Paris) for hosting. Processing locations vary by service; European storage does not imply EU-only processing.Stated in our privacy policy, with the subprocessor list.
GDPRAccess, correction, deletion and portability requests are supported.Privacy policy; email us to exercise a right.
Card dataCashbox never stores card details. Stripe handles payment data in its own PCI-compliant environment.Stripe is listed as a subprocessor.
Tenant isolationPer-organisation scoping enforced by PostgreSQL row-level security and server-side membership checks on every request.Isolation is covered by automated database and browser test suites in the repository.
Audit trailFinancial changes are recorded with actor and timestamp, written server-side.Visible in-product on each event's history view.
Data processing agreementPart of your Cashbox agreement, for every plan that processes personal data on your organisation’s instructions.data-processing agreement
Formal certificationCashbox is not currently SOC 2 or ISO 27001 certified. We will not claim otherwise.Ask us directly about current plans and timelines.
Operational practices

How event teams set this up.

Access and permissions

Only owners change the plan; accounts can see the invoices. Owners and management can invite. Give the rest of the production team the event manager role and your bookkeeper the accounts role.

Approval controls

Set the approval threshold at the amount you would want to see before it is spent. Anything at or under it is approved on submission; anything above waits for a reviewer. Nobody but an Owner approves their own expense, and only an Owner moves the threshold.

Documentation attached to records

Attach the invoice file to the expense as you file it. It stays on the record, behind the same org check as everything else, so close-out is not a search through inboxes.

Reviewability for close-out

Export from the same records the approvals ran through. Your accountant gets the event's numbers with the trail behind them, not a spreadsheet someone retyped.

Need the DPA, or a closer look?

Part of your Cashbox agreement, for every plan that processes personal data on your organisation’s instructions.