Security & privacy
Protection built into the architecture.
Our products hold some of the most private things people write. That shapes how they are engineered, not just how they are described.
Encryption
Your writing is encrypted on your device, using AES-256, before it is stored. What our servers hold is ciphertext.
In ShareLync, a biodata is decrypted in the reader’s browser rather than on our infrastructure. In Mann, entries are encrypted locally before they are saved. Data is encrypted in transit throughout, and our production databases are hosted in India.
We use the language we can stand behind: encrypted on your device, stored as ciphertext. We do not describe our products as end-to-end encrypted, because we hold ourselves to what that term actually means.
Your controls
- Sharing is deliberate. A ShareLync biodata is visible to the people you hand it to, and to nobody else by default
- Access can be withdrawn. Revoking a share takes one tap and applies to links you have already sent
- Deletion is real. You can delete your content and close your account from inside either app, and we remove it from live systems
- The key stays with you. Because we do not hold the key to your Mann entries, nobody at MzeusLabs can open them
How we handle AI
Mann uses a language model to write reflections. When you request one, that entry is processed to generate your reflection and is not retained afterwards. It is never used to train a model, ours or anyone else’s.
Reflections are something you ask for. The journal works without them, and nothing is sent for processing unless you choose it.
Our commitments
- We do not sell personal data, to anyone, for any purpose
- We do not train models on your entries or your biodata
- We do not run advertising trackers or profiling on this site
- We do not claim a protection we have not shipped, in an app store listing, in marketing, or here
The full detail of what we collect, why, and how long we keep it is in the privacy policy. Each app also carries its own privacy screen, kept current with the release it ships in.
Reporting a vulnerability
If you believe you have found a security issue in either product, write to alefiya@mzeuslabs.com. We will acknowledge your report, keep you informed while we work on it, and credit you if you would like us to.
We ask that you give us a reasonable opportunity to resolve an issue before disclosing it publicly, and that you avoid accessing or modifying data that is not your own while testing.