BumbleB Technologies Terms of Service
Thank you for choosing BumbleB Crunch™. These Terms explain what you can expect from us and what we expect from you.
1. About these Terms
1.1 Who we are. These Terms of Service ("Terms") are an agreement between BumbleB Technologies Pvt Ltd, a company incorporated in India ("BumbleB Technologies", “we”, “us”), and the customer that uses the Service ("you"). If you accept these Terms for an organisation, “you” means that organisation.
1.2 What the Service is. Service means the software, apps, agents, APIs, connectors, integrations, interfaces, tools and other products and services BumbleB Technologies provides under these Terms, now or later, however you reach them: in a browser, in an app on a computer or phone, from another product such as an AI assistant, or through an API or command line. It includes BumbleB Crunch™, our tracking tag, pixel and SDKs, and their documentation. Depending on your plan and the features you use, the Service works with data from your Connected Systems (Section 3.4) and does the things Section 3.12 describes, such as answering your questions in plain language with charts and tables as supporting evidence, making dashboards and documents, and doing work you set up for it. The Service does not include Connected Systems or other third-party products, even when you reach them through the Service.
1.3 Accepting these Terms. You accept these Terms when you create an account, sign an Order Form that refers to them, or use the Service. If you do not agree, do not use the Service.
1.4 Other documents that form part of these Terms. The following are part of your agreement with us:
- any Order Form — a signed order form or other ordering document that you and we agree to and that refers to these Terms;
- the DPA — our Data Processing Agreement, which applies to every customer, paid or free and is incorporated into these Terms by reference; and
- our Plans, credits and billing terms, our Current limits and settings page, our Connections and integrations page and, for anyone who tries the Service as a guest, our Demo terms, which hold the details that change as the Service grows (Section 20.2). We keep earlier versions of these pages available, and each page shows its “last updated” date.
Our Privacy Policy explains how we handle personal data as a controller. Our How we use your data page explains our data commitments in plain language. Where that page and these Terms differ, these Terms apply.
1.5 Which document wins. On data-protection matters, the DPA prevails over these Terms and the Order Form, unless an Order Form expressly says that it overrides a specific clause of the DPA. On other matters, the Order Form prevails over these Terms. An Order Form may also name a different BumbleB Technologies entity and a different governing law. Where it does, that entity is “we” for your agreement, and the law and dispute terms in the Order Form replace Section 19.
1.6 Defined terms. Capitalised terms are defined where first used and collected in the Glossary in Section 24.
2. Who can use the Service
2.1 Who can use it. Organisations and individuals can use the Service, for work or for personal use. If you use it for personal use, Section 23 also applies to you. To use the tracking tag on a website, you must own or control that website (Section 2.4).
2.2 Age. Individuals must be at least 18 years old to create an account or to be a User.
2.3 Authority. If you accept these Terms for an organisation, you confirm that you have authority to bind it.
2.4 Approval before the tag goes live. We may ask you to verify your domain and confirm your responsibilities under Section 6 before we activate a tracking tag, pixel or SDK. We may decline an account or a website for a reasonable reason, such as a failed verification or a breach of Section 7.
2.5 Your account and Users. Users means the individuals you allow to use the Service under your account. You are responsible for all activity under your account, including your Users' activity and their compliance with these Terms. Keep passwords and API keys confidential, and tell us promptly at security@bumbleb.co if you suspect unauthorised access.
2.6 Joining an organisation. If you join an organisation’s account, you become one of its Users. Before you confirm, we show you what happens to what you already have, which depends on how you join: it may move under the organisation’s control, or stay in your own account, which may then end, be paused or carry on separately. Whatever moves, the organisation becomes responsible for it under Section 6. Export anything you want to keep for yourself before you join.
3. The Service
3.1 Conclusions grounded in your data. The Service delivers a plain-language answer to your question, with charts and tables as the evidence beneath it. Outputs support your decisions; they do not make them (Section 8).
3.2 Availability. We aim for 99.5% availability each calendar month, not counting scheduled maintenance. We schedule maintenance to keep disruption low and give advance notice of planned downtime where we can. Any service credits or enterprise service levels are set out in your Order Form or a separate service-level addendum.
3.3 Changes to the Service. We improve the Service over time and may add, change or remove features. If we remove a feature that is material to your paid plan, we will give you at least 30 days’ notice. If the change materially reduces what you paid for, you may end the affected plan before the change, and we will not charge you for it again. Fees already paid are not refunded, except where the law requires.
3.4 Connected Systems. Connected Systems are the systems you or your Users connect to the Service, point it at, or tell it to read from, receive from or act on, by any method the Service offers. They include, for example, files, databases, data lakes and warehouses, apps, stores, websites, devices, cloud and platform accounts, APIs, tool servers, AI assistants, and AI model providers or routers you connect with your own account or key; and they may be connected by upload, by a connector we host or one you run in your own network, by our tracking tag, pixel or SDK, by events your systems send us, by a permission you grant on another platform, or with credentials you give us. Our Connections and integrations page lists the kinds we currently support. You must have the right to connect each one and to let us process what it holds. Your use of a Connected System is governed by your agreement with its provider, and where a platform’s own terms apply to our access, we follow them. When the Service works with a Connected System, it sends it what is needed for what you ask, and you choose who in your account may use a connection and its credentials. We are not responsible for Connected Systems, including for how an AI assistant restates or uses our Outputs. You are responsible for the access and permissions you grant to and through a Connected System, and for the instructions you give it through the Service. The same applies to services on your own device that you choose to use with the Service, such as speech-to-text. If access to a Connected System is removed at the source, we stop reading from it, and we may delete what we already brought in after telling you. A Connected System may process data outside the regions where we host, under its own terms. What we say about where data is processed covers our own systems and our Sub-processors only.
3.5 Apps on your devices. Some parts of the Service, such as BumbleB Acorn, run on your own computer and connect to systems you choose. An app can reach whatever your connection allows, so use credentials that reach only the data you want analysed. You are responsible for your devices and for the data the app keeps on them, which we do not hold.
3.6 Preview features. A feature we label beta, preview, early access, experimental or similar is a preview feature. It may change or end at any time, may be less reliable, and is provided as it is. Our data commitments in Section 9 and the DPA still apply to it, and any vendor that processes Customer Content for it is on our sub-processor list.
3.7 Feature settings and terms. Some features come with their own settings, limits or additional terms, which we show when you turn the feature on, describe in our help center, or set out in our Plans, credits and billing terms, Current limits and settings, Connections and integrations or Demo terms page. They form part of these Terms for that feature. They cannot reduce our commitments in Section 9 or the DPA, and they work within the maximum periods and other limits these Terms, the Privacy Policy and the DPA set. If we add a feature with its own terms after you sign up, the terms in effect when you first use it apply to it, and later changes to them follow Section 20. For that feature, its own terms take precedence over these Terms where they differ, after any Order Form, and the DPA still prevails on data protection (Section 1.5).
3.8 Limits. We may set reasonable limits, such as on usage, file sizes, storage or how often something runs, how much history a plan keeps, or how long an invitation or link stays valid, to keep the Service working well for everyone. Our Current limits and settings page and help center show the current limits.
3.9 Sharing and publishing. Some features let you share or publish Outputs or other content, for example by link. You choose what to share and with whom. Anyone you share it with, or who has the link, can see it. You are responsible for what you share, and we may remove shared content that breaches Section 7.
3.10 Apps from app stores. If you get one of our apps from an app store, such as Apple’s App Store or Google Play, the store’s terms also apply to that app and to anything you buy through the store. These Terms are between you and us, not the store, and the store is not responsible for the app or its support. Where a store’s terms require it, that store may enforce these Terms for its app.
3.11 Work the Service does for you. Where you or your account set it up, the Service may do work without you asking each time, such as running a question on a schedule, refreshing connected data or sending you a summary, or let an agent you set up work through a task. It handles that work as it handles a question you ask, under Section 9.
3.12 What the Service does with your data. On your instructions, which include your account’s settings, your Users’ use of its features and work set up under Section 3.11, the Service may collect, receive, read, sync, store, organise, transform, query, analyse, model, summarise, generate from, answer about, publish, share, export and send your Customer Content, and notify you about it through channels such as email, the product, or a Connected System you choose. It acts in a Connected System, for example by writing, posting or changing something there, only where a feature you turn on says it does so, and only within the permission you give. Each feature does only some of these things; our help center describes what each does. Section 9 and the DPA apply to all of it.
3.13 Actions in Connected Systems. Where the Service acts in a Connected System or on your own systems at your request, for example by writing, changing, deploying, running code or restarting something, the action may be wrong, partial or of an unknown outcome. You approve what the Service does, you choose the permissions you grant, and you are responsible for the results. Some plans let you require approval before an action runs and let an admin decide which tools or commands may run without it. Where your plan includes these controls, how you set them is up to you. Approval steps, allow-lists and run modes are best-effort guard rails, not a security boundary, so keep the permissions you grant to what the work needs and keep a way to undo changes, such as version control or backups. You alone are responsible for actions and commands you set to run without approval. We are not liable for the outcome of an action you approved, or that you set to run without approval, except as Section 14 otherwise says.
3.14 Credentials, code and work the Service generates. Credentials we hold for you are kept encrypted, used only for the connection they were given for, and you may revoke them at any time. You are responsible for rotating credentials on your own systems. Code and other work the Service generates for you are Outputs, which belong to you (Section 5). Where the Service runs code from a repository or tool you point it at, it does so on your instruction.
3.15 Servers, tools and APIs you add. We do not check the servers, tools and APIs you add to the Service. What comes back from them may contain instructions meant to steer the AI. You decide which ones to trust, and what you let them do.
3.16 AI models and providers. To run the Service, we may choose, add, change, remove or route between AI models and AI model providers, routers and gateways, and reach them directly or through a cloud platform. Which model handles a request may vary. Where we choose the provider, router or gateway, it is our Sub-processor: it is on our sub-processor list, bound as Section 10 describes, including by our no-training promise in Section 9.2. Where you choose one yourself, for example by connecting your own account or key with an AI model provider or router, it is a Connected System: we send it what your instructions need, under your agreement with that provider, and it is not our Sub-processor.
4. Fees and payment
4.1 What you pay for. Your plan sets what you pay for. Fees may be based on Answered Questions (questions submitted to the Service that return an answer, excluding errors and clarification turns), subscriptions, seats, usage allowances, credits, balances or other measures, as shown on our pricing page or in your Order Form. Credits and balances are units or amounts you buy, are given or earn and then use up on the Service; they are not money, and they may expire. Credits you buy last at least 12 months from the day you buy them. Credits we give you, such as for a trial, a pilot or a promotion, or that you earn, expire as shown when we give them. We always show the expiry before you buy credits or when we give them.
4.2 Plans, billing and no refunds. Your plan, prices, billing cycle and currency are set in your Order Form or online checkout. How plans, credits, balances, top-ups, renewals and non-payment work is set out in our Plans, credits and billing terms. Unless an Order Form says otherwise, you pay in advance. Fees, credits and balances are not refundable, including when you change plan or close your account, except where the law requires (for example Section 23.6), where Section 20.3 gives a refund of unused prepaid subscription time, or where an Order Form says otherwise. Credits and balances are never refunded.
4.3 Taxes. Fees do not include taxes. You pay applicable taxes, such as GST, other than taxes on our income. If you must withhold tax by law, tell us, and we will work with you on the paperwork so that we receive the full fee or you provide a valid withholding certificate.
4.4 Non-payment. Overdue amounts may carry interest at 1% per month, or the maximum the law allows if lower. If a payment fails or an undisputed amount is not paid when due, or a balance runs out, we will tell you. If it stays unpaid for at least 7 days after that notice, we may limit or suspend the Service under Section 16, and if it stays unpaid after a further notice, close the account. Our Plans, credits and billing terms describe how this currently works.
4.5 Disputed invoices. Tell us about a disputed charge in good faith within 30 days of the invoice date. You must pay the undisputed part on time while we resolve it together.
4.6 Free trials and free plans. A free plan never turns into a paid subscription unless you choose to upgrade. These Terms apply in full to free trials and free plans, including every data commitment in Section 9. If a free trial ends without moving to a paid plan, we treat that as the end of your agreement for the purposes of Section 16.5.
4.7 Renewal and price changes. Unless your Order Form says otherwise, plans renew automatically for the same term unless you cancel before renewal, and renewals may be collected by your payment method’s standing instruction, under the payment provider’s and your bank’s rules. We will give you at least 30 days’ notice of a price increase, which applies from your next renewal. You may cancel before it applies.
5. Ownership and licences
5.1 You own your Customer Content. As between you and us, you own your Customer Content, including Outputs. To the extent we have any rights in Outputs, we assign them to you. Outputs may not be unique, and the Service may produce similar Outputs for other customers.
5.2 Your licence to us. You give us a non-exclusive, worldwide licence to host, copy, process and display Customer Content only to provide, secure and support the Service for you, as these Terms and the DPA describe.
5.3 We own the Service. We own the Service and all related technology, software, models and materials, and we own Usage Data. We control Account Data and handle it as our Privacy Policy describes. We grant you a non-exclusive, non-transferable right to use the Service during your subscription, under these Terms. We reserve all rights we do not expressly grant. BumbleB Crunch™ and the BumbleB Technologies name and logo are trademarks of BumbleB Technologies Pvt Ltd; these Terms give you no right to use them.
5.4 Feedback. Feedback means suggestions and ideas about the Service that you or your Users give us. You give us a perpetual, irrevocable, worldwide, royalty-free licence to use Feedback for any purpose, without obligation to you. Feedback does not include Customer Content. A Submitted Conversation is not Feedback and is covered only by Section 9.4.
6. Your responsibilities
6.1 You control your Customer Content. For Customer Content, you are the controller (under the GDPR), the Data Fiduciary (under India’s Digital Personal Data Protection Act 2023) or the business (under US state privacy laws). We act as your processor or service provider, on your instructions, as set out in the DPA.
6.2 Lawful basis and notices. You are responsible for having a lawful basis, and all notices and consents required by law, for the Customer Content you give us or ask us to collect. This includes Visitor Data. You will not give us data you are not permitted to share.
6.3 Tracking tag, pixel, SDK and consent. You decide where our tracking tag, pixel or SDK is installed, what your systems send us, and how it is configured. You are responsible for:
- showing a compliant cookie or consent banner where the law requires one;
- getting valid consent for non-essential tracking where the law requires it; and
- telling your visitors, in your own privacy notice, that you use the Service.
We collect only what your configured tag, pixel or SDK, or your systems, send. We honour the consent signals the tag receives, including Global Privacy Control and “necessary only” choices, and we do not collect beyond what you have authorised.
6.4 Requests from your visitors. Your visitors’ requests to access, correct or delete their data are addressed to you, as their controller. We help you respond, as the DPA describes.
6.5 No properties directed at children. We do not onboard websites or apps directed at children. You confirm that no property you track with the Service is directed at children under 18. If we find that one is, we will stop collecting data from it, delete the data collected from it, and may end the Service for that property without liability.
6.6 Sensitive uses. Do not present Outputs to others as professional legal, medical, financial or tax advice without your own review and disclaimers.
7. Acceptable use
7.1 You must not, and must not allow anyone else to:
- use the Service in breach of any law or anyone’s rights;
- upload malware, or content you have no right to share;
- reverse-engineer, decompile or try to extract the source code, models or prompts behind the Service, except where the law allows it despite this restriction;
- use the Service or its Outputs to build, train or improve a competing analytics or AI product;
- resell, sublicense or share access to the Service without our written consent;
- try to access other customers’ accounts or data, or circumvent security, rate or usage limits;
- use the Service to track a property directed at children (Section 6.5); or
- use the Service as a factor in a decision that has legal or similarly significant effects on an individual (Section 8.3).
7.2 If we find a breach, we may remove the offending content or suspend the affected account or property under Section 16.
8. Outputs are conclusions, not decisions
8.1 AI can be wrong. The Service produces Outputs using AI, including large language models. Outputs are probabilistic. They may be inaccurate, incomplete or out of date, and the same question may produce different answers. An AI assistant you connect may also restate an Output differently from how BumbleB Crunch gave it (Section 3.4).
8.2 We deliver the conclusion; you make the decision. Outputs support your judgment; they do not replace it. Review Outputs, including the supporting charts and tables, before you rely on them, publish them or act on them. Outputs are not legal, medical, financial, tax or regulatory advice.
8.3 No automated decisions about people. The Service does not make automated decisions that have legal or similarly significant effects on any individual, and you must not use it to do so. Outputs are conclusions for a person to consider. The Service is not designed to be a substantial factor in a consequential decision about a person, such as one about employment, education, healthcare, housing, insurance, credit or access to government services.
8.4 No profiles of individuals. We do not build profiles of your website visitors or of other individuals in your data, for ourselves or for anyone else. Analysis you ask for about people in your own data, such as which of your customers are most active, is done for you, on your instructions. The Service may remember a User’s own settings, preferences and saved work, and personalise features that User turns on, for that User only.
9. Your data and how we use it
9.1 Three kinds of data. We keep three kinds of data apart:
| Customer Content | Account Data | Usage Data | |
|---|---|---|---|
| What it is | Inputs, Outputs and Visitor Data. | Who you are and how you use your account. | Our identity-free record of how the Service ran. |
| Who controls it | You | Us | Us |
| What we use it for | Delivering the Service, keeping it secure, and support you ask for | Running and billing your account, security, customer success and communications | Operating, securing, measuring and improving the Service |
Inputs means what you or your Users type, say, upload or connect, and what the Service receives from or reads in your Connected Systems. Outputs means what the Service writes back or makes for you: answers, explanations, charts, tables, generated queries, and things such as dashboards, documents, sheets and slides. Visitor Data means 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. Our sales and customer-success teams see Account Data only: which features your account uses and how much, never what was asked or answered. We do not sell or share Customer Content.
9.2 Our promises. These promises apply to every customer, on every plan, in every country.
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.
9.3 How we learn from Usage Data. Improving the Service includes training our own service components, such as the part that decides which tool to call. Usage Data is the only data derived from Customer Content that we use to train anything. We never sell or share Usage Data. Automated processes may re-check conversations within their 90-day retention period; they record labels only, and no person reads the conversations. Individual users in India are asked first, for both Usage Data and re-checks.
9.4 Submitted Conversations. A Submitted Conversation is a conversation a user chooses to send us, for example using “Report a bug”. Before it is sent, the user is shown how we will use it. When a user sends one, our team may read it and use it to improve the Service, including to train our models. We mask Visitor Data in it before anyone reads it. A user can withdraw a Submitted Conversation at any time, and we then delete it and remove it from future improvement work; a model already trained using it is not retrained. Admin control: some plans let a company admin turn off Submitted Conversations for the whole workspace. Where your plan includes this control and it is off, no user in that workspace can send one. Our pricing page or your Order Form shows which plans include it and how it is set by default.
9.5 Support access. When you ask for help, our support staff may read the relevant Customer Content in place, against a logged support ticket. We do not copy what they read into Usage Data, evaluation sets or training data.
9.6 How long we keep data.
| Data | Kept for |
|---|---|
| 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 |
| Backup copies of conversations | Deleted on the backup schedule shown on the same page |
| Account Data | While your account is open, then as long as the law requires |
| Records of who accessed what (no content) | As long as needed for security and to meet the law; the current period is on the same page |
| Submitted Conversations | Until withdrawn, and no longer than the period on the same page |
| Visitor Data, uploaded files and connected data | While your agreement runs, or until you delete them or disconnect the source and choose to delete it |
| Other content you create, save, share or publish | Until you delete it, or while your agreement runs |
| Prompts held by AI model providers, routers and gateways we choose | As shown for each one on our sub-processor list, which also says whether zero data retention is on and any exception, such as for abuse monitoring. None may use them to train any model |
Where we say we delete Customer Content, that includes the copies, caches and summaries we made from it; backups follow their own schedule. These are the longest periods. We may keep data for less, and our Current limits and settings page shows the current periods within them. We keep data longer only when the law requires it, for example tax records or during a legal dispute. Section 16.5 explains what happens to Customer Content when your agreement ends. Usage Data is not deleted with your account, because it identifies no one.
9.7 Where to find the detail. The DPA sets out our processing terms in full. The Privacy Policy covers Account Data and individual rights. The How we use your data page explains all of this in plain language.
10. Sub-processors
10.1 Who we use. Sub-processor means a third party we engage to process Customer Content on your behalf to deliver the Service. They include, for example, hosting and cloud providers, AI model providers, routers and gateways (reached directly or through a cloud platform), search providers, and providers that deliver, secure or support the Service. Where a Sub-processor passes requests on to other providers, such as a model router to the model providers it works with, those providers are part of that Sub-processor’s chain, bound in the same way, and shown on the list. Our sub-processor list names each one, what it does, where it processes data and, for AI model providers, routers and gateways, how long each keeps prompts, whether zero retention is on and any exception it keeps, such as for abuse monitoring. AI model providers or routers you connect with your own account or key are Connected Systems, not Sub-processors (Section 3.16).
10.2 Same rules, passed down. Each Sub-processor is bound by written data-protection terms consistent with the protections in the DPA, including no training on Customer Content (Section 9.2), confidentiality, security, and prompt breach notice that lets us meet our own 24-hour commitment in Section 12.4. We remain responsible for their performance.
10.3 New Sub-processors. You authorise us to engage the Sub-processors on our list. Before we add or replace one, we update the list and notify subscribers at least 15 days before it starts processing Customer Content. You can subscribe to the list to receive notice by email. You may object on reasonable data-protection grounds. If we cannot resolve your objection, you may end the affected Service, and we will not charge you for it again. In an emergency, that is a security incident or a sub-processor suddenly being unable to provide its service, we may replace it sooner. We will then give notice promptly and in any case within 5 business days, and your right to object still applies.
10.4 Where we host. We currently host in the region our sub-processor list shows. We may host or process data in other regions, or with other providers on the list; a new region or provider is added to the list under Section 10.3. Transfers between countries are made under the safeguards the Privacy Policy and the DPA describe.
11. Confidentiality
11.1 What is confidential. Confidential Information is non-public information one party discloses to the other that is marked confidential or that a reasonable person would treat as confidential. Your Customer Content is your Confidential Information.
11.2 How we each protect it. Each party will use the other’s Confidential Information only to perform under these Terms, protect it with at least reasonable care, and share it only with people who need to know it and are bound by similar duties.
11.3 Exceptions. These duties do not apply to information that is or becomes public through no fault of the recipient, was already known to the recipient, is independently developed, or is rightfully received from someone else. A party may disclose Confidential Information where the law requires, after giving the other party notice where the law allows.
11.4 How long. These duties last for 3 years after your agreement ends, and for trade secrets for as long as they remain trade secrets.
12. Security
12.1 Our safeguards. We maintain technical and organisational security measures, including encryption in transit (TLS 1.2 or higher) and at rest (AES-256 or equivalent), role-based access and least privilege, logging and monitoring, secure development, vulnerability management, security testing and staff training. The DPA describes them in more detail.
12.2 Certifications. We do not currently hold SOC 2 or ISO 27001 certification. On reasonable request, once a year, we will share evidence of our security practices.
12.3 Staff access. Access to your sessions is limited to named support, on-call and security staff, tied to a ticket or incident, logged and time-limited. On request, we will tell you whether your sessions were accessed and under which ticket.
12.4 Security incidents. If we become aware of a breach affecting Customer Content, we will tell you without undue delay and within 48 hours of becoming aware. We will tell you what happened, what data is affected, the likely consequences and what we are doing about it, so you can meet your own legal deadlines.
12.5 Your part. You are responsible for securing your own systems, your Users’ credentials and the configuration of your tracking tag, pixel or SDK, and the access your connections grant.
13. Warranties and disclaimers
13.1 What we promise. We will provide the Service with reasonable skill and care, in line with the documentation and these Terms. If the Service does not meet this promise, tell us and we will use reasonable efforts to fix it. If we cannot, either of us may end the affected plan, and we will not charge you for it again.
13.2 What each party promises. Each party confirms that it has the authority to enter into these Terms and will comply with the laws that apply to it in performing them.
13.3 Disclaimer. EXCEPT AS SET OUT IN THESE TERMS, THE SERVICE AND OUTPUTS ARE PROVIDED “AS IS”. TO THE EXTENT THE LAW ALLOWS, WE DISCLAIM ALL OTHER WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT AND ACCURACY OF OUTPUTS, AND WE DO NOT PROMISE THAT THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE.
14. Limitation of liability
14.1 No indirect losses. Neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue or data, arising from these Terms, even if told they were possible.
14.2 Liability cap. EACH PARTY’S TOTAL LIABILITY ARISING FROM THESE TERMS IS LIMITED TO THE GREATER OF (A) THE FEES YOU PAID OR OWE US IN THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM AND (B) US$100.
14.3 Higher cap. For breach of Section 9 (Your data and how we use it), Section 11 (Confidentiality) or the DPA, and for our obligations under Section 15.2 (IP indemnity), the cap in Section 14.2 is doubled. An Order Form may set a different cap.
14.4 What is not limited. Sections 14.1 to 14.3 do not limit liability for gross negligence, wilful misconduct or fraud, your obligation to pay fees, or any liability that the law does not allow us to limit.
15. Indemnities
15.1 Your indemnity. You will defend us against third-party claims, and pay resulting damages and reasonable costs, arising from your Customer Content, your failure to give notices or obtain consents required under Section 6, your use of the Service in breach of these Terms, or your breach of law or third-party rights.
15.2 Our IP indemnity. We will defend you against a third-party claim that your paid use of the Service, as we provide it, infringes that third party’s intellectual property rights, and pay resulting damages and reasonable costs. This does not cover claims arising from your Customer Content, your changes to the Service, or its combination with products we did not provide. If a claim is made or likely, we may get you the right to keep using the Service, change it so it no longer infringes, or, if neither is reasonably possible, end the affected Service, and we will not charge you for it again.
15.3 How claims are handled. The party seeking protection must tell the other party promptly, let it control the defence and settlement, and give reasonable help. No settlement may admit fault for, or impose obligations on, the protected party without its consent.
16. Suspension and termination
16.1 Term. Your agreement starts when you accept these Terms and continues for the subscription term in your Order Form or online checkout. Unless your Order Form says otherwise, subscriptions renew automatically for the same term unless either party gives notice before renewal.
16.2 Ending for convenience. You may close your account at any time. Fees, credits and balances are not refunded, and unused credits and balances end with the account, except where the law requires or your Order Form says otherwise.
16.3 Ending for breach. Either party may end the agreement if the other materially breaches it and does not fix the breach within 30 days of written notice.
16.4 Suspension. We may suspend all or part of the Service if it is needed to deal with a security risk, if an amount stays unpaid after notice under Section 4.4, or if you breach Section 7. We will give notice first where we reasonably can, limit the suspension to what is needed, and restore the Service promptly once the issue is resolved.
16.5 Your Customer Content when your agreement ends. For at least 30 days after your agreement ends, you may export your Customer Content, through the Service or by asking us. After that, we delete it from our active systems within 30 days, and from backups within 90 days. On request, we will confirm deletion in writing. Deleting Customer Content includes the copies, caches and summaries we made from it; backups follow their own schedule above. Account Data is kept only for as long as the law requires. Usage Data is kept, as Section 9.6 explains. Closing an account may include a short period in which you can change your mind, as our Current limits and settings page shows; it never shortens the export period.
16.6 Ending a free plan or free trial. We may end a free plan or free trial by giving you 30 days’ notice, or immediately if you breach these Terms or abuse the Service.
16.7 Survival. Sections 4 (for unpaid fees), 5, 8, 9, 11, 13, 14, 15, 16.5, 19, 21, 23 and 24 survive the end of your agreement.
17. Force majeure
Neither party is liable for delay or failure to perform caused by events beyond its reasonable control, such as natural disasters, war, terrorism, civil unrest, government action, widespread internet or power failures, or failures of third-party hosting not caused by that party. This does not excuse payment obligations. If such an event stops the Service for more than 30 days, either party may end the affected plan, and we will not charge you for it again.
18. Export controls and sanctions
You confirm that neither you nor any of your Users is the target of sanctions that apply to us or to you, or located in a country or region subject to comprehensive sanctions. You will not use the Service in breach of export-control or sanctions laws.
19. Governing law and disputes
19.1 Governing law. These Terms are governed by the laws of India.
19.2 Talk first. If a dispute arises, each party will try in good faith to resolve it through senior representatives for 30 days before starting arbitration.
19.3 Arbitration. Any dispute arising from or relating to these Terms that is not resolved under Section 19.2 will be finally resolved by arbitration administered by the Mumbai Centre for International Arbitration (MCIA) under its arbitration rules in force when the arbitration starts, and under the Arbitration and Conciliation Act 1996. The seat of arbitration is Bengaluru, India. The tribunal will be a sole arbitrator appointed under those rules. The arbitration will be conducted in English.
19.4 Courts. The courts of Bengaluru, Karnataka have exclusive jurisdiction over applications for interim relief and any matter that cannot be arbitrated. Either party may seek urgent interim relief there at any time.
19.5 Your Order Form may differ. An Order Form may name a different BumbleB Technologies entity and select a different governing law and forum, as Section 1.5 explains.
19.6 Rights that cannot be waived. Nothing in these Terms takes away any right you or your Users have under mandatory consumer-protection or data-protection laws that apply to you, whatever law governs these Terms.
20. Changes to these Terms
20.1 Material changes. A change is material if it reduces your rights, increases your obligations or expands how we use your data. We will give you at least 30 days’ notice of a material change by email and in the product before it takes effect. The notice will say what is changing and when.
20.2 Other changes. We may make changes that are not material, such as clarifications or adding terms for a new country, by publishing a new version with a change log entry. These take effect on the effective date shown in the new version, which is never earlier than the day we publish it. Changes to the Service itself, including its features, settings and limits, and changes to our pricing page, help center, feature terms under Section 3.7, our Plans, credits and billing terms or our Current limits and settings, Connections and integrations or Demo terms page, are not changes to these Terms and need no new version. That includes adding a feature, an app, a way to reach the Service, a kind of Connected System, a kind of data, or an AI model that works within these Terms, the Privacy Policy and the DPA. A new Sub-processor, model provider or hosting region is added as Section 10 describes. Those pages stay within these Terms, the Privacy Policy and the DPA. Where a change to one of them would materially reduce your rights, we give you notice as Section 20.1 describes before it applies to you. We keep earlier versions of those pages available, and each shows a “last updated” date. Section 3.3 covers removing a feature from a paid plan.
20.3 If you do not agree. If you do not agree to a material change, you may end your agreement before the change takes effect, and we will not charge you again. If you do, we refund the part of any prepaid subscription period that is unused when your agreement ends. Credits and balances are never refunded. Apart from this, fees already paid are not refunded, except where the law requires.
20.4 Order Form customers. If you have an Order Form, you stay on the version of these Terms it refers to until your next renewal, unless you accept a newer version earlier. Changes to our Sub-processors follow Section 10.3 whichever version you are on.
20.5 Versions. Each version shows its effective date and last-updated date. Previous versions are archived and linked from the top of this page.
20.6 Changes the law requires, and past disputes. Where the law or a regulator requires a change, it may take effect sooner than Section 20.1 allows; we tell you as soon as we reasonably can. A change never applies to a dispute that arose before it took effect.
21. General
21.1 Entire agreement. These Terms, your Order Form and the DPA are the whole agreement between us about the Service. They replace earlier discussions and proposals. Terms in your purchase order or similar document do not apply, even if we accept the order.
21.2 Assignment. Neither party may transfer these Terms without the other’s written consent, except to an affiliate or to a successor in a merger, acquisition or sale of substantially all of its relevant business or assets, with notice to the other party.
21.3 Notices. We send notices to the email address on your account. You send legal notices to legal@bumbleb.co. A notice is received when sent, unless the sender receives a delivery failure.
21.4 Independent parties. We are independent contractors. These Terms do not create a partnership, agency or employment relationship.
21.5 No waiver, severability. Not enforcing a term is not a waiver of it. If a court or tribunal finds a term unenforceable, the rest of these Terms still apply, and that term is applied as far as the law allows.
21.6 Publicity. We will not use your name or logo in our marketing without your consent.
21.7 Language. These Terms are written in English. If we provide a translation, the English version applies if they differ, unless the law requires otherwise.
21.8 No third-party beneficiaries. Only you and we have rights under these Terms. No one else may enforce them, except an app store as Section 3.10 allows.
21.9 Electronic acceptance and counterparts. These Terms and any Order Form may be accepted or signed electronically, and an Order Form may be signed in counterparts, which together form one document.
22. Contact us
- Legal — legal@bumbleb.co
- Privacy — privacy@bumbleb.co
- Security — security@bumbleb.co
- India Grievance Officer — Chinmaya Reddy, grievance@bumbleb.co. We resolve grievances within one month, and we support nomination of another person to act for you.
BumbleB Technologies Pvt Ltd, 581, Second Floor, 1st Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India.
23. Personal use
23.1 Who this applies to. This Section applies if you use the Service as an individual, mainly for purposes outside your trade, business or profession ("personal use"). Where it differs from the rest of these Terms, this Section wins.
23.2 Your legal rights. Consumer laws where you live may give you rights that these Terms cannot take away. Nothing in these Terms limits them.
23.3 Liability and indemnity. Sections 14 and 15.1 apply to you only as far as the law where you live allows.
23.4 Disputes. You may bring a claim in the courts, or before the consumer commission or forum, where you live. Section 19.3 (arbitration) applies to you only if you choose it.
23.5 Paid plans. Before you pay, we show you the price, what is included, how often you will be charged and how to cancel. You can cancel at any time from your account; your plan then runs to the end of the period you paid for, and you are not charged again.
23.6 Cancelling within 14 days. Where the law where you live gives you a right to cancel a new paid plan within 14 days, such as in the EU and the UK, you can do so and get the refund that law gives you. If you ask us to start the plan within those 14 days, we may deduct a fair amount for what you used, as that law allows.
23.7 Your data. If you use the Service only for personal or household purposes, data protection laws may not treat you as a controller. Section 6 and the DPA then apply to you only as far as those laws do. The Privacy Policy explains how we handle your own personal data.
24. Glossary
| Term | Meaning |
|---|---|
| Account Data | Who you are and how you use your account. |
| Balance | An amount held in an account or organisation wallet and used up on the Service. It is not money and is not refundable, except where the law requires (Section 4). |
| Answered Question | A question submitted to the Service that returns an answer, excluding errors and clarification turns, where your plan charges for them. |
| Credits | Units you buy, are given or earn and use up on the Service. Credits you buy last at least 12 months from purchase; credits we give or you earn expire as shown when given (Section 4). |
| Current limits and settings | Our page showing current limits and periods within the maximums in these Terms, the Privacy Policy and the DPA. |
| Confidential Information | Non-public information one party discloses to the other that is marked confidential or that a reasonable person would treat as confidential, as Section 11.1 describes. |
| Connected Systems | The systems you or your Users connect to the Service, point it at, or tell it to read from, receive from or act on, by any method the Service offers (Section 3.4). |
| Connections and integrations | Our page listing the kinds of Connected Systems we currently support, what the Service reads from each and whether it can act there. |
| Customer Content | Inputs, Outputs and Visitor Data. |
| DPA | Our Data Processing Agreement, which applies to every customer, paid or free, and is incorporated into these Terms by reference. |
| Enterprise plan | A plan sold under an Order Form designated Enterprise. |
| Feedback | Suggestions and ideas about the Service that you or your Users give us. |
| Inputs | What you or your Users type, say, upload or connect, and what the Service receives from or reads in your Connected Systems. |
| Plans, credits and billing terms | Our page setting out how plans, credits, balances, top-ups, renewals and non-payment work. |
| Order Form | A signed order form or other ordering document that you and we agree to and that refers to these Terms. |
| Outputs | What the Service writes back or makes for you: answers, explanations, charts, tables, generated queries, and things such as dashboards, documents, sheets and slides. |
| Privacy Policy | Our Privacy Policy, which explains how we handle personal data as a controller. |
| Service | The software, apps, agents, APIs, connectors, integrations, interfaces, tools and other products and services BumbleB Technologies provides under these Terms, now or later, however you reach them, including BumbleB Crunch™, our tracking tag, pixel and SDKs, and their documentation (Section 1.2). |
| Submitted Conversation | A conversation a user chooses to send us, for example using “Report a bug”. |
| Sub-processor | A third party we engage to process Customer Content on your behalf to deliver the Service. |
| Usage Data | Our identity-free record of how the Service ran. |
| Users | The individuals you allow to use the Service under your account. |
| Visitor Data | 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, an approximate location derived from their IP address, and session recordings where you turn them on. |
| Personal use | Use of the Service by an individual, mainly for purposes outside their trade, business or profession (Section 23). |