← ReminDiary

Privacy Policy

Last updated 2026-08-24

ReminDiary is built to work fully offline. Your journal entries never leave your device unless you export them yourself. The only network activity the app performs at all is a single opt-in, off-by-default analytics toggle in Settings, which — when turned on — reports which screen you're on. Nothing else. No entry content, no dates, no account, no device identifier.

Your journal entries

Entries are stored locally on your device — SQLite on Android, IndexedDB in a browser. They are never transmitted anywhere by the app itself. CSV export/import moves data between a file and your device's storage; both stay entirely under your control.

The analytics toggle

Settings has a toggle, off by default, labelled "Share anonymous usage analytics." Turning it on sends a screen-view event — nothing more — to a self-hosted Umami instance the developer runs, each time you switch between the Write, Memories, and Settings tabs.

FieldExampleWhat it's for
url /Write Which tab you switched to. Only ever one of /Write, /Memories, or /Settings.
hostname android or web Which build sent the event, nothing more specific than the platform.

That's the entire payload. It never includes:

Umami counts unique visits without cookies: it derives a session identifier server-side from the requesting IP address and browser/app identifier, salted and rotated on its own schedule, and does not persist a long-lived identifier tying your visits together over time.

Turning it off

Open Settings and switch "Share anonymous usage analytics" off at any time. No event is sent while it's off, including the very first launch — it defaults to off and nothing is sent until you deliberately turn it on.

Changes to this policy

If what's collected ever changes, this page changes with it. The source for both the app and this site is public — see the repository for the exact code that builds and sends these events (src/platform/analytics.*.ts).