Black Friday Black Friday: the new LetsBot bundles save up to 60% — until 30 November only. See the bundles See the bundles
LetsBot Menu
Get Started English Language

Meta Business Partner UK Registered Company

Language

Privacy & data

Subprocessors

Every company that processes data for LetsBot: what it does, the data it receives, where it is, and how you get notice of changes.

Last updated
12 October 2026
Hosting
United States
Change notice
30 days
Governing version
English
Questions and requests
support@letsbot.net
On this page (6)

About this list

A sub-processor is a company we engage to process the personal data our customers manage in LetsBot. This page shows each one, what it does, the data it receives, where it is located, and the safeguard for international transfers. It forms part of our Data Processing Agreement.

Where data is hosted: all our servers and backups are on Google Cloud in the United States (region us-east1). We do not offer hosting in any other region. Our staff who access the data do so remotely, and work mainly in Egypt through our affiliate.

The page has three separate lists: sub-processors for your customer data, integrations you choose to connect yourself, and providers we use for our own data as a controller.

The English version of this page governs; the Arabic version is provided for convenience.

Sub-processors for your customer data

These companies process the personal data you manage in LetsBot on our behalf.

ProviderPurposeDataLocationTransfer safeguard
Google Cloud (Google)Hosting: servers, databases, file storage and backupsAll customer dataUnited States (us-east1)Provider's data processing terms (being verified)
Cloudflare, Inc.Network security, DNS, content and media deliveryAll website and panel traffic in transit; media when openedGlobal network (US company)Provider's data processing terms (being verified)
OpenAIDefault provider for AI replies, AI agents and AI tools; voice-note transcription; storage and search of knowledge files (only when enabled)Messages, conversation history, voice notes, knowledge files, product catalogue, and the contact's name and numberUnited StatesOpenAI Data Processing Addendum: EU Standard Contractual Clauses with the UK addendum (signature being verified)
Anthropic (Claude)Alternative or backup provider for AI tasks, including AI replies, AI agents, summaries, classification, reply suggestions and learn from history, and quality-comparison samples (only when the feature is enabled)Messages, conversation history, knowledge excerpts and product information the task needs, and the contact's name where the task uses itUnited StatesAnthropic Data Processing Addendum, incorporated into its Commercial Terms: EU Standard Contractual Clauses with the UK and Swiss addenda
Google (Gemini API)Alternative or backup provider for the same AI tasks, and image and text generation in Social Studio (only when used)Messages, conversation history, knowledge excerpts and product information the task needs, and the prompts you provideUnited States; abuse-monitoring logs may be cached transiently in any country where Google has facilitiesGoogle's data processing terms for the paid Gemini API: EU Standard Contractual Clauses and the Brazilian standard contractual clauses
Zoho Corporation (Zoho Mail, ZeptoMail)Sending e-mail notifications and handling support e-mailE-mail addresses, notification content and support e-mailsUnited States (being verified)Provider's data processing terms (being verified)
OneSignalPush notifications to your team's mobile appDevice identifiers, and notification content that may include a contact name and message previewUnited StatesProvider's data processing terms (being verified)
Apple (APNs)Incoming-call notifications on iOSVoIP push token and call notification dataUnited StatesProvider's data processing terms (being verified)
TelnyxSMS channel (only when enabled)Phone numbers and SMS contentUnited StatesProvider's data processing terms (being verified)
Microsoft (Clarity)Usage analytics on our website and on the checkout pages of the panel, according to the visitor's cookie choice (in the EU/EEA, UK and Switzerland only after they accept)Interactions on those pages, with text typed into forms maskedUnited StatesProvider's data processing terms (being verified)
AnthropicAI assistance for our engineering and operations teamProduction data an engineer inspects during a specific taskUnited StatesProvider's data processing terms (being verified)
DiscordInternal error alerts for our engineering teamError messages and workspace identifiers, with phone numbers and e-mail addresses maskedUnited StatesProvider's data processing terms (being verified)
Bot for Digital Solutions LLC («بوت للحلول الرقمية» ش.ذ.م.م)Our affiliate, through which the staff who access customer data work: support, operations and engineeringAny data the task requiresEgyptIntra-group agreement (being prepared)

Integrations chosen by the customer

These services are not our sub-processors. You connect them, data flows to them because you asked for it, and they process it under their own terms with you.

ServiceWhat happens to the data
Meta Platforms: WhatsApp (official Cloud API), Messenger, InstagramIntegration chosen by the customer. Messages are sent and received through Meta, which processes them under the WhatsApp Business Terms and the other Meta terms you accept with Meta. When you send marketing templates through Meta's Marketing Messages API, message activity is shared with Meta.
WhatsApp by QR codeIntegration chosen by the customer. The connection runs on our servers using the WhatsApp Web protocol. No data processing agreement with Meta covers it, and messages travel over WhatsApp's own network.
Telegram and XIntegration chosen by the customer; messages are processed under each platform's terms.
Salla, Zid, Shopify, WooCommerce and MagentoIntegration chosen by the customer to bring in orders, carts and products and to send notifications.
HubSpot, Pipedrive, Zapier, Salesforce and Stripe (your own account)Integration chosen by the customer to sync contacts, deals and payments.
Your mailbox at Google, Microsoft or ZohoIntegration chosen by the customer for the e-mail channel.
ChatGPT and Claude through the MCP connectorIntegration chosen by the customer; the assistant you connect can read your workspace data within the permissions you grant.
Social Studio publishing (X, LinkedIn, TikTok, Pinterest, Threads, YouTube, Google Business Profile)Integration chosen by the customer to publish content.
Your own webhooksWe send message events to the address you set.

Providers we use for our own data as controller

These providers handle your account data, our website visitors and support conversations with us, as described in our Privacy Policy.

ProviderPurposeDataLocation
StripeSubscription payments and invoicesBilling details and card data (held by Stripe)United Kingdom and global
Zoho CorporationCompany mailboxesCorrespondence with customersUnited States (being verified)
Meta PlatformsMeta Pixel, Conversions API and Custom AudiencesWebsite events, advertising identifiers, hashed e-mail and mobileUnited States
GoogleGoogle Tag Manager and Google Ads (according to the visitor's cookie choice; in the EU/EEA, UK and Switzerland only after they accept), and Google Calendar for meetingsWebsite events, conversion data and invitee e-mail addressesUnited States
AnthropicDrafting LetsBot's AI assistant replies to support requestsSupport conversations with LetsBotUnited States
OpenAIInternal assistant for our support teamSupport conversations with LetsBotUnited States
TelegramInternal alerts to LetsBot managementCustomer name and a summary of the issueGlobal

Change notices and objections

  1. Subscribe: write to support@letsbot.net with the subject "Subprocessor updates", from the address where you want to receive notices.
  2. Notice period: we send notice at least 30 days before we add or replace a sub-processor for customer data, and update this page the same day.
  3. Objections: you can object in writing during the notice period on reasonable data protection grounds, as set out in section 6 of the Data Processing Agreement.
  4. Emergency replacement: if we must replace a sub-processor immediately to protect security or continuity, we tell you as soon as possible, and you keep the right to object.

Change log

  • 12 October 2026: Anthropic (Claude) and Google (Gemini API) became alternative or backup providers for workspace AI tasks alongside OpenAI, and the transfer mechanisms in the three AI providers' terms were added.
  • 1 October 2026: first published list.

Change notices

Subscribe to subprocessor updates

Email us with the subject "Subprocessor updates" to get notice 30 days before any change.