Sub-processors

Last updated: October 14, 2026

Who touches your data: the third-party services we use to deliver Jamdesk. This page is the authoritative list and is updated as infrastructure changes.

Change Notifications

We provide customers with at least 30 days' advance notice before adding or replacing a sub-processor that processes customer personal data. To subscribe to changes, email us with the subject "Subprocessor Updates".

Customer Data Sub-processors

These services process Jamdesk customer account data, documentation content, or application data.

ServicePurposeLocationData Categories
Google Cloud PlatformInfrastructure, compute, object storage, secret managementUnited StatesAccount data, documentation content, logs
Firebase (Google)Authentication, Firestore database, hostingUnited StatesAccount email, auth tokens, application data
CloudflareCDN, DDoS protection, R2 object storage, WorkersGlobal (edge)IP addresses, request metadata, documentation assets (R2)
VercelHosting for published documentation sites and the marketing siteUnited StatesIP addresses, request metadata
StripeSubscription billing and payment processingUnited StatesBilling name, address, payment method metadata
MailfullyTransactional and marketing email deliveryUnited StatesEmail address, email content
UpstashRate limiting (Redis), vector search and AI chat context retrieval (Vector)United StatesIP addresses in short-lived rate-limit keys, rate-limit counters, documentation embeddings, chat query vectors
AnthropicAI inference for documentation chat and AI features (Claude)United StatesUser chat messages, documentation context passed to the model
OpenAIAI inference for documentation translation (only for projects that turn translation on), Fix with AI suggestions for build warnings, and editor commit messagesUnited StatesDocumentation page content submitted for translation, page titles and up to 4,000 characters of page text for Fix with AI, diffs of files changed in the editor
GitHubSource repository access through the Jamdesk GitHub App: reading documentation, receiving push webhooks, and committing editor and translation changesUnited StatesRepository content, GitHub usernames, commit author names and emails
Plausible AnalyticsCookieless usage analytics for the marketing site and the Jamdesk dashboardEuropean UnionPage URLs, referrer, browser, OS and country. IP addresses are used only to compute a daily rotating hash and are not stored
CrispLive chat widget on the marketing site and the Jamdesk dashboardFrance (EU)Chat messages, visitor IP, and the email address of signed-in dashboard users

Marketing & Operational Processors

These services support the Jamdesk marketing site, analytics, ad measurement and internal operations. They do not receive customer documentation or billing data. On the Jamdesk dashboard they receive page URLs, and a sign-in link can include the user's email address in its URL.

ServicePurposeLocationData Categories
DigitalOceanJamdesk blog (Ghost CMS) hosting — marketing onlyUnited StatesBlog subscriber emails, blog comments (if enabled)
Google Analytics & Google AdsAnalytics and ad measurement on the marketing site (consent-gated in the EU/UK) and the Jamdesk dashboardUnited StatesCookie identifiers, IP address, page URLs
RedditAd measurement (Reddit Pixel) on the marketing site (consent-gated in the EU/UK) and the Jamdesk dashboardUnited StatesCookie identifiers, IP address, page URLs

International Transfers

Most sub-processors are located in the United States. For transfers of EU/EEA/UK personal data to the US, we rely on the 2021 EU Standard Contractual Clauses (Module 2: Controller-to-Processor) and, where applicable, the UK International Data Transfer Addendum. These are incorporated by reference into our Data Processing Addendum.

Questions

For sub-processor questions, audit requests, or to request our DPA, contact privacy@jamdesk.com.

We use cookies for analytics. Learn more