Privacy policy

einkreader · last updated August 2026

einkreader is local-first. Your feeds, articles, reading progress, highlights and notes are stored on your device, as plain files and a local database. There are no analytics, no trackers, and no accounts required.

What stays on your device

Your sources, downloaded articles and images, reading progress, highlights, notes, and contacts.
Your profile's secret key, if you create a profile. It is generated on the device and never sent to us.

What leaves your device — only when you choose

Fetching content: the app contacts the feeds and sites you add, and the services you connect (e.g. Twitter/X with your own API key, Nostr relays you configure).
Public profile (optional): if you create one, your chosen username is registered at einkreader.app and the profile details and highlights you explicitly share are published to Nostr relays. Sharing is opt-in, per highlight, every time.
Email features (optional): if you enable the Email plugin, mail sent to your @einkreader.app address from senders you whitelist is processed to deliver it to your reading feed, and one-tap shares are sent from your address on your instruction.

What we store server-side

Only what the optional services need: your username-to-key mapping (for name@einkreader.app), your whitelisted sender addresses, and pending email items until your device collects them. No reading history, no highlights (other than those you publish), no device identifiers.

Your data, your files

Everything the app stores locally is readable Markdown you can copy, back up or delete at any time. Deleting the app deletes its local data. To remove server-side data (username, whitelist, pending email), use the app or contact us.

Deleting your account

You can delete your profile, your name@einkreader.app address and everything we store for it at any time — in the app (Profile → Delete profile) or by email. See how to delete your account.

Contact

Questions: xdamman@opencollective.com · github.com/xdamman/einkreader