Security

Last updated 28 October 2026

Myla holds your customer conversations, so we treat their safety as part of the product. This page explains how, in plain terms, for you and for your IT or compliance team.

Where your data lives

  • The application, database and queues run in the EU (Frankfurt). Files are stored with Cloudflare.
  • Everything is encrypted in transit and at rest. Passwords and access tokens for the tools you connect are encrypted again with a separate key.
  • Every provider we use is listed on our sub-processor page.

Your workspace is yours alone

Every record belongs to one workspace. Each request is limited to the signed-in workspace, and a second check on every database query watches for anything that reaches another workspace’s data. Anonymous benchmarks only ever combine totals from at least five businesses.

Who can get in

  • Sign-in is handled by Clerk. Your team can use two-step sign-in, and you can require it for everyone in your workspace.
  • Roles decide who can change settings, see store data or send messages. Admin actions, AI actions and data downloads are recorded in an audit log you can see.
  • Developer API keys can be limited to specific permissions and set to expire.
  • Inside our company, access to production systems is limited to the people who run the service, with two-step sign-in, and reviewed every quarter.

AI with guardrails

  • Replies are drafts for a person to approve unless you choose automatic sending. With it on, replies about refunds, cancellations and complaints wait longer so your team can step in, and refunds above your limit always wait for a person.
  • Messages that try to give the AI instructions are detected and never sent automatically.
  • Card, ID and bank numbers are removed before anything reaches an AI provider, and our AI providers don’t train on your data.

More detail is on How we use AI.

Your customers' privacy

  • Download everything held about a customer, or delete it completely, from their page.
  • Choose how long conversations are kept; older ones are deleted automatically.
  • Marketing consent and opt-outs are recorded, and broadcasts can be limited to customers who agreed.
  • Call recordings and transcripts are off unless an admin turns them on. They are kept in our EU file storage, deleted after the period you choose, and only supervisors, admins and the person on the call can play them; each playback is logged.
  • Our logs have personal details removed before they are written.

How we build and run it

  • Every change is reviewed and tested before release, including automated checks that one workspace can’t reach another’s data.
  • Dependencies are updated weekly and checked for known vulnerabilities.
  • Browser security headers stop other sites from framing the app.
  • The database can be restored to any point in its recent history, and we follow a written incident response plan. If a breach affects your data, we tell you within 48 hours, as our Data Processing Agreement promises.

Certifications

We aren’t certified to SOC 2 or ISO 27001 yet. We follow written security policies modelled on them, and can share our policies, risk register and Data Processing Agreement with your compliance team on request.

Reporting a security issue

If you think you’ve found a vulnerability, email contact@myla.cx with “Security” in the subject. We reply within 5 working days. Please don’t access other people’s data or disrupt the service while testing, and give us time to fix the issue before sharing it.