Pip Privacy Policy
Effective October 20, 2026 · Last updated October 20, 2026
1. Pip and your privacy, in plain words
Your period dates, symptoms, moods and setup answers stay on your phone unless you sign in. Pip keeps them out of your phone’s iCloud and computer backups. Your phone data
Signing in is optional and enables an encrypted backup. We hold its key and could unlock it. Our server systems do not open it. A binding legal demand could require disclosure. Your backup
During setup, Pip creates a server account after the age question, even without sign-in. It keeps your pet, rewards, purchases and friend connections. Your account
Accepted friends see your first name and pet, not your cycle logs, symptoms or moods. Heart notifications can show the sender’s first name. Friends · Notifications
Before setup goes further, Pip asks you to agree to it using your health information for tracking and insights. “Help improve Pip” is a separate, optional choice. It is off unless you tick it during setup or turn it on in Settings. When it is on, Pip sends usage and diagnostic reports under a random ID. Turning it off does not delete earlier reports. Usage and diagnostics
No ads. No tracking you across other apps. We never sell your data. Who receives information
You can export your phone data in Settings. Delete account removes a signed-in account and its server backup. Erase everything clears this phone and resets its analytics ID. For never-signed-in users, it also tries to delete the server account; this needs a successful connection. For signed-in users, the account and backup remain. Your controls
Pip is intended for people aged 13 and older. Children and teens
Questions or requests? Contact us. Our Consumer Health Data Privacy Policy explains health-data rights in Washington and Nevada.
The details
2. Your cycle, answers and backups
Your phone stores period dates and flow, symptoms, moods, check-in days and comforts done. Setup answers include your goals, tracking experience, cycle regularity, usual period length, usual cycle length if your cycle is regular, symptoms and helpful comforts. Your profile includes age range, setup progress and reminder choices. These support cycle tracking and related features. Estimates are calculated from this information rather than saved as separate history or backup fields; a local reminder can retain a scheduled date.
The cycle-history file uses iOS complete file protection and cannot be read while your phone is locked.
Your phone’s backup. Pip excludes its saved app data, including cycle history and setup answers, from iCloud Backup and computer backups. To keep your history when you change phones, sign in to use Pip’s encrypted backup. Export my data in Settings gives you your own readable copy, but Pip can’t import it back in.
Pip’s server backup. Signing in with Apple or email enables automatic encrypted backups to Supabase Storage in US East. These contain your saved app state, including cycle history, setup answers, profile and age range, pet, care packages, balances and inventory. Creation time, format version and device/key identifiers accompany the encrypted contents as readable metadata.
Your phone encrypts the backup before upload. We store its key encrypted under a separate master secret outside the database and return it only to the owning account at sign-in. Pip’s server systems do not open the backup, but authorized operators could unlock it because we hold the key. A binding legal demand could require disclosure.
The key is also kept in iPhone Keychain and is eligible for iCloud Keychain sync. Ordinary sign-out and Erase everything retain it for restoration. Account deletion with phone erasure requests removal of the local key.
Your privacy choices. Health consent, Help improve Pip and Terms acceptance are saved on your phone with the time and wording version. They are included in an encrypted backup if you sign in, but are not sent to our server in readable form.
Without sign-in, Pip does not upload this app-state backup. Server account records and any consented usage reports are separate, as explained below.
3. Your account, pet, friends and purchases
After you answer the age question, Pip creates a server account with a generated ID. Pip calls this an anonymous account, but its ID and records can still be personal information. Signing in links that account to your sign-in details.
Our server keeps these records in readable form:
| Information | Why Pip keeps it |
|---|---|
| First name; your pet’s name, species, age and outfit | Your profile and pet; showing your first name and pet to accepted friends |
| Account ID and Pip code; friends, friend requests, and hearts sent and received | Running your account and friend features |
| Coin and moonstone balances; a coin ledger, including the day you earned check-in or comfort coins and which comfort you marked done; items owned; care-package claims, including opening time and tier; and records of claims or coin earns held back for review | Keeping your rewards, inventory and balances, and preventing misuse of rewards |
| Purchase records and Pip Plus entitlement received from Apple | Providing what you bought and checking subscription access |
| Email address, if you use email sign-in | Signing you in; sending a six-digit code through our email delivery provider. Friends do not see it, and we do not use it for marketing |
| Sign in with Apple identifier and relay email, if Apple provides one | Signing you in with Apple |
| A push token for each phone, and whether it uses Apple’s test or production environment | Sending heart and friend-request notifications through Apple |
Apple handles purchases. Pip receives purchase confirmation, not your payment-card details. This covers Pip Plus, moonstones and one-time egg purchases. Coins are earned only.
Care packages arrive when you log a period. Their opening times may therefore hint at cycle activity, even though these records do not contain the logged period date. Check-in and comfort coins are recorded by day, so the ledger can show which days you checked in and which comforts you marked done. It does not contain your moods, symptoms or period dates.
Accepted friends see only your first name and pet. They do not see your cycle history, symptoms or moods. There are no public profiles or name searches.
4. Notifications
Pip notifications do not name your period, cycle or symptoms. Period heads-ups use indirect wording, such as “Today could be the day,” and can appear on your lock screen at your chosen time.
Daily reminders and period heads-ups are scheduled on your phone and are off unless enabled. The trial reminder is also local, two days before a free trial ends.
Heart and friend-request notifications use Apple Push. A heart notification can include the sender’s first name. Manage permission in iPhone Settings. Account deletion removes push tokens. Sign-out or erasure of a signed-in phone attempts to unregister its token; an offline or failed request can leave the registration until later successful reassignment.
5. Usage events, crash reports and security logs
Help improve Pip is optional and off unless you tick it during setup or turn it on in Settings. It controls usage-event collection and diagnostic uploads, used to improve Pip’s features and reliability. These pipelines stay off until you have also answered the age question as 13 or older.
Usage events describe setup steps, feature use, return visits, purchases and trials. Health-related examples include saving a check-in, logging a day and opening a care package. Events contain:
- random analytics and session IDs, separate from your account ID;
- the hour, event name and properties selected from fixed values;
- app/build and iOS versions, device class, language and text size;
- sign-in and subscription status; and
- age range: 13–17, 18–24, 25–34, 35–44, 45–54 or 55+. We do not ask for your birthday.
Events exclude your name, email and entered cycle values. The usage-event table does not store an account-ID link. Diagnostics use the same analytics ID. These records are not anonymous: identifiers and feature activity can still be personal information and reveal use of health-related features.
Crash, hang and performance reports come from Apple’s MetricKit. Reduced crash/hang reports include call stacks, exception and termination details, duration where relevant, app/OS/device information and the last recorded screen. That screen may be from the previous run. Daily reports cover launches, hangs, memory and processor use, app exits and foreground/background time. They exclude entered cycle values. Raw reports are stored with Supabase; no outside analytics or crash-reporting SDK receives them.
Changing your choice. Turning Help improve Pip off stops new collection and clears queued reports. It does not recall an upload in progress or delete earlier reports. Erase everything and Settings sign-out reset the choice and analytics ID; Pip asks again at the next setup. Restoring a backup brings back its saved choices, unless you changed a choice on this phone more recently; then your newer choice stays. Account deletion without phone erasure leaves the choice and ID in place. Requests and retention are in §8 and §9.
Support messages. We receive your email address, message and attachments when you contact us. “Send app details” lets you review an attachment before sharing. It includes app/iOS versions, hardware model, purchase status, backup status, pending-sync count and up to 200 recent log lines. The builder excludes saved cycle history, name, Pip code and analytics ID; anything you add yourself goes to your chosen recipient. We use this information to resolve your request.
Service and security records. Failed server requests can log the function, account identifier and error code. Our analytics-upload rate limiter uses IP addresses in memory without storing them. Supabase’s authentication and API gateway security logs do record IP addresses and are accessible to Supabase and our team. These records protect and troubleshoot the service. Slack alerts and web-delivery records are described in §6.
6. Where information comes from and who receives it
Information comes from you, your use of Pip, your phone and Apple’s services. Friend requests and hearts come from other users. Apple supplies sign-in, purchase, push and MetricKit information. Hosting, email and web-delivery services generate technical records. We do not obtain information from data brokers or public records.
| Who helps run Pip | Information and purpose | Processing locations |
|---|---|---|
| Supabase | Database, file storage, sign-in and server functions; account records, encrypted backups, sealed keys, usage/diagnostic reports and logs | Primary database and backup storage: US East. Provider logs: European Union. Other operational/support processing can occur elsewhere |
| Apple | Sign in with Apple, purchases, push delivery and MetricKit; sign-in tokens, transaction records, push tokens and notification text. Device backup is a separate Apple service | United States and other countries where Apple operates |
| Email delivery provider | Email addresses, sign-in codes and delivery/routing records to deliver and protect email sign-in | United States |
| Google Workspace | Support and privacy messages and attachments you choose to send | Google’s international infrastructure; storage and other processing are not limited to Canada |
| Slack | Operational service-failure alerts with service-level counts and technical details, excluding names, emails, account/analytics IDs and health-answer values | United States and other countries where Slack operates |
| Cloudflare | Pip’s website, friend-link pages and the shared image in sign-in emails. Handles IP addresses, requested URLs and technical request information; a friend-link URL can contain a Pip code | International hosting and delivery network |
Our team accesses these services from Canada. Provider support, server functions, service logs and content delivery can involve other countries. A primary storage region does not restrict every processing activity.
For content processed on our behalf, the data-protection terms for Supabase, Google Workspace and our email delivery provider address permitted uses, confidentiality, security and deletion. Providers may separately handle account and technical service information to operate, secure and maintain their services, manage billing and meet legal obligations. This includes our email delivery provider’s delivery and routing records. Those uses are not all governed solely by Pip’s instructions. Pip has no affiliates that receive your information.
Apple runs its platform services under its own terms and Privacy Policy. Deleting a Pip account does not delete Apple’s purchase records or your Apple Account.
Some providers use automated security tools, including AI. Our email delivery provider describes sampling emails for abuse checks. Pip’s sign-in emails do not contain cycle history, symptoms or moods.
We may disclose information in response to a binding legal requirement, including a backup we can unlock as explained in §2.
If Pip is involved in a merger, acquisition or sale of all or part of its business or assets, your information may transfer to the new owner as part of that transaction. The new owner must continue to honor this policy. We will notify you before your information becomes subject to a different privacy policy, and we will ask for your consent where the law requires it.
No ads. No tracking you across other apps. We never sell your data. We do not “share” personal information for cross-context behavioral advertising—advertising based on activity across different businesses—or use health information for advertising or marketing.
7. Countries and international transfers
Pip’s operator is based in Canada; its legal name and contact details are in §14. Our primary application database and backup storage are in the United States. Provider logs and other processing can take place elsewhere, as described in §6.
Information is sent outside Quebec and may leave your country. Other countries’ laws, including government-access rules, may differ from yours. We use contractual and security safeguards for information handled on our behalf. Contact us for information about these safeguards; we may redact confidential details.
8. Your controls and requests
| Control | What it does |
|---|---|
| Export my data, in Settings | Exports the saved app data on your phone as an unencrypted file. Store it carefully. It does not contain every server record or technical log |
| Delete account, in Settings when signed in | Requires a connection and successful server response. Deletes the current and previous server backup objects, then the account and associated profile, friends, requests, hearts, balances, ledger, inventory, claims, purchases, entitlements, server-held backup keys and device tokens. Apple sign-in token revocation is attempted when its authorization code is provided |
| Erase everything — never signed in | Clears the phone’s saved app data, signs out and resets the analytics ID. Pip also tries to delete the anonymous server account while it still has a connection and session. If offline or the request fails, the server account can remain; see §9 |
| Erase everything — signed in | Clears the phone’s saved app data, signs out and resets the analytics ID. The signed-in server account and backup remain until account deletion |
| Sign out, chosen in Settings | Offers to finish a backup, then resets this phone. If a backup fails, you can retry or choose to sign out anyway. The server account and backup remain |
| Help improve Pip, in Settings | Turns usage-event collection and diagnostic uploads on or off. It is off unless you chose it. See §5 for resets and earlier reports |
| Health information, in Settings | Shows that you agreed to Pip using your health information. Pip can’t track your cycle without it, so turning it off offers to erase everything on this phone and, if you are signed in, to delete your account and its backup |
| Period and check-in editors | Let you edit period dates and saved check-ins on your phone. The period editor also lets you delete a period |
Account deletion alone does not erase your phone history or reset the analytics ID. You can separately choose to erase the phone during deletion; that also requests removal of the local backup key. Ordinary Erase everything and Sign out retain that key in Keychain. Automatic loss or revocation of a sign-in session can leave phone history in place, so it is different from choosing Sign out in Settings.
If Erase everything could not reach our server, the old anonymous account stays there. We can’t link it to your phone after the erase. If it has no purchases, the monthly cleanup in §9 deletes it after one year without activity.
Deleting the app does not delete server records. Apple’s subscription controls are separate from Pip’s data-deletion controls.
You can request access, correction or deletion, including for server records outside the phone export, through the privacy contact.
Email privacy@pip.club with what you want to do and where you live. You do not need legal wording, a special subject line or a new account. If you use the Privacy request link in Settings, the email can include account and analytics IDs to help locate records. Those IDs help us find information; they do not prove your identity.
We use existing account information and ask only for additional information reasonably needed to verify you or an authorized representative. If you use Pip without signing in, or cannot access your account, contact us so we can assess another way to verify your request. You do not have to create an account. If we cannot reasonably verify it or identify the records, we explain the limitation and your available next steps.
Do not email cycle history, passwords or sign-in codes. We return personal records through a secure, verified channel.
We respond within the time required by the law that applies to your request; regional deadlines are described in §12 and the Consumer Health Data Privacy Policy. If a lawful extension is needed, we explain why and give the revised deadline within the original response period. Requests are free. If we cannot act on all or part of a request, we explain why and how to appeal or complain.
Where use of your information depends on consent, you can withdraw it. Withdrawal does not change whether earlier use was lawful. You can withdraw Help improve Pip in Settings at any time. Because tracking depends on your health information, withdrawing that consent means erasing it, as described in the table above. Signing out leaves an existing server backup in place; Delete account removes it.
Use the privacy contact to withdraw consent for a particular use or disclosure. We will stop the use covered by your withdrawal within the applicable deadline and explain any effect on the features you use. You can request deletion at the same time. We will check the account records linked to the account ID in your request. 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; records we cannot link follow the normal schedule in §9, and we explain any resulting limitation.
9. How long information stays
| Information | Retention |
|---|---|
| Cycle history, setup answers and age range on your phone | Until you delete the relevant entry or erase the saved data, including a reset through Settings sign-out. Account deletion without phone erasure can leave them on the phone. Deleting the app removes its app-container data; Keychain items are separate |
| Cycle estimates | Recomputed from source history, rather than saved as separate history or backup fields. Local notifications can retain scheduled dates until canceled or replaced |
| Pip’s encrypted backups, readable backup metadata and server-held sealed keys | Until account deletion; updates can retain a current and previous backup |
| Local backup key | Retained in Keychain through ordinary erase/sign-out; eligible for iCloud Keychain sync. Account deletion with phone erasure requests removal |
| Server account, sign-in, profile, pet, friends, requests, hearts, Pip code, balances, ledger, inventory, claims, purchases and entitlements | Until successful account deletion. A monthly cleanup also deletes anonymous accounts with no purchases after more than one year without sign-in or session activity. Accounts with purchases are excluded from that cleanup |
| Push tokens and their environment | Until account deletion or successful unregistration/reassignment. Offline or failed sign-out/erase requests can leave a registration in place |
| Raw usage events, including age range | Removed in whole monthly batches by a daily cleanup: roughly 13–14 months from the event date, plus the daily cleanup interval |
| Crash, hang and daily performance reports | Removed by a daily cleanup after 13 months from receipt, plus the daily cleanup interval |
| Operational alerts in Slack | Retained to investigate service failures, resolve related incidents and maintain service security. Retention depends on the incident, any ongoing investigation and applicable legal requirements |
| Our hosting provider’s daily database backups | Kept for 7 days, so a deleted record can remain in a recovery copy for up to 7 days after deletion. These copies are for service recovery. Encrypted health backups are stored as files, which are not included in these database backups. Applicable deletion requirements also cover copies held for us |
| Function, authentication and API gateway log history available to Pip | Available for 7 days under our hosting plan. Provider-held security or compliance records can follow different periods |
| Sign-in emails and delivery logs | Ordinarily retained by our email delivery provider for 30 days; its backup copies follow a separate seven-day cycle |
| Support and privacy correspondence | Retained to resolve the inquiry and any related complaint, appeal or dispute, and meet applicable legal obligations. The content and sensitivity of the message, whether the matter is closed and any required recordkeeping determine the period |
Provider deletion is not always immediate. For Workspace customer data that we have irrecoverably deleted, Google’s terms allow up to 180 days for deletion from its systems, unless law requires retention. Ending the service has a separate recovery period. Providers’ own account, billing, security and legally required records can have different retention periods; these are distinct from the Pip records in the table.
Changing or discarding an analytics ID does not delete earlier events or diagnostics. Those records follow their retention schedules unless a deletion request requires earlier action. The same applies to records already uploaded when you turn off Help improve Pip.
Privacy-request records are limited to what is needed to handle the request, any appeal and applicable recordkeeping obligations. They are not used for marketing. Extra verification information is kept only while needed to verify and resolve the request or meet a legal requirement. A legal hold or specific recordkeeping duty can require longer retention; that information is restricted to the relevant purpose.
10. Children and teens
Pip is intended for people aged 13 and older. New-user setup asks for an age range. Before that answer, Pip does not create a server account or send usage reports, and privacy choices made earlier in setup wait on the phone. Choosing “I’m under 13” ends setup and erases what was entered on the phone, including those choices; nothing about that answer is sent to us. A returning user can choose to sign in and restore an existing backup before that setup step. Technical reports may wait on the phone before upload. The available ranges are listed in §5. The range is self-reported; Pip does not ask for your birthday.
If you believe a child under 13 has provided information, use the privacy contact.
We review under-13 reports promptly. Once we establish that an account belongs to a child under 13, we stop collecting their personal information through Pip and delete the information we hold about them, except any limited records the law requires us to keep. We also ask the companies holding that information for us to delete it where required.
A parent or guardian may use the same contact to request action where the law allows them to act for a child. We check their identity and authority using only the information needed. We explain the outcome without giving automatic access to a teenager’s cycle history.
11. What setup asks for, and Pip’s estimates
You choose whether to sign in, buy something, add friends, enable reminders or turn on Help improve Pip. New-user setup requires your agreement to Pip using your health information and an age-range answer, then creates a server account. It also asks for a first name, pet name and whether you have tracked before. Cycle questions depend on your answers: regularity, usual period length and, for a regular cycle, usual cycle length require a choice when shown, including uncertainty options; a precise last-period date is not required. Goals, usual symptoms and comforts can be left unselected. Saving a check-in requires a mood; you do not need to save a check-in every day. An email address is needed for email sign-in; Sign in with Apple is an alternative. Notifications need your system permission. Usage-event collection is explained in §5.
Pip estimates the next period, cycle phases and patterns in your logged symptoms and moods from your own data on your phone. These are planning estimates, not decisions about your legal rights or eligibility for services. Pip does not provide fertility or contraception features. Check with a qualified health professional before making medical decisions.
12. Rights where you live
If you’re in Washington or Nevada
Read the separate Consumer Health Data Privacy Policy for health-data access, withdrawal, deletion and appeal rights.
If you’re in California
This notice at collection describes the categories Pip handles. Detailed fields, sources and recipients are in §§2–6. The retention schedule, including provider copies, is in §9.
| Category | Purpose | Retention |
|---|---|---|
| Sensitive health information: cycle history, health answers and related inferences | Tracking, planning and optional encrypted backup; related activity also supports rewards | Phone history until erase/app deletion; setup answers until erase; server backup until account deletion. Health-related activity follows the account/event periods in §9 |
| Identifiers, contact details and profile: account/Pip code, first name, pet, sign-in details and push tokens | Accounts, pets, sign-in and requested social notifications | Account and push-token periods and deletion limits are in §9 |
| Age range | Eligibility and usage analytics | Local and backup periods: §9; raw events: roughly 13–14 months plus cleanup |
| Commercial and social records: purchases, entitlements, rewards, inventory, claims, friends, requests and hearts | Delivering purchases, rewards and friend features | Until successful account deletion or qualifying anonymous-account cleanup, as explained in §9 |
| Usage records, device/session details and random analytics ID, if you turn on Help improve Pip | Understanding app use | Raw events: roughly 13–14 months plus cleanup |
| Crash, hang and performance reports; IP and function security logs | Understanding failures and protecting the service | Diagnostic reports: 13 months plus daily cleanup; other logs: §9’s additional schedule |
| Support correspondence and attachments | Responding to support requests | §9’s additional schedule |
The no-sale and no-advertising-sharing statements in §6 also cover information about people under 16.
Pip does not currently meet the thresholds for coverage as a business under the California Consumer Privacy Act (CCPA). Your health information remains protected by other applicable laws. The choices and request procedures described in §8 remain available.
If the CCPA applies to Pip and your information, you can request to know, access, correct or delete it. You can use an authorized agent where the law allows and exercise your rights without unlawful discrimination. Use the contact and request procedure in §8. Health information may have separate California protections even when the CCPA does not apply.
If you’re in another US state
Depending on the law that covers you, including Connecticut or Colorado law, you may have rights to access, correct, delete or obtain a portable copy of your information, withdraw consent, and appeal a refused request. Use §8’s contact and request procedure.
If we refuse your request, reply to our decision or use the privacy contact to ask for an appeal. No special subject line is needed. We will send a written decision with reasons within 45 calendar days of receiving your appeal, or sooner if required. If we deny it, we will include the applicable regulator’s complaint link or contact method.
If you’re in Canada or Quebec
You can request access and correction and challenge how we handle information. You can withdraw consent, subject to applicable legal or contractual limits and reasonable notice. Quebec also provides portability rights for eligible computerized information.
Under PIPEDA, access requests generally have a 30-calendar-day response period. Under British Columbia’s PIPA, the usual response period is 30 business days. Quebec access and correction requests have their own 30-day rule. Extensions are used only as the applicable law permits, with required notice. Use the contact and procedure in §8. You can contact the Office of the Privacy Commissioner of Canada, the Office of the Information and Privacy Commissioner for British Columbia, or the Commission d’accès à l’information du Québec, as applicable. Our privacy officer is in §14. Information leaves Quebec as described in §7.
Our privacy contact handles inquiries about requests, complaints, retention and safeguards. Access to personal information is limited to authorized people who need it for their work. You can ask for further information about these practices through the contact in §14.
If you’re in Australia
Where Australian privacy law applies, you can request access and correction and complain about how we handle your information. Use the contact and procedure in §8. You can also take a complaint to the Office of the Australian Information Commissioner, following its complaint process. Overseas locations are in §§6–7.
If you’re in New Zealand
Where New Zealand privacy law applies, you can ask for access to your information and request a correction. If a correction is not made, you can ask for a statement of the correction you sought to be attached. Use the contact and procedure in §8. Decisions on access and correction requests are generally due as soon as reasonably practicable and within 20 working days, subject to lawful extensions with notice. You can also complain to the New Zealand Privacy Commissioner. Information sent overseas is described in §§6–7.
Privacy complaints
Use the privacy contact to complain.
Tell us what happened and how we can contact you. We review the concern and explain the outcome, any action taken and the relevant regulator’s complaint route. If more time is needed, we explain why and provide an update. Applicable legal response deadlines still apply.
13. How we protect information
Production access is limited to authorized operators using two-factor authentication. Database rules limit which account can reach records. Writes go through server functions. Backup download links expire quickly and are restricted to the owner’s path. The master secret protecting server-held backup keys is kept separately from the database.
No security measure removes every risk. Someone who obtains both the stored data and the secrets protecting its keys could read the backups.
If a breach requires notice, we will notify affected people, regulators and any other required recipients using the methods and timing required by applicable law.
14. Changes and contact
We update this policy when our practices change and show the effective and last-updated dates above. For material changes, we provide notice through the app or another appropriate channel. Where a change requires fresh consent, we ask before beginning that use. A policy update alone is not consent to new health-data collection, use or sharing. You can request an earlier version through our privacy contact.
- Pip’s operator, responsible for your information: Thursday Horse Racing Inc., a federally incorporated Canadian company.
- Privacy requests and complaints: privacy@pip.club.
- Person responsible for personal information: our Privacy Officer, reachable at privacy@pip.club.