Omen Privacy Policy

what omen collects

Omen stores the information you choose to add to your personal tracker, including your name, username, email address, date of birth, an optional profile photo, timezone, time logs, tasks, habits, goals, tags, experiments, optional weight and height measurements, workouts, check-ins, notes, app settings, and product feedback you choose to submit with a bounded app-screen label.

If you connect optional integrations, Omen may store data returned by those integrations, including Oura or Garmin health, fitness, device, and workout data, Apple Health mindful-session durations used to record daily mindfulness minutes and check your Meditation habit, workout routes recorded in the iOS app, Google Calendar or Gmail data for the specific permissions you connect, Microsoft Outlook calendar events linked to scheduled todos, Plaid financial accounts and transactions, and selected FinanceKit records if that integration is enabled.

If you enable Location Timeline in the iOS app, Omen collects precise location samples and associated timestamps, accuracy, altitude, speed, and course in the foreground and background. Omen requests ongoing balanced-accuracy location updates; iOS chooses the underlying sensors and delivery frequency, and Omen generally batches observations after at least about five minutes and 50 meters of movement. Omen uses the samples to derive private arrival cues that help you reconstruct your calendar. Raw samples and arrival cues are associated only with your account.

When you use an Apple Watch workout with Omen, Omen may store the workout's Apple Health identifier and heart-rate samples with that workout so you can review the workout in Omen.

Omen also stores operational data needed to keep the service working, including login and consent records, hashed one-time authentication challenges, session times, normalized device/browser/operating-system categories, IP address or a protected hash of it, approximate geography derived from network headers, error logs, request metadata, OAuth state, and security audit records. Omen does not store raw email authentication codes or the full browser user-agent string for new sessions.

how omen uses data

Omen uses your data to provide and improve the app: dashboards, search, trends, reminders, calorie estimates, agent workflows, summaries, correlations, visualizations, sync, security, debugging, support, and product improvement based on feedback you choose to submit.

Financial data is used only for user-requested personal finance features such as transaction history, categorization, budgeting, trends, search, and optional user-controlled correlations with your own tracker data.

Precise location is used only to provide your personal location timeline, calendar arrival cues, workout routes, security, debugging, and support. Health, location, finance, email, calendar, and other tracker data are not used for advertising, resale, data brokerage, lending, credit decisions, or third-party marketing.

sharing

Omen does not sell your personal data. Omen shares data only when needed to operate the app, when you connect an integration, when you ask Omen to send information somewhere, or when required for security, legal compliance, or abuse prevention.

Connected services may include Cloudflare for hosting, network protection, and automated abuse checks; Resend for authentication and transactional email; AWS for backend infrastructure; Google APIs for calendar or email features; Microsoft Graph for Outlook calendar sync; Oura, Garmin, Plaid, Apple services, Telegram, and LLM providers used to power agent or coaching features.

your choices

You can disconnect supported integrations from Omen settings. You can stop Apple Health sync in Omen settings and separately revoke Omen's Health access in Apple Settings or the Health app. You can also revoke access directly with other connected providers, such as Google, Microsoft, Oura, Garmin, or Plaid.

Location Timeline is off until you enable it in the iOS app and grant location permission. You can disable it at any time to stop new passive location collection. Disabling collection does not immediately erase existing samples; raw samples age out after 30 days, and account deletion removes the derived arrival cues with your other account data.

You can initiate account deletion in Omen settings. Access is locked immediately, recovery remains available for 30 days, and active account data is then purged. Encrypted daily backups are retained for 90 days, so a copy may remain in backup storage for up to about 120 days from the deletion request before aging out.

retention and security

Omen keeps tracker data while your account is active, except that raw Location Timeline samples are automatically deleted after 30 days. One-time authentication codes expire after 10 minutes, cannot be reused, and are stored only as protected hashes; short-lived pending signup data expires after 10 minutes. Derived arrival cues remain so your historical calendar stays useful. Profile photos are stored as private, encrypted AWS objects and removed from active storage when replaced, removed, or purged with the account; protected object versions may remain for up to 90 days for recovery. Daily encrypted database backups are retained for 90 days for disaster recovery and are not used as an active account store.

Omen uses access controls, encrypted transport, provider OAuth flows, token protection, and server-side controls to protect stored data. No system is perfect, so sensitive integrations should be connected only when you want Omen to process that data.

children and changes

Omen is not intended for children under 13, and account creation is blocked for anyone who reports being under 13.

This policy may be updated as Omen adds features or integrations. The effective date above will change when the policy changes materially.