Memoir privacy
Privacy starts with clear boundaries
Privacy is easier to evaluate when each surface has one job. The public site explains Memoir. The diary app handles private entries. Optional providers are contacted only for actions you choose.
The public site
Information, not your diary
The public information site does not receive diary entries, entry titles, photos, encryption material, recovery keys, or Google OAuth tokens.
This static site has no sign-in form, diary database, advertising tracker, or behavioral analytics SDK. Like an ordinary website, its host may still process technical request data needed to deliver and protect the service, such as an IP address, request path, and user agent.
Inside the application
Core writing begins locally
Memoir stores diary data in a local SQLite database so writing and browsing core entries do not depend on a cloud connection.
- Local diary
- Entries are application data in the local SQLite database. Local-first is not a claim that this database is SQLCipher-encrypted.
- Optional cloud sync
- If you connect Google Drive, supported payloads are encrypted before upload and stored in your Drive.
- Network features
- Sync, maps, weather, OAuth, and other network-backed actions contact the services needed for that action.
Your choice
Cloud storage is optional
Google Drive sync stores supported encrypted diary data in the connected user's own Drive rather than Memoir-operated diary storage.
Google's terms and privacy practices apply when you authorize Drive. Memoir does not claim control over Google's availability, account access, or storage quota. Dropbox and OneDrive are not launched providers.
Next step
Review the security model
See how cloud encryption, local storage, app lock, biometrics, and recovery differ before you decide how to use Memoir.