Privacy Policy

What we collect

• Your email address and password. Used to sign you in. Passwords are stored hashed by our authentication provider — we never see them.
• Your display name, shown to your partner.
• Your partnership. The invite code you shared or entered, and which account you are linked to.
• Your prompt responses. Every yes, no, or maybe you swipe, and any prompts you write yourself.
• Whether you have children, a single yes/no used only to decide whether to show childcare prompts.
• A push notification token, if you allow notifications. It identifies your device to Apple's and Google's push services so we can tell you when your partner adds something. We remove it from your account when you sign out, and the next time the app starts up after you turn notifications off in your phone's settings.
• Notification records — which notification we owe you, when it is due, and whether it was sent.
• A record of invite codes you enter, kept only to rate-limit code guessing. It stores who tried and when, not what was typed.
• Crash and performance diagnostics. When the app or website errors, we receive the error, a stack trace, basic device and OS information, and your account ID — not your email address — so a report can be tied back to the account that hit it. We also sample roughly one session in five for performance timings: which screens were opened and how long requests took. Your prompt responses are not included in either.
• Sign-in records. Our authentication provider logs sign-in and password-reset events, including the IP address they came from, as a security measure.

We do not collect your location, contacts, photos, health data, or advertising identifiers. There are no advertising or ad-tech trackers in the app, and nothing here is used to profile you or build an audience.

Who can see it

Your partner sees your display name and your prompt responses. That is the point of the app — share accordingly. While you are linked, their app can also read the rest of your account row, including the email address you signed up with; the app never displays it, but treat it as visible to them.

No other user. Access is enforced in the database itself: your rows are readable only by you and the partner you are actively linked to. If a partnership ends, the link is severed and neither of you can read the other's responses from that point on.

We can. Running the service means we hold administrative access to the database, which is how account deletion and support work at all. We use it to operate and fix the app, not to read your responses for any other purpose.

We use three service providers to run the app: Supabase (database and authentication), Expo (push notification delivery), and Sentry (crash reporting). They process this data on our behalf and for no other purpose.

Deleting your data

Clear your responses: Settings → Clear All My Responses. This deletes every answer you have given. Your account and partnership stay.

Delete your account: Settings → Delete Account. This immediately and permanently deletes your login, your profile, your email address, your push token, your responses, and your pending notifications. Your partnership ends.

One thing survives on purpose: prompts you wrote yourself stay visible to your partner, with your authorship removed, because deleting them would also delete the answers your partner gave to them. Nothing identifying you remains attached.

Two things outlive the delete. Crash and performance reports sit with Sentry until their retention window expires — up to 90 days — carrying the deleted account's ID but no email address or responses. Sign-in logs age out on our authentication provider's own schedule. Write to us if you need either cleared sooner.

Children

PreParty is for adults in a relationship. It is not directed at children, and we do not knowingly collect data from anyone under 13.

Changes

If this policy changes in a way that affects what we collect or who sees it, we will update the date at the top of this page.

Contact

Questions, or a request to access or delete data you cannot reach from inside the app: privacy@preparty.app.