BumbleB Technologies Privacy Policy
What this policy covers. This policy explains how BumbleB Technologies handles personal data where we decide how and why it’s used — as a “controller” or, in India, a “Data Fiduciary”. That means your Account Data, information from our own website, the creation of Usage Data, and your own personal data in an individual account (one you hold yourself, not through a company). In an individual account, Visitor Data and any data you upload about other people are yours to control: we process them for you under our Data Processing Agreement, as we do for a company.
What it doesn’t cover. When a company uses BumbleB Crunch, we process its Customer Content — including Visitor Data about people who visit its website — on that company’s behalf and only on its instructions. That processing is governed by our Data Processing Agreement with the company and by the company’s own privacy notice. If you visited a website that uses BumbleB Crunch, or you use BumbleB Crunch through your employer, please contact that company about your data. We’ll help them answer you.
Previous versions of this policy, with a short change log, are available at https://bumbleb.co/legal/archive.
Who we are
In short: BumbleB Technologies Pvt Ltd, an Indian company, runs BumbleB Crunch and is responsible for the data this policy covers.
BumbleB Crunch™ is an analytics service. You connect your data, from files, databases, apps, platforms and other systems, or send us events from your websites, stores and apps; you ask questions in plain language, and BumbleB Crunch answers with explanations, charts and tables, makes things such as dashboards and documents, and does work you set up for it. The “Service” means all the software, apps, agents, APIs, connectors, integrations and other products and services BumbleB Technologies provides, now or later, however you reach them. “We”, “us” and “BumbleB Technologies” mean BumbleB Technologies Pvt Ltd, registered office 581, Second Floor, 1st Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India. “You” means the person reading this — an account holder, a user, or a visitor to our website.
The three kinds of data
In short: your content, your account, and our record of how the Service ran are kept apart and treated differently.
We sort everything we handle into three kinds, and we never mix them.
- Customer Content means Inputs, Outputs and Visitor Data. Inputs are what you or your users type, say, upload or connect, and what the Service receives from or reads in your Connected Systems: the files, databases, data lakes, apps, stores, websites, devices, platform accounts, APIs, tool servers, AI assistants and other systems you connect or point the Service at, by any method it offers. Outputs are what the Service writes back or makes for you: answers, charts, tables, generated queries, and things such as dashboards, documents, sheets and slides. Visitor Data is what our tracking tag, pixel or SDK, or events your systems send us, record about the people who visit or use your websites, stores and apps, including identifiers and attributes you send with them, an approximate location derived from their IP address, and recordings of their sessions where you turn that on.
- Account Data is who you are and how you use your account.
- Usage Data is our identity-free record of how the Service ran.
| Customer Content | Account Data | Usage Data | |
|---|---|---|---|
| What it is | Your questions, files and data from your Connected Systems; what our tag, pixel or SDK, or your systems, send us about your visitors and users; and every answer, chart, table and other thing we make for you. | Names, emails, organisation, logins, seats, plan, invoices, payment records, credits and balances, usage counts, the campaign that brought you to us, support tickets and notes from calls with us. | Which tools the Service called, in what order, the types of arguments (never the values), the kind of question, errors, retries, timing, and whether the answer was accepted — with no names, account identifiers or data values. |
| Who controls it | You | Us | Us |
| What we use it for | Answering your questions; keeping the Service secure; support you ask for | Running and billing your account; security; customer success; telling you about your account and the product | Operating, securing, measuring and improving the Service |
| Contains personal data? | Often | Yes | No. We create it from your sessions as they run, and that step uses personal data. The record we keep is designed so it can’t identify anyone |
Two more defined terms. A Submitted Conversation is a conversation a user chooses to send us, for example by using “Report a bug”. Before it is sent, you see how we will use it. Feedback means suggestions and ideas about the product, which you send us however you like. They’re different: Feedback is about BumbleB Crunch; a Submitted Conversation contains Customer Content and has its own rules, set out below.
Our three promises
In short: we don’t train on your content, we learn only from an identity-free record of how the Service ran, and our staff don’t read your content to improve the product.
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.
Usage Data. BumbleB Technologies records how the Service runs — which tools were called, in what order, and whether they worked — without names, account identifiers or the values in your data. We use Usage Data only to operate, secure, measure and improve the Service.
No human reading. BumbleB Technologies staff do not read Customer Content to improve the Service. Staff read it only to provide support you ask for, to investigate security or abuse, or when you send us a conversation.
These apply to every customer: individuals and companies, on every plan, in every country. The same words appear in our Terms of Service, our Data Processing Agreement and our How we use your data page.
What we collect and why
In short: each purpose is listed separately below, with the data it uses and the legal basis we rely on.
What we collect.
- From you: your name, email, organisation, role, password or single sign-on details, billing details, support requests, Feedback, ratings and comments you give on answers, and anything you tell us on calls.
- Automatically, when you use the Service: login records, IP address and device information (on our apps, also details such as the app version and operating system), usage counts (for example, how many questions you ran this month, or how many credits you used), and Usage Data.
- When you arrive from a link: if you reach us from an advertisement or a campaign link, the campaign details in that link, such as its source and click identifiers. We keep them with your account, to learn which of our campaigns work, only if you agreed to analytics or advertising cookies in our cookie banner. Otherwise we don’t keep them.
- From your organisation: if your employer adds you to its workspace, it gives us your name and email.
- On our websites and in our apps: anything you submit in a form. Only if you agree, for example through our cookie banner, we also measure how you use them: the pages you open, your clicks and scrolling, your device and browser, an identifier stored in your browser, and recordings of your visits, with what you type hidden. The banner offers separate choices (analytics, session recordings and advertising), and each runs only with its own choice. When you’re signed in, we may link these records to your account. Measurement and advertising providers may help us, for example to measure our own advertising campaigns. A provider that processes data for us is named on our sub-processor list before it runs. Currently, on bumbleb.co, Google Analytics works for us as our processor (listed there), and Google Ads conversion measurement is run by Google as an independent controller, under Google’s privacy policy; it is not on the sub-processor list. A provider that acts as an independent controller is named here before it runs. We don’t use these records to target ads to you on other sites. If your browser sends a Global Privacy Control signal, none of this runs. You can withdraw any choice at any time from “Cookie settings”.
- When you visit our website: bumbleb.co is served by Google Firebase Hosting, which sees your IP address and request details in its access logs.
- When you try a demo: see “Guest demo” below.
- In an individual account: your Customer Content, which we process as described in this policy.
- From your Connected Systems: whatever the systems you connect or point the Service at hold or send, within the access you give. If you give us a password, key or token for one, or a permission on another platform, we keep it encrypted and use it only for that connection. If you run one of our connectors inside your network, it sends the data you allow under the rules you set, and technical details about itself, such as its version and which columns it left out (never their values). When you disconnect a source, you choose whether we keep or delete what was already brought in; if you don’t choose, we delete it after a short period.
Why we use it. The legal basis column applies to the “Everywhere else” baseline. India has its own rules — see the India section below.
| Purpose | Data | Legal basis |
|---|---|---|
| Deliver the Service — answer your questions, run your workspace, show your history, and do work you set up, such as scheduled questions and summaries | Customer Content (individual accounts); Account Data | Contract |
| Billing — meter usage, manage credits and balances, invoice, collect payment, keep tax records | Account Data (plan, usage counts, credits and balances, invoices, payment records) | Contract; legal obligation |
| Security and abuse prevention — detect misuse, investigate incidents, keep access logs | Account Data; access and security logs; Customer Content when investigating a specific incident | Legitimate interests (keeping the Service and its users safe); legal obligation |
| Support — fix a problem you report | The Account Data and Customer Content involved in your request, read in place | Contract; your request |
| Improve the Service using Usage Data — find which tool sequences fail and fix them, tune our own service components | Usage Data, created from each session as it runs | Company accounts: on our customer’s instruction, under the DPA. Individual accounts: legitimate interests (a working, improving Service), with your right to object; in India, consent by ticking a box that starts unticked |
| Automated re-check of recent sessions — machines re-scan sessions less than 90 days old to add a new label or verdict; output is labels only and no person reads the sessions | Customer Content from the last 90 days (excluding Visitor Data) | Company accounts: on our customer’s instruction, under the DPA. Individual accounts: legitimate interests, with your right to object; in India, consent by ticking a box that starts unticked |
| Submitted Conversations — our team reads the conversation you send and uses it to improve BumbleB Crunch, including to train our models | That one conversation, with Visitor Data hidden first | Consent — you choose to send it, and can withdraw it |
| Customer success and account communications — onboarding help, renewal, notices about your account and your work in it, invoices, security and changes to our sub-processors, by email, in the product or through other channels you choose | Account Data, including usage counts — never what you asked or what the answers said. A notice about your own work, such as a finished report, may name it, for example by its title | Contract; legitimate interests (looking after the account) |
| Measuring our marketing — learning which campaigns bring people to us | The campaign details from the link you arrived by, kept with your account only if you agreed to analytics or advertising cookies | Consent — your choice in our cookie banner, which you can withdraw from “Cookie settings” |
| Measuring and improving our own websites and apps — seeing where they are hard to use, and measuring our own campaigns | The measurement records described under “On our websites and in our apps”, linked to your account when you’re signed in | Consent — you make the matching choice in our cookie banner, and can withdraw it from “Cookie settings” |
| Guest demo and sales contact — let you try a demo, reply to you and follow up about the Service | The email and company you give to start a demo; counts and topics of demo questions, never the questions themselves | Legitimate interests (answering a person who asked to try the Service) |
| Marketing — news about features, events and offers | Name, email, organisation, your marketing preferences | Consent where the law requires it, otherwise legitimate interests with an opt-out. Every marketing email has an unsubscribe link |
What we never do. We don’t build profiles of your website visitors or other people in your data, for ourselves or for anyone else; analysis you ask for about people in your own data is done for you, on your instructions. We don’t use Visitor Data to improve BumbleB Crunch. We don’t make automated decisions about you that have legal or similarly significant effects. Our sales and customer-success team sees which features an account uses and how often — never what you asked or what the answers said.
How we learn whether BumbleB Crunch got it right
In short: machines check our work and keep only labels; a person reads real content for improvement only when you send it to us.
BumbleB Crunch answers by calling a series of tools — filter the data, compare two periods, draw a chart. To tell whether it chose well, without anyone reading your conversations, we use methods such as these:
- Live labelling. While answering, a classifier gives the question a type, such as “period comparison”. We keep the type, not your words.
- Automatic signals. Did a tool fail? Did BumbleB Crunch retry? Did you rephrase, accept the answer or rate it? A rating you give is kept with that conversation, and Usage Data records only that an answer was rated and how. A comment you add stays with the conversation, on its schedule; no one reads it to improve the product unless you send the conversation to us.
- Automated checking. A separate model compares your question with the steps BumbleB Crunch took and records a verdict from a fixed list, such as “right tool, wrong time period”. It stores the verdict only.
- Re-checking recent sessions. For up to 90 days, automated tools may re-check recent sessions for a new kind of problem. They output labels only. No person reads the sessions. Individual users in India are asked first.
- Submitted Conversations. If you send us a conversation, our team may read it and use it to improve BumbleB Crunch, including to train our models. Visitor Data is hidden before anyone reads it. You can withdraw it at any time: we delete it and stop using it, but we can’t undo training that has already finished. If your plan lets your company’s admin turn this off and they have, you can’t send one.
When you delete your account, we delete your Customer Content, including the copies, caches and summaries we made from it, and your personal data on the schedule below. Backups follow their own schedule. We keep Usage Data, because it identifies no one and can’t be traced back to you. We’d rather tell you that now than have you find out later.
How we use AI providers
In short: AI model providers, routers and gateways named on our sub-processor list generate answers for us. None may train on your data, and the list shows how long each keeps anything.
To answer a question or do work you set up, we send the relevant Inputs to AI model providers, routers and gateways named on our sub-processor list, for inference only: the provider generates a response and sends it back. We may reach a model directly or through a router, gateway or cloud platform; where a router passes a request on to another model provider, that provider is part of the router’s chain and is shown on the list. We may choose, add, change or route between models and providers to run the Service, so which one answers can vary. We may also use them to create embeddings that power search. Our contracts with every provider we choose prohibit training any model on your data or using it for their own purposes.
Retention. The list shows, for each provider, router and gateway, how long it keeps prompts and responses, whether zero data retention is on for our account, and any exception it keeps, such as for abuse monitoring or where the law requires. A zero-retention statement covers only the party it is made for.
Providers you choose. If you connect your own account or key with an AI model provider or router, BumbleB Crunch sends it what your requests need, under your agreement with that provider. It is one of your Connected Systems, not our sub-processor.
Web search. Where your plan includes web search and you use it, BumbleB Crunch sends the search terms it writes for that search, and nothing else, to a web search provider named on our sub-processor list, and uses the results to answer you. A search provider is used only when web search is on for that turn.
Apps on your computer
In short: some BumbleB Technologies apps, such as BumbleB Acorn, run on your own computer and work with data you connect there. What they keep on your computer is yours; what they send us to answer you is your Customer Content.
Some BumbleB Technologies apps, such as BumbleB Acorn, run on your own computer, sign in to your BumbleB Crunch account and work with databases and files you connect there.
- What stays on your computer: what the app keeps there, such as your connection details and passwords, and copies or results it saves. We don’t receive or hold it, and it’s yours to manage and delete. We don’t receive passwords the app keeps on your computer.
- What reaches us: what BumbleB Crunch needs to answer you, such as your questions, the names and structure of the tables you choose, and results of the queries it runs. This is your Customer Content (Inputs), handled like any other question, including by our AI providers.
- What we keep: your conversations and what BumbleB Crunch learns about your data to answer you, on the schedule in “How long we keep data”.
The app’s listing and our help center describe what each app does and the settings it offers.
AI assistants and other systems you connect
In short: if you connect BumbleB Crunch to another system, such as an AI assistant like Claude, or a server or API you add, what goes to that system goes under your agreement with its provider.
You can connect BumbleB Crunch to other products you use, such as an AI assistant like Claude. When you do, the questions you ask through that product and the answers BumbleB Crunch returns, including tables of your data, are sent to its provider. They handle that data under your agreement with them, not ours, and they are not our sub-processors. We return only data you are allowed to see. We keep records of sign-ins and requests, without content, with our access and security logs, and sign-in tokens until they expire or you disconnect. You can disconnect at any time, from the other product or from your account with us.
Servers, APIs and other systems you add. If you or your workspace connect BumbleB Crunch to a server, API or other system so it can call it for you, BumbleB Crunch sends it the requests and data needed for what you ask. It changes something there only where a feature you turn on says it does, and only within the permission you give. Its provider acts under your agreement with them, not as our sub-processor. Credentials for it are kept encrypted, and your workspace chooses who may use a connection.
Platform rules. Where a platform you connect, such as Google, Shopify, Microsoft or an app store, has its own rules for apps that use its data, we follow them for the data we receive from it.
Voice input. If you speak instead of typing, your browser or device turns your speech into text using its own speech service, under its own terms. BumbleB Crunch receives the text, which it handles like anything you type.
Google user data
In short: we use data from your Google account only for what you choose, signing in and any Google products you connect, only the data you grant, and only within Google’s rules.
Signing in. When you choose “Sign in with Google” — on bumbleb.co, in BumbleB Crunch, or when you
connect an AI assistant to BumbleB Crunch — Google shares your name, email address, Google account ID
and, if you have one, your profile picture with us (the openid, email and profile
permissions). We use them to create your BumbleB Crunch account and sign you in, and, for a connected
AI assistant, to check that you are a BumbleB Crunch user and that you haven’t removed BumbleB
Crunch’s access.
Google products you connect. You may connect Google products, for example Business Profile, Google Analytics, Google Ads, Gmail, Google Drive, Google Calendar or Google Sheets, as the Service offers them. Google asks your permission first and shows what it covers. Our Connections and integrations page lists the Google products you can currently connect, what we read from each and whether a feature can act there. We access only the data you grant, and use it only to provide the features you use with it. We bring that data into your workspace so you can see it, ask about it and use it in your work. We change something in a Google product only where a feature you turn on says it does, and only within the permission you gave.
- How we use it: only to provide the features you use with it in BumbleB Crunch. We don’t sell it, use it for advertising, or use it to train or improve any AI model. People at BumbleB Technologies don’t read it, except with your permission, for security, or where the law requires.
- How we keep it: sign-in details with your account; data from a Google product you connect in your workspace, like data from your other Connected Systems. Both on the hosting listed on our sub-processor list, and deleted on the schedule in “How long we keep data”. When you disconnect a product, you choose whether we keep or delete what was already brought in.
- Who we share it with: only the sub-processors that run BumbleB Crunch for us, including our AI model providers when they write an answer you asked for, and any system you yourself tell BumbleB Crunch to send it to.
- Removing access: disconnect the product in BumbleB Crunch, or remove BumbleB Crunch’s access to your Google account at any time at myaccount.google.com/permissions. Removing access stops further reads. If access is removed at Google, we stop reading, and we may delete what we already brought in after telling you.
BumbleB Technologies’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Who we share data with
In short: only companies that help us run BumbleB Crunch, and otherwise only where the law requires it or in a business sale.
- Sub-processors and service providers — such as hosting and cloud providers, email delivery, AI model providers, routers and gateways, search providers, measurement providers for our own websites and apps, and payments — who process data only on our instructions, under written data-protection contracts. Our sub-processor list names every vendor that processes Customer Content, and the vendors, such as payment and email providers, that handle Account Data only. We notify subscribers at least 15 days before a new one starts, or, in an emergency (a security incident, or a sub-processor suddenly unable to provide its service), sooner, with notice within 5 business days.
- AI assistants you connect, such as Claude. Your questions and our answers go to the assistant’s provider under your agreement with them (see “AI assistants and other systems you connect” above).
- Your organisation. If you use BumbleB Crunch through a company workspace, its administrators can see your account details, the content in that workspace, and records of your use of it, such as your usage and costs, shown by name. If your workspace pays for your use, it can see what you used.
- Legal requests. We disclose data when the law requires it — for example, a valid court order — and only what is required. Where we’re allowed to, we tell you first.
- Business transfers. If BumbleB Technologies is merged, acquired or sells its assets, data may pass to the new owner, who must honour this policy. We’ll tell you before that happens.
- Professional advisers, such as lawyers and auditors, under a duty of confidentiality.
- People you share with. If you share or publish something, the people you share it with, or anyone with its link, can see it.
- Anyone else, only with your consent.
We never sell your personal data, and we don’t share it for targeted advertising.
International transfers
In short: we currently host in the United States, may use other regions and listed providers, and protect data wherever it goes.
We currently host the Service in the United States, and some processing, such as email delivery, happens in other countries. We may host or process data in other regions, or with other providers on our sub-processor list, which shows where each provider processes data; a new region or provider is added to that list first. Our hosting provider’s global edge network may carry data in transit, only where we use it to deliver the Service. A connected service you choose may process data outside our hosting regions, under its own terms; what we say about where data is processed covers our own systems and our sub-processors only. Wherever data goes in our hands, the same contractual protections apply. Where data about people in the European Economic Area, the United Kingdom or Switzerland is transferred, we use the European Commission’s Standard Contractual Clauses and the UK Addendum. Details of each sub-processor’s location are on our sub-processor list.
Guest demo
In short: a demo uses sample data. We don’t read your questions, and we keep your email and company as a sales contact.
You can try a demo of BumbleB Crunch as a guest, on a sample business with simulated data. Our Demo terms apply.
- Your questions: we don’t read the questions guests ask. We see only counts and topics, and keep them at most 90 days.
- Email and company: to start a demo you give us your email and company. We keep them as a sales contact, to reply to you and follow up about the Service. Marketing beyond that follow-up happens only with your separate consent, which you can withdraw at any time.
How long we keep data
In short: only as long as needed for the purpose, deleted automatically. The current periods are on our limits page.
| Data | How long |
|---|---|
| Your conversations — questions and answers, in any BumbleB Technologies app | As long as needed to provide the Service, then deleted automatically; the current period is on our Current limits and settings page, with backups on the schedule shown there |
| Data a BumbleB Technologies app keeps on your own computer | On your computer, under your control; not held by us |
| Records of who accessed what (access and security logs — no content) | As long as needed for security and to meet the law; the current period is on the same page |
| Submitted Conversations | Until you withdraw them, and no longer than the period on the same page |
| Visitor Data, uploaded files and data from Connected Systems in an individual account, including how each dataset was built | While your account is open, or until you delete them or disconnect the source and choose to delete it |
| Our own measurement of our websites and apps (only if you agreed) | Kept as long as needed for that purpose; deleted when you withdraw consent or ask us to, or when no longer needed. The same goes for recordings of visits |
| Other content you create, save, share or publish | Until you delete it, or while your account is open |
| Guest demo: counts and topics of questions | At most 90 days |
| Guest demo: email and company given to start a demo (sales contact) | Kept as long as needed to follow up; deleted when you withdraw consent or ask us to, or when no longer needed |
| Account Data | While your account is open, then as long as the law requires; tax invoices and payment records as long as tax and company law require |
| Usage Data | As long as it’s useful. It identifies no one, so it isn’t deleted with your account. |
| Prompts held by AI model providers, routers and gateways we choose | As shown for each one on our sub-processor list, including whether zero data retention is on and any exception, such as for abuse monitoring |
Our Current limits and settings page shows the current periods; if we lengthen one, we tell you first. We keep data longer only when the law requires it, for example during a legal dispute. When an account ends, we offer an export and then delete its Customer Content as set out in our Terms of Service and Data Processing Agreement.
How we protect data
In short: encryption, tight access controls, logged staff access and fast breach notice.
We encrypt data in transit (TLS 1.2 or higher) and at rest (AES-256 or equivalent). Access is role-based and limited to the people who need it. Staff can open a conversation only for support you asked for or to investigate security or abuse; that access is tied to a ticket or incident, read in place, never copied into our improvement work, and recorded in an access log, kept for the period on our limits page. We also test for vulnerabilities, train our staff and review our sub-processors’ security.
No system is perfectly secure. If a breach affects your personal data, we’ll tell you without undue delay, and tell regulators where the law requires. We notify affected business customers without undue delay, and within 48 hours of becoming aware.
Your rights
In short: you can see, correct, delete and take your data, object to how we use it, and complain to a regulator.
Everywhere else. Wherever you are, you can ask us to:
- Access — confirm whether we hold your personal data and give you a copy.
- Correct — fix data that’s wrong or incomplete.
- Erase — delete your personal data, unless we must keep it by law.
- Restrict — pause our use of your data while a question about it is resolved.
- Port — give you your data in a machine-readable format.
- Object — stop processing based on legitimate interests, including creating Usage Data from your sessions and re-checking them. If you object, we stop doing so for your future sessions, where we can identify your sessions when they happen. Usage Data already created identifies no one, so we can’t find it to remove it. You can always object to marketing.
- Withdraw consent — at any time, as easily as you gave it, without affecting what we did before.
- Complain to your data protection regulator. We’d appreciate the chance to fix things first.
Usage Data isn’t covered by access or erasure requests, because nothing in it links to you. Your rights apply to the step that creates it, which is why you can object to it or, in India, withdraw consent to it.
How to ask. Email privacy@bumbleb.co, or use the settings in your account. We may need to confirm your identity first. We reply within 1 month, or sooner where the law requires; if a request is complex we may extend this as the law allows, and we’ll tell you why. If you use BumbleB Crunch through a company, or your data reached us through a website’s or app’s tracking tag, pixel or SDK, the company is responsible for your request — contact it, and we’ll help it answer you.
The sections that follow add the rights and details that apply in India and in the United States.
India
In short: under India’s Digital Personal Data Protection Act, 2023, you get an itemised notice, consent you can withdraw as easily as you gave it, a named Grievance Officer who resolves complaints within one month, and the right to nominate someone to act for you.
This section applies to personal data we process in India or in connection with offering the Service to people in India, under the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025. Some of the Act’s duties begin later, during 2026 and 2027; we follow everything in this section from the day this policy takes effect.
Our role. We are the Data Fiduciary for Account Data, for the personal data we use to create Usage Data, and for your own personal data in an individual account. Visitor Data and any data you upload about other people are yours to control, even in an individual account: you are their Data Fiduciary and we are your Data Processor, under our Data Processing Agreement. When a company uses BumbleB Crunch, the company is the Data Fiduciary for its Customer Content, including Visitor Data, and we are its Data Processor: we process that data only on the company’s instructions, under a contract. If your data reached us through a company, send requests to that company; we’ll help it respond.
Until the Act’s main duties begin. Until then, the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 also apply. Your password and payment details are sensitive personal data under those Rules. We collect them only to run your account and take payment, with the consent you give when you sign up; we transfer personal data outside India only to recipients bound to protect it to at least the standard of those Rules; and our Grievance Officer resolves grievances within one month.
What we use your data for — each purpose separately.
Delivering the Service — answering your questions and running your account. Uses your Inputs, Outputs and Account Data.
Billing — metering usage, invoicing and keeping tax records. Uses Account Data.
Security and abuse prevention — protecting the Service and investigating incidents. Uses Account Data and access logs, and Customer Content only for a specific investigation.
Support — fixing a problem you report. Uses the data involved in your request, read in place.
Improving the Service using Usage Data — learning which tool sequences work. Uses an identity-free record of how the Service ran, created as each session runs. Only if you tick the box described below.
Re-checking recent sessions — automated re-checks of sessions less than 90 days old, producing labels only. Only if you tick the box described below.
Submitted Conversations — reading and learning from a conversation you choose to send us, including to train our models. Only when you send one.
Account communications — invoices, security notices, renewal and changes to our terms or sub-processors. Uses Account Data.
Marketing — news about features and events. Only if you opt in, with a box that starts unticked. Every marketing email has an unsubscribe link.
Measuring our marketing — learning which campaign brought you to us, from the campaign details in the link you arrived by. Only with your consent: we keep them only if you agreed to analytics or advertising cookies in our cookie banner, and you can withdraw from “Cookie settings”.
Measuring and improving our own websites and apps — the measurement described under “On our websites and in our apps”, including recordings of visits with what you type hidden, linked to your account when you’re signed in. Only if you make the matching choice (analytics, session recordings or advertising) in our cookie banner, and you can withdraw it from “Cookie settings”.
Guest demo and sales contact — letting you try a demo and following up about the Service. Uses the email and company you give to start a demo, which you choose to give us. Marketing beyond that follow-up only if you opt in, separately.
At signup we show you this list. Purposes 1 to 4 and 8 use the data you choose to give us in order to use the Service, which the Act treats as a “legitimate use”; keeping records the law requires is also a legitimate use. You can tell us at any time that you no longer want this, and we’ll explain what that means for your account. Purposes 5, 6, 7, 9 and 11, and 10 where the Act requires it, happen only with your consent, which you give separately for each.
Improving the Service — your choice. If you hold an individual account in India, you’ll be asked two separate questions at signup, both off unless you turn them on: whether BumbleB Technologies may learn from an identity-free record of how its tools ran in your sessions, and whether it may automatically re-check your recent sessions to improve answers.
If you leave the first off, we don’t create Usage Data from your sessions. If you leave the second off, our automated re-checks skip your sessions. Live labelling and automated checking still run while BumbleB Crunch answers you, because they’re part of answering. You can change either at any time in your account settings or by emailing privacy@bumbleb.co.
Withdrawing consent. You can withdraw any consent as easily as you gave it — in your account settings, by withdrawing a Submitted Conversation, through the unsubscribe link, or by emailing privacy@bumbleb.co. We then stop that processing and delete the data used for it, unless the law requires us to keep it. Usage Data already created identifies no one, so we can’t find it to delete it; we stop creating more. Withdrawal doesn’t affect processing that happened before. If you ask us to stop purposes 1 to 4, we may no longer be able to provide the Service, and we’ll tell you what that means before closing anything.
Consent Managers. Once Consent Managers registered with the Data Protection Board of India are operating, you may give, review, manage and withdraw your consent to us through one, and we’ll act on it in the same way.
Your rights. You can ask us for:
- Access — a summary of the personal data we hold about you, what we do with it, and the other Data Fiduciaries and Data Processors we’ve shared it with, with a description of what was shared.
- Correction, completion and updating of data that’s inaccurate, incomplete or out of date.
- Erasure of data we no longer need for the purpose you gave it for, unless the law requires us to keep it.
- Grievance redressal — see below.
- Nomination — you can name another person to exercise your rights if you die or become unable to do so. Tell us who, through your account settings or by emailing grievance@bumbleb.co.
Grievance Officer. Our Grievance Officer is Chinmaya Reddy, grievance@bumbleb.co, 581, Second Floor, 1st Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India. We acknowledge every grievance and resolve it within one month. If you’re not satisfied with our answer, you can complain to the Data Protection Board of India.
Language. This notice is available in English or, on request, in any language listed in the Eighth Schedule to the Constitution of India. Ask at grievance@bumbleb.co.
Children. We don’t offer individual accounts to anyone under 18, and we don’t onboard websites directed at children. If we learn that a website is directed at children, we stop collecting from it and offboard it.
Data breaches. If a breach affects your personal data, we’ll tell the Data Protection Board of India and you without delay — what happened, what it means for you and what you can do — and send the Board a detailed report within 72 hours.
Transfers outside India. We currently host the Service in the United States, and our AI providers currently process Inputs there; we may use other regions or listed providers, as our sub-processor list shows. Your personal data is therefore transferred outside India. Indian law allows this except to countries the Central Government restricts by notification. None has been notified yet; if one is, we won’t transfer personal data there.
Retention. We erase personal data once the purpose it was collected for is served, on the schedule in “How long we keep data” above. Access and security logs, which contain no content, are kept for at least 12 months, as Indian law requires.
United States
In short: if you live in a US state with a privacy law, you can access, delete and correct your data and opt out of sale, sharing and targeted advertising. We don’t sell data; advertising measurement on our own website may count as sharing, and you can opt out.
This section applies to residents of US states with comprehensive privacy laws, including the California Consumer Privacy Act as amended by the California Privacy Rights Act. Where we process personal data on behalf of a business customer — its Customer Content, including Visitor Data — we act as its service provider or processor. That customer handles your request; send it to them, and we’ll assist.
Your rights. Depending on your state, you can ask us to:
- Know and access — tell you what personal data we’ve collected about you, where it came from, why we use it and who we disclose it to, and give you a copy in a portable format.
- Delete the personal data we’ve collected from you.
- Correct inaccurate personal data.
- Opt out of the sale or sharing of your personal data, and of targeted advertising. We don’t sell personal data. With your advertising choice in our cookie banner, advertising measurement on our own website may count as “sharing” for cross-context behavioural advertising under California law. We offer a “Do not share” choice, and we treat the Global Privacy Control signal as an opt-out. Either one stops it. We don’t use personal data for targeted advertising on other sites.
What we collect, why, and who we disclose it to. We collect the categories below. We collect them from you, automatically when you use the Service or our website, and from your organisation if it adds you to its workspace. We keep each for the periods in “How long we keep data” above.
| Category | Examples | Purpose | Disclosed to | Sold or shared? |
|---|---|---|---|---|
| Identifiers | Name, work email, account ID, IP address | Delivering the Service; billing; security; support; account communications; marketing | Hosting, email delivery and support providers | No |
| Commercial information | Plan, seats, invoices, payment records | Billing; account management | Hosting and payment providers | No |
| Internet or other electronic network activity | Login records, feature-level activity counts; with your consent, how you use our websites and apps, including recordings of visits | Delivering the Service; security; customer success; measuring and improving our websites and apps | Hosting provider; measurement providers named on our sub-processor list or in our Privacy Policy | Advertising measurement may be “sharing”; see above |
| Professional information | Job title, organisation | Account management; account communications | Hosting and support providers | No |
| Customer Content in an individual account | Your questions, uploads, connected data, answers and charts | Delivering the Service; support you ask for; security | Hosting and AI providers | No |
| Account login credentials (sensitive) | Password or single sign-on details | Letting you sign in; security | Hosting provider | No |
Usage Data is deidentified. We keep it in a form that can’t reasonably be linked to you, we don’t try to re-identify it, and we don’t disclose it to anyone.
Sensitive personal information. We use your login credentials, and any sensitive information in an individual account’s content, only to provide the Service, keep it secure and meet legal obligations. We don’t use sensitive personal information to infer characteristics about you.
Global Privacy Control. Our website honours the Global Privacy Control signal as a request to opt out of sale and sharing for that browser.
No discrimination. We won’t deny you the Service, charge you a different price or give you a different quality of service because you exercised these rights.
How to make a request. Email privacy@bumbleb.co or use the settings in your account. To protect you, we verify your identity before acting — usually by asking you to confirm the request from the email address on your account, or to sign in. We’ll confirm receipt within 10 business days and respond within 45 days, or tell you if we need up to 45 more.
Authorised agents. Someone else can make a request for you if you give them signed, written permission. We may still ask you to verify your identity directly with us.
Appeals. If we decline your request and your state gives you a right to appeal, reply to our decision with “Appeal” in the subject line. We’ll respond within the time your state’s law sets and explain our reasons. If you’re still not satisfied, you can contact your state’s Attorney General.
Children
In short: BumbleB Crunch is for adults and for businesses that don’t target children.
We don’t offer individual accounts to anyone under 18. We don’t knowingly collect personal data from children, and we don’t onboard websites or apps directed at children. If we learn that a website is directed at children, we stop collecting from it, delete the data and offboard it. If you think a child’s data has reached us, contact privacy@bumbleb.co.
Changes to this policy
In short: 30 days’ notice before any material change, and every past version stays available.
If we make a material change — one that reduces your rights or expands how we use your data — we give you 30 days’ notice by email and in the product before it takes effect. Other changes, such as adding a section for a new country, are recorded in the change log with a new version number and take effect on the date shown, which is never earlier than the day we publish them. Each version shows its effective date and last-updated date, and previous versions are archived at https://bumbleb.co/legal/archive.
Contact us
In short: one address for each kind of question.
- Legal — legal@bumbleb.co
- Privacy — privacy@bumbleb.co
- Security — security@bumbleb.co
- India Grievance Officer — Chinmaya Reddy, grievance@bumbleb.co
By post: BumbleB Technologies Pvt Ltd, 581, Second Floor, 1st Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India.