heartpact Get the app

Privacy Policy

Last updated: 26 October 2026

Heartpact is a private space for two people. You link phones with your partner, set each other exercise dares, share an album, and keep track of the things that matter to you both. A lot of what you put into Heartpact is personal, and some of it is very personal. This policy explains, in plain English, what we collect, why, who can see it, and how you stay in control.

The short version:

1. Who we are

Heartpact is run by HeartPact, 651 N Broad Street, Middletown, Delaware 19709, USA ("we", "us"). We are the controller of the personal data described in this policy. If you have a question or want to use any of your rights, email us at [email protected].

This policy covers the Heartpact Android app, our website and the service behind them. You must be 18 or older to use Heartpact.

2. What we collect and why

We only collect what we need to make Heartpact work. The table shows each kind of data, what we use it for, and who can see it. "Us" means our staff through our admin tools (see section 5).

Data Why we need it Who can see it
Account details: email address, a password (stored only as a salted hash) or your Google account ID if you sign in with Google, display name, date of birth, gender (you can choose "prefer not to say"), the country you live in (chosen when you sign up, and changeable under Us), the language of your app, time zone, map colour, and your profile picture if you add one (the picture itself, at most 400 KB, stored with your account in our database). To create your account, sign you in, keep it secure, check that you are 18 or over, send password reset codes, show times in your own time zone, write notifications and emails in your language, show photos, food tips and game versions from your part of the world, and set up features such as cycle tracking (choosing Woman turns it on). You. Your partner: your name, profile picture and map colour, and your time zone, so that a dare they set for you rings at your local time. Us: your email, name, time zone, sign-in method, whether your email is verified, when you signed up and were last active, and your country (in totals by country, and in the live feed when you sign up). Never your date of birth or gender.
Your couple link: invite codes and links (stored only in hashed form, valid for 48 hours), when you linked and when the link ended. To connect you with your partner, and to end the link cleanly if either of you unlinks. You and your partner. Us: whether you are linked, to whom (by email and name), and when you linked or unlinked, including in the live feed (for example, "Maya & Theo linked up").
Dares: the exercise, target, time, time zone and grace period; for each attempt, its status and times, the number of reps or seconds counted, a confidence score, form faults, reps that were too fast, surprise check-ins passed and missed, reps counted while the phone was moving, seconds out of frame, a Google Play Integrity result, and any short note you add when asking to be let off. To ring the alarm at the right time, decide whether a dare is done, and show you both the result, your streaks and your history. You and your partner (your partner can also watch your count live while you exercise). Us: how many dares were set, completed or missed, on which days and for which exercise, including in the live feed with both your names (for example, "Maya did the dare · squats, set by Theo"); and, across everyone, the times, confidence and failed checks of dares, as totals.
Shared album: photos and videos you choose to sync, their thumbnails, captions, the date taken, file type and size; how many items are waiting to sync on your phone. To keep your shared album, show it to both of you, apply storage limits, and remind you when photos are waiting. You and your partner. Us: how many items you have shared, on which days, and how much space they use.
Daily questions, games and messages: your answers to daily couple questions, your moves, answers and drawings in games, scores (including your 0 to 100 score for each Heart to heart skill round), and any messages you send through Heartpact. To run these features for the two of you. You and your partner. Your partner sees your daily answer only once they have answered too, and your score for a Heart to heart round once they have played it too. Us: how many questions you have answered and on which days, which types of game you finished and when; and, across everyone, Heart to heart scores as numbers in charts. Never what you wrote or drew.
Food log: meals and snacks, calories, optional protein, carbs and fat, your daily targets and sharing setting; for each photo estimate, a record of when it ran, the photo's size and type, the AI model used, how much processing it took and how long, the result and whether it worked. The record is made as soon as the photo is sent, so the scan counts towards your daily limit however it ends. We do not keep the meal photo itself. To keep your food log, estimate meals from photos, apply the daily scan limit, keep an eye on what estimates cost, and show your partner what you have chosen to share. You. Your partner: depends on your setting: nothing, daily totals only (the default), or full detail. Us: how many meals and scans you have logged, and on which days.
Cycle tracking (health data): period start dates, average cycle and period length, and daily logs of flow, symptoms, mood, whether you had sex and used protection, and notes. To show your cycle, predict upcoming dates, tell you when a period is late, and share what you choose with your partner. You. Your partner: depends on your setting: nothing (the default), predictions only, or predictions plus your logs. Predictions include that your period is late, and by how many days. Shared logs show the date, flow, symptoms, mood and notes, only from the day you linked, and never whether you had sex or used protection. Us: only whether the feature is in use, never the details.
Pregnancy (health data): due date, appointments (title, time, place and notes) and kick counts. To run pregnancy mode for you and, if you choose, your partner. You. Your partner: only while the pregnancy is active, you share it (sharing is on unless you switch it off), and you are still linked with the partner you started it with. Us: only whether the feature is in use, never the details.
Location: your latest position, its accuracy and when your phone took it, whether you are sharing, when your phone last checked in, and when a pause ends. To show you and your partner to each other on the map while you both share. You. Your partner: your position only while you are both sharing; your sharing status (off, sharing or paused) at all times. Us: only how many people are sharing, never where anyone is.
Notifications and devices: your notification history (title and text), notification preferences and quiet hours, your phone's push token, platform and app version, and when it was last seen. To deliver alarms and notifications to your phones, respect your preferences, and stop sending to phones that are no longer in use. You. Us: your devices' platform, app version and when they were last seen. We never show push tokens in full.
Subscription: the Heartpact Plus product, its status (for example active, cancelled but paid up, in a grace period or on hold after a failed payment, paused or expired), expiry date, whether it auto-renews, and the Google Play purchase token; and any complimentary Plus we give your couple, with its reason and end date. To check your purchase with Google, unlock Plus for you and your partner, and handle refunds or support requests. You. Your partner: that your couple has Plus. Us: yes, to manage payments and support, including when Plus started or ended (also in the live feed). We never see your card or payment details; Google handles those.
Usage: when you were last active, which days you used the app, and when you did things in it (for example, when a dare was done or a meal logged). To understand how Heartpact is used (for example, how many people were active this week, or how far new couples get), help with support, and keep it running well. Us, as described in section 5.
Security signals: the IP address a request comes from. To limit repeated failed sign-ins, sign-ups, password resets and invite code guesses. Nobody. It is held briefly in our server's memory (an hour at most) and not written to our database.
Account deletions: that an account was deleted, when, and whether it was one of our test or team accounts. Nothing that says whose it was. To count how many people leave. Us, as a count and in the live feed ("An account was deleted").

Our legal bases

If you are in the UK or the European Economic Area, the law asks us to say why we are allowed to use your data:

3. What stays on your phone

When a dare rings, your phone's camera counts your reps. The pose detection (Google's open-source MediaPipe) runs entirely on your phone, using a model built into the app. Camera frames are never stored and never uploaded, not to us and not to anyone else. When you finish, the app sends us only the numbers listed above: the count, the confidence score and the form and fairness checks.

Other things that stay on your phone:

The app asks for camera, notification, alarm, location and (for album uploads) foreground service permissions. You can change any of these in your phone's settings; the related feature will stop working until you allow it again. Heartpact does not ask for permission to read the location embedded in your photos.

On our website, a language you pick is remembered in your browser. The pictures on the home page are chosen from the time zone your device reports; that happens in your browser and nothing is sent to us.

4. What your partner can see

Heartpact is built for two, so your partner sees a lot of what you do in the app. In particular:

When you unlink, your partner stops seeing all of this. See section 10 for what happens to shared things after a couple ends.

5. What our staff can see

A small number of people who run Heartpact use an admin dashboard. It shows account details, counts, and when things happened, with names:

The dashboard never shows what you wrote, photographed, drew or logged: no photos, captions, answers, messages, drawings, meals, cycle or pregnancy details, or location. There is no admin function that returns any of it.

Accounts we use for testing, and our team's own accounts, can be marked as internal. They work as usual but are left out of every chart and total.

Admins can help with your account: disable or re-enable it, sign you out everywhere, email you a password reset code, give your couple complimentary Plus, refund or cancel a Google Play subscription, or delete your account. Every admin sign-in and action is recorded in an audit log with who did it, when, why and from which IP address. Admins sign in with a password and a one-time code from an authenticator app, and must enter a fresh code again before disabling or deleting an account, refunding or cancelling a subscription, giving Plus, or marking an account as internal.

The people who maintain our servers could, in principle, reach the database directly. They do so only when it is needed to keep Heartpact running, fix a problem, or meet a legal obligation.

6. Third-party service providers

We use a few trusted providers to run Heartpact. They process data only on our behalf or to provide the specific service described, and we give them only what that service needs.

Provider What it does What it gets
Our hosting provider (Railway) Runs our servers and database. All the data described in section 2, stored on our behalf.
Cloudflare (R2 storage) Stores the photos and videos in your shared album. The files and thumbnails you sync. Your phone uploads and downloads them directly using short-lived links.
Cloudflare (Pages) Serves our website, heartpact.me. The requests your browser makes to the website, as any web host does.
Anthropic Estimates calories and nutrients from a meal photo, when you choose to scan one. The meal photo (shrunk to at most 1600 pixels and re-encoded, which removes embedded details such as location), any notes you add about the meal, and the country on your account so it can think of local dishes first, sent from our server. It is not sent with your name or email, and we do not store the photo.
Google: Firebase Cloud Messaging Delivers notifications and dare alarms to your phone. Your phone's push token and the notification itself, which can include your partner's name and a short line of text.
Google: Sign-In Lets you sign in with your Google account, if you choose to. We receive your Google account ID, email address, whether Google has verified it, and your name.
Google: Play Billing and the Play Developer API Sells and manages Heartpact Plus subscriptions, and handles refunds. Google handles your payment. We exchange the purchase token, product and an anonymous account reference with Google to confirm and manage the subscription.
Google: Play Integrity Confirms that a finished dare came from the genuine Heartpact app on a genuine device. Google checks your app and device. We send Google the resulting token to decode, and keep only the outcome (passed, failed, missing or not checked).
Google: Maps Draws the map when you share location. The Google Maps component in the app loads map tiles for the area on screen.
Google Play services: location Works out your position on phones older than Android 12, while you share location. Your phone's location provider, run by Google Play services on your phone. We receive only the position the app sends us.
Our email provider (Resend) Sends password reset codes. Your email address and the code.
Word-check services: Genderize.io, OpenStreetMap Nominatim and the Free Dictionary API Check whether an answer in the "I call on" game is a real name, place or word. The single word being checked, sent from our server. Nothing that identifies you.
Open Trivia Database Supplies trivia questions for some games. Nothing about you; we only download questions.

Each provider handles data under its own terms and privacy policy. We may also disclose data if the law requires it, to protect someone's safety, or as part of a merger or sale of our business, in which case this policy would continue to apply to your data.

7. Health data: cycle and pregnancy

Cycle and pregnancy information is health data, which the law treats as especially sensitive. We handle it with extra care:

While your pregnancy is shared, your partner can add appointments to it, and change or delete the ones they added. Those appointments are part of your record and stay with you, even if your partner later deletes their account; what they wrote is then erased (the title becomes "Appointment", and the place and notes are removed).

Cycle predictions and pregnancy information are for planning only. They are not medical advice and must not be used as contraception.

8. Location

When you stop sharing, your last position is wiped straight away. When a couple ends, both partners' location records are deleted. If your sharing lapsed because your phone went quiet, your last point stays stored, hidden from your partner, until you share again (when it is thrown away) or until it has gone untouched for 7 days, when it is deleted automatically.

9. How long we keep data

We keep your data for as long as your account exists, unless something below says otherwise. When you delete your account, it is erased as described in section 10.

10. Unlinking and deleting your account

When a couple ends

Either partner can unlink at any time, without the other's permission. When that happens:

Deleting your account

You can delete your account at any time:

Accounts that sign in with Google confirm with their email address instead of a password.

Deletion is immediate and permanent:

Deleting your account does not cancel a Google Play subscription. Cancel it in Google Play first. If you have one that will renew, the app warns you before you delete.

11. Downloading your data

You can download a copy of everything we hold about you as a single file (JSON format) by emailing [email protected] from the address on your account. It includes:

It leaves out your partner's data (their messages, answers, food log and uploads belong to them) and security secrets such as your password hash, push tokens and purchase tokens.

12. Your rights

Depending on where you live, you have some or all of these rights:

If you are a California resident, or live in another US state with a privacy law, you have the right to know what personal information we collect, use and disclose; to access, correct and delete it; and not to be treated differently for using these rights. We do not sell your personal information, and we do not share it for cross-context behavioural advertising. We use sensitive information, such as health and precise location data, only to provide the features you asked for.

To use any right, email [email protected] from the address on your account. We may need to confirm it is you. We reply within one month (or the time your local law sets), and we do not charge for reasonable requests.

13. Children

Heartpact is for adults only. You must be 18 or older to create an account. We ask for your date of birth when you sign up and do not create an account for anyone under 18. We do not knowingly collect data from anyone under 18. If you believe someone under 18 is using Heartpact, tell us at [email protected] and we will delete the account.

14. Security

We work hard to protect your data. For example:

No system is perfectly secure. If we learn of a breach that affects you, we will tell you and the authorities as the law requires.

15. International transfers

We are based in the United States, and our servers are in the eastern United States (Railway's US East region). If you use Heartpact from outside the United States, including from the UK or the European Economic Area, your data is transferred to the United States. Some of our providers, including Google, Cloudflare and Anthropic, may also process data in other countries. Where the law requires it, we rely on recognised safeguards for these transfers, such as the European Commission's Standard Contractual Clauses and the UK's equivalent, or an adequacy decision.

16. Changes to this policy

We will update this policy when Heartpact changes. If a change is significant, we will tell you in the app or by email before it takes effect. The date at the top always shows when it was last updated.

17. Contact us

HeartPact
651 N Broad Street, Middletown, Delaware 19709
USA
Email: [email protected]