Tablewide Subprocessors
Last updated: October 1, 2026
This page lists the third parties ("subprocessors") that Aaron Vontell d/b/a Tablewide uses to provide Tablewide and that may process personal data on behalf of our customers. It forms Annex III of our Data Processing Agreement.
Regions. Customers are hosted in the US region by default; the EU region is available on request. The "Region" column shows which subprocessors apply to which region. Customer Content (your pages, diagrams, files) is hosted and backed up only in your chosen region. The exceptions are listed plainly below.
Change notices. We give at least 30 days' notice before adding or replacing a subprocessor that processes Customer Content or customer personal data. To get notices, email privacy@tablewide.com and ask to join the notice list. Notices also go to each workspace's admin email. You can object under Section 8 of the DPA.
Current subprocessors
| Subprocessor | Purpose | Data processed | Location | Region applicability |
|---|---|---|---|---|
| Hetzner Online GmbH | Infrastructure hosting: servers running each customer's container and database | All Customer Content and workspace data; server logs | EU region: Germany (Falkenstein/Nuremberg) and/or Finland (Helsinki). US region: Ashburn, Virginia, USA (operated through Hetzner US LLC) | EU and US (each customer's data only in its chosen region) |
| Backblaze, Inc. | Off-site storage of nightly encrypted backups | Encrypted backup files of Customer Content and workspace data. Backblaze cannot read them: encryption keys are held by us, not Backblaze | US region: US East (Reston, Virginia). EU region: EU Central (Amsterdam, Netherlands) | EU and US (each customer's backups only in its chosen region) |
| Stripe, Inc. and Stripe Payments Europe, Ltd. | Subscriptions and payments. Through Link, its merchant-of-record service, Stripe sells the subscription, charges the card, collects taxes and issues receipts; for that payment it acts as a separate controller under its own terms | Billing contact name and email, company name and address, VAT/tax ID, payment card details (held by Stripe only), transaction history. No Customer Content | United States and Ireland (global infrastructure) | EU and US |
| Postmark (ActiveCampaign, LLC) (planned, not yet in use) | Transactional email: sign-up, billing notices, security notices, and workspace notification emails | Recipient names and email addresses; email content. Workspace notification emails may include page titles, comment text or short content excerpts | United States | EU and US |
| Cloudflare, Inc. | Website hosting, DNS for our domain, and the database behind the website's sign-up form and visit counts | Website sign-up form entries (name, work email, company); request data needed to serve the website. No Customer Content: traffic to customer workspaces goes directly to our servers, not through Cloudflare | Global network; database in the United States | EU and US |
| Google LLC (Google Workspace) | Support and company email inbox | Contents of emails you send us: names, email addresses, and anything you include (which may include Customer Content you choose to paste or attach) | United States (global infrastructure) | EU and US |
| Anthropic, PBC | AI agents (Claude) that help our staff perform migrations and support requests | Only the Customer Content and user data needed for a specific migration or support request that the customer asked for. Not used for routine operation of your workspace | United States | US region: used for migrations and support requests you make, unless you ask for a request to be handled without AI access. EU region: used only when you consent for that specific request (for example by confirming in the ticket); otherwise never receives your Customer Content |
Not our subprocessors
- Your users' sign-in providers (Google or Microsoft). Your team signs in with your organisation's Google Workspace or Microsoft Entra ID; admins and invited guests may use their own Google or Microsoft account. Those providers are chosen by you and your users, not engaged by us. We receive only the sign-in result (name, email, a user identifier, and group or tenant information where configured). We do not store passwords.
- Source systems in a migration. If you give us access to Confluence, Notion or another tool so we can migrate your content, that tool's vendor is your provider, not ours.