Security data sheet

Control by control, with status.

This isn't a security brochure. It's the list of what's actually in place, what each control actually does, and what's still only planned.

Document: MM-SEC-01
Scope: The service and its case data
Operated from: EU · own infrastructure
Revision: Ongoing

Controls

Encryption

Data should be unreadable to anyone outside the case.

TransportLIVE: All traffic to and from the service is encrypted. Unencrypted calls are rejected.; LIVE
StorageLIVE: Database and backups are encrypted at rest.; LIVE
Contact detailsLIVE: Phone numbers and email addresses are stored as encrypted fields, separate from the rest of the case data.; LIVE

Isolation

One person should never be reachable through another person's case.

Row-level isolationLIVE: Each person is their own bounded row. A query without a valid link to that person returns nothing — not an empty response, nothing at all.; LIVE
Separated environmentsLIVE: Test and development never operate against production data.; LIVE
Access controlLIVE: Staff have the minimum access needed, tied to a specific task rather than a role that applies forever.; LIVE

Evidence chain

What happened in a case shouldn't be rewritable after the fact.

Hash-chained eventsLIVE: Every action is cryptographically linked to the one before it. A broken chain is visible.; LIVE
Append-onlyLIVE: Entries are added. They aren't overwritten and aren't deleted individually.; LIVE
Tracked readsLIVE: Even reading a case leaves a trace in the same chain.; LIVE
ExportLIVE: The full chain can be handed over as one coherent record, in the order events occurred.; LIVE

Operations and continuity

An outage shouldn't cost the evidence.

Off-site copiesLIVE: Database backups are kept separate from the production environment. Evidence storage currently has no backup of its own.; LIVE
Restore testingPLANNED: An initial restore test (download, decrypt, verify contents) has been completed. Regular restore testing and a full restore to a running database are not yet established.; PLANNED
Hosting locationLIVE: The service runs on its own infrastructure within the EU.; LIVE
Independent reviewPLANNED: External technical review of the controls in this data sheet.; PLANNED

Boundaries

No certification
This data sheet is our own description of technical controls. It isn't a third-party attestation, and we never call it one.
No outcome promise
Controls reduce risk. They don't remove it. A page that claims otherwise isn't describing security, it's marketing.
Honest status words
If it says LIVE, the control is in place. What isn't done yet says PLANNED and doesn't change wording until it is.

If you find a hole, we want to know before anyone else does.

The reporting channel, what we need in a report, and how a case is handled are in the documentation. We respond to reports even when they turn out to be false alarms.

Read the documentation Privacy policy

Listening …

Control by control, with status.

Encryption

Isolation

Evidence chain

Operations and continuity

No certification

No outcome promise

Honest status words

If you find a hole, we want to know before anyone else does.

Control by control, with status.

Encryption

Isolation

Evidence chain

Operations and continuity

No certification

No outcome promise

Honest status words

If you find a hole, we want to know before anyone else does.