Privacy Policy
This page describes what the system actually does, without decoration. If we do not deliver it technically, we do not promise it.
Your draft is never shared
The raw text you write never reaches the other person: they only see the reformulated version you approve. Content is encrypted in your browser before storage, so our database only holds unreadable characters.
What we cannot promise you
Melyara is not "zero knowledge" nor end-to-end encrypted in the strict sense. To reformulate your text, the content is decrypted and sent to our AI provider. We also keep an encrypted copy of the conversation key on the server so it can be recovered if you lose the link. We would rather tell you than have you discover it by reading the code.
What data do we collect?
We collect the minimum information necessary for the service to function correctly:
- Account: If you register, we save your email and basic name to manage your access and subscription.
- Usage: Anonymous technical data to improve application performance.
- Conversations: Stored encrypted and decrypted with the link key. Melyara keeps an encrypted copy of that key for recovery.
Artificial intelligence processing
To reformulate, translate and prepare the Melyara Guide, your text is sent to OpenAI, our AI provider. Under the current OpenAI API policy, that content is not used to train their models and is retained for at most 30 days for abuse monitoring, unless legally required otherwise. We ask for explicit consent before the first submission and record the accepted version and timestamp. You can revoke it, but without that processing Melyara cannot reformulate anything.
The conversation key
Each pause has an AES-256 key that travels in the "#key=" fragment of the link you share. URL fragments are not sent to the server in a normal request, but the full link is included in the invitation email, and we keep an encrypted copy of the key on the server so the conversation can be recovered. That means Melyara can technically access the content if needed.
Mobile Device Data and Identifiers
To guarantee system security, prevent quota abuse, and implement Melyara's Cost Governor (passive rate-limiting control), the mobile application collects anonymous hardware identifiers and IP address hashes (IP Hash). For guest users, we collect the unique Device ID to manage their pauses in a completely isolated environment without requiring them to register.
Advertising
Melyara shows no advertising. There are no rewarded ads, no third-party ads and no advertising identifiers in the launch experience.
Account Erasure and Data Deletion Rights
You can delete your account from your profile panel, in the app or on the web. Deletion happens immediately and removes your email, your name, your notification devices, your sessions and your identity in analytics. We do not delete everything, and we would rather say so: we keep purchase records because accounting and tax law require it, content reports and blocks other people created because those protect them, proof that you gave consent for AI processing as a legal record, and the pauses you shared with someone, which lose your name but which we do not destroy because that conversation is theirs too. To delete an account you have to sign in with it: go to the account deletion page.
Cookies and Tracking
We use essential cookies to keep your session and first-party analytics with no third-party cookies. Analytics records only event names and categorical labels: never drafts, reformulated messages, needs, hand-written emotions, emails or micro-agreements.
Contact
If you have any questions about how we handle your data, write to us at hello@melyara.com.