Omen Privacy Policy

what omen collects

Omen stores the information you choose to add to your personal tracker, including your name, username, email address, an optional date of birth, an optional profile photo, timezone, time logs, tasks, habits, goals, tags, optional weight and height measurements, workouts, dry-sauna, steam-sauna and cold-plunge sessions, book and movie library records and notes, meditative practice sessions, check-ins, meal and nutrition logs, private custom foods, optional metabolic-equation inputs, notes, app settings, friend connections, friend requests, sharing settings and calendar event invitations, Coach sessions, messages, proposals and Coach memory, a per-day record of the local days you open the app once Omen keeps one, and product feedback you choose to submit with a bounded app-screen label. Saved meals, recipes and food favorites are retired: Omen no longer offers them, and any saved meals and recipes retained from earlier use stay in your account export and are purged with account deletion until Omen deletes them.

When you search for books, Omen sends the search text to Open Library and retrieves book metadata and covers from that service. For the capability-gated movie library, Omen sends search text and movie identifiers to TMDB using a server-side token and retrieves movie metadata and posters. Omen stores the library records and notes you choose to save; those notes are not sent to the catalog providers.

When you search for food or enter or scan a barcode, Omen may send the minimum search text, barcode, or country to food-data providers such as USDA FoodData Central or Open Food Facts. Omen does not send those providers your Omen identity, email, location, unrelated health data, or diary history. Confirmed diary entries retain a bounded nutrition snapshot and source attribution so later catalog changes do not rewrite your history.

If you choose meal-photo or natural-language assistance, Omen sends the image and the meal details you provide to OpenAI to propose ingredients and portions. Images are resized, stripped of available metadata, processed for that request, and not retained by Omen after the proposal is returned. Nothing is added to your diary until you review and confirm it.

If you use Trends chat, Omen sends your request, bounded relevant conversation context, and selected data needed to answer it to OpenAI. This can include sleep and wearable metrics, Apple Health mindful minutes, time logs, habits, todos, goals, day tags, cardio and strength workouts, dry-sauna, steam-sauna and cold-plunge sessions, Practice sessions, recorded weight and height, nutrition, book and movie library records, and other permitted personal records or summaries; your timezone, unit system and age band; counts of your friends, close friends, friend requests and event invitations, and your own sharing settings; your sex for metabolic equations; for adults only, basal-metabolism and calorie-balance estimates; a history of the local days you open the app, once Omen records it; and, only when your account-level AI location access consent is on, arrival times and the distances between arrivals, never coordinates or routes. Personal notes and descriptions are retrieved only when you explicitly request them. Your calendar tag text and calendar block notes are sent only when you explicitly ask about your calendar, time blocks, time slots or tags. Graph calculations run on Omen's backend; viewing an existing graph does not itself send its data to a language-model provider. Omen retains Trends conversations until you clear them or your account is deleted. Clearing chat does not delete saved graphs or their source records. Omen retains Trends graph proposals with no expiry, although a pending proposal can be confirmed only within 24 hours. Provider processing and retention are governed by the provider terms and settings applicable to Omen's account.

If you use Coach, Omen sends your messages, the current session's conversation, a frozen recap and the tool results needed to answer them to OpenAI. Coach context can include sleep and wearable metrics, Apple Health mindful minutes, time logs, habits, todos, goals, day tags, cardio and strength workouts, dry-sauna, steam-sauna and cold-plunge sessions, Practice sessions, recorded weight and height, nutrition, finished books, Coach memory and the previous session's recap and goals handoff; your timezone, unit system and age band; counts of your friends, close friends, friend requests and event invitations, and your own sharing settings; your sex for metabolic equations; for adults only, basal-metabolism and calorie-balance estimates; a history of the local days you open the app, once Omen records it; and, only when your account-level AI location access consent is on, arrival times and the distances between arrivals, never coordinates or routes. Your calendar tag text and calendar block notes are sent only when you explicitly ask about your calendar, time blocks, time slots or tags. Friend-sharing audiences and friend detail settings control what your friends see; they do not limit what Trends chat and Coach read from your own data. Trends chat and Coach never receive your friends' identities, other people's records, precise coordinates, workout routes or financial data. Omen stores Coach sessions, messages, proposals and Coach memory with your account; you can review and edit Coach memory in Omen, and all of it is purged with account deletion.

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 show daily mindfulness minutes and, when you choose, save a completed Omen meditation to Apple Health, workout routes recorded in the iOS app, Google Calendar data for the read-only permission you connect, Microsoft Outlook connection details such as protected OAuth tokens and account identifiers, and Plaid financial accounts and transactions for admin-only finance features. Google Calendar and Outlook remain optional connections that Omen keeps until you disconnect them. Omen does not write Outlook calendar events. Until Omen's read-only Outlook update is active, Outlook grants include calendar write permission (Calendars.ReadWrite); once it is active, Omen requests only read-only access (Calendars.Read), never write access, and reconnecting replaces an earlier grant with read-only access. Omen no longer keeps its separate unencrypted copy of Plaid accounts and transactions; legacy copies retained from earlier connections stay in your account, are included in your account export and are purged with account deletion until Omen deletes them. Finance data retained from earlier connections stays in your account even if you no longer have admin access, is included in your account export, and is purged with account deletion.

Disconnecting a wearable stops new syncing, but its retained history stays in your account. That history remains visible in Today and Trends and available to Trends chat and Coach. Omen sends the requested data to OpenAI only when you use Trends chat or Coach. Coach chat automatically includes a summary of recent sleep history. Account deletion purges retained wearable history with your other account data after the recovery period.

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 balanced-accuracy updates on a five-minute cadence with no distance threshold; iOS controls the underlying sensors and delivery timing. Samples with reported accuracy worse than 100 meters are rejected, and raw samples are kept for 30 days. Live cardio recording suspends passive collection. 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.

Omen no longer offers an Apple Watch app or live Watch workout controls. A workout recorded earlier with an Apple Watch may retain its Apple Health identifier and heart-rate summary statistics; raw workout heart-rate observations are discarded after those statistics are calculated. Omen keeps clearing legacy Apple Watch workout artifacts from your devices when you log out, switch accounts or delete your account.

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. Omen keeps the region, city and country recorded for each session and may clear the raw IP address from session records after 30 days. Newer account exports and profile views omit session IP addresses and locations; the legacy CSV export keeps its existing columns. To keep offline changes safe, Omen keeps deletion markers for synced records for at least 15 days and keeps the latest version marker for each synced record. Until Omen's sync-receipt retention update is active, per-device sync receipts keep submitted change payloads, which can include workout route coordinates, until account deletion; once it is active, receipts are reduced to a minimal status record right away and deleted after 180 days. Changes made offline more than 15 days before they reach Omen may not be saved, and the mobile app may warn you when queued changes are about 10 days old.

Omen stores social safety data, including reports and their submitted details or captured content, blocks, account restrictions, moderation actions, and report-notification delivery records. Report notifications send the information needed for the operator to review the report through transactional email.

how omen uses data

Omen uses your data to provide and improve the app: dashboards, meal and nutrient summaries, food search, optional basal-metabolism and recorded-workout context for adults, 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 for admin-only personal finance features, including account and transaction history, categorization, monthly spending summaries, ledger imports, and rewards tracking, and for owner account export and deletion, including retained legacy finance data. Financial data is excluded from Trends and Coach and is not sent to their language-model provider.

Precise location is used only to provide your personal location timeline, calendar arrival cues, workout routes, security, debugging, and support. Trends chat and Coach may read only the arrival times and distances derived from it, never coordinates. Health, location, finance, 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 read-only calendar features; Microsoft Graph for an optional Outlook account connection; Oura, Garmin, Plaid, Apple services, USDA FoodData Central, Open Food Facts, and OpenAI for Trends, agent, coaching, or optional meal-assistance features. OpenAI is the only language-model provider Omen currently uses; Omen does not send your data to other language-model providers.

Open Library provides book search and covers, and TMDB provides movie search, metadata, and posters. For workout-location labels, Omen sends the submitted precise latitude and longitude to OpenStreetMap Nominatim for reverse geocoding. The coordinates sent to Nominatim are not rounded.

Omen shares data with your accepted friends only as you choose. Each sharing section, including Library, Habits, Todos, Workouts and an opt-in Practice section, can be set to not shared, all friends or close friends, and todo text and habit names have separate controls. Friend views never include workout notes, routes or location. Movie library records are never shared with friends. Accepted friends may see your profile photo. Reporting a user also covers their profile photo, you can block a user, and moderation can remove a photo.

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. Disconnecting a wearable stops new syncing, but its retained history stays in your account, remains visible in Today and Trends, and remains available to Trends chat and Coach. After you disconnect Oura, you can delete its retained history from your data settings; reconnecting later starts a fresh import. Omen sends the requested data to OpenAI only when you use Trends chat or Coach. Coach chat automatically includes a summary of recent sleep history. Account deletion removes this retained history after the 30-day recovery period.

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. AI location access is a separate account-level consent, offered on by default in the initial location-permission flow and available in the AI section of Settings. Turning AI location access off immediately stops new Trends and Coach reads of arrivals and distances, while keeping calendar arrival cues. You can delete your location history, including raw samples and derived arrival cues, from your data settings at any time; samples recorded before that deletion are not accepted again. Account deletion removes the derived arrival cues with your other account data.

Meal times are private diary metadata. Logging a meal does not create a calendar block or allow calendar data to create or infer a meal log.

You can download an export of your account data. Omen's newer export is a compressed ZIP file for you only, capped at 100 MB, and can include one GPX file for each GPS workout you select, built from the simplified route Omen stores. If the cap would be exceeded, Omen keeps the newest routes that fit and lists the omitted routes and the reason in the export's manifest.json. GPX route files are never sent to Trends chat, Coach or friends.

You can initiate account deletion in Omen settings. Access is locked immediately, recovery remains available for 30 days, and active account data, including meal and nutrition records, 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 and optional meal-assistance images are not retained by Omen after processing. 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 until you delete them so your historical calendar stays useful. Trends conversations stay until you clear them. 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. Users ages 13 through 17 may use the basic private meal diary and nutrient information, but Omen does not provide them with basal-metabolism comparisons, calorie goals, exercise-adjusted calorie values, or meal-photo estimates, and Omen never computes or sends basal-metabolism or calorie-balance estimates for them to Trends chat or Coach.

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