Legal
Data processing addendum
If your app stores personal data on Berth, this addendum sets out how Berth handles it on your behalf, for the GDPR, the UK GDPR and US state privacy laws. It is part of the Terms and applies automatically to every account. Last updated October 28, 2026.
Who is who
For the data in your apps (tables, files, your end users, function and request logs) you are the controller and Berth is your processor. Berth is run by Michael Shobitan ("Berth", "we"). For your own account details, Berth is the controller, as the Privacy policy describes.
| Subject matter | hosting your apps' databases, files, functions, sites and sign-in |
| Duration | while your account exists, plus the backup period below |
| Purpose | providing Berth to you, and nothing else |
| Data | whatever your apps store: typically names, emails, profile data, content, files and IP addresses in logs |
| People | your app's users and anyone whose data your app holds |
What Berth commits to
- Your instructions only. We process app data only to run the service as you configure it through the console, CLI and API, and never for our own purposes. We do not sell it, use it for advertising, or train models on it.
- Confidentiality. Only Berth's operator can reach the servers, and is bound to keep app data confidential. We look at app data only when you ask us to, to keep the service running, or when the law requires it.
- Security. The measures listed below, kept up to date.
- Subprocessors. Only those listed below. We give at least 30 days' notice of a new one by email and on the status page. If you object and we cannot address it, you may close your account without charge for the unused period.
- Helping with requests. You can export, change and delete your users and their data yourself through the API (for example
GET /auth/users,DELETE /auth/users/{id},GET /export). We help with anything you cannot do yourself. - Breaches. We tell you without undue delay, and within 72 hours of becoming aware, of any breach affecting your app data, with what we know and what we are doing about it.
- Deletion. When you delete an app or your account, its database, files and functions are deleted at once. Copies in encrypted backups expire within 35 days.
- Records and audits. We answer reasonable questions about how your data is handled, and provide the information you need to show compliance.
Where data is
Berth runs in one region: Oracle Cloud's US East (Ashburn, Virginia) data center. Apps cannot choose another region today. For transfers of personal data from the EEA, the UK or Switzerland to the United States, the Standard Contractual Clauses (Module Two, controller to processor) adopted by the European Commission, with the UK Addendum where it applies, are incorporated into this addendum by reference, with you as the data exporter and Berth as the data importer.
Subprocessors
| Provider | What for | Data involved | Location |
|---|---|---|---|
| Oracle Cloud Infrastructure | servers, storage and encrypted backups | all app data | United States |
| Resend | sending sign-in codes and other emails | end users' email addresses, email contents | United States |
| Postmark (ActiveCampaign) | backup email delivery if Resend is down | the same, only then | United States |
| Google, Apple | Sign in with Google and Apple, only if your app turns them on | the sign-in token the user's device sends | United States |
Stripe processes payments for your Berth plan. It sees your billing details, never your apps' data.
Security measures
- Each app has its own Postgres database and database role. Row level security enforces your table policies inside the database.
- TLS on every connection. Disks are encrypted at rest by Oracle. Backups are encrypted with age (X25519) before they leave the server, and the decryption key is kept offline.
- Passwords of your users are stored only as salted scrypt hashes.
- The database is never exposed to the internet. Server access is by SSH key only, from one allowed address, with fail2ban.
- Secret keys can be scoped and set to expire. Changes to an app are recorded in its audit log.
- Nightly backups, a weekly test restore of every database, monitoring every minute, and a public status page with incident reports.
Signed copies and questions
This addendum applies without a signature. If your company needs a countersigned copy, or has a question, email hello@atberth.com.