Skip to content
muninn

Privacy

Your thoughts should
stay yours.

Muninn is designed around private journaling. Journal content is encrypted before it is stored and the public site never asks for journal content, account credentials, or authenticated API access.

Encryption and access

Encryption protects journal content in storage and during synchronization. For accounts with automatic recovery, the service stores recoverable account keys encrypted under a separate server key and releases them after browser email verification. The service can recover these keys, so this is not end-to-end encryption against the service. Access still requires account authentication and ownership.

Recovery limits

New accounts use automatic recovery after email verification. Older accounts must first migrate using an unlocked browser or their original key. Keys that were never enrolled cannot be recreated. Revoking a browser ends its access but cannot erase data it already downloaded.

Optional AI processing

AI features are optional and privacy modes determine whether content may leave the device. Plaintext processing requires explicit consent. Features that do not need plaintext keep encrypted content encrypted.

Public site data

This static site does not set account cookies or call private application APIs. It contains synthetic examples only. Questions about privacy can be sent to hello@muninn.qb8s.net.

This marketing site uses Umami, hosted at analytics.qb8s.net, to measure visits to public pages. The tracker excludes URL query strings and fragments and respects your browser’s Do Not Track setting. It does not receive journal content or account identifiers from this site.