Privacy policy
Last updated: 18 November 2026
Service status (18 November 2026)
Sign-up is not yet open. Until it opens, the service only receives Mabi Labs' own test notifications from Meta. It checks the signature on each one and then discards it, without storing or forwarding anything.
This policy explains what data Mabi Labs Connect processes today, what it will process when sign-up opens, why, how long we keep it and how you can ask us to delete it. It covers the website at connect.mabilabs.ai and the Meta app called Mabi Labs Connect (together, "the service").
1. Who we are
The service is run by MABI VF LTD, trading as Mabi Labs ("Mabi Labs", "we", "us"). We are a company registered in England and Wales, company number 16989125. Our registered office is Unit C1a, Poole Hall Road Industrial Estate, Ellesmere Port, Cheshire CH66 1ST, United Kingdom.
Contact us about privacy at mk@mabilabs.ai.
2. What the service does today
- These web pages are served by Cloudflare, which processes your IP address and request details to deliver them. We set no cookies and use no analytics. Cloudflare may set a strictly necessary security cookie if it needs to check that a visitor is not an automated attack.
- The service has a webhook endpoint that Meta calls with notifications. Until sign-up opens, the only notifications are Mabi Labs' own test notifications. The service checks the cryptographic signature on each one and then discards it. It stores nothing and forwards nothing.
- Service logs hold only the type labels of those notifications, how many arrived, a note when one could not be read and, if something goes wrong inside the service, the page path and the type of error. They never hold notification content. Notifications that fail the signature check are refused and not logged. Full web addresses and query strings, including any verification token, are left out of the logs.
- If you email us, we hold your email and our reply in our email service, Google Workspace.
3. Lawful bases today
Under the UK General Data Protection Regulation (UK GDPR):
| Purpose | Lawful basis |
|---|---|
| Serving these pages and keeping the service secure, including checking notification signatures. | Our legitimate interest in running a secure website and service (Article 6(1)(f)). |
| Answering emails and handling privacy and deletion requests. | Legal obligation (Article 6(1)(c)) and our legitimate interest in responding to people (Article 6(1)(f)). |
| Keeping business and tax records. | Legal obligation (Article 6(1)(c)). |
4. Who processes data for us
- Cloudflare, Inc. hosts the service and keeps short-lived service logs, on a global network that includes the United Kingdom, the European Economic Area and the United States.
- Google provides our email service (Google Workspace) and holds emails you send us.
Each of them uses its own sub-processors under its data processing terms, which it publishes. We use no other providers for the service.
When Cloudflare or Google processes data outside the United Kingdom, including in the United States, we rely on UK adequacy regulations, including the UK Extension to the EU-US Data Privacy Framework where the provider is certified, or on the International Data Transfer Addendum to the European Commission's standard contractual clauses in the provider's data processing terms. Contact us for a copy of the relevant safeguards.
We may also share data where the law requires it, for example with a court or regulator. We do not sell data.
5. Security today
- The service only works over HTTPS.
- Every notification is checked with a cryptographic signature, and anything that fails the check is refused.
- The service stores no notification data, and its logs exclude request addresses and query strings.
6. How long we keep data
- Service logs: Our hosting provider, Cloudflare, deletes service logs automatically within 30 days.
- Backups: none. Today the service stores no notification data, so there is nothing to back up.
- Emails: We keep emails about the service, and records of privacy requests, for up to 6 years after our relationship with the person or business ends, to meet legal and tax duties.
7. When sign-up opens
This section describes how the service will handle data once client businesses can sign up. None of it happens today.
7.1 Our role
Mabi Labs Connect will connect a business's WhatsApp Business number to that business's own helpdesk, using Meta's official WhatsApp Business Platform. We call these businesses "client businesses".
For WhatsApp message content and the contact details of people who message a client business, we will act as a processor on behalf of that client business. The client business will be the controller. It will decide why and how that data is used, and it will be responsible for telling its own customers how it uses their data.
We will be the controller for the account details, access tokens and IDs we hold to run the service, and for security logs.
The client business will use WhatsApp under its own agreement with Meta, on WhatsApp's business terms. Meta will not be our sub-processor.
If you message a business that uses our service and want to know how it uses your messages, please contact that business first. We will help it answer your request.
7.2 The data we will receive from Meta
When a client business connects through Meta's sign-up window, and while it stays connected, the service will be able to receive the following data from Meta's platform:
| Type of data | What it includes |
|---|---|
| Business account IDs | The WhatsApp Business account ID (also called the Messaging account ID), the business phone number ID and the Meta business portfolio ID. |
| Access tokens | A business access token that Meta issues when the client business completes sign-up. It will let the service act for that business on the WhatsApp Business Platform. |
| Message notifications | Notifications about messages sent to and from the business's WhatsApp number. These include message text and media, sender phone numbers, WhatsApp user IDs, usernames and profile names, delivery and read statuses, and edits and deletions. Because client businesses can keep using the WhatsApp Business app alongside the platform, this also covers messages the business sends from the WhatsApp Business app. |
| Contacts | A one-time copy of the contacts saved in the business's WhatsApp Business app, followed by notices of later changes to those contacts. |
| Chat history (optional) | Only if the business chooses to share its chat history during sign-up: up to 180 days of past chats, including media from roughly the last 14 days. |
| Account events | Notices about the business's WhatsApp account, for example when it connects, disconnects or changes its number. |
We will not receive anyone's Facebook or WhatsApp password. Sign-in will happen in a window run by Meta.
7.3 How we will process it
- Sign-up will work only through a personal, single-use link from us that expires.
- When sign-up finishes, the service will swap a short-lived code from Meta for the business access token, check that the token covers the business's account, and store the token with the account IDs.
- Meta will send every notification for the business's number to our service. The service will check each one is genuinely from Meta, then pass it on straight away to the helpdesk the client business chose, signed so the helpdesk can check it came from us.
- Messages, contacts and chat history will pass through the service in transit only. The service will not store them or write their content to logs. If the helpdesk cannot accept a delivery, the service will ask Meta to try again later, and Meta retries for up to 7 days.
- The contacts copy and the chat history copy will each happen once, and only when the client business has instructed us to start them. We will record that instruction. Later contact changes will then arrive as they happen. Chat history will be sent only if the business chose to share it during sign-up.
- When a business disconnects its number, Meta will tell our service and the service will delete its access token automatically.
- Service logs will then also hold account IDs and delivery statuses, still never message content.
We will not sell this data, use it for advertising, use it to build profiles of people, or use it to train AI models. We will use Meta platform data only to provide the service to the client business that connected it, and as Meta's terms allow.
7.4 Purposes and lawful bases
| Purpose | Lawful basis |
|---|---|
| Connecting a client business's WhatsApp number and keeping it connected, using the access token and account IDs. | Performance of our contract with the client business (Article 6(1)(b)). Where the data relates to people acting for the client business, our legitimate interest in providing the service they asked for (Article 6(1)(f)). |
| Passing messages, contacts and chat history to the client business's helpdesk. | We will act on the client business's instructions as its processor. The client business will be responsible for its own lawful basis. |
| Keeping the service secure, checking that notifications come from Meta, and preventing misuse. | Our legitimate interest in running a secure service (Article 6(1)(f)). |
7.5 How long we will keep client data
The service will store only what it needs to operate. It will not store message content, contacts or chat history. Clean-up will run automatically once a day. Where the table gives a period, the data will be deleted at the next successful daily clean-up after that period ends. Where it says "straight away", deletion will happen as part of the same step. Deleted data will leave Cloudflare's backups within 30 days. Service logs and emails keep the retention set out in section 6.
| Data | How long we will keep it |
|---|---|
| Access token, account IDs and sync records (date, Meta's reference and the client's instruction for each sync) | While the number is connected. They will be deleted straight away when the business disconnects its number (Meta tells us) or we disconnect it at the business's request. |
| Helpdesk address, the key used to sign deliveries to it, and the result of the latest helpdesk check | Until the client business ends the service or asks us to delete them. |
| Sign-up links | Unused links: 30 days after they expire. Used links will be kept as a record of the connection until the client business's settings are deleted; the account ID will be removed from them when the number is disconnected. |
| Removal records: a salted one-way fingerprint of the account ID (not the ID itself), a connection number, our client reference, the reason or outcome, and dates | 90 days after the removal. They will let the service handle repeated notices from Meta safely. |
| Markers for a connect or disconnect step in progress (the account ID and a 2-minute expiry) | Deleted straight away when the step finishes. If a step never finishes, the marker will expire after 2 minutes and be deleted at the next successful daily clean-up. |
| Mabi Labs' own test accounts, listed so their notices are ignored | Until we remove them from the list. |
| Messages, contacts and chat history delivered to a client business's helpdesk | Held by that client business under its own retention rules. |
7.6 Additional security
- Access tokens will be stored in encrypted storage, never shown in web pages or responses, and never written to logs.
- Every delivery to a helpdesk will be signed with a key unique to that client business.
- Administrative functions will be available only to Mabi Labs, protected by a secret key we hold.
8. Your rights
Under UK data protection law you have the right to:
- ask for a copy of your personal data;
- ask us to correct data that is wrong or incomplete;
- ask us to delete your data;
- ask us to restrict how we use your data;
- object to our use of your data where we rely on legitimate interests;
- ask for your data in a portable format, where that right applies.
Email mk@mabilabs.ai to use any of these rights. We decide on a valid request and reply without undue delay, and in any case within one calendar month of receiving it, subject to any exceptions the law allows. Once sign-up has opened, if a request is about data we process for a client business, we will pass it to that business without delay and help it respond.
You also have the right to complain to the Information Commissioner's Office (ICO), the UK data protection regulator, at ico.org.uk/make-a-complaint or by phone on 0303 123 1113. We would appreciate the chance to put things right first, so please contact us before you go to the ICO.
9. How to ask us to delete your data
Data deletion requests
Email mk@mabilabs.ai with the subject line Data deletion request: Mabi Labs Connect.
Tell us what the request is about, for example the business name and the WhatsApp number or WhatsApp Business account ID. Please do not send copies of messages or ID documents.
What happens next:
- We confirm we have your request within 5 working days.
- We check that the request comes from the person or business the data is about. We may ask one short question to confirm this.
- We decide on a valid request and reply without undue delay, and in any case within one calendar month of receiving it, subject to any exceptions the law allows.
- We email you to confirm what we deleted.
Once sign-up has opened, deletion for a business will mean we stop forwarding its messages, disconnect our app from its WhatsApp account, and delete the access token, account IDs, helpdesk settings and sync records we hold. That will not end the number's connection to Meta's WhatsApp Business Platform: in the WhatsApp Business app, go to Settings, then Account, then Business Platform, then Disconnect Account. Full steps are on our data deletion page.
10. Children
The service is for businesses. It is not aimed at children.
11. Changes to this policy
We will update the date at the top of this page when we change this policy, including when sign-up opens. We will tell client businesses about important changes by email before they take effect.
12. Contact
MABI VF LTD, trading as Mabi Labs, Unit C1a, Poole Hall Road Industrial Estate, Ellesmere Port, Cheshire CH66 1ST, United Kingdom. Email mk@mabilabs.ai.