Legal
Privacy Policy
Last updated · October 9, 2026
Who we are
muro.chat is operated by GTA GO TO AGENCY, SAS (société par actions simplifiée), France, RCS Dijon 944 980 762. For your account data we are the controller. For the data the widget collects on your site we are your processor: you decide what is collected and we process it on your behalf, under our DPA.
What we collect from you
The data you give us (workspace name, email, password) and minimal usage data (IP for rate limiting, browser for support). We do not track you across sites.
What the widget collects on your site
A random visitor ID; the address of the page the widget loaded on, cut to domain and path (the query string and the fragment are never stored, and you can store the domain only, or nothing); browser, operating system and device type from the user agent; the country from the network edge; the IP address cut to its network (IPv4 /24, IPv6 /48); the messages; and a name or email only if the visitor types them or your site passes them. Only the latest page address is kept per visitor. No third-party analytics, no ads, no cross-site tracking.
What the widget stores in the browser
Five keys in localStorage, no cookies. All of them are erased 13 months after the first one was written, whatever happens in between, or sooner if the visitor clears site data. Loaded with lazy: true, the widget reads and writes nothing, and sends nothing to muro, until the visitor opens the chat.
| Key | Purpose |
|---|---|
| muro_fp | Random visitor ID (a UUID plus its creation time). Not a device fingerprint: nothing about the browser goes into it. |
| muro_vis | The visitor ID muro assigned to that random ID. |
| muro_conv | The ongoing conversation, so the thread survives a page change. |
| muro_email | The email the visitor typed in the pre-chat form, or that the site passed with identify(). |
| muro_pro_at | When the optional proactive message was last shown (7-day cooldown). |
AI
When AI features are on for a site, message content is sent to Anthropic (US) to triage the conversation, summarize it, suggest a reply, draft a help article or, if you enabled it, answer the visitor. Page addresses and IP addresses are never sent. Replies written by the AI are labelled as AI in the widget. You can turn AI off for a site in its settings: nothing from that site then reaches the AI provider.
Where data lives
Servers and database: Hetzner, Nuremberg, Germany. Email: Amazon SES, Ireland. Cloudflare sits in front of muro.chat for DNS and DDoS protection, so all traffic passes through it. Backups are encrypted with AES-256 on our servers before an off-site copy is stored with Cloudflare R2, which cannot read them. Payments run through Stripe. Full list with transfer safeguards at /legal/subprocessors.
How long we keep it
Visitor records and conversations stay as long as your workspace does, unless you erase them. Erasing a visitor from the dashboard deletes them, every visitor in the workspace with the same email, and all their conversations, immediately. A deleted workspace is purged 30 days after deletion is requested. Audit logs are kept 90 days, the email notification log 90 days, and the AI cost ledger (token counts, no content) 180 days. Backups are not edited: erased data leaves them as they rotate out.
Your rights and your visitors' rights
You can export your data from Settings and delete your workspace from Settings. Your visitors exercise their rights with you, as the site owner: you can export or erase any visitor from their page in the dashboard. If a visitor writes to us, we forward the request to you and help you answer it within the legal deadline.
Contact
Privacy questions: contact@muro.chat.