Privacy

Short version: Enve has no servers, no analytics, no tracking, no third-party SDKs, and no account system. Your data goes between your device and whichever servers you chose to connect to. That's it.

What Enve doesn't collect

• No analytics events.
• No crash reporting service. iOS has none. Android keeps local-only logs.
• No third-party SDKs. No Firebase, no Sentry, no Crashlytics, no Mixpanel.
• No account system. You don't sign up for anything to use the app.
• No advertising identifier collection.
• No background telemetry of any kind.

Where credentials live

• iOS: every server password, token, and API key is stored in the iOS Keychain.
• Android: stored in Android's encrypted storage layer.
• Credentials are never written to logs and never transmitted anywhere except to the server they're for.

Where your reading data lives

• Locally on your device. The primary store.
• iCloud (CloudKit), if you have iCloud sync enabled. Your account, your data, nothing routed through Enve servers.
• Your servers (Audiobookshelf, Plex, Grimmory, and so on). Only the ones you connected.
• External sinks like KOReader Sync or Hardcover. Only if you enabled them.

Network behavior

Enve only makes network requests to:

• Servers you explicitly added.
• Apple iCloud (for CloudKit sync).
• External sinks you enabled (KOReader Sync, Hardcover).
• Cover art URLs returned by your servers.

No Enve-controlled endpoint is contacted. There isn't one.

Crash logs

• iOS: no in-app crash reporting at all. Apple's standard system crash logs only apply if you've enabled "Share with App Developers" in iOS Settings. Recommended. It helps the dev fix bugs.
• Android: local-only logs you can view or export from Settings → Debug.

This website

No analytics on this site either. No tracking pixels, no fingerprinting, no third-party fonts, no third-party scripts. Static HTML on a server somewhere.