Data Processing Agreement
Last updated 2 November 2026
This agreement forms part of the Myla Terms of Service. It applies whenever Myla CX Ltd processes personal data on behalf of a business using Myla, and it covers the UK GDPR, the EU GDPR and the UAE Personal Data Protection Law. Accepting the Terms of Service accepts this agreement; no separate signature is needed.
1. Parties and roles
The business using Myla (“the Customer”) is the controller of the personal data of its own customers and staff. 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 (“we”) is its processor. We process that data only to provide Myla and only on the Customer’s documented instructions, which are the Terms of Service, this agreement, and the settings the Customer chooses in Myla, including an instruction to import its contacts and conversations from a provider it used before. If we believe an instruction breaks data protection law, we will say so.
2. Confidentiality
Everyone at Myla CX Ltd who can access Customer personal data is bound by confidentiality and has access only where their work needs it.
3. Security
We keep in place the technical and organisational measures in Annex 2. We may improve them over time but will not reduce the overall level of protection.
4. Sub-processors
The Customer authorises the providers on our sub-processor list. We bind each one by written contract to data protection terms at least as protective as these, and we remain responsible for them. We update the list before a new provider starts processing personal data. If the Customer objects on reasonable data protection grounds, we will discuss it in good faith; if we cannot resolve it, the Customer may end the affected service and receive a pro-rata refund of prepaid fees.
5. International transfers
Our main hosting is in the EU (Frankfurt). Where personal data is transferred to a country without an adequacy decision, the transfer is covered by the European Commission’s Standard Contractual Clauses (module 2 or 3 as appropriate) and the UK International Data Transfer Addendum, which are incorporated into this agreement by reference. For data subject to UAE law, we transfer data outside the UAE only as that law permits.
6. Helping the Customer
Myla lets the Customer find, correct, delete and download everything it holds about a person from within the product. Where that is not enough, we will help the Customer answer requests from individuals, and help with data protection impact assessments and consultations with regulators, as far as is reasonable given our role. If an individual contacts us directly, we will pass the request to the Customer and not answer it ourselves unless the Customer asks us to.
7. Personal data breaches
We will tell the Customer without undue delay, and within 48 hours, after becoming aware of a personal data breach affecting its data. We will share what we know about what happened, the data and people likely to be affected, the likely consequences, and what we are doing about it, and update the Customer as we learn more. Telling the Customer is not an admission of fault.
8. Ending the service
When the Customer’s subscription ends, we delete its personal data within 30 days, unless the law requires us to keep it. Backups are overwritten within a further 30 days. Before the end date the Customer can export its contacts from Myla, and we will provide a copy of its conversations on request.
9. Audits
We will provide the information reasonably needed to show that we meet this agreement, including our security documentation and, when we have them, independent audit reports. If that is not enough, the Customer may carry out an audit, at its own cost, once a year, with 30 days’ notice, under confidentiality, and in a way that does not disrupt the service or expose other customers’ data.
10. Liability and order of precedence
Liability under this agreement is subject to the limits in the Terms of Service. If this agreement conflicts with the Terms of Service on the processing of personal data, this agreement wins. If the Standard Contractual Clauses apply and conflict with either, the Clauses win.
Annex 1: Details of processing
| Subject matter | Providing Myla: a shared inbox that receives, stores, drafts and sends customer messages, and connects to the Customer's store and tools. |
| Duration | The term of the subscription, plus the deletion period in section 8. |
| Nature and purpose | Storing and displaying conversations; drafting, rewriting and translating replies with AI; handling voice calls, including recording, transcribing and summarising them where the Customer turns this on; searching the Customer's knowledge sources; looking up and acting on orders, bookings and CRM records; sending messages; importing contacts and conversation history from a previous provider at the Customer's instruction; reporting. |
| People whose data is processed | The Customer's customers and prospects who message it, and the Customer's staff who use the service. |
| Types of personal data | Names, phone numbers, email addresses, social media and channel identifiers, message content, attachments and voice notes, files the Customer saves to its library, the link, ad or page a conversation started from, call details (time, duration, participants), call recordings and transcripts where the Customer turns them on, order and delivery details, booking details, notes and tags added by staff. |
| Special category data | Not intended. Customers may volunteer it in a message or on a call; the Customer should not ask for it through the service, and decides whether calls are recorded or transcribed. Card numbers and national ID numbers are removed automatically. |
Annex 2: Security measures
- Encryption. All traffic uses TLS. Databases and file storage are encrypted at rest by our hosting providers. Passwords and access tokens for connected services are encrypted again with a separate key before they are stored.
- Separation between businesses. Every record belongs to one business, and every request is checked against the business of the signed-in user. Anonymous benchmarks combine figures from at least five businesses and contain no messages or contact details.
- Access control. Sign-in is handled by Clerk, with multi-factor authentication available. Inside a business, roles limit who can change settings, see store data or send messages. Only supervisors, admins and the staff member who was on a call can play its recording or read its transcript, and each playback is logged. Production access at Myla CX Ltd is limited to the people who need it.
- Audit trail. Administrative actions and AI actions are written to an audit log the Customer can see.
- Data minimisation. Card numbers, Emirates IDs, UK National Insurance numbers and US Social Security numbers are masked before storage. Bank account numbers are also removed before text is sent to an AI provider.
- AI safeguards. Drafts are suggestions unless the Customer turns on automatic sending. Actions that change an order or booking need approval unless the Customer chooses otherwise, and are re-checked against live data before running.
- Outbound requests. Calls to Customer-supplied addresses are blocked from reaching private or internal networks.
- Webhooks. Incoming webhooks are verified with a signature or secret before they are processed.
- Deletion. Deleting a contact or conversation also deletes stored files and everything derived from it. Files the Customer saves to its library are removed from storage within 7 days of the Customer deleting them, or at termination; copies sent in a conversation follow that conversation. Call recordings and transcripts are deleted at the end of the retention period the Customer chooses.
- Resilience. Our database provider keeps point-in-time backups. Code changes are reviewed and tested before release.
- Incidents. We follow a written incident response plan covering detection, containment, notification and review.
Contact
Data protection questions: contact@myla.cx.