Processors
Who else handles personal data for TruePlinth, what for, where, and on what basis it goes there.
Last changed October 28, 2026
The list
| Who | What for | Where | Basis for a transfer |
|---|---|---|---|
| Supabase | The database, sign-in and stored files | Ireland (EU); the company is in Singapore | Its data processing agreement and the EU's standard contractual clauses |
| Cloudflare | Serving the website and app; counting visits without cookies | Worldwide network | Its data processing agreement; the EU–US Data Privacy Framework and standard contractual clauses |
| Resend | Sending the app's emails | United States | Its data processing agreement; the EU–US Data Privacy Framework |
| PostHog | Measuring use, only after consent | Germany (EU) | Its data processing agreement; standard contractual clauses for its own processors |
| GitHub | An encrypted nightly backup, kept seven days | United States | Its data protection agreement; the EU–US Data Privacy Framework |
| Paddle | Selling plans and kitchens, as reseller and merchant of record (a controller of payment data in its own right) | United Kingdom | Its data sharing addendum; the UK is recognised by the EU as protecting data |
| Google, Microsoft | Signing in, only when you choose them | United States | Their terms; the EU–US Data Privacy Framework |
Changes
We tell businesses 30 days before adding or replacing a processor that handles their clients' details, and update this page and the date above. A business that objects may end its plan with a refund of what's unused (see the data processing addendum).