Sub-processors
Updated 2026-08-01
The third parties that process personal data on our behalf, so merchants can assess them and object if they need to.
Current sub-processors
| Provider | What it does | Data it touches | Where |
|---|---|---|---|
| Cloudflare | Application hosting, CDN and network delivery | Request metadata, IP addresses, anything in transit | Global edge network |
| Neon | The PostgreSQL database holding store data | Merchant accounts, products, orders, shopper names and emails | The region configured for the deployment |
| Clerk | Merchant authentication and session management | Merchant names, email addresses, credentials | See Clerk's own documentation |
| Stripe | Payment processing and merchant identity verification | Merchant identity and bank details, shopper payment details | See Stripe's own documentation |
[Counsel / engineering: confirm each provider's processing region and link its current DPA before publishing.]
Who holds what
Card numbers reach Stripe only. Merchant identity documents reach Stripe only — we receive a verification status, never the documents. Shopper names and email addresses are held in our database on the merchant's behalf.
Changes
We give notice before adding a sub-processor that will process merchant or shopper personal data. A merchant who objects on reasonable data protection grounds may raise it with us, and may terminate if we cannot resolve it. [Counsel: fix the notice period and the objection window.]
To be told about changes, or to raise an objection, write to privacy@tokolane.com.