Skip to main content
Annual Tabletop
Menu

Legal

Sub-processors

The third parties that process customer data on our behalf. We commit to a 30-day notice on changes that affect this list, with a contractual right to object built into every paid agreement.

Last updated 20 April 2026. Subscribe to change notices by emailing privacy@annualtabletop.com.

CategoryProviderPurposeRegionTouches customer data
Cloud hostingAmazon Web Services (AWS)Compute, storage, database, KMS, networkingUS (us-east-1, us-west-2)Yes
Foundation model — primaryAnthropicAtlas facilitator runtime. Zero-retention DPA in force; not used for training.USYes
Foundation model — fallbackOpenAIAtlas facilitator fallback. Zero-retention DPA in force; not used for training.USYes
Transactional emailResendAccount, magic-link, AAR delivery, and exercise-invite email. Transactional only — no marketing blasts.USYes
Error monitoringSentryApplication error and performance telemetryUSNo
Product analyticsVercel Analytics + StatcounterPage-level marketing analytics. PII-stripped at collection.US / EU edgeNo
BillingStripeSubscription billing and invoicingUSYes

Sub-processors that handle Atlas inferences are bound by a zero-retention data-processing addendum — they do not retain your exercise text and do not use it to train models. See the Security page for the full data-flow description.

Authentication and session management are handled inside the Annual Tabletop application using an open-source TypeScript auth library (BetterAuth). User records, sessions, and credentials live in our own Postgres database under our primary hosting provider — no third-party identity sub-processor is used for self-serve tiers. Enterprise/FI tiers that require SAML 2.0 or OIDC SSO will add a dedicated identity partner (typically WorkOS) at the time of that deployment; we will update this page and notify customers in writing before any such sub-processor is added to an environment.