Privacy Policy

Cave ("we," "us," "the app") is built around a simple idea: your focus sessions are yours. This policy explains, in plain language, exactly what Cave stores, what (very little) leaves your device, and how you can delete all of it whenever you want.

By using Cave, you agree to the practices described here. If anything below is unclear, email us — see Contact at the bottom of this page.

1. The short version

• Cave has no account and no login. There is nothing tying your data to your identity.
• Your sessions, streaks, and settings are stored only on your device, in a local database. We never see them.
• We collect anonymous usage and crash data to fix bugs and understand which features are used — never tied to your name, sessions, or blocking activity.
• App blocking works entirely on-device: Cave checks which app is in the foreground and never reads your screen content.
• One button — Settings → Delete all data — permanently erases everything Cave has stored about you, on the spot.
• No ads. We don't sell or share your data with advertisers.

2. Information stored on your device

Cave uses a local database (Room/SQLite) that never leaves your phone or tablet unless you explicitly export it. This includes:

• Focus sessions — start and end time, duration, preset used, and whether the session was completed.
• Streaks and goals — your daily focus goal and the streak calculated from your session history.
• Preferences — your selected theme, default preset, keep-screen-on and background-animation toggles, session chime setting, and auto-continue preference.
• Your name, if you choose to enter one during onboarding or in Settings — used only to personalize the greeting on the Focus screen. It is never transmitted anywhere.
• Focus Shield preferences — which apps you've allowed to stay usable during a session (your "skip list"), and whether blocking is enabled.
• Join date — recorded locally the first time you open the app, used only to personalize your experience.

None of the above is sent to us or to any third party.

3. Anonymous analytics & crash reports

Cave uses Firebase Analytics and Firebase Crashlytics (provided by Google) to understand, in aggregate, how the app is used and to catch bugs before they affect more people. This data is anonymous and is not linked to your name, session content, or blocking activity.

What this can include:

• Usage events — e.g. a session started or completed, a screen was viewed, onboarding was skipped, a theme was changed, a backup was exported or restored, or data was deleted.
• Anonymous device properties — e.g. your selected theme, default preset, daily goal length, current streak length, and whether blocking is enabled. These describe app configuration, not you personally.
• Crash and diagnostic reports — technical information (device model, OS version, stack trace) used solely to identify and fix bugs. These reports never include your session content, your name, or your blocking activity.

This data is processed by Google under Firebase's own privacy and security practices. We don't control how Google secures its infrastructure, but we don't send it anything beyond the anonymous signals above.

4. Permissions Cave asks for, and why

Android

• Accessibility Service — required for Focus Shield to detect when a blocked app opens during a session. It reads only which app is currently in the foreground; it never reads on-screen content, and this check never leaves your device.
• Usage Access — an optional fallback signal for the same detection, used only if the Accessibility Service is unavailable.
• Notifications — shows a quiet, ongoing notification while a focus session is active, so you know blocking is on.

iOS

• Screen Time / Family Controls — Apple's on-device framework for app blocking. Selections you make (which apps to block) are handled by Apple's Screen Time APIs directly on your device; Cave does not see which specific apps you've chosen to block, only whether blocking is active.

Every permission above can be revoked at any time from your system Settings, and Focus Shield can be turned off at any time from within Cave.

5. Backups you create

Settings → Backup & Restore lets you export your full session history as a .zip file. That file is created and saved directly to your device — Cave does not upload it anywhere. Where you store it, share it, or move it afterward is entirely up to you, and entirely your responsibility.

6. Deleting your data

Settings → Delete all data lets you permanently erase every focus session, streak, preference, and blocking setting Cave has stored, directly on your device. You'll be asked to type DELETE to confirm, since this cannot be undone. The app then logs you out and returns to onboarding, as if freshly installed.

Because analytics events already sent are anonymous and not linked to any identifier we hold, they cannot be individually retrieved or deleted on request — there is nothing in that data that points back to you. Uninstalling the app has the same effect as Delete All Data for everything stored locally.

7. Children's privacy

Cave is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we'll address it.

8. Third-party services

The only third-party service Cave uses is Firebase (Google), for anonymous analytics and crash reporting as described above. You can read Google's own privacy practices at policies.google.com/privacy. Cave does not use advertising SDKs and does not sell or share your data with data brokers or advertisers.

9. Changes to this policy

If we materially change how Cave handles your data, we'll update the "Last updated" date above and, where appropriate, note it in the app's release notes. Continuing to use Cave after a change means you accept the updated policy.

10. Contact us

Questions about this policy or your data? Email narendraanjana09@gmail.com.