Privacy policy

Updated 18 November 2026 (the waitlist). Effective October 24, 2026

The short version

Who we are

Meanwhile is run by Jens Parfitt, a sole trader based in London, UK, trading as Meanwhile (“we” or “us”). We’re the data controller for the personal data described here, under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

Questions, requests or worries: email hello@joinmeanwhile.com. A real person reads every message.

What we collect

This is the complete list of what the Meanwhile app stores about you.

Data the app stores, and why
WhatDetailsWhy
Your account Your email address and password. Your password is handled by our sign-in provider, Supabase Auth, and stored only as a one-way hash, so nobody (including us) can read it. We also store when you signed up and last signed in. To create your account and let you sign in.
Sign in with Apple If you choose it, Apple gives us an identifier for your Apple Account and an email address. That can be a private relay address (ending in privaterelay.appleid.com) that forwards to your real inbox. Apple may also share your name the first time you sign in; we keep only your first name. To sign you in without a password.
Your profile Your first name; the city you type (we never use GPS); your phone’s time zone (for example, Europe/London), which updates when you open the app after traveling; and your status (for example, “At the gym”) with the time you set it. So your partner can see your name, your local time and what you’re up to.
Notification settings Which notifications you want (taps, the daily question, moments, countdown changes) and the hour for your daily question reminder. To send only the notifications you’ve chosen, at your local time.
Pairing The invite codes you create (when each was made, when it expires, and who used it), which couple you’re in, and when you joined. To connect you with your partner, and only your partner.
Taps Who sent each “thinking of you” tap, and when. To deliver taps and show your recent ones.
Daily question answers The text of your answers, which question and day each one is for, and when you answered. To show them to your partner once you’ve both answered, and to keep your history and streak.
Countdown The date you’ll next be together, an optional label, and who last changed it and when. To show you both the same countdown.
Moments Photos you choose to share (resized and saved as a JPEG on your phone before upload), notes and captions, the day you posted, and each photo’s dimensions. Photos are kept in a private storage area that only your couple can reach, through links that expire. To build your private timeline together.
Notification tokens A push token for each phone you sign in on, which device platform it is, and when it was last updated. To deliver notifications to your phone.
Security records Failed invite-code entries (an internal ID and a time), a log of question reminders sent (so you get at most one a day), and technical logs kept by Supabase, which include IP addresses, device and app details, sign-in events and request times. To stop code guessing and abuse, keep accounts safe, and fix problems.
Support emails Your email address and whatever you tell us. To help you.

Things you write and share can be personal. Answers, notes and photos might touch on your health, beliefs or relationship. We treat everything you share as private: we don’t analyze it, profile you with it, or use it for anything except showing it to your partner.

Crash reports

If the app crashes or hits an error, it sends a crash report to Sentry (Functional Software, Inc.), our crash-reporting service. A report includes the error and where in the code it happened, your device model, operating system and app version, and the time. We set it up so reports don’t include your name, email address, IP address, answers, notes or photos. We use these reports only to find and fix bugs.

Why we use it (our lawful bases)

Purposes and the UK GDPR basis for each
PurposeLawful basis
Running Meanwhile for you: your account, pairing, sharing with your partner, and the notifications you’ve turned on Contract. We need this data to provide the app you signed up for (Article 6(1)(b)).
Keeping Meanwhile safe: rate limits, protection against code guessing, security logs, and investigating misuse Legitimate interests. Keeping your account and the service secure (Article 6(1)(f)).
Finding and fixing crashes Legitimate interests. Keeping the app reliable (Article 6(1)(f)).
Answering your support emails Legitimate interests, or contract when it’s about your account.
Meeting legal obligations, such as responding to a valid legal request Legal obligation (Article 6(1)(c)).

Notifications, photo access and camera access are also controlled by your phone’s permissions. We ask for notifications after you pair, and for photos only when you pick one. You can change these any time in your phone’s settings.

What we don’t do

Who can see your information

The companies that help us run Meanwhile

Service providers and what they handle
CompanyWhat they doWhere
Supabase, Inc. Hosts our database, sign-in, photo storage and server functions. Everything in the table above is stored here. Ireland (EU – Dublin region)
Expo (650 Industries, Inc.) Delivers push notifications through the Expo Push Service. It receives your push token and the notification text, which contains a first name and what happened (for example, “Sam is thinking of you.”), never your answers, notes or photos. It then passes them to Apple or Google for delivery. When the app checks for updates, Expo also receives a random installation ID, the app version and the device platform. United States
Apple Distributes the app (App Store and TestFlight), delivers notifications to iPhones through the Apple Push Notification service, and runs Sign in with Apple. Apple handles App Store data under its own privacy policy. We only see summary statistics, plus crash reports if you’ve chosen to share them with app developers in your iPhone settings. United States and worldwide
Google Delivers notifications through Firebase Cloud Messaging, for devices that use Google’s push service. United States and worldwide
Sentry (Functional Software, Inc.) Receives crash reports as described above. United States, or the EU if we choose Sentry’s EU data region

Each of these companies may only use your data to provide its service to us, under a data processing agreement. Apple acts as a separate controller for its own App Store services.

Data outside the UK

Your account and everything you share are stored in Ireland, in the EU. The UK recognises EU data protection as adequate, so no extra safeguards are needed for that. Some providers above (Expo, Apple, Google and Sentry) may process the data they handle in the United States or elsewhere. When personal data leaves the UK, we rely on the UK–US Data Bridge where the company is certified under it, or on contracts approved for UK transfers: the UK International Data Transfer Agreement, or the UK Addendum to the EU Standard Contractual Clauses. Email us if you’d like more detail.

How long we keep it

Retention periods
DataKept until
Account, profile and notification settingsYou delete your account.
Shared couple data: taps, answers, moments and photos, and the countdownEither of you unpairs or deletes their account. Then it’s deleted for both of you.
Invite codesYou delete your account. A code stops working after 7 days or once it’s used.
Notification tokensYou sign out, delete your account, or Apple or Google tells us the token no longer works.
Failed code entries and the reminder logUp to 14 days.
Supabase technical logsA short period (currently about a day), then deleted automatically.
Crash reportsUp to 30 days.
Support emailsUp to 12 months after your conversation with us ends.

Deleting is immediate and complete in our live database and photo storage. The only leftovers are the short-lived security records above, which hold just an internal ID and a time, link to nothing once your account is gone, and clear within 14 days. Copies can remain in our hosting provider’s encrypted backups for a short period until those backups are overwritten automatically. We never restore deleted accounts from backups.

Unpairing and deleting your account

Delete your account

In the app, go to Settings → Delete my account and confirm. Settings is the gear at the top of the Home screen. This immediately deletes your sign-in, profile, answers, moments and photos, taps, status, countdown, notification tokens and invite codes, and ends your pairing.

Because answers, moments, taps and the countdown live in the space you share, that whole shared space is deleted for both of you. Your partner keeps their own account and can pair again.

If you signed in with Apple, you can also stop using your Apple Account with Meanwhile in your Apple Account settings, under Sign in with Apple.

Can’t get into the app? Email hello@joinmeanwhile.com from the address on your account and we’ll delete it for you.

Unpair

Go to Settings → Unpair. You both keep your accounts. Your shared answers, moments and photos, taps and countdown are deleted for both of you, and your partner gets a quiet notification that you’re no longer paired. Your own profile stays with your account.

Delete one moment

Long-press a moment you shared on the Moments tab and choose Delete. It disappears for both of you, photo included.

Your rights

Under UK data protection law you can ask us to:

Email hello@joinmeanwhile.com from the address on your account. It’s free, and we’ll reply within one month. We may ask you to confirm it’s really you first.

If you’re unhappy with how we’ve handled your data, please tell us so we can put it right. You also have the right to complain to the UK Information Commissioner’s Office (ICO) at ico.org.uk or on 0303 123 1113. If you live outside the UK, you may also be able to complain to your local data protection authority.

Age

Meanwhile is for people aged 16 and over, and it isn’t directed at children. If you believe someone under 16 has an account, email us and we’ll delete it.

Security

No system is perfect. If a breach puts your data at risk, we’ll tell you and the ICO as the law requires.

This website

This site has no cookies, no analytics and no trackers. It’s hosted by Cloudflare, which processes visitors’ IP addresses to deliver the site and protect it from attacks. The fonts load from Google Fonts, so your browser connects to Google, which receives your IP address.

On an invite page (a link like /pair/?code=…), the code is shown by your own browser and our page doesn’t send it anywhere. Like any web address, the link itself reaches Cloudflare’s servers when you open it. Codes work once and expire after 7 days.

The waitlist

If you join the waitlist on this site, we keep your email address, the date you joined, where you came from (for example “instagram”, from the link you followed) and the wording you agreed to. We use it only to email you about Meanwhile’s launch and early access. Our lawful basis is your consent, which you can withdraw any time.

Your email is stored with Supabase (in Ireland, see above). Supabase also receives your IP address when you submit the form, to deliver and protect the service. When we send the launch emails, the email provider we use receives your address to deliver them; we’ll name it here before we send anything.

Every email has an unsubscribe link. To leave the list or have your address deleted, email hello@joinmeanwhile.com. We delete the list once Meanwhile has launched and the launch emails have gone out, or sooner if you ask.

Changes and contact

If we change this policy, we’ll update the date at the top. If the change is significant, we’ll also tell you in the app before it takes effect.

Contact: Meanwhile, London, UK. Email hello@joinmeanwhile.com.