Privacy Policy
BlueB Privacy Policy
Version 2.0
Effective date: 16 September 2026
Last reviewed: 16 September 2026
This Privacy Policy explains how BLUEB TECH UK LTD (BlueB, we, us or our) collects and uses personal data when you visit blueb.ai or a related BlueB website, join our waitlist, create or use a BlueB account, use BlueB Chat, BlueB ERP or another BlueB application, communicate with us, or receive our messages (together, the Service).
It also explains the difference between personal data we use for our own purposes and business data that we process for a customer.
1. Who We Are
BLUEB TECH UK LTD is a private limited company incorporated in England and Wales.
Company number: 15522090
Registered office: 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ
ICO registration: ZB782232
Privacy and data-rights contact: info@blueb.ai
General contact: info@blueb.ai
For account, website, waitlist, marketing, security and service-administration data, BlueB is generally the controller, meaning we decide why and how that personal data is used.
When a business customer submits personal data about its employees, customers, suppliers or other people to BlueB for processing within its workspace, chat, ERP records, integrations or files (Customer Data), the customer is generally the controller and BlueB is its processor. In that case, the customer’s privacy notice governs its use of the data, and BlueB processes it under the customer’s instructions and the Data Processing Terms in the BlueB Terms of Use or a separate data processing agreement. Requests concerning Customer Data should normally be directed to the relevant customer.
2. Scope
This Policy applies to personal data processed through the Service and our related business interactions. It does not govern a third-party website, application, integration or service that has its own privacy policy, even if it connects to BlueB.
The Service is designed for business users aged 18 or over. It is not directed to children.
3. Personal Data We Collect
The personal data we collect depends on how you interact with BlueB, the features you use, your organisation’s configuration and the information you choose to provide.
3.1 Waitlist and onboarding data
We may collect your name, business name, role, email address, WhatsApp-enabled telephone number, country, preferred language, industry, business size, business needs, referral source, consent choices and onboarding responses.
3.2 Account and profile data
We may collect your name, profile name, telephone number, email address, business and job information, account role, permissions, language, time zone, currency, country, settings, linked organisation, and records of agreement to our terms and policies.
3.3 WhatsApp, login and authentication data
Where you sign in, verify your identity or communicate through WhatsApp, we may process:
- your telephone number and country code;
- WhatsApp profile name and platform identifiers;
- OTP request, issue, delivery, expiry and verification records;
- message content, voice notes, images, documents and other attachments you send;
- message timestamps, delivery, read, failure and status information;
- opt-in, opt-out and communication-preference records; and
- security information such as IP address, device, session and risk signals.
Meta and WhatsApp also process information under their own terms and privacy notices. You should not send confidential or sensitive information through WhatsApp unless it is necessary and appropriate for your business and you are authorised to do so.
3.4 Chat, files and business content
We process prompts, messages, instructions, conversation history, files, photographs, camera uploads, voice recordings, transcriptions, PDFs and other content you submit. Depending on your use, this may include customer and supplier details, invoices, receipts, products, transactions, journal entries, notes, tasks, approvals, reports and other business information.
This information may contain personal data about people who do not directly use BlueB. The customer that submits it is responsible for having a lawful basis and providing any required privacy information.
3.5 ERP and integration data
If you connect an ERP, accounting platform or another integration, we may process connection identifiers and tokens, configuration details, company records, account structures, customers, suppliers, invoices, sales, purchases, payments, stock, journal entries, reports and related metadata, to the extent selected or required by the integration.
We do not ask you to place passwords or private keys in ordinary chat. Connection credentials should be entered only through designated secure methods.
3.6 AI inputs, outputs and inferences
We process the inputs you submit, relevant conversation or business context, tool results, generated responses, confidence or routing information, confirmation status and feedback. The Service may infer intent, business categories, entities, proposed actions or operational insights from the information provided.
BlueB does not use Customer Data to train a general-purpose AI model for other customers without the customer’s explicit opt-in. We may use de-identified or aggregated data that does not identify a person or customer to evaluate reliability, security, usage and performance and to improve the Service, as permitted by law.
3.7 Billing and transaction data
For paid services, we may collect billing name and address, business and tax identifiers, subscription, invoice, currency, payment status and transaction-reference information. Payment-card details are processed by our payment provider, such as Stripe; BlueB does not ordinarily receive or store the full card number or card security code.
3.8 Device, usage and diagnostic data
We may collect IP address, approximate location derived from IP, browser and device type, operating system, app version, language, time zone, session identifiers, pages and features used, request and response times, crash reports, error logs, security events, rate-limit events and performance data.
The BlueB application may also store some conversation or application data locally on your device. Local data remains subject to your device security, backup and deletion settings.
3.9 Support and communications data
We collect messages, emails, call or meeting details, support requests, attachments, troubleshooting information, survey responses and feedback. If a call or meeting will be recorded, we will provide appropriate notice and obtain consent where required.
3.10 Marketing and preference data
We may collect your marketing choices, the date, wording and source of consent, campaign and delivery information, whether you opened or interacted with a message where lawful, event or webinar registration, and unsubscribe or objection records.
3.11 Cookies and similar technologies
Our websites and web applications may use strictly necessary cookies or local storage for authentication, security, language, load balancing and session continuity. If we use analytics, advertising or other non-essential technologies, we will provide information and obtain consent where required before activating them. See section 12.
3.12 Information from other sources
We may receive information from:
- the organisation that creates or manages your account;
- Authorised Users who invite or mention you;
- Meta, WhatsApp and communications providers;
- payment, email, hosting, security and integration providers;
- ERP or business systems you choose to connect;
- public business registers, websites and professional profiles;
- referral partners where lawful; and
- authorities, advisers or other parties where required or permitted by law.
4. Special Category and Sensitive Data
BlueB does not require special-category personal data for ordinary use. Depending on what customers upload, Customer Data may nevertheless contain health, biometric, religious, political, trade-union, sexual-orientation, racial or ethnic information, or data about criminal allegations or convictions.
Do not submit such data unless it is necessary, lawful and appropriate, and your organisation has identified both a lawful basis and any additional legal condition required. BlueB processes it as a processor under customer instructions unless we clearly state another role.
The Service is not designed for full payment-card data, passwords, private encryption keys, state secrets, or data subject to a sector-specific regime that requires safeguards we have not expressly agreed to provide.
5. How and Why We Use Personal Data
We use personal data only where we have a lawful basis. The lawful basis depends on the purpose and context.
| Purpose | Typical data | UK GDPR lawful basis |
|---|---|---|
| Manage the waitlist and respond to requests | Contact, business and onboarding data | Legitimate interests in preparing and offering the Service; steps requested before a contract; consent where required |
| Create, authenticate and administer accounts | Identity, account, WhatsApp number, OTP and session data | Performance of a contract; legitimate interests in secure account administration |
| Provide chat, ERP, automation, reporting and integrations | Account, Customer Data, inputs, outputs and integration data | Performance of a contract for data about the user; legitimate interests; processor instructions for Customer Data |
| Generate AI-assisted responses and proposed actions | Prompts, context, business records, tool results and feedback | Performance of a contract; legitimate interests in providing and improving the requested feature; processor instructions where applicable |
| Deliver service messages | Telephone number, email, account and transaction status | Performance of a contract; legitimate interests; legal obligation where relevant |
| Process payments and maintain financial records | Billing, subscription, tax and transaction data | Performance of a contract; legal obligation; legitimate interests in revenue administration |
| Support users and troubleshoot | Contact, communications, account, device and diagnostic data | Performance of a contract; legitimate interests in support and service improvement |
| Secure the Service and prevent fraud or abuse | Account, device, IP, logs, content flags and risk signals | Legitimate interests in security, fraud prevention and protecting users; legal obligation where applicable |
| Monitor reliability and improve the Service | Usage, diagnostic, feedback and de-identified or aggregated data | Legitimate interests in quality, performance and product development; consent where required for non-essential tracking |
| Send marketing and invitations | Contact, preference and engagement data | Consent where required; limited legitimate interests or permitted customer exception where applicable |
| Comply with law and protect legal rights | Relevant account, transaction, content and communication data | Legal obligation; legitimate interests in establishing, exercising or defending claims |
| Corporate transactions | Relevant business, account and contractual data | Legitimate interests in corporate administration and transactions, subject to safeguards |
Where we rely on legitimate interests, we consider the necessity of the processing, its likely impact and reasonable expectations, and apply safeguards. You may object as described in section 15.
Where we rely on consent, you may withdraw it at any time. Withdrawal does not affect processing already carried out lawfully and does not prevent processing under another valid legal basis.
If we need personal data to enter into or perform a contract and you do not provide it, we may be unable to create or secure your account or provide the requested feature.
6. WhatsApp Login, Service Messages and Marketing
6.1 Login and service communications
When you request access, BlueB may use your telephone number to send an OTP through WhatsApp or another available channel. We may also send security alerts, account-readiness notices, support responses, transaction confirmations, approval requests, incident notices, billing information and other messages necessary to provide or protect the Service.
These are operational communications. They may be sent because they are necessary to perform the contract, respond to your request, meet a legal obligation or pursue our legitimate interests in secure service administration. You cannot opt out of essential operational messages while keeping the affected feature, although you can close your account.
6.2 Marketing consent
Marketing by WhatsApp, email, SMS or similar electronic message is separate from login and service messaging. Where consent is required, we ask through a clear, optional and unticked choice. We record the consent wording, channel, date, source and policy version. Declining marketing does not prevent account creation or Service use.
You can opt out at any time by using an unsubscribe link, changing available settings, replying with the stated opt-out word such as STOP, or contacting info@blueb.ai. We may retain a minimal suppression record so that we continue to respect your choice.
We do not sell contact lists or send marketing on behalf of unrelated businesses without a lawful basis and appropriate notice.
7. Artificial Intelligence Processing
BlueB may send a prompt, recent conversation context, relevant business records, instructions and tool results to an AI provider to generate a response, classification, extraction, summary, recommendation or proposed action. We aim to send only the information reasonably necessary for the requested function.
AI output can be inaccurate. Users are required to review material outputs and confirm important actions. BlueB is not intended to make solely automated decisions that have legal or similarly significant effects on individuals. If we introduce such processing, we will provide additional information and safeguards required by law, which may include human intervention, an opportunity to express a view and a way to contest the decision.
Authorised BlueB personnel may access limited conversation or account information where necessary for support, security, abuse investigation, quality review or legal compliance, subject to access controls and confidentiality.
8. When We Share Personal Data
We do not sell personal data. We do not share personal data for cross-context behavioural advertising.
We may disclose personal data to the following recipients when necessary:
8.1 Service providers and subprocessors
- Hosting and infrastructure providers, including Contabo-hosted environments, for servers, storage, databases and backups.
- Network and security providers, including Cloudflare, for DNS, content delivery, traffic protection, rate limiting and security.
- Communications providers, including Meta and WhatsApp, for OTP, messaging and WhatsApp-related features.
- AI providers, which may include OpenAI when an AI feature is used, for processing prompts and relevant context.
- Email providers, including Brevo, for account, support and marketing email delivery.
- Payment providers, including Stripe, for payment processing, fraud controls and billing.
- Support, monitoring, backup and professional-service providers where reasonably necessary to operate and protect the Service.
We use contracts and due diligence designed to require providers to protect personal data and use it only for authorised purposes. The exact provider may vary by feature and location. You may request current subprocessor information from info@blueb.ai.
ERP, and other self-hosted software components may be used within BlueB infrastructure. Their software authors do not necessarily receive personal data merely because we use that software.
8.2 Your organisation and connected users
Account administrators may access and control Authorised User details, roles, permissions, messages, business records, usage and activity within the organisation’s workspace. Other users may see information according to permissions and collaborative features.
8.3 Third-party integrations you enable
When you connect another service, we share the data needed to perform your instruction. The third party may process the data as an independent controller under its own privacy terms. Disconnecting an integration stops new exchanges but does not automatically delete data already received by that provider.
8.4 Legal, safety and professional disclosures
We may disclose information to courts, regulators, law-enforcement bodies, tax authorities, professional advisers, insurers or other parties where we reasonably believe disclosure is required by law, necessary to protect rights or safety, or needed to investigate fraud, abuse or a security incident.
8.5 Corporate transactions
We may disclose relevant information under confidentiality in connection with financing, due diligence, merger, acquisition, reorganisation, insolvency or sale of assets. A successor may use personal data only consistently with this Policy unless it provides legally required notice or obtains consent.
9. International Data Transfers
BlueB is established in the United Kingdom, and our providers and users may be located in the UK, European Economic Area, United States and other countries. Personal data may therefore be accessed or processed outside the country where it was collected.
When UK personal data is transferred to a country not covered by UK adequacy regulations, we use an applicable safeguard where required, such as the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, and carry out a transfer risk assessment where appropriate. For EEA data, we may use an EU adequacy decision or the EU Standard Contractual Clauses with supplementary measures where required.
Some transfers may rely on a legally recognised certification framework or a specific statutory exception where appropriate. You may contact info@blueb.ai for information about the relevant safeguards and how to obtain a copy, subject to protection of confidential information.
10. Retention
We keep personal data only for as long as reasonably necessary for the stated purposes, including providing the Service, meeting legal obligations, resolving disputes and enforcing agreements. Retention may vary if law, litigation, fraud prevention or a regulator requires a longer period.
Our normal retention schedule is:
| Data | Normal retention |
|---|---|
| Waitlist and pre-launch enquiries | Until converted to an account, withdrawn, or 24 months after the last meaningful interaction, whichever occurs first, unless a shorter period is required |
| Account and profile data | While the account is active, then ordinarily 30 days after closure or termination |
| Chat, files, ERP and Customer Data | During the service term and an export period of up to 30 days after termination, then deleted or anonymised |
| Protected backups | Automatically overwritten or purged within 90 days after deletion from active systems |
| OTP values | Until expiry or successful verification; short-lived values are not retained as reusable credentials |
| Authentication and security logs | Ordinarily up to 12 months, or longer where needed to investigate an incident, fraud or legal claim |
| Billing, invoice and tax records | Ordinarily 6 years after the end of the relevant financial year, or longer if law requires |
| Support records | Ordinarily up to 24 months after the issue is closed, unless needed for a continuing account, dispute or security matter |
| Marketing contact and engagement data | Until consent is withdrawn, an objection is made, or 24 months of inactivity, subject to applicable law |
| Suppression records | A minimal record for as long as reasonably necessary to honour an opt-out and demonstrate compliance |
We may retain de-identified or aggregated information that can no longer identify an individual. Data held as a processor is deleted or returned according to customer instructions and the applicable data processing agreement.
11. Security
We use technical and organisational measures designed to protect personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access. Depending on the system and risk, these measures may include:
- encryption in transit;
- secure token and credential handling;
- role-based or least-privilege access;
- tenant or logical separation;
- logging, monitoring and rate limiting;
- backups and recovery controls;
- vulnerability, patch and incident management;
- personnel confidentiality and access procedures; and
- supplier security and contractual controls.
No online service is completely secure. You must protect your device, WhatsApp account, email, OTPs and account access; use authorised connection methods; assign appropriate permissions; and notify us promptly of suspected compromise.
If a personal-data breach requires regulatory or individual notification, we will notify the relevant parties within the time and manner required by applicable law.
12. Cookies, Local Storage and Tracking
Strictly necessary technologies may be used without optional consent where permitted. They support login, authentication, security, fraud prevention, language, load balancing, preferences and core application functions.
We will not activate non-essential analytics, advertising or cross-site tracking technologies where consent is required until you choose to allow them. A consent control, where used, will let you accept, reject or change non-essential preferences. Rejecting non-essential technologies will not prevent core Service use, although optional features may be affected.
Cookie duration and provider information should be displayed in the consent interface or a cookie list when such technologies are deployed. Browser “Do Not Track” signals do not have a single legally binding technical standard. Where applicable, we recognise legally required opt-out preference signals, including Global Privacy Control for a covered sale, sharing or targeted-advertising activity. BlueB currently does not sell or share personal data for cross-context behavioural advertising.
13. Accuracy and Your Choices
You may update certain profile and business information in the Service. Please keep it accurate. If your organisation manages your account, contact its administrator for changes it controls.
You may disconnect integrations, remove permissions, close an account, withdraw marketing consent, object to certain processing or request deletion, subject to technical capability, your organisation’s instructions and legal retention requirements.
Deleting the BlueB app does not necessarily close your account or delete server-side data. Use the account-closure process or contact us.
14. Automated Decision-Making
BlueB uses automation to authenticate, route requests, detect abuse, extract data, generate suggestions and propose business actions. These functions ordinarily assist a user and do not make a solely automated decision that produces legal or similarly significant effects on an individual.
If that changes for a particular feature, we will provide meaningful information about the logic involved and the significance and likely consequences, and provide safeguards required by law. These may include the right to obtain human intervention, express your point of view and contest the decision.
15. Your Data Protection Rights
Depending on your location and our role, you may have rights to:
- obtain confirmation of whether we process your personal data and receive a copy;
- correct inaccurate or incomplete data;
- request deletion;
- restrict processing;
- receive certain data in a portable format and transmit it to another provider;
- object to processing based on legitimate interests or direct marketing;
- withdraw consent at any time;
- obtain safeguards relating to certain automated decisions; and
- complain to a data-protection authority.
These rights are not absolute. An exemption may apply, for example where retention is required by law, information would reveal another person’s rights, a request is manifestly unfounded or excessive, or BlueB processes data only under a customer’s instructions.
To exercise a right, email info@blueb.ai. Describe your request and the account, telephone number or email involved. We may ask for proportionate information to verify identity and authority. We will respond within the period required by applicable law. We do not charge a fee unless the law allows one.
If the request concerns data controlled by a BlueB business customer, we may refer it to that customer and assist it as processor.
16. Complaints
Please contact info@blueb.ai first so we can investigate. We will acknowledge and handle privacy complaints in accordance with applicable law.
You may complain to the UK Information Commissioner’s Office (ICO):
Information Commissioner’s Office
Wycliffe House
Water Lane
Wilmslow
Cheshire SK9 5AF
United Kingdom
Telephone: 0303 123 1113
Website: https://ico.org.uk/make-a-complaint/
If you live in the EEA, Switzerland or another jurisdiction with a local supervisory authority, you may also complain to that authority. We encourage you to contact us first, but you are not required to do so.
17. Children
The Service is intended for business users aged 18 or over. We do not knowingly create accounts for or market the Service to children. If you believe a child has provided personal data directly to BlueB, contact info@blueb.ai so we can investigate and take appropriate action.
Customers must not use the Service to process children’s data unless it is necessary for a lawful business purpose, the customer has a valid legal basis, all required notices and consents have been provided, and appropriate safeguards are in place. The ordinary Service is not designed for services directed at children.
18. Regional Privacy Information
The following provisions apply only where the relevant law applies. They supplement the rest of this Policy and do not reduce stronger rights.
18.1 European Economic Area and Switzerland
Where EU GDPR or Swiss data-protection law applies, references to UK GDPR rights include the corresponding local rights. BlueB relies on the legal bases in section 5 and transfer safeguards in section 9. You may contact your local supervisory authority.
If BlueB is required to appoint an EU or Swiss representative because of the nature and scale of its activities, representative details will be published before the relevant offering is made. The absence of a listed representative does not limit your rights.
18.2 California
For California residents and to the extent the California Consumer Privacy Act as amended (CCPA) applies, the categories collected in the preceding 12 months may include:
- identifiers, such as name, email, telephone number, IP address and account identifiers;
- customer-record and commercial information, such as company, subscription, invoices and transaction history;
- internet or electronic-network activity, such as device, usage and security logs;
- audio, visual or similar information, such as voice notes, images and uploaded files;
- professional or employment-related information;
- inferences derived from use, such as request intent or proposed business categories; and
- sensitive personal information only where submitted or required for authentication or an enabled feature, such as account-login credentials or message contents.
We collect these categories from you, your organisation, enabled integrations, providers and public business sources for the purposes described in section 5. We disclose them to the categories of recipients in section 8 for business purposes.
BlueB does not sell personal information or share it for cross-context behavioural advertising and has not done so in the preceding 12 months. We do not knowingly sell or share personal information of consumers under 16. We do not use or disclose sensitive personal information to infer characteristics or for purposes that trigger a right to limit under the CCPA.
Subject to applicability and exceptions, California residents may request access to categories and specific pieces of personal information, correction, deletion, and information about collection, disclosure, sale or sharing, and may exercise applicable opt-out rights without discrimination. An authorised agent may submit a request where legally permitted, subject to verification. Use info@blueb.ai.
18.3 Other United States states
Where an applicable US state privacy law grants rights, you may request access, correction, deletion or portability and may opt out of covered sale, targeted advertising or qualifying profiling. BlueB does not currently sell personal data or use it for targeted advertising across unaffiliated contexts.
If we deny a request and applicable law gives you an appeal right, reply to our decision with the subject Privacy Appeal. We will explain the result and any right to contact the relevant state authority.
18.4 Türkiye
Where Türkiye’s Law No. 6698 on the Protection of Personal Data (KVKK) applies, BlueB processes personal data for the purposes and on the legal grounds described in this Policy, which may correspond to establishment or performance of a contract, compliance with law, establishment or protection of a right, legitimate interests, or explicit consent where required.
Personal data may be transferred abroad subject to the cross-border transfer rules and safeguards required by KVKK. Data subjects may apply to learn whether data is processed, request information, learn the purpose and recipients, request correction or deletion where conditions are met, object to certain results produced through automated analysis, and claim compensation where legally available. Requests may be sent to info@blueb.ai, with sufficient information to verify identity.
18.5 Kingdom of Saudi Arabia
Where the Saudi Personal Data Protection Law (PDPL) applies, you may have rights to be informed, access personal data, obtain it in an available readable format, request correction or completion, and request destruction where the legal conditions are met. Cross-border transfers will be made under an available legal basis and required safeguards. You may complain to the competent Saudi authority.
18.6 United Arab Emirates
Where the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data applies, you may have rights of access, portability, correction, erasure or restriction, objection to certain automated processing, and withdrawal of consent, subject to legal conditions and exceptions. Cross-border transfers will use an available lawful mechanism.
18.7 Brazil
Where Brazil’s General Personal Data Protection Law (LGPD) applies, you may request confirmation, access, correction, anonymisation, blocking or deletion where appropriate, portability, information about sharing and consent, and review of qualifying automated decisions. The legal bases described in section 5 apply to the extent recognised by LGPD. You may contact Brazil’s National Data Protection Authority where entitled.
18.8 Canada and Australia
Where Canadian privacy law applies, you may request access and correction and may withdraw consent subject to legal or contractual restrictions. Where the Australian Privacy Act applies, you may request access and correction and complain about our handling of personal information. International recipients may be located in the countries described in section 9.
19. Changes to this Policy
We may update this Policy to reflect changes in law, the Service, providers or our practices. We will post the updated version and change the effective date. If a change materially affects how we use personal data, we will provide additional notice through the Service, email, WhatsApp service message or another appropriate channel and obtain consent where law requires it.
Previous versions may be available on request. A change to this Policy does not itself change a customer’s data-processing instructions or permit materially incompatible processing without an appropriate lawful basis.
20. Contact Us
For questions, privacy complaints or data-rights requests, contact:
Privacy Team
BLUEB TECH UK LTD
71-75 Shelton Street
Covent Garden
London WC2H 9JQ
United Kingdom
Email: info@blueb.ai
For general support or contractual enquiries: info@blueb.ai