BumbleB Technologies sub-processors
BumbleB Technologies Pvt Ltd (“BumbleB Technologies”) uses the third parties below to help provide the Service. This list covers every vendor that processes Customer Content, plus the vendors that handle Account Data only, listed in Section 4. Each one processes Customer Content or Personal Data only to provide its service to BumbleB Technologies, under written data-protection terms consistent with the protections in BumbleB Technologies’ Data Processing Agreement. BumbleB Technologies remains liable for their performance.
No training. BumbleB Technologies will not use Customer Content to train, retrain or fine-tune any AI model, and will not allow any sub-processor to do so. The only exception is a Submitted Conversation, which a user chooses to send us.
1. Hosting and email
| Sub-processor | Purpose | Data | Location | Retention & training terms |
|---|---|---|---|---|
| Microsoft Azure (Microsoft Corporation) | Primary hosting: application services, databases and storage; hosting and delivering the tracking tag and receiving tag events; logs and monitoring; secrets and stored connection credentials (Azure Key Vault); the event stream (Azure Event Hubs) | All Customer Content (including Visitor Data from the tag), Account Data and Usage Data, and the credentials you give us for a Connected System (kept encrypted) | United States (East US), and Microsoft’s global edge network, in transit only, where we use it to deliver the Service | Holds data only as BumbleB Technologies directs and deletes it on BumbleB Technologies’ schedule. No training on Customer Content. Visitor Data is never used to improve the Service. |
| MongoDB Atlas (MongoDB, Inc.) | Managed database service, running on Microsoft Azure | Customer Content, Account Data and Usage Data stored in BumbleB Technologies’ databases | United States (Azure East US 2, Virginia) | Holds data only as BumbleB Technologies directs and deletes it on BumbleB Technologies’ schedule. No training on Customer Content. |
| Amazon Web Services (Amazon Web Services, Inc.) — Amazon SES | Transactional email: account, billing, security and service notices, including notices about a user’s own work | Recipient email addresses and the content of those notices, which may include the name or title of the item a notice is about, such as a conversation or report. No data tables, no Visitor Data. | Asia Pacific (Mumbai) | Holds message data only as needed to deliver email. No training on Customer Content. |
2. AI model providers, routers and gateways
These providers receive the question and the context needed to answer it, to generate an answer (inference), and for nothing else. No provider receives data for training, evaluation or its own product improvement. BumbleB Technologies may reach a model directly, or through a model router, gateway or cloud platform listed here. Where a router or gateway passes requests on to other model providers, those providers are part of its chain: they are shown in its row, with their retention terms, and bound in the same way. Each row states whether zero data retention is on and any exception the provider keeps, such as for abuse monitoring; a zero-retention statement covers only the party it names.
| Sub-processor | Purpose | Data | Location | Retention & training terms |
|---|---|---|---|---|
| OpenAI (OpenAI, L.L.C.) | Inference — generating answers, directly; text embeddings for search, directly | Inputs and the context needed to answer them; Outputs; text submitted to create search embeddings | United States | Inference only. Contractually barred from training on Customer Content. Zero data retention for our requests, except that the provider may keep them for a limited period solely to monitor for abuse, then delete them. Never used for training. |
| Anthropic (Anthropic, PBC) | Inference: generating answers and doing agent work, when a Claude model is used | The Inputs and the context needed for each request; Outputs | United States | Inference only. Contractually barred from training on Customer Content. Zero data retention for our requests, except that the provider may keep them for a limited period solely to monitor for abuse, then delete them. Never used for training. |
Currently, BumbleB Technologies reaches both directly; no router or gateway is in use. BumbleB Technologies may choose, add, change, remove or route between the models and providers on this list to run the Service. A new provider, router or gateway is added to this list with the notice in Section 7, with its retention terms. Any model BumbleB Technologies trains or fine-tunes for itself uses only Usage Data and Submitted Conversations, as the DPA allows.
AI model providers or routers you connect with your own account or key are not sub-processors. If you connect BumbleB Crunch to a model provider or router using your own account or key, BumbleB Crunch sends it what your requests need, on your instruction and under your agreement with that provider. It is one of your Connected Systems (DPA Section 3.6), so it isn’t listed here, and its retention and training terms are the ones you agreed with it.
Web search. Where a plan includes web search, the search terms BumbleB Crunch writes for a search go to a web search provider, and nothing else. A provider is used only when web search is on for that turn. We currently use the two below. We add or replace a search provider only with the notice in Section 7.
| Sub-processor | Purpose | Data | Location |
|---|---|---|---|
| Firecrawl | Web search | The search terms only | United States |
| Brave Search (Brave Software, Inc.) | Web search | The search terms only | United States |
AI assistants you connect are not sub-processors. If you connect BumbleB Crunch to an AI assistant you use, such as Claude or ChatGPT, the assistant’s provider receives your questions and BumbleB Crunch’s answers under your agreement with that provider. It acts for you, not for BumbleB Technologies, so it isn’t listed here (DPA Section 3.6). OpenAI and Anthropic appear on this list only as BumbleB Technologies’ providers for generating answers. Using Claude through BumbleB Crunch is different from connecting Claude yourself: when we use a Claude model to answer you, Anthropic acts for us and is listed above.
3. Tracking tag, pixel and SDK
The tracking tag, pixel and SDK are served from, and send their events to, BumbleB Technologies’ own infrastructure on Microsoft Azure (Section 1), as do events customers’ systems send us. No other vendor is involved.
Customers who deploy the tag through their own Google Tag Manager account do so under their own Google terms, and Google is not BumbleB Technologies’ sub-processor for that.
4. Vendors that handle Account Data only
These vendors help BumbleB Technologies run its business. They receive Account Data, or for our website, the details of a visit. BumbleB Technologies never sends them Customer Content; anything you choose to put in an email to us is held in Google Workspace.
| Vendor | Purpose | Data | Location |
|---|---|---|---|
| Razorpay | Taking payments and managing billing | Account Data only — no Customer Content | India |
| Google Firebase Hosting (Google LLC) | Serving our website, bumbleb.co | A visitor’s IP address and request details, in access logs. No Customer Content | Global |
| Google (Google LLC) — Google Sign-In and Google Workspace | Signing in users who choose “Sign in with Google”; BumbleB Technologies’ email, including support requests | Name, email address and Google profile identifier; emails to and from BumbleB Technologies | United States |
Measurement providers for our own websites and apps
These help BumbleB Technologies measure its own websites and apps. They never receive Customer Content. Each runs only for people who make the matching choice in our cookie banner, never under Global Privacy Control, and stops when consent is withdrawn. We list each provider that works for us here, with the notice in Section 7, before it runs. Advertising providers that act as independent controllers, not for us, such as Google Ads conversion measurement, are not listed here. Our Privacy Policy names them instead.
| Vendor | Purpose | Data | Where it runs | Status |
|---|---|---|---|---|
| Google (Google LLC) — Google Analytics | Measuring how visitors use bumbleb.co | Pages viewed, referrer, device and browser details, IP address, Google cookie identifiers | bumbleb.co only | Google acts as our processor. In use from the effective date of this version, only after the visitor’s analytics choice |
5. Software that is not a sub-processor
These run inside BumbleB Technologies’ own hosting environment. They are software BumbleB Technologies operates, not third parties that receive data: PostgreSQL, TimescaleDB and Valkey (databases); DuckDB (query engine); Grafana Loki (log storage); Caddy (secure web proxy). Our event stream is not self-run: it is Azure Event Hubs, a service of Microsoft, listed in Section 1.
Third-party services that never receive Customer Content: GitHub (source code and container images) and Let’s Encrypt (TLS certificates).
Currently, no third-party error tracker, session-replay tool, product-analytics tool or AI debugging tool receives Customer Content. If that changes, this list changes first, with the notice in Section 7.
6. What every sub-processor is bound to
Each sub-processor is bound by written data-protection terms, consistent with the protections in the DPA, that require it to:
- process Personal Data only as needed to provide its service to BumbleB Technologies, on BumbleB Technologies’ instructions;
- not use it for its own purposes, and not sell or share it;
- not train any AI model on Customer Content;
- keep it confidential and secure;
- notify BumbleB Technologies of a breach promptly enough for BumbleB Technologies to meet its own 24-hour breach-notice commitment to customers, and help BumbleB Technologies respond to rights requests; and
- delete or return it when its service ends.
7. Changes, notice and objections
General authorisation. Customers authorise BumbleB Technologies to engage the sub-processors on this list and those added under this section.
15 days’ notice. Before a new or replacement sub-processor starts processing Customer Content, BumbleB Technologies updates this page and emails everyone subscribed to changes and each customer account’s administrators, at least 15 days ahead. In an emergency, that is a security incident or a sub-processor suddenly being unable to provide its service, BumbleB Technologies may replace it sooner, and will give notice promptly and in any case within 5 business days.
How to subscribe. Subscribe at https://bumbleb.co/legal/sub-processors#subscribe, or email privacy@bumbleb.co with the subject “Subscribe to sub-processor changes”.
Right to object. A customer may object to a new sub-processor on reasonable data-protection grounds by writing to privacy@bumbleb.co within the notice period. BumbleB Technologies will discuss the objection in good faith and may offer a way to provide the Service without that sub-processor processing the customer’s data. If the objection is not resolved within 30 days, the customer may terminate the affected Service and is not charged for it after termination. The full terms are in Section 8 of the DPA.
Previous versions of this list are archived and linked from the top of this page.
8. Contacts
- Legal and contracts: legal@bumbleb.co
- Privacy: privacy@bumbleb.co
- Security: security@bumbleb.co
- Grievance Officer (India): Chinmaya Reddy, grievance@bumbleb.co
- Post: BumbleB Technologies Pvt Ltd, 581, Second Floor, 1st Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India