Security at PrimDB
How PrimDB protects your data: EU residency, per-tenant isolation, encrypted secrets with audit logging, self-serve erasure, and the hardening we ship. Honestly, without invented certifications.
Security at PrimDB is described the way everything else here is: by what actually exists. This page tells you where your data lives, how tenants are kept apart, how secrets are protected, and how to report a problem. No invented certifications, no logos we have not earned.
EU data residency
PrimDB runs on infrastructure we host in the EU (Hetzner, Germany). Your account data and the data your apps store live in Europe by default. Sub-processors such as Stripe (payments) handle only the limited data they need for their function.
Per-tenant isolation
The platform enforces per-tenant isolation across databases, caches, and object storage, so one tenant cannot reach another tenant’s data. Workloads run on shared infrastructure with per-tenant RAM, CPU, and disk limits, which keeps a noisy neighbor from starving everyone else.
Encrypted secrets and audit logging
Environment variables and connection strings are stored encrypted at rest and revealed only to the owner. Access to secrets is recorded in an audit log, so there is a trail of who read what and when. Audit logs are retained for about 365 days and you can export yours.
Data minimization and retention
We aim to collect little and keep it briefly. A daily automated cleanup job enforces concrete retention windows so data does not linger:
- Expired sign-in and magic-link tokens are purged within about 7 days.
- Resolved feedback comments are purged after about 90 days.
- Audit logs are retained for about 365 days.
- Backups are rotated on a rolling schedule and age out automatically.
You are in control of your data
You can delete your account and all associated data self-serve from the dashboard, which tears down your apps, databases, and account data. Your code and data remain yours and can be taken with you. See the Privacy Policy for the full GDPR rundown.
Billing security
Payments are processed by Stripe. PrimDB never receives or stores your full card number.
Reporting a vulnerability
If you find a security issue, please report it privately to security@primdb.com before disclosing it publicly, so we can fix it and protect other tenants. We read these quickly and will work with you in good faith.
Honest note. An honest note on certifications: PrimDB does not hold SOC 2 or ISO 27001, and we will not pretend otherwise. What we describe here is what the platform actually enforces today. As the product matures, formal attestations are on the roadmap, and this page will say so plainly when they land, not before.