YOUR HABITS, YOUR TRUST
Privacy Policy
A clear look at what stays on your device, what reaches the cloud, and the choices you control.
Effective date: 2026-11-01
1. Who operates Simply Habits
Simply Habits is operated by Jorge Castillo (“we,” “us,” or “our”). This policy describes the app as implemented, including its optional account, cloud synchronization, and notification features. For privacy questions or requests, contact schorts@outlook.com.
2. Local-first habit data
You can use personal habit tracking without an account. Habit names, descriptions, categories, weekday schedules, targets, check-in history, and archive status are saved in your browser's IndexedDB. A local outbox records changes waiting for cloud synchronization. The service worker caches public app files so the app and these policy pages can open offline.
Guest and signed-in accounts use separate local vaults. Signing out returns you to the guest vault; it does not erase either vault. Browser storage and downloaded exports can be accessed by someone with access to your device or browser profile. Browser clearing, device loss, or storage eviction can remove local data.
3. Optional accounts and cloud sync
If you sign in with Google, Google and Firebase Authentication handle the sign-in. The app uses your account identifier and the available display name and email address to identify your account and show account settings. We do not receive or store your Google password. Firebase maintains an authentication session in your browser and sends identity tokens to our server for authenticated requests.
Cloud sync stores habit records and their history in Firestore under your account identifier. When you explicitly connect a guest session to Google, guest habits are copied or merged into that account's local vault and then synchronized. Resuming an existing signed-in session does not automatically import guest habits.
The browser communicates with an authenticated server API over HTTPS on the deployed service. The API verifies your identity and determines the account data path from your token. Direct browser access to Firestore is denied by the supplied database rules; the server uses privileged Firebase Admin credentials.
4. Optional reminders and Web Push
Notification permission is requested only when you choose to enable notifications. For an enabled device, we store its account identifier, browser push endpoint and encryption keys, selected habit identifiers and reminder times, IANA timezone, language, daily encouragement settings, and operational timestamps. A hash of the endpoint identifies the subscription; it is not a claim that the subscription is anonymous.
A scheduled server checks cloud-synced habits to avoid reminding you about completed, archived, deleted, or unscheduled habits. Offline check-ins cannot suppress a cloud reminder until they synchronize. Notification text does not include habit names, but encouragement or a generic habit nudge may still appear on your lock screen according to your device settings.
Your browser vendor's push service receives a routing request with an encrypted notification payload. Browser and operating-system notification services deliver and display messages, even when the app is closed, subject to their availability and settings.
Turning off notifications removes this device's server subscription and unsubscribes the browser. Signing out also attempts to disable this device; other devices remain enabled. An offline sign-out unsubscribes at the browser provider, while an expired server record can remain until delivery detects expiration. Delivery receipts contain deduplication keys, timestamps, and a lease; they are marked for expiration after seven days. Firestore TTL cleanup must be configured and may occur later than the expiry time. Account deletion removes its subscriptions and receipts, but an already-dispatched message may still arrive.
5. Purposes and service providers
We process data to provide habit tracking, authenticate requests, synchronize devices, deliver requested reminders, and diagnose operational failures. Cloud data is processed by Google Firebase/Google Cloud. The deployment hosting provider processes requests to serve the app and API. Browser vendors process Web Push delivery. These providers handle data under their own applicable terms and privacy policies.
The app does not implement advertising, analytics tracking, marketing pixels, or sale of personal data. Its browser storage serves app functionality, offline access, and authentication. If the operator adds analytics, advertising, payments, or other processing, this policy and any required consent controls must be reviewed before those features are enabled.
6. Operational logs, security, and locations
Hosting, authentication, database, and push services may process IP addresses, browser/network details, request timestamps, and service logs. Application error logs can contain identifiers and diagnostic details. Habit content is not deliberately sent to an analytics service, but diagnostic errors may include context from failed operations. Do not put secrets or highly sensitive information in habit descriptions.
We use account-scoped access checks, server-side credentials, and HTTPS for the deployed service. These measures do not guarantee absolute security. Data locations, international transfers, backup practices, and log retention depend on the operator's Firebase and hosting configuration and the providers' terms. Ask schorts@outlook.com for the details of the live deployment.
7. Retention and your choices
Local data remains until you clear it or the browser removes it. Archived habits retain history. Permanently deleting a habit removes its content and history and retains a minimal identifier/date marker to prevent old devices or backups from restoring it. Deletion synchronizes when connected. Cloud records remain until deleted or removed under a disclosed retention policy. Resetting a guest vault also removes its local deletion markers; old backups may then restore deleted guest habits.
Settings provides JSON export and validated backup restoration: habits merge while preserving newer edits and permanent deletions. Exports do not include all provider-held account or operational data. After signing out you can clear the local guest vault. Account deletion requires signing in again and removes cloud habits, push subscriptions and receipts, the Firebase account and this device's account vault. It does not delete your Google account, guest data, exports or copies on other devices. A minimal account-identifier deletion marker blocks stale writes. Partial failures are reported and may require retrying or contacting support.
Signing out, archiving or uninstalling does not delete cloud data. For access, correction, deletion or other applicable rights, contact schorts@outlook.com. We may verify account ownership. Requests are subject to legal requirements and legitimate retention obligations, including provider backups and logs. Export before clearing data. Removing the app icon may not clear browser storage; on shared devices sign out and clear site data in browser privacy settings.
Account deletion is queued, not instantaneous. A configured five-minute scheduler removes data in resumable batches before deleting the Firebase identity. Temporary job checkpoints contain identifiers, document paths, processing status and lease/retry timestamps; completed jobs retain only a minimal completion marker. The app shows pending/failed status and checks completion while open and online, then clears this device's account vault and signs out. Keep the app open or return while the session remains valid for local cleanup; if completion cannot be verified, clear this site's data after exporting what you need or contact support. Scheduler/provider failures can delay cleanup.
8. Sensitive information and younger users
Simply Habits is a general-purpose personal productivity tool, not a medical service or a confidential records system. Please avoid entering medical records, passwords, or sensitive information about other people. The service is not designed for children who require parental consent under applicable law. If you believe such a child has provided personal data without the required authorization, contact schorts@outlook.com.
9. Changes and contact
We may revise this policy as the service or legal requirements change. The effective date above will identify the current version. Material changes will be communicated as required by applicable law; publication alone is not a substitute for consent where consent is required.
Privacy requests and questions: schorts@outlook.com.