Privacy Policy
Last updated 2 November 2026
Myla is a customer-support platform. Businesses connect their messaging channels and their own reference material, and Myla helps them read, answer and act on customer conversations. This policy explains what personal data is involved, who is responsible for it, and what we do and do not do with it.
Who we are
Myla CX Ltd, a company registered in England and Wales (company number 17557973), whose registered office is at Unit 2 Foley Trading Estate, Hereford, HR1 2SF, United Kingdom operates Myla. We are the data controller for the personal data of account users.
For privacy requests, contact contact@myla.cx.
For end-customer data, the business is the controller and Myla is the processor. We process that data only on the business’s instructions.
Who this policy covers
Myla CX Ltd operates Myla (“we”, “us”). This policy covers the Myla application, its API, and the connections it makes to third-party services on a customer’s instruction.
Two different groups of people appear in this policy:
- Account users — the people at a business who sign in to Myla: owners, admins and support agents. We are the data controller for their data.
- End customers — the people who message that business. We are a data processor for their data. The business decides what is collected and why; we process it on their instructions and nothing else.
If you messaged a business and want your data corrected or deleted, contact that business directly. They control it. We will help them act on your request, but we cannot act on it without them.
What we collect
For demo bookings and sales enquiries, we collect your name, email, store website, platform, conversation volume, notes, booking details and consent choices to arrange and follow up your call, keep them while needed for the enquiry and any resulting business relationship, and send tips and offers only with your consent, which you can withdraw at any time.
| Category | What it includes | Why |
|---|---|---|
| Account data | Name, email address, WhatsApp number, role, and the business you belong to. Authentication is handled by our identity provider; we never see or store your password. | To give you an account and apply permissions, and to send you account messages (such as your trial ending or a payment problem) by email and WhatsApp. Set-up tips on WhatsApp are only sent if you ask for them, and you can turn them off at any time. |
| Conversation data | Messages exchanged between a business and its customers on connected channels, along with the contact record: name, phone number, email address, channel identifiers, tags, notes and lifecycle stage. It also includes how a conversation started, such as the ad, chat link, QR code or web page that led to it (for example, when someone messages from a Facebook or Instagram ad, Meta tells us which ad it was), and any contacts and past conversations a business asks us to import from a support tool it used before. | This is the product. Without it there is nothing to read, answer or search. |
| Attachments and media | Images, documents and voice notes sent in a conversation, plus transcripts of voice notes, and files a business saves to its file library to send to customers. | So attachments can be viewed in the inbox and their content used when drafting an answer, and so the team can send saved files again without uploading them each time. |
| Calls | Details of WhatsApp calls between a business and its customers: who called whom, when, for how long, which team member answered or made the call, and whether the customer has allowed the business to call them. If the business turns it on, a recording and a written transcript of the call, and an AI-written summary of the transcript. | So calls appear alongside messages and can be followed up, reviewed and used when answering the customer. |
| Knowledge sources | Documents, web pages, spreadsheets and other reference material a business connects, and the search index built from it. | So answers are grounded in that business's own material rather than guessed. |
| Commerce data | Orders, fulfilment and tracking information, where a store is connected. | So questions about an order can be answered with the actual order. |
| Operational data | Audit logs, error reports, and usage counts of AI features. | Security, troubleshooting and billing. |
Google user data
Where a business connects a Google account, Myla requests only the access needed for the feature being used:
| Access requested | What it is used for |
|---|---|
spreadsheets | Reading a Google Sheet the business adds as a knowledge source, and appending rows to a sheet the business nominates as a conversation log. |
drive.file | Reading only files you choose in Google's file picker as knowledge sources. |
calendar.readonly | Checking availability when answering a booking question. |
calendar.events | Creating or amending a booking, where the business has enabled that. |
Limited Use
Myla’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: Google user data is used only to provide and improve the features described above; it is never sold; it is never used for advertising; and it is never used to develop, improve or train generalised artificial intelligence or machine-learning models.
Google data is read on demand or on a schedule the business sets, and the extracted text is stored so it can be searched. A business can disconnect Google at any time under Settings, and can revoke our access directly from its Google account’s security settings. Removing a knowledge source deletes the text and search index derived from it.
Artificial intelligence
Myla uses large language models to draft replies, rewrite or translate replies the team writes (including with instructions the business sets), classify conversations, transcribe voice notes and calls, summarise calls and search a business’s knowledge base. To do that, the relevant conversation text, call transcripts and knowledge extracts are sent to our model providers, listed below.
We use these providers under enterprise API terms which state that content sent to them is not used to train their models. We do not train any model on customer data, and we do not use one business’s data to answer another business’s customers. Each business’s knowledge base and conversations are scoped to that business.
Within one business, replies its team has already sent (with names, email addresses, phone numbers and order numbers removed) can be shown to the AI as examples when it drafts a reply to a similar question, so it answers the way that business does. The business can switch this off, which deletes the collected examples, and deleting a conversation deletes its examples too.
Drafted replies are suggestions. Unless a business explicitly turns on automatic sending, a person reviews every message before it goes out.
Card numbers, national ID numbers and bank account numbers are removed before any text reaches a model provider, and card and ID numbers are also masked in what we store. When a reply is sent automatically, the customer is told it was written by AI. More detail is on our How we use AI page.
Call recording
WhatsApp calls are only recorded or transcribed if the business turns this on, and an admin must first confirm they have read a notice about the business’s own legal duties. At the start of a call that is being recorded or transcribed, WhatsApp plays a spoken announcement to both people saying so and why; anyone who does not agree can end the call.
Recordings and transcripts can be played or read only by the business’s supervisors and admins and by the team member who was on the call, and each playback is logged. The business decides whether to record calls and is responsible for explaining it in its own privacy notice.
Sub-processors
We use a small number of providers to run the service: hosting and databases in the EU (Frankfurt), sign-in, AI models, billing, email and notifications. Other providers, such as messaging channels, stores, calendars and CRMs, are used only when a business connects them. The full, current list, with what each provider does and where, is on our sub-processor page.
We will give notice of a material change to this list. A business that objects to a new sub-processor may terminate before the change takes effect.
Anonymous benchmarks
If an admin turns on anonymous benchmarks for a business, Mylacalculates aggregate service figures, such as response times, resolution rates, how often AI drafts are sent unchanged, and survey satisfaction rates, and combines them with other participating businesses to show typical figures. We publish a figure only when at least five businesses contribute, and show only medians and ranges. We never share message content, customer personal data, order or product information, or a business’s knowledge and policies. The figures never identify a business or a person. Benchmarks do not affect the AI replies of any business, and an admin can turn them off at any time.
How long we keep it
Conversation and contact data is kept for as long as the business keeps its account, unless the business sets a shorter limit: it can choose to delete conversations automatically after 3 months, 6 months, 1 year or 2 years without new messages. A business can delete individual contacts, conversations and knowledge sources at any time from within Myla; deletion removes the record and anything derived from it, including search index entries.
Files in a business’s file library are kept until the business deletes them, when they are removed from storage within 7 days, or until the account closes. A copy sent in a conversation is part of that conversation and is kept and deleted with it.
Call recordings and transcripts are deleted after the period the business chooses (90 days unless it changes this), or sooner if the conversation or contact is deleted or the account closes. Meta, which makes the recording, says it deletes its own copy within 7 days. The call’s details and any AI summary stay with the conversation and follow its retention.
When an account closes, we delete its data within 30 days, except where we are required to keep records to comply with a legal obligation. Backups are cycled out within a further 30 days.
Where data is processed
Our providers operate in the United Kingdom, the European Economic Area and the United States. Where personal data is transferred outside the UK or EEA, that transfer is covered by the UK International Data Transfer Addendum or the European Commission’s Standard Contractual Clauses.
Customers in the United Arab Emirates
Where the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) applies, we process personal data on the same basis and with the same safeguards described in this policy. People in the UAE have the rights that law gives them, including access, correction, deletion, restriction, objection and a portable copy, and can exercise them as described under “Your rights”. Data may be processed outside the UAE by the providers on our sub-processor page, under contracts that protect it as that law requires.
Security
- Data is encrypted in transit and at rest.
- Credentials and access tokens for connected services are encrypted with a separate key before being stored, and are never displayed back in full.
- Access within a business is controlled by role, and administrative actions are written to an audit log.
- Actions that reach the outside world — sending a message, calling an external system — are gated and, by default, require a person to approve them.
No system is perfectly secure. If we become aware of a breach affecting personal data, we will notify affected businesses without undue delay and, where required, the Information Commissioner’s Office.
Your rights
Under UK and EU data protection law you may request access to your personal data, correction of it, deletion of it, restriction of its processing, a portable copy, or object to processing. You may also withdraw consent where processing relies on consent.
Account users can exercise these rights with us at contact@myla.cx. End customers should contact the business they were messaging, which controls that data.
You have the right to complain to the Information Commissioner’s Office, or to your local supervisory authority.
Changes
We will post any change to this policy on this page and update the date at the top. A change that materially affects how personal data is handled will be notified to account holders in advance.
Contact
Myla CX Ltd — contact@myla.cx.
Our Terms of Service, Data Processing Agreement and Acceptable Use Policy govern use of Myla.