Legal
Subprocessors
Third parties that process data for NamiDB Cloud, what they process and where, and how to be notified of changes.
- Last updated
- Version
- 2026-11-02
- Questions
- info@namidb.com
Contents
01Current subprocessors
These third parties process personal data for NamiDB Cloud under written agreements that impose data protection obligations at least as protective as our Data Processing Addendum. “Customer Content” says whether they process the data inside your databases; the others process only account, billing or email data.
Cloudflare
Cloudflare, Inc.
- Purpose
- Storage of every organization's databases and database backups, dedicated to each organization; DNS for NamiDB hostnames.
- Data
- Customer Content and customer database backups, encrypted at rest. DNS queries for NamiDB hostnames.
- Location
- The storage location assigned to each organization when it is created.
- Transfer safeguard
- EU–U.S. Data Privacy Framework certification; EU Standard Contractual Clauses in Cloudflare's DPA.
Stripe
Stripe, Inc.
- Purpose
- Subscription billing, usage-based invoicing, payment processing, tax calculation, the customer billing portal.
- Data
- Billing contact name, email and address, tax ID, payment method details (entered directly on Stripe; NamiDB never receives full card numbers), invoices, aggregated usage quantities.
- Location
- United States
- Transfer safeguard
- EU–U.S. Data Privacy Framework certification; EU Standard Contractual Clauses in Stripe's DPA.
Resend
Plus Five Five, Inc. (Resend)
- Purpose
- Delivery of transactional email: sign-up and sign-in codes, password recovery, invitations, billing and service notices.
- Data
- Recipient email address, name, message content and delivery metadata.
- Location
- United States
- Transfer safeguard
- EU–U.S. Data Privacy Framework certification; EU Standard Contractual Clauses and UK Addendum in Resend's DPA.
02Services we run ourselves
NamiDB operates these functions itself. They are not subprocessors; we list them so the picture is complete.
- Authentication and account records: Sign-in, sessions and the database of accounts, organizations, keys and billing state.
- Monitoring and logs: Metrics, alerting and service logs.
- Status page: Service status and incident history at status.namidb.com.
- Error reports: Console error reports, without request headers, cookies, bodies or user identifiers.
GitHub and Google receive data only if you choose to sign in with them, as independent controllers, so they are not subprocessors either.
03Changes and notifications
We give at least 30 days’ notice before a new subprocessor starts processing Customer Personal Data, by updating this page and emailing everyone subscribed to subprocessor updates. During the notice period you may object as described in the DPA.