Privacy and local processing
What stays on device in TimeCove?
TimeCove is designed around local-first reminder storage: reminder titles, schedules, status, and completion state stay on the device unless you enable optional provider-backed features.
Short answer
TimeCove keeps reminder data local by default while documenting optional provider, Firebase Analytics, Crashlytics, and speech-model download boundaries.
Privacy boundaries to understand
- Reminder data is stored on the device for the app workflow.
- Local speech and deterministic parsing are preferred for the core reminder path.
- System speech, cloud voice, weather, and AI fallback are optional and depend on configuration.
- Firebase Analytics and Crashlytics may collect technical app activity and diagnostics in configured releases.
- Free-form reminder content, transcripts, exact schedules, API keys, and private paths are excluded from the app analytics contract.
Questions this page answers
Does TimeCove require an account?
No account system is currently provided. Local app data can be removed by deleting reminders, clearing app storage, or uninstalling the app.
Does TimeCove send reminder text to AI by default?
No. AI fallback is optional, disabled by default, and intended only to help parse reminder commands when local parsing is not confident.
What does Firebase collect?
Configured releases may use Firebase Analytics and Crashlytics for app interactions, performance, diagnostics, and crash reporting, without adding reminder content or free-form transcripts to custom analytics events.
Where is the authoritative privacy policy?
The authoritative privacy policy is the English policy page linked from this site and the Google Play listing.