How Core 137 protects the estimates, drawings and financial records you keep here — written plainly, and limited to what we actually do today.
Everything you send us travels over TLS 1.3. There is no unencrypted route into Core 137 — plain HTTP is redirected, and the database refuses connections that are not encrypted.
Data at rest sits on encrypted volumes, and files you upload are stored in object storage with encryption enabled by the provider.
Every row that belongs to a workspace carries its organisation, and the database enforces that boundary itself through row-level security rather than trusting the application to remember. A query that forgets to scope itself returns nothing instead of returning someone else’s data.
Passwords are never stored — we keep a salted SCRAM verifier, which cannot be reversed into the password that made it. Internal access to production is limited to the people who operate it, over key-based SSH only, with password and root login disabled.
Administrative actions inside a workspace are recorded in an audit log the workspace owner can read.
The database is backed up on a schedule, encrypted, and stored in a separate provider from the server that produced it — so losing the machine cannot lose the backups with it.
Backups are restored on a drill, not assumed. A backup that has never been restored from is a hypothesis, and we treat it as one.
Core 137 runs on dedicated European infrastructure behind a network edge that filters malicious traffic before it reaches us. The application server is not reachable directly from the internet: it accepts traffic only from the edge, and the database accepts it only from the application.
We do not claim certifications we have not been issued. Where a formal audit is required for your procurement, write to us and we will tell you exactly where we are in that process rather than pointing at a badge.
If you believe you have found a security issue, email security@core137.com. Tell us what you found and how to reproduce it, and give us a reasonable window to fix it before publishing.
We will acknowledge your report, keep you updated while we work, and credit you when it is resolved if you would like us to.
