Pip Consumer Health Data Privacy Policy
Effective October 20, 2026 · Last updated October 20, 2026
Your period information is personal. This policy explains what Pip keeps, who receives it, and how to ask for access or deletion. It covers people protected by Washington’s My Health My Data Act and Nevada’s consumer health data law. Pip is operated by Thursday Horse Racing Inc., a federally incorporated Canadian company. Contact us at privacy@pip.club. The main Privacy Policy explains our other privacy practices.
H1. Health information and why Pip uses it
“Consumer health data” means information linked or reasonably linkable to you that reveals something about your health. It can include reproductive information and clues about health activity, even without your name.
| Category | Examples in Pip | Purpose and handling |
|---|---|---|
| Menstrual and physical-health information | Period starts and ends, flow, symptoms, regularity, usual period length and usual cycle length | Tracking and planning on your phone; encrypted server backup if you sign in |
| Moods, check-ins and care information | Moods, check-in days, comforts done, usual symptoms, comforts that help, goals and whether you tracked before | Tracking and related features; encrypted backup of setup answers and cycle history if you sign in |
| Cycle estimates | Estimated next period, cycle phases and patterns in logged symptoms and moods | Calculated on your phone for planning; recomputed from source history and not stored as separate fields in saved history or Pip’s encrypted backup. Local reminders can retain scheduled dates until canceled or replaced |
| Health-related activity and associated identifiers | Care-package opening time and tier; the days you earned check-in or comfort coins and which comforts you marked done; check-in, logged-day and care-package usage events if you turn on Help improve Pip; diagnostic screen names and technical support details you choose to send; associated account or analytics IDs, age band, device/session details, security-log IP addresses, email delivery records and web/app-link request information where linkable to health activity | Providing rewards, sign-in and web/app-link delivery; understanding app use, diagnosing failures and protecting the service |
Care packages arrive when you log a period. Their opening times may therefore hint at cycle activity. Coin records show the days you checked in and the comforts you marked done, but not your moods, symptoms or period dates. Usage events do not include the cycle values you enter, but may show use of a health-related feature. A crash report’s screen name may do the same.
Cycle history and setup answers are stored on your phone. Signing in enables automatic encrypted backups to Supabase in US East. These include your saved profile and age range, pet, rewards and inventory as well as health history. Readable backup metadata includes creation time, format version and device/key identifiers. Pip holds its key, encrypted under a separate secret, and returns it only to the owning account at sign-in. Nothing in Pip’s server systems opens your backup. Because we hold the key, authorized server operators could unlock it on purpose. A binding legal demand could require disclosure. The backup key is also kept in Keychain and can sync through iCloud Keychain; ordinary erase/sign-out retains it.
Pip excludes its saved app data, including cycle history, from your phone’s iCloud Backup and computer backups. Without signing in, your history stays only on this phone.
H2. Where the information comes from
Information comes from you and your use of Pip. Your phone produces usage and crash records and local cycle estimates. Apple’s services provide technical and purchase information. Supabase’s security logs, our email delivery provider and Cloudflare’s website/app-link delivery generate technical records, including IP or routing information where applicable. Where those records are linkable to health activity, they fall within H1’s associated-information category. These sources do not include health-data brokers, clinicians or public records.
H3. Who receives health information
| Recipient category | Information and purpose |
|---|---|
| Cloud hosting, storage and sign-in — Supabase | Encrypted backups, sealed keys and associated account, usage, diagnostic and security records to run Pip and restore backups |
| Platform services — Apple; email delivery provider | Sign-in, purchase, push and email-delivery records where linkable to health activity. Pip does not send cycle logs to the email delivery provider or put cycle values in push text |
| Support email — Google Workspace; operational alerts — Slack | Workspace receives messages and attachments you send. Slack receives service-failure counts and technical details without user identifiers or health-answer values; this policy covers alerts reasonably linkable to your health activity |
| Website and app-link delivery — Cloudflare | IP addresses, requested URLs and related request information, including friend-link codes, where reasonably linkable to you and your health activity. This does not include your cycle-history file |
| Authorities acting under a binding legal requirement | Information covered by the requirement, potentially including a backup Pip can unlock; applicable law governs the disclosure |
| A new owner, if Pip is involved in a merger, acquisition or sale of all or part of its business or assets | Consumer health data transferred as part of that transaction. The new owner must continue to honor this policy, and any new collection, use or sharing requires the consent described in H6 |
Recipients include Supabase, Apple, our email delivery provider, Google Workspace, Slack and Cloudflare. Pip has no affiliates that receive consumer health data. Their processing locations and roles are explained in §6 of the main policy, with international transfers in §7.
Supabase, Google Workspace and our email delivery provider process content for Pip under applicable service and data-protection terms. Providers may also use account and technical service information for their own service operations, security and legal compliance; our email delivery provider’s delivery/routing records are included in that distinction. Apple operates its own platform services. These roles do not mean every record is handled only on Pip’s instructions.
Accepted friends see your first name and pet, not cycle history, symptoms or moods. App-usage and diagnostic reports are hosted by Supabase. Provider automated security processing, including email abuse checks, is described in §6 of the main policy.
We do not sell consumer health data or use it for advertising or marketing. Pip has no advertising trackers collecting health information across websites or services.
H4. Your choices and health-data rights
Consent. During setup, before Pip collects your health information, it asks you to agree to Pip collecting and using it to provide core app features, cycle tracking and insights. Setup does not continue without that agreement. Your agreement is saved on your phone with the time and the version of the wording you saw. Help improve Pip is a separate, optional choice on the same screen.
Backup and app controls. Signing in enables the encrypted server backup. Without signing in, Pip still keeps server account records, and usage events if you turned on Help improve Pip. Signing out leaves an existing server backup in place. Help improve Pip is off unless you choose it during setup or in Settings. Turning it off clears queued reports and stops future collection through those pipelines, but does not delete records already received or recall an upload already in progress. Erase everything and Settings sign-out reset that choice, so Pip asks again at the next setup. Changing the analytics ID does not erase earlier events. Turning off Health information in Settings offers to erase everything on your phone and, if you are signed in, to delete your account and its backup, because Pip can’t track without it.
Washington and Nevada give covered consumers rights to confirm relevant health-data use, withdraw consent to future collection or sharing, and request deletion. Washington also provides access to health data and a list of third parties and affiliates receiving it, with a way to contact them. Nevada provides a list of third parties to whom data was shared or sold, where applicable.
To request access, correction, withdrawal or deletion, email privacy@pip.club.
Tell us what you want to do and whether you live in Washington or Nevada. No legal wording, special subject line or new account is required. If you use the Privacy request link in Settings, the email can include IDs to help locate records. IDs alone do not authenticate you.
We use existing information and request only what is reasonably necessary to verify you or your representative. Guests and people locked out of an account can contact us to assess an alternative verification route. We explain if a request cannot reasonably be verified or records cannot be identified. Do not email health history, passwords or sign-in codes. Personal records are returned through a secure, verified channel.
To withdraw consent, tell us which collection or sharing you want to stop. We stop the use covered by your withdrawal within the applicable deadline and explain any effect on your features. You may request deletion at the same time.
Review and correction. Export my data in Settings gives you the information on your phone as an unencrypted file. You can edit saved check-ins and use the period editor to change or delete a period. You can also request access to server-held health information and ask for corrections through the privacy contact.
Tell us which information needs correction without including unnecessary health details in email. We arrange a secure way to review the record, make any required correction and explain the result. For phone-held entries, we provide the applicable in-app steps.
Deletion. Delete account is available in Settings when signed in. After a successful server response it removes Pip’s current and previous server backup objects, server-held keys and associated account records, including care-package claims. You can choose to erase this phone too, which also requests removal of the local backup key.
Erase everything clears saved phone data, signs out and resets the analytics ID. For a never-signed-in installation it tries to delete the anonymous server account, but an offline or failed request can leave that account on the server. For signed-in users, ordinary erase leaves the server account and backup until account deletion. Ordinary erase/sign-out retains the backup key in Keychain. If an anonymous account remains after erasure, contact us for help locating it without sending your health history or sign-in secrets.
Deleting the app does not delete server records. Raw usage events are removed in monthly batches after roughly 13–14 months, plus the daily cleanup interval. Crash, hang and performance reports are removed after 13 months from receipt, plus daily cleanup. Changing their ID does not delete earlier records. Other retention periods and anonymous-account cleanup exceptions are in §9 of the main policy.
For a health-data deletion request, we check relevant account records, linkable usage and crash records, logs and copies held for us. We delete usage events and diagnostic reports under the analytics ID in your request. Earlier IDs are not automatically linked to your account. We assess whether relevant records can reasonably be identified and explain any limitation; records we cannot link follow the normal schedule. We notify the recipients required by law and coordinate deletion. Our hosting provider’s daily database backups keep deleted records for up to 7 days. Other provider recovery copies and retention limits are explained in §9 of the main policy. These database backups are for service recovery. A deletion request also covers identifiable copies held for us to the extent required by law. We explain any applicable retention exception and when remaining copies are due to expire.
The legal response periods are:
- Washington: without undue delay, within 45 days of receiving a request. One further 45-day extension is allowed when justified and explained within the first period. Authentication does not restart this clock.
- Nevada: general responses are due without undue delay and within 45 days after authentication. A justified further 45 days requires timely notice. Deletion has a separate deadline of 30 days after authentication, subject to the law’s limited backup exception.
We begin authentication promptly, respond within the applicable deadline and notify you of any lawful extension within the original period. Requests are free.
You have protection against unlawful discrimination for exercising these rights.
H5. How to appeal
If we refuse your request, reply to our decision or use Pip’s privacy contact to appeal. No special subject line is needed. We send a written decision with reasons within 45 calendar days of receiving your appeal. If denied, it includes the appropriate Attorney General’s complaint route.
You can complain to the Washington Attorney General or Nevada Attorney General, as applicable.
H6. Nevada notice details and changes
This policy’s effective and last-updated dates are at the top. For material changes, we provide notice through the app or another appropriate channel. Before collecting, using or sharing additional categories of consumer health data or using it for additional purposes, we make the required disclosures and obtain the affirmative consent required by law. A policy update alone is not that consent. You can request an earlier version through privacy@pip.club.
Pip does not enable advertising tracking of your consumer health data over time across other websites or services. H3 describes who receives information to provide storage, account functions and delivery.