Legal

Subprocessors

Effective date: November 12, 2026

What a subprocessor is

A subprocessor is a company we use to help provide TalkingDot that may process personal data on our behalf, such as the provider that hosts our servers. We use only subprocessors that are bound by written data-protection obligations, and we remain responsible for them under our Data Processing Addendum.

Current subprocessors

SubprocessorPurposeLocationData
Hosting: OwrbitRuns the servers, database and file storage for the whole serviceNorwayAll service data: accounts, workspace content, contacts, conversations and attachments
Email delivery: MXrouteSends account emails, teammate notifications and emails to visitors, such as missed replies and transcriptsGermanyNames, email addresses and email content, which can include message text
Cloudflare, Inc. (if used for DNS/CDN)DNS, content delivery and protection against attacks; can supply the visitor-country header used for approximate locationGlobal networkIP addresses and all request data passing through its network
CAPTCHA provider (if enabled): Cloudflare Turnstile, hCaptcha or Google reCAPTCHABot protection on the sign-up, sign-in and contact formsCloudflare: global network; hCaptcha and Google: United StatesIP address and browser signals of people using those forms
Google LLC: Firebase Cloud Messaging (if teammates use the Android app)Delivers push notifications to the Android appUnited States and other countries where Google operatesThe app's push token and notification text: a visitor's name and the start of their message, the workspace and conversation number
Apple Inc.: Apple Push Notification service (if teammates use the iPhone app)Delivers push notifications to the iPhone appUnited StatesThe app's push token and notification text: a visitor's name and the start of their message, the workspace and conversation number
Payment providers (when a customer buys a paid plan): Stripe, PayPal, Razorpay, NOWPayments or Whop, whichever the customer chooses at checkoutTake the payment for a paid plan, under their own terms and privacy policiesWhere each provider operatesThe details needed to take the payment, such as the customer's email address and the amount, and the payment details they enter on the provider's page; we never receive full card numbers
Google Analytics (public website only, after consent, if enabled)Visit statistics for our public websiteUnited States and other countries where Google operatesPseudonymous identifiers, pages visited, device type and approximate location of visitors to our public website; no dashboard or messenger data

Rows marked "if used" or "if enabled" apply only while that service is switched on.

Services you choose to connect

If a workspace connects Slack, Microsoft Teams, Google Chat, Discord or Telegram, WhatsApp or Telegram customer channels, its own AI provider, sets up webhooks or uses the REST API, data goes to the destinations that workspace chooses. Those services are chosen by the customer, not by us, so they are not our subprocessors. Browser push notifications for teammates pass through the browser maker's push service in encrypted form, which that service cannot read. Notifications to our mobile app pass through Google (Android) and Apple (iPhone), listed above.

The same applies when a workspace connects its own WHMCS or WordPress site: customer details are looked up there, and with WHMCS ticket sync, tickets and their messages are copied between the workspace and its own WHMCS. That site is the customer's own system, not one of our subprocessors.

How we tell you about changes

Before a new subprocessor starts processing personal data, we update this page and the effective date at the top. Customers can object as described in our Data Processing Addendum. To receive an email when this list changes, write to privacy@talkingdot.com.