Pause for Two privacy policy
Last updated: 2 November 2026
Pause for Two keeps your names and your agreement on your phones. Our server never receives them.
Who is responsible
OORUK Engineering is the controller of the personal data in this policy. For questions or requests about your data, write to privacy@ooruk.io.
Data that stays on your phones
- Your names.
- Your agreement.
- The pairing key. Your phones exchange it through the pairing code. The pairing key encrypts the data that the server must pass on but must not read.
- The camera image of the pairing code. The phone reads the code and keeps no image.
Pause for Two has no accounts. We do not ask for your email address, phone number or name.
Data that our server keeps
| Data | Purpose | Kept until |
|---|---|---|
| A random pairing number and the side of each phone | To connect your two phones. | The pairing ends. |
| A hash of a random secret for each phone | To identify each phone when it sends a request. | The pairing ends. |
| A notification address for each phone, from Apple or Google | To send notifications to your phones. | The pairing ends, or Apple or Google reports that the address is no longer valid. |
| The platform and model of each phone, for example "iPhone15,2" | To find notification problems on specific phone models. | The pairing ends. A copy stays in the usage records. |
| Whether notifications are on for each phone | To find notification problems. | The pairing ends. |
| Whether each person has completed the agreement (yes or no, not the content) | To let you start a pause only after both of you have completed it. | The pairing ends. |
| The second person's name, encrypted with the pairing key | To pass the name to the first phone during pairing. The server cannot read it. | The first person completes the agreement. |
| For each pause: which side started it, the start and end times, the extensions, the delivery times and what each of you chose at the end | To keep both phones on the same timer and to send the notifications. | 30 days after the pause ends. If you chose to talk later, 30 days after that time. |
| Usage records: the type of event, its time, the side, the phone model and the random pairing number | To find out if Pause for Two works and if notifications arrive on time. | No time limit. After the pairing ends, nothing links them to a phone. |
Ending the pairing in the app deletes the data above at once, except the usage records. After one year without use, the server deletes a pairing in the same way.
The server keeps the address of each connection in memory for about one hour to limit misuse. It does not write the address to disk or to a log.
We make backup copies of the database to recover from failures. We delete each backup copy 30 days after we make it. Until then, data that you delete stays in the backup copies made before the deletion.
Legal basis
- To provide Pause for Two (pairing, the shared timer and notifications): performance of the service that you ask for, under Article 6(1)(b) of the GDPR.
- For the usage records and the protection against misuse: our legitimate interest in a reliable and safe service, under Article 6(1)(f) of the GDPR.
- For crash reports: our legitimate interest in finding and correcting errors in Pause for Two, under Article 6(1)(f) of the GDPR.
Who else receives data
- Hetzner Online GmbH hosts our server in Helsinki, Finland.
- Google delivers notifications through Firebase Cloud Messaging. Google receives the notification address, the notification type, its times and a short general text. The notification never contains a name. The Firebase component in the app also sends Google an identifier for the app installation.
- Google also receives a crash report through Firebase Crashlytics when Pause for Two stops because of an error. A crash report contains the technical state of the app at that moment: the error and the program code that it occurred in, the time, the app version, the phone model, the iOS version, the memory and storage sizes, and identifiers for the app installation. It does not contain your names, your agreement or text that you write. Google keeps crash reports for 90 days.
- Apple delivers notifications to iPhones and receives the same notification data.
Google and Apple can process this data outside the European Union.
We do not sell data. We do not use advertising, tracking or third-party analytics.
Your rights
You have the right to access, correct and delete your data. You also have the right to restrict or object to its use, and to receive it in a portable format. You can delete the data on our server at any time: end the pairing in the app. Crash reports are not linked to your pairing. Google deletes them after 90 days.
Pause for Two has no accounts, so we cannot find your data from your name or email address. If you write to us, we will tell you what we need to identify your pairing.
You also have the right to complain to a data protection supervisory authority.
Changes
If we change this policy, we publish the new version on this page and change the date at the top.