Privacy Policy

Version 1.2 · Effective 15 September 2026

The short version

• Your Apple Health data stays on your device. Only the daily totals for commitments you created are sent to our servers, and only to work out your own status.
• Your teammate sees the status of a commitment — nothing more — unless you specifically choose to share a progress band or exact numbers, one commitment at a time.
• We do not sell your data, do not use it for advertising, and do not track you across other apps or websites.
• No health value or target ever appears in a notification, an email, an analytics event, a crash report, or a log line.
• Privacy controls, pausing, blocking, and account deletion are never behind a paywall.

This summary is not the policy. The sections below are.

1. Who we are

Daypair is operated by Alexander Ouellet, a sole proprietor, referred to here as “we”, “us”, or “Daypair”. You can reach us at the addresses in section 16.

2. What this policy covers

The Daypair iOS app and the pages on this website. It does not cover Apple Health itself, the nutrition or fitness app you log in, or any other service you connect to Apple Health — those are governed by their own policies.

3. Information we collect

3.1 Account information

When you sign in with Apple we receive an account identifier and an email address. Apple’s Hide My Email gives us a @privaterelay.appleid.com relay address instead of your real one, and Daypair works exactly the same either way — we never use your email address as a key or an identifier for your data.

You may add a display name, which defaults to “Teammate”. Your one teammate sees it. You may add an avatar.

3.2 Settings

Your IANA time zone, so a “day” means your day and quiet hours land at the right time in your own zone; your unit preferences; and the timestamp of your confirmation that you are 18 or over. We do not collect your date of birth and do not calculate your age.

3.3 Apple Health data

With your permission, Daypair reads daily totals from Apple Health for the categories you choose. Access is read-only — Daypair never writes to Apple Health, and never asks to.

Apple requires us to name the specific data we read. It is exactly these nine categories, and nothing else: dietary energy consumed, protein, carbohydrates, total fat, fiber, water, steps, Apple Exercise Time, and active energy burned.

We ask for the first five when you set up Apple Health. Water is added only if you turn it on. The three activity categories are requested individually, and only when you create a commitment that needs one. You can change or withdraw any of this in the iOS Health app at any time.

We never read food names, meal entries, meal times, medical records, clinical records, prescriptions, or anything from Apple Health beyond the nine categories above.

Raw Apple Health samples never leave your device. They are held in memory while the app is open, combined into one total per day per category, and then discarded. What we receive is that daily total, together with which app it came from, how many samples went into it, and a checksum used to detect edits. We receive no individual sample and no time of day.

We also store which app you selected as the source for each category — for example the name and bundle identifier of your nutrition logger. This exists so we do not add up the same food twice when two apps have written to Apple Health.

3.4 Your commitments and results

The commitments you write, including the label you give them and the targets you set; and for each day, whether the commitment was met, a coarse progress band, and the evaluated value. You set your own targets. Daypair does not generate, recommend, or adjust nutrition or fitness targets.

3.5 Pacts, invitations, and check-ins

Your pact with one other person and its membership. Invitations are stored only as cryptographic hashes — the invite link and the short code exist in plain form only in the response that creates them, and we cannot recover them afterwards.

Check-ins are chosen from a fixed list of seven approved messages. There is no free-text messaging in Daypair, so there is no message content for us to hold. Acknowledgements are likewise chosen from a fixed list.

If you block someone we record that, with a category code. If you report someone we record the report as a category only — we deliberately do not collect a free-text description.

3.6 Device and notification information

If you enable notifications: your Apple push token, the device platform, app version and build, time zone, and when the app was last active.

3.7 Subscription information

If you subscribe to Daypair Pro: the state of your subscription, the product, the billing period, whether it will renew, and Apple’s transaction identifier. We never receive or store your payment method, card details, or billing address — Apple handles payment and tells us only whether your subscription is active.

3.8 What we do not collect

No advertising identifier (IDFA), no vendor device identifier (IDFV), no precise or coarse location beyond your time zone, no contacts, no photos, no microphone or camera data, no browsing history, and no biometric data. We do not use Apple’s App Tracking Transparency framework because we do not track you.

4. How we use your information

Only for these purposes:

• to work out your daily commitment status;
• to show your teammate the level you chose to share;
• to run the pact — invitations, membership, and check-ins;
• to send the notifications you turned on;
• to give you access to Daypair Pro;
• to keep the service secure and prevent fraudulent purchases;
• to answer your support requests;
• to prove that you gave the permissions you gave.

We do not use your information to build advertising profiles, to train machine-learning models, or for any purpose you did not ask for.

5. What we never do with health data

These are commitments, and they are also how the software is built:

• No sale of health data, ever, to anyone, for anything.
• No advertising, marketing, or use-based data mining with data gathered in a health, fitness, or medical context — including anything read from Apple Health.
• No cross-app or cross-site tracking.
• No health value or target in any notification, email, analytics event, crash report, or log line. Notifications carry one of seven fixed sentences and no numbers.
• No meal names or meal-level records collected at all.
• No health data in iCloud.
• No public profiles, leaderboards, or feeds. A pact is two people.

6. Sharing with your teammate

This is the only person-to-person sharing in Daypair, and you control it per commitment.

Status only is the default for every commitment. Your teammate sees a status — met, still open, not met, or no recent data — and when it was last updated. No number.

You can raise a single commitment to:

• a progress band, a coarse range rather than a figure; or
• exact totals and targets, which requires a separate, explicit choice for that commitment. Choosing it once does not apply it to anything else.

Two things worth knowing about how this is enforced. First, a status-only or progress-band record cannot physically hold a number — the database rejects the row, so a mistake in our code cannot leak an exact value to someone you granted status-only. Second, when you withdraw sharing, pause, leave a pact, or block someone, the shared records are deleted immediately, in the same operation — not hidden, not scheduled for later cleanup.

Your teammate never sees your food diary, your meal names, which app you log in, your email address, or any commitment you did not share.

7. Service providers

Three companies process data on our behalf. This is the complete list.

• Supabase, Inc. — authentication, database, and server functions. Receives all of the information in section 3, stored in the United States.
• RevenueCat, Inc. — subscription and entitlement management. Receives your account identifier and your purchase and subscription data. No health data, no display name, no email address.
• Apple Inc. — Sign in with Apple, the App Store and payments, push delivery, and Apple Health on your device. Receives your Apple account identifier, purchase records, and push tokens with notification content that contains no health values.

Each of these providers is contractually required to protect your information to the same standard as this policy requires of us, and to use it only to provide the service to us. We do not permit them to use your data for their own purposes.

We use no analytics provider, no crash-reporting provider, no advertising network, and no data broker. No analytics software is installed in the app.

We may also disclose information if the law requires it, to enforce our terms, or to protect someone’s safety — and if a business transfer ever happens, we will give notice before your information becomes subject to a different policy.

8. How long we keep things

• Raw Apple Health samples: never stored.
• Invitation hashes: cleared 30 days after the invitation expires, is used, or is revoked.
• Check-ins: deleted after 90 days.
• Device records and push tokens: deleted after 90 days without activity, and when you sign out.
• Shared records visible to your teammate: deleted immediately when you withdraw sharing, pause, leave, or block.
• Your account, commitments, results, and consent records: for as long as your account is open.
• Subscription and transaction records: for as long as your account is open, and afterwards where accounting or fraud-prevention law requires.

Please note: Daypair Pro shows a longer history than the free tier. That is a limit on what the app displays, not a deletion schedule. Your own records are kept while your account is open regardless of which tier you are on.

When your account is deleted, everything tied to it is removed in a single operation. One exception: Apple’s transaction identifier remains in our billing records, detached from you and from any other information about you, because we need it to reconcile purchases and to prevent the same purchase being claimed twice.

9. Your choices and rights

You can, at any time:

• change or withdraw Apple Health permissions in the iOS Health app;
• change what each commitment shares, or stop sharing it;
• pause a pact, leave it, or block the other person;
• turn notifications off, wholly or by type, and set quiet hours;
• ask us for a copy of your information, or ask us to correct or delete it.

Depending on where you live you may also have the right to confirm whether we hold your data, to receive a list of the third parties who received it, to withdraw a consent you gave, and to appeal a refusal.

To exercise any of these, email privacy@daypair.app. We will respond within 45 days. If we genuinely need longer we will tell you why within that period and may take up to 45 additional days. There is no charge, and we will not treat you differently for asking.

If we refuse a request we will tell you why and how to appeal. If an appeal is refused, we will tell you how to complain to your state Attorney General.

10. Deleting your account

In the app: Settings → Account → Delete account. You will be asked to confirm once. When you do, we delete your account and everything associated with it, subject to the single exception in section 8.

This happens immediately and cannot be undone. There is no waiting period and no window in which we hold your data in case you change your mind — when the confirmation completes, it is already gone. Your teammate’s view of you disappears in the same operation, any pact you were in ends, and any unused invitation into it stops working.

You can also email privacy@daypair.app and ask us to do it, which is the route to use if you can no longer open the app. We will verify it is you and complete it within the 45-day period described in section 9.

Deleting your Daypair account does not cancel an App Store subscription. Those are separate systems and only you can cancel a subscription, in your Apple account settings. The app shows you how to do both.

11. Security

Access to your data is enforced at the database level, per row, so a request can only ever reach the records belonging to the person who made it. Your teammate’s access comes from separate records built specifically for them, holding only what you chose to share. Invitations are stored as hashes. Everything travels over TLS. Payments are handled by Apple and never touch our systems.

No system is perfectly secure, and we will not claim otherwise. If a breach affects your health information we will notify you as the FTC Health Breach Notification Rule requires — without unreasonable delay and no later than 60 days after we discover it — and notify the FTC and, where required, the media.

12. Children

Daypair is for adults 18 and over, and you confirm your age when you set it up. It is not directed at children and we do not knowingly collect information from anyone under 18. Our age check is a confirmation you give us during setup rather than something we can verify. If you believe someone under 18 is using Daypair, email us and we will delete the account.

13. Washington, Nevada, and other state health-privacy laws

If you are in Washington or Nevada, or your consumer health data is collected there, separate laws apply and we publish a separate Consumer Health Data Privacy Policy for them, as those laws require. That document, not this one, governs consumer health data for those purposes.

If you are in California, the categories we collect, our purposes, and our disclosures are in sections 3, 4, and 7. We do not sell personal information and do not share it for cross-context behavioral advertising. You have the rights described in section 9 and we do not discriminate against anyone who exercises them.

14. Where your data is, and which law applies

Your data is stored in the United States. If you use Daypair from outside the United States, you are sending your information to the United States, where privacy law differs from your own country’s. This policy is governed by the laws of California, without regard to its conflict-of-laws rules.

15. Changes

If we change this policy we will raise the version number and update the effective date at the top. If a change is material — a new category of data, a new purpose, or a new recipient — we will tell you in the app and ask for your agreement before the change applies to you. We will not collect, use, or disclose a category of data, or share it with a party, that this policy does not already describe.

16. Contact

• Privacy questions, and all rights requests under section 9: privacy@daypair.app
• Support: support@daypair.app

Operated by Alexander Ouellet, sole proprietor.