1. Subject, duration and nature
- Subject: hosting, operating, backing up and restoring the databases you create (PostgreSQL and, where we offer them, key-value and MariaDB databases).
- Duration: for as long as we hold your databases or their backups (backups of a deleted database: 7 days).
- Data and people: whatever you store; you decide the categories of personal data and of data subjects (for example your users or customers).
- Location: the region you choose for each database (EU, US or Asia); data and backups stay in that region.
2. Your instructions
We process the data only on your documented instructions: the Terms, this agreement, and what you do through the dashboard and the API (create, resize, restore, delete). If an instruction seems to break data protection law, we tell you. If the law makes us process data otherwise, we tell you first unless the law forbids it.
3. Confidentiality
Only staff who need it for operations and support can access the systems holding your data. They are bound to confidentiality, and we do not open database contents unless you ask or an incident requires it.
4. Security measures
- TLS for every database connection (certificate verifiable with sslmode=verify-full), HSTS on the website.
- An IP allowlist per database, managed by you.
- Every database in its own isolated namespace with network policies; firewalled servers, SSH from admin networks only.
- Backups encrypted before upload with a separate key per database; each database's backups in their own storage area with their own credentials.
- Database passwords and internal secrets encrypted at rest; account passwords hashed with Argon2id; API keys and tokens stored as hashes.
- Synchronous standby in a second site (high-availability plans), continuous backups, point-in-time restore, weekly automated restore tests.
- Least-privilege access between our own components, an audit log of administrative actions, automatic security updates on servers.
5. Sub-processors
You authorise the sub-processors on the Sub-processors page. We bind each to data protection terms no weaker than these. We give at least 30 days' notice by email before adding or replacing one; you may object on reasonable data protection grounds, and if we cannot address the objection you may terminate the affected service without penalty. We remain responsible for our sub-processors.
6. International transfers
Databases in the EU region stay in the EU. Where personal data is transferred outside the EEA (a database you create in the US or Asia region, or a sub-processor outside the EEA), the EU Standard Contractual Clauses or another valid transfer mechanism apply, and are incorporated into this agreement by reference.
7. Assistance
Taking into account what we can see as your processor, we help you answer data subjects' requests (you can query, export and delete data in your databases directly), with data protection impact assessments, and with consultations of supervisory authorities.
8. Personal data breaches
We notify you without undue delay, and within 48 hours at the latest, after becoming aware of a breach that affects your data, with what we know about its nature, likely consequences and the measures taken, and we keep you updated.
9. Deletion and return
You can export your data at any time with the standard tools of each database (for example pg_dump for PostgreSQL, mariadb-dump or mysqldump for MariaDB). When you delete a database, or the agreement ends, the database is removed at once and its backups 7 days later, unless the law requires us to keep them.
10. Audits
We make available the information needed to demonstrate compliance with article 28 GDPR, and allow audits by you or an auditor you appoint, on 30 days' notice, during business hours, under confidentiality, at most once a year unless there was a breach or a supervisory authority requires it.
11. Precedence
For the processing of personal data in your databases this agreement takes precedence over the Terms. The liability rules of the Terms apply to it.