Oomi · Privacy
Privacy
Draft for counsel review. The payments and shopping sections are proposed disclosures, pending approval before publication. Payment and payout integrations currently support test mode only.
Oomi is a cycle-aware wellness app operated by Oomi LLC. This page explains what Oomi collects, where it lives, who else ever sees any of it, and what deletion means for each kind of record. Oomi holds menstrual, reproductive, and other health information, so this page tries to be specific rather than reassuring. There is no advertising, no tracking, and nothing about you is ever sold. If anything here is unclear, email support@oomiwellness.com and a person will answer.
Version 1 App Store privacy summary
The current release keeps Studio, Shop, payments and Concierge disabled. It does not collect phone number, physical address, payment information or purchase history through those dormant features. Every active category below is linked to your account and marked Tracking: No.
| Data type | Purposes |
|---|---|
| Health | App Functionality; Product Personalization |
| Fitness | App Functionality; Product Personalization |
| Sensitive Info | App Functionality; Product Personalization |
| Name | App Functionality |
| Email Address | App Functionality |
| User ID | App Functionality |
| Coarse Location | App Functionality |
| Photos or Videos | App Functionality |
| Other User Content | App Functionality; Product Personalization |
| Product Interaction | App Functionality; Analytics |
| Customer Support | App Functionality |
| Other Diagnostic Data | App Functionality |
| Other Data Types | App Functionality; Product Personalization |
Product Interaction uses first-party Analytics to measure content views, progress, completions and saves. Customer Support covers feedback and reaction reports. Other Diagnostic Data covers only the allowlisted error codes described below.
The short version
- Your wellness logs are stored in Oomi's database with account-scoped access. Optional sharing and shopping have the limited access described below.
- A small number of outside services are involved, and only for specific features you use. They are all named below, with what each one receives.
- Optional partner, stylist and Studio features share the specific information described below when you choose to use them.
- You can request account deletion from inside the app. Oomi reports what it removed and names any outside copy that still needs action from you. Shared Studio and shopping records follow the more specific rules below.
Health and reproductive data
Oomi is built around your cycle, so most of what it holds is health information, and some of it is sensitive by any standard. Depending on what you use, that can include your period dates and bleeding history, cycle phase, symptoms and check-ins, pregnancy or trying-to-conceive status, life stage (for example hormonal birth control, IUD, perimenopause, post-menopause), bloodwork results you type in, cancer-screening history and family cancer history, and, if you turn it on, substance-recovery details including what substance and your sobriety start date.
Oomi does not use any of this for advertising, does not sell it, and does not share it with data brokers, insurers, or employers. It is used to run the app for you and nothing else.
How you sign in
Oomi supports four ways to sign in, and you pick one:
- Google. Google confirms it is you and tells Oomi your email address.
- Apple. Sign in with Apple, including Apple's Hide My Email if you prefer.
- Email and password. The password is handled and stored by Oomi's authentication provider, hashed; Oomi cannot read it.
- Email and a six-digit code. No password at all. Oomi emails you a code and you type it in.
However you sign in, Oomi receives your email address and a stable account id. Oomi never sees your Google or Apple password.
What Oomi stores
- Your profile. One record per account holding your name, birth date, ZIP code, your intake answers, cycle and period history, journal and reflection entries, evening check-ins, bloodwork, screening and family-history answers, goals, dietary preferences and disliked ingredients, self-care and habit loops, completed workouts and exercise and meditation logs, recovery settings if enabled, your personal planning notes (things like vision and wishlist items, weekly commitments, and any career or job-search notes you add), and anything else you write into the app.
- Food and drink. Meals you log with their nutrition values, custom foods you create, foods added by scanning a barcode or importing a recipe, your pantry list, and your water logs.
- Body and activity metrics. One record per day per source: sleep hours, a sleep score and quality band, steps, active minutes, resting heart rate, heart-rate variability, and a recovery score where a source provides one. The raw response from the source is kept alongside it.
- Cycle and readiness records. Your computed cycle state per day, including cycle phase and a daily readiness score and band, so your history and trends can be shown back to you.
- Photos. If you add a photo, the image itself goes into a private storage bucket in a folder that only your account can read, and a small amount of metadata about it (an internal key, when it was taken, its type and dimensions) is kept with your profile.
- Connection records. If you connect Fitbit or Google Calendar, Oomi stores the access and refresh tokens for those connections so it can keep syncing without asking you to reconnect constantly. See the next section.
- An Apple Health sync token. If you use the iOS Shortcut route to send Apple Health data in, Oomi stores a single long-lived token for your account. It expires after a year and can be rotated or revoked.
- Partner sharing. Only if you invite a partner. See below.
- Studio bookings. Class and service reservations, their time, price, payment method, status, cancellation or attendance times, and whether you said you were new to the studio. If you separately choose contact sharing, Oomi also creates or links the Studio contact record described below.
- Shopping. Stylist connections, invitations, selected style information, shopping preferences and limits, finds, approvals, messages, order numbers, tracking links, delivery addresses, receipt files, charge and refund records, Stripe identifiers, card brand and last four digits, and payout and transfer status. Oomi does not store full card numbers, card security codes, or Connect bank and identity documents.
- Coach content. Only if you are an approved Oomi coach. See below.
Stored access tokens
This is worth saying plainly because it is easy to miss. When you connect Fitbit, Oomi stores a Fitbit access token and a long-lived Fitbit refresh token for your account. When you connect Google Calendar, Oomi stores a long-lived Google refresh token. Both are held so background sync keeps working; both live in tables that your browser and the app cannot read at all, reachable only by Oomi's own server-side functions. Disconnecting Fitbit from inside the app revokes the tokens with Fitbit and marks the record revoked. Deleting your account removes both records.
Optional device and wearable data
- Apple Health (iOS). If you grant access, Oomi reads a fixed, small set of metrics: steps, exercise minutes, resting heart rate, heart-rate variability, and sleep. Access is read-only. Oomi never writes anything into Apple Health.
- Fitbit. If you connect it, Oomi requests the activity, heart rate, sleep, and profile scopes, and pulls daily activity, sleep, and resting-heart-rate summaries into your body metrics.
Where your data lives
Oomi's database, authentication, file storage, and server-side functions all run on Supabase. Tables holding your data use row-level security to control access. Wellness records are scoped to your account; partner and shopping features allow the limited access described below. Personal photos sit in a private bucket scoped to your account, and shopping receipts use a separate private bucket shared with the client and stylist for that purchase. Data is encrypted in transit and at rest. It is not end-to-end encrypted, which means Oomi's systems can read it in order to run the service, for example to compute your cycle phase and your plans.
Who else receives anything, and why
Oomi uses the following outside services for the features named. Shopping may also involve the retailers and delivery services described below:
- Supabase — hosting, database, authentication, and file storage. Supabase processes everything described on this page as Oomi's infrastructure provider.
- Anthropic processes two optional features only after you make an explicit, just-in-time choice. Meal-photo estimation sends the photo of your plate. Meal ranking sends your standing food note, how you said you are feeling, your current cycle phase and goal, and the titles and summaries of candidate recipes. Neither request includes your name, email, or account id. Anthropic's standard API policy retains inputs and outputs for up to 30 days, and Anthropic says commercial API content is not used to train its models. You can decline and keep using manual meal logging and Oomi's deterministic recipe recommendations. You can withdraw permission later in Your data. Once the withdrawal is saved, Oomi prevents new Anthropic requests started after that point, but cannot stop a request already in flight or recall a request already sent. Oomi's API key stays server-side.
- Stripe processes supported card payments and Connect payouts. Payment details entered into Stripe's payment form go to Stripe. Oomi sends internal account and purchase identifiers, amounts and currency to associate payments with your purchases; it stores Stripe customer and payment-method identifiers, card brand and last four digits, charges, refunds and transfers. Connect onboarding collects identity, bank and tax details directly on Stripe's pages; Oomi stores the connected-account identifier and onboarding/payout status. Oomi does not send cycle logs, journal entries or health records to Stripe. Stripe acts as a payment processor and also has its own responsibilities for fraud prevention, security and legal compliance. See Stripe's privacy policy.
- Fitbit — only if you connect it. Oomi calls Fitbit's API with your token to read your data, and calls Fitbit again to refresh or revoke that token.
- Google Calendar — only if you connect it. Oomi creates its own separate calendar in your Google account and writes events into it. Those events contain cycle information: the phase label, a short piece of phase guidance, the cycle-day range, and the names of training and self-care items. If you do not want cycle phases written into your Google Calendar, do not connect it; you can still export a calendar file and import it yourself.
- Google and Apple — as sign-in providers, if you choose one. They know you signed in to Oomi.
- Open Food Facts — when you scan a barcode, the barcode number is sent to their free public product database to look up the product and its nutrition. Nothing about you is sent with it.
- Cloudflare Stream — only if you are an approved Oomi coach uploading a video. The video file and your Oomi account id (recorded as the creator) go to Cloudflare, which hosts and serves the video.
Oomi uses these services to provide the features described here. Providers may also process data for their own legal, security and fraud-prevention obligations under their policies, including Stripe's policy linked above.
Oomi records the version of the Anthropic choice, the choice you made and when you made it so the app can honor it consistently.
Partner sharing
Oomi has an optional partner feature. Nothing exists until you choose to create an invite code and give it to someone. If you do, that person's account can see a deliberately minimal slice: your current cycle phase and day, roughly when your next period is due, a short care tip, and the name you entered. They cannot see your logs, symptoms, journal, bloodwork, or anything else, and they cannot change your data. You can see whether they have looked at it. Shopping and coach features have the separate sharing described on this page.
Studio booking and contact sharing
Draft for counsel review. When you reserve a class or service, the studio can see the operational reservation record: the class or service, date and time, price and payment method, booking status, cancellation or attendance time, and whether you said you were new to that studio. The studio needs these values to run its schedule, honor the reservation, manage capacity and resolve a booking or payment dispute. This shared Studio record does not include your cycle, symptoms, journal, bloodwork or other Oomi wellness data.
Contact sharing is a separate choice. If you choose it while booking, Oomi shares your first name and account email with that studio and records the date of your consent. Studio staff can then use that contact record for the follow-up you agreed to and can record whether a follow-up step was sent or skipped. Oomi does not share your phone number through an Oomi consumer booking. If you do not choose contact sharing, the studio sees the reservation as a guest booking and Oomi does not create a contact record for that booking.
The free beta does not ask studios to collect optional notes about Oomi visitors. Oomi will not enable optional Studio visitor notes until their purpose, access and deletion lifecycle are defined and disclosed.
Shopping and stylist sharing
When you connect with a stylist, each party can see the other's display name and the shopping relationship, including agreed budget, buying limits and shopper fee. The stylist can see selected body-style quiz results when enabled, color season, confirmed style details, and style-session requests you send, including the style snapshot, palette, values and note. This does not give the stylist access to your wellness profile, cycle logs, journal or bloodwork.
You and the stylist assigned to a find can see its suggestions, approvals, messages, order and tracking details, receipt, charges and transfers. Finds you add for yourself without a stylist remain private to you. An actively linked stylist can read your default delivery address while a purchase assigned to them is approved, ordered or shipped, so they can fulfill it. Retailers and delivery services receive the information needed to fulfill an order when you or your stylist place it with them; their own policies apply. Avoid adding health details or unrelated personal information to shopping notes or receipts.
Oomi stores delivery addresses in its database and receipts in a private Supabase storage bucket. Receipt access is restricted to the client and stylist for the associated purchase. Disconnecting a stylist limits connection-based access, but does not erase purchase records or copies already received, and some purchase and receipt access remains tied to the original parties. Contact support about access or deletion concerns.
Coach content
If you are an approved Oomi coach, videos you publish and their details (title, description, category, level, cycle phases, length) are visible to other signed-in Oomi members once you publish them. Oomi also records member interactions with your published content — a view, watch time, completion, a save — so your own dashboard can show real numbers. Members' own interaction records are private to them and to the coach who owns that piece of content.
Plain error signals
When a signed-in screen fails to render, the browser reports a window error, or a request is left unhandled, Oomi can store one fixed error code with your account. It does not send the error message, stack, page URL, device details, profile fields, or health data. These codes are used to see whether the beta is functioning and to prioritize repairs.
What Oomi does not do
- No third-party analytics, ad networks, tracking SDKs, or marketing pixels. The iOS app declares no tracking to Apple.
- No selling, renting, or trading of your data, in any form, ever.
- No sharing of your health data with advertisers, data brokers, insurers, or employers.
Your controls
From Settings inside the app you can, at any time:
- Export your profile record as a JSON file. This is the large one: intake answers, cycle and period history, journal entries, bloodwork, goals, preferences, and the rest of your profile. It does not include your food, water, and body-metric logs, which are stored separately, or your photo files. Email support@oomiwellness.com if you want a complete copy of everything and it will be sent to you.
- Delete your account. Settings, then delete. Oomi removes the live account data it controls and reports the result for each system. If an outside copy cannot be removed because access was revoked or Oomi lacks permission, the result names that copy and tells you how to remove it. Shared Studio and shopping records follow the specific deletion rules on this page.
- Disconnect Fitbit from the health integrations panel, which revokes the tokens with Fitbit.
- Disconnect Google Calendar by removing Oomi's access in your Google account's security settings. Oomi's stored refresh token stops working and is deleted the next time it is tried. Events already written stay in your Google Calendar until you delete them there, and you can delete the whole Oomi or Cove calendar in Google at any time.
What deleting your account actually does
When you confirm deletion, Oomi runs a checked workflow across its live database, private file storage, sign-in account, provider tokens, Oomi-created Google Calendar events and Cloudflare-hosted coach media. It records a non-health operational result for every step. A failure that would make continuing unsafe stops the workflow, and Settings reports what completed and what remains. It applies across every Oomi app and you are signed out after the live account is removed. There is no recovery window and it cannot be undone, so export a copy first if you want one. Shared Studio and shopping records are handled as described below, so Oomi does not describe account deletion as complete erasure of every record held by Oomi or another recipient.
Oomi deletes an outside copy when it still has both permission and the identifier needed to do so. If Google or another provider no longer permits that deletion, the result identifies the remaining copy and gives removal steps. For Google Calendar, open Google Calendar, find the calendar named Oomi or Cove and delete that calendar. For Cloudflare-hosted coach media that Oomi could not remove, email support@oomiwellness.com with the deletion result so the remaining asset can be investigated without sending health information.
For a valid deletion request involving Studio records, Oomi deletes or deidentifies your first name, email, consent link and other personal values in visitor, booking, appointment and follow-up records. A studio may keep only the operational values needed for a documented legal obligation or an active booking, payment or dispute purpose. Where a shared record can be retained without identifying you, Oomi severs its link to your account and keeps only the deidentified class or service, time, price, status and attendance information. Any exception requires counsel review and a documented purpose and duration that Oomi discloses to you. There is no blanket multi-year retention period for Studio records.
Shopping rows tied to your account and associated receipt files are also removed by account deletion. Deleting an Oomi account does not automatically close a Stripe or Connect account, erase records held independently by Stripe, a retailer or a stylist, or cancel an outstanding purchase, refund or dispute. Contact support about outstanding transactions before deletion and contact the provider about records it must retain.
One deliberate exception: if you were linked as someone else's partner, her share record survives with the link to you severed. Deleting it would be deleting another person's data.
If you cannot reach the in-app delete for any reason, email support@oomiwellness.com. Oomi will process the request within 30 days and report what was removed and any remaining action.
Data retention
Oomi keeps your data for as long as your account exists. It is not kept on a timer and it is not deleted for inactivity. Account deletion removes data from Oomi's live database and storage through the deletion workflow described above. The production Supabase plan, its configured backup window, any manual database exports and the real restore behavior have not yet been verified, so Oomi cannot honestly give a shorter backup-removal deadline today. For deletion requests covered by Washington law, deletion from archives or backups must be completed as soon as restoration allows and no later than six months after the request. Six months is a legal ceiling, not Oomi's target. Oomi must verify the production backup and manual-export process before publishing a shorter promise, and a restore must not make deleted data active again. Shared Studio records use the purpose-based deletion and deidentification rules above, not an arbitrary blanket period. Shopping addresses, receipts and transaction records follow the account lifetime in Oomi; Stripe and retailers may retain their own records for legal, accounting and fraud-prevention purposes under their policies. Two things expire on their own: the Apple Health sync token after a year, and the short-lived state records created during a Fitbit connection after ten minutes.
Adults only
You must be at least 18 years old to use Oomi. Oomi is not directed to children and does not knowingly collect data from anyone under 18. If you believe someone under 18 has created an account, email support@oomiwellness.com so Oomi can process the deletion workflow and report the result.
Changes
If this policy changes in a material way, the date below will be updated and, where appropriate, you will be notified in the app. Continued use after a change means you accept the updated policy.
Contact
Questions, a data request, or something on this page that does not match what you see in the app: support@oomiwellness.com. See also Support and the Terms of use.