Tablinum Subprocessors
Version 2026-10-24. Permanent address of this version: tablinum.app/legal/subprocessors/2026-10-24
Version: 2026-10-24 (last updated) · Effective: not yet in effect (a draft, published 2026-10-24 for review) · Published at tablinum.app/legal/subprocessors. To be told of changes, [owners of a shop are emailed automatically / email privacy@tablinum.app].
1. Subprocessors (they process shop data on Tablinum's behalf)
| Subprocessor | What it does for Tablinum | Shop data it processes | Where | Status |
|---|---|---|---|---|
| Google Cloud (Google LLC) [VERIFY entity] | Runs the application (Cloud Run), the database (Cloud SQL for PostgreSQL), task queues and schedulers, secret storage, logs and monitoring, and the nightly backup copy of files (Cloud Storage, Coldline). | All shop data held in the database, all files (backup copy), and application logs. | USA: region us-central1 (Iowa). [VERIFY: the region of Cloud Logging's log buckets, which default to "global" unless set.] | In use |
| Cloudflare (Cloudflare, Inc.) | Edge network in front of every page and API call (DNS, TLS, request routing through Cloudflare Workers, protection against attacks); file storage (R2); bot check on public client sign-up (Turnstile); certificates for shop hostnames; custom hostnames for shops that add their own domain. | All traffic in transit, including request contents. Every stored file and its versions (R2). Browser signals during the sign-up bot check. | Global network for traffic (served from the data center nearest the user). R2 storage: [VERIFY: the buckets' location hint or jurisdiction; not yet managed in Terraform]. | In use |
| Resend (Resend, Inc.) [VERIFY entity] | Delivers the emails the Service sends: sign-in links and codes, invitations, quote and invoice emails, notifications. | Recipient name and email address, sender name (your shop's), message subject and body. | USA [VERIFY: region] | In use |
| Stripe (Stripe, Inc.) | (1) Tablinum's own billing of shops, including tax calculation (Stripe Billing, Stripe Tax). (2) Carrying payment requests from the Service to the shop's own Stripe account (see §2). | (1) The shop's billing email, tax address and payment method: Tablinum's own customer data. (2) Client names and email addresses, and payment amounts, sent to the shop's Stripe account. | USA, and Stripe's global infrastructure | In use |
| Google Workspace (Google LLC) | Tablinum's email, used for support conversations. | Whatever a shop's staff send to support, which may include shop data. | USA [VERIFY] | In use |
2. Services the shop chooses (not Tablinum's subprocessors)
These are services a shop connects under its own agreement with the provider. When a shop turns one on, the Service sends data to it on the shop's instruction (Terms §8; DPA §6.5). The provider's own terms and privacy policy then govern that data.
| Service | When data goes to it | What is sent | Status |
|---|---|---|---|
| Stripe (the shop's own connected account) | When the shop takes card or bank payments from its Clients. The shop is the merchant of record under its own agreement with Stripe. | Client name and email address (as a Stripe customer), amounts, invoice references, saved payment methods the Client chooses to keep. Card and bank numbers go straight from the Client's browser to Stripe. | In use |
3. Not subprocessors (for the record)
- ClamAV: the malware scanner runs inside Tablinum's own Google Cloud project; no third party receives files.
- Azure Artifact Signing: signs the desktop installer. It never receives shop data.
- Anthropic: Tablinum's automated test agents run against non-production systems that hold only fictional data, with their own separate account. No shop data reaches them.
- HubSpot as Tablinum's own CRM (if adopted for sales conversations): Tablinum's own controller processing of prospects' details. It belongs in the Privacy Policy, not here.