This describes what OlaTime actually does with your data — not boilerplate legal language disconnected from how the app works.
By default, OlaTime doesn't send your data anywhere. It lives in this device's local storage (IndexedDB), full stop. There is no analytics SDK, no ad network, and no tracking pixel anywhere in this app.
If you choose to sign in and turn on Cloud Sync, your appointments, habits, and workspace data are synced to a Firebase project used by this app, so they can follow you across your own devices. This is the only scenario in which your data leaves your device, and it only happens because you turned it on.
A local Workspace (church, clinic, team, etc.) created without Cloud Sync stores everything the same way as your personal data — locally, on that one device, never transmitted. A Workspace connected to Cloud Sync follows the same Firebase-backed sync described above, scoped to that workspace's members.
Browser notification permission, when granted, is used only to show you your own reminders. No notification content is sent through any third-party push service unless you are in a Workspace with real-time push explicitly configured by whoever set up that workspace's backend — and even then, it's your own reminder text, not anything else.
mailto: draft instead.None of these are contacted unless the specific feature that needs them is actually used.
Export your appointments to CSV, Word, PDF, or a full JSON backup at any time, from Settings. Clearing your browser's site data removes everything stored locally — there's no separate deletion request process needed, because there's no server copy to begin with (unless you opted into Cloud Sync, in which case deleting your account removes the synced copy too).
If this changes, this file changes with it — there's no separate hidden policy.