The short version: On iPhone, iPad and Android, LoveClock keeps your relationship to yourself. Used solo, everything you enter stays on your device and none of it is sent to us. If you choose to pair with your partner, the data you share is end-to-end encrypted on your phone before it leaves, and our server only ever stores scrambled data it cannot read. There is no account, no analytics, no advertising, no tracking, and no location tracking.
Using LoveClock solo (the default)
LoveClock works fully without pairing. Your relationship start date, an optional wedding date, milestones, reunion countdowns, plans, the moments in Our Story, and your theme preferences are stored locally on your device: on iPhone and iPad using Apple's on-device storage, and on Android in the app's private storage, which other apps cannot read. In solo use the app does not contact our server, and nothing you enter is sent to us. On Android, two things are still worth knowing. When the app starts, Google's Firebase Cloud Messaging makes sure the phone has a push token from Google, so notifications can work if you pair later; that request carries nothing you have entered, and the token only reaches our server once you pair. And if your phone's Google backup is on, Android includes LoveClock's data in it, as explained in the section on losing your devices below.
Pairing with your partner (optional)
You can optionally pair with one partner using a short code or invite link. Pairing is built so that we cannot read what you share:
- The pairing code never leaves your phones. The one exception is the optional iCloud backup on iPhone and iPad, which also keeps it in your personal iCloud Keychain, and Apple end-to-end encrypts that, so we cannot read it either. On Android the code is locked with a key held in the Android Keystore, which never leaves the phone, and it is left out of Android's backup. The encryption key is derived from the code on your devices, and our server only ever sees a one-way fingerprint of the code used as a room address.
- Everything you sync (dates, milestones, reunions, plans) is encrypted on your device before upload. The server stores only this ciphertext and has no way to decrypt it.
- There are no accounts. Your devices authenticate with a random per-device secret; we never ask for a name, email address, or phone number.
What our server stores when you pair
When (and only when) you pair, our server holds these kinds of data:
- A room record: the hashed room address, hashed device credentials, and a version counter. No readable content.
- Your encrypted records: the end-to-end encrypted data described above, kept for up to 400 days after the last update. A room that is created but never joined is deleted after 15 minutes.
- A push token: your device's push token, issued by the Apple Push Notification service on iPhone and iPad or by Google's Firebase Cloud Messaging on Android, used only to deliver sync updates and nudges, and kept for up to 90 days after your phone last sent it. While you are paired, the Android app sends it again about once a week so it does not lapse. This is the only piece of server-side data that is not encrypted, because Apple and Google need it in readable form to route notifications.
- Encrypted snap photos (in transit): a snap you send is encrypted on your device with a fresh one-time key before upload, and the key itself only ever travels inside your end-to-end encrypted records, so the photo blob on our server is unreadable to us. Blobs are deleted automatically within about a day, and the one-time key is destroyed on your devices when the snap fades, which makes any remaining ciphertext permanently meaningless. Both halves matter: brief unreadable storage on our side, key erasure on yours.
- Encrypted voice notes (in transit): a voice note works exactly the same way as a snap: encrypted on your device with its own one-time key, unreadable to us on the way through, deleted from our side within about a day, and made permanently meaningless when the key is erased on yours. The audio is only ever unscrambled in your phone's memory and is never written to your phone's storage unless you deliberately keep it.
Unpairing removes your device from the room, and the retention windows above age the rest out automatically.
Notifications and nudges
Anniversary and milestone reminders are scheduled locally on your device by iOS or Android, with no server involved. When you are paired, sync updates arrive as silent pushes, and a partner's nudge shows a fixed, generic banner. The optional note attached to a nudge is end-to-end encrypted like everything else and is shown transiently on your partner's screen rather than stored. On Android, a nudge that carries a note shows the note itself in the banner instead of the generic text. The note travels inside the push still encrypted, so Google only ever handles scrambled data; it is unlocked on the receiving phone, and the notification is marked private, so a lock screen set to hide sensitive notifications keeps it hidden. The banner stays in the notification list until it is opened or swiped away. A snap photo is just as temporary: it is shown for about 20 minutes after your partner opens it and is then erased, unless they deliberately choose to keep it. If they keep a snap you sent, you are told, and a kept snap stays on their phone and can be saved elsewhere from there. The one exception is a snap kept while reporting it to us: that save is silent, so that reporting something never announces itself to the person being reported. We cannot see snaps, and we cannot prevent a phone from taking a screenshot; the fading is a promise between the two of you, not a technical impossibility.
A voice note follows the same rules, with one difference worth stating plainly: its twenty minutes start when your partner plays it, not when it appears. A voice note sitting on screen tells them nothing, so it would be unfair to start the clock before they had a chance to listen. A voice note that is never played is erased automatically a day after it was sent. Voice notes never play by themselves, not from a notification and not on arrival, and we cannot hear them any more than we can see a snap.
What never syncs
Sharing is selective: reunions and plans you keep private stay on your phone even while paired. Your theme and animation preferences, your pinned widget choice, and your purchase receipts are never synced to your partner or sent to our server. If you are paired, a single encrypted entry shares your Premium status and its expiry date with your partner so one subscription can cover you both; it reveals nothing else.
If you lose your devices
Because we never have your pairing code or encryption key, data on the server cannot be recovered by us. If you enabled the optional iCloud backup on iPhone or iPad, a new or reinstalled device signed into your iCloud account can offer to restore your pair from your personal iCloud Keychain, a path that runs entirely between your devices and Apple. LoveClock on Android does not back up your pair: the pairing code and keys stay on the phone and are deliberately left out of Android's own backup, so on a new or reset Android phone, or after reinstalling the app, you need to pair again. Without a pair backup, losing both phones means the encrypted data ages out unread. That is a deliberate trade: it is the property that keeps us unable to read your relationship.
The same is true of the photos, voice notes and notes you keep: they live on your phone and never reach our servers at all. On iPhone and iPad you can optionally turn on iCloud backup — a single switch that covers both your pair and your content — which copies your dates, moments, plans and kept keepsakes into your own iCloud Drive. Every file is encrypted on your device first, with a key stored only in your iCloud Keychain, so the backup is unreadable to us and to Apple. Content your partner sent that you did not keep is never backed up. It stays as temporary as it was meant to be. Turning the backup off deletes it.
On Android, LoveClock has no backup switch of its own and follows your phone's Google backup setting. If that backup is on, or you copy your old phone to a new one, Android includes what LoveClock stores on the device, such as your dates, moments, plans and theme, and the photos, voice notes and notes you kept. LoveClock does not encrypt this copy first, the way it does the iCloud backup; Google's backup service stores it in your Google account under Google's own terms, and we have no access to it. It never includes your pairing code or the keys that go with it, your push token or your purchase status, which is why a restored phone needs to pair again. Photos and voice notes your partner sent that you did not keep are never saved on your phone, so they are not in it either.
Service providers
The sync server runs on Cloudflare (Workers, KV, and Durable Objects), which stores the ciphertext and push tokens described above on our behalf. Notifications are delivered through the Apple Push Notification service on iPhone and iPad, and through Google's Firebase Cloud Messaging on Android; LoveClock uses Firebase for nothing else, including analytics. Purchases are handled by the App Store or Google Play, and we never see your payment details. Apart from your phone's own backup described above, none of these providers receives readable relationship data from us.
No account required
You can use every feature, including pairing, without creating an account, signing in, or giving us an email address. There is no login wall.
No analytics, ads, or third-party tracking
LoveClock contains no advertising, no analytics or telemetry SDKs, and no third-party tracking frameworks. We do not build a profile of you and we do not share data with advertisers or data brokers.
No location tracking
LoveClock does not track where you or your partner are, and never uses your location in the background. On iPhone and iPad, the “near me” button in Our places can ask to use your location while the app is open. It takes one reading so Apple Maps search can show places nearby; that reading is not stored and is never sent to us. If you say no, everything else works the same. Reunion countdowns are time-zone aware, but that is calculated on your device from the dates and zones you choose.
On iPhone and iPad, places you save in Our places (names, addresses, map pins, your ratings and notes) are stored on your device with the rest of your data. They are restaurants and cafés you chose to save, not a record of where you have been. A place you choose to share with your partner is end-to-end encrypted like your dates and plans, and saved places are included in the optional iCloud backup. Searching for a place and opening it in Apple Maps uses Apple's Maps service under Apple's privacy policy; we never see those searches.
Visiting this website
This website is served by Cloudflare. It sets no cookies, runs no analytics, and loads its fonts from this site rather than from Google or another third party. Your theme and language choices are remembered only in your own browser. To deliver a page, Cloudflare necessarily handles your IP address; we keep no visitor logs of our own.
Why we use data, and on what legal basis
The GDPR asks us to name a legal basis for each way we use personal data. They are:
- Pairing and sync: the room record, your encrypted records, snaps and voice notes in transit, and your push token are used only to provide the pairing you asked for. Legal basis: performance of a contract (GDPR Article 6(1)(b)). Pairing is optional, and without it none of this is processed.
- Security and abuse prevention: our server sees your IP address with each request and uses it in memory only, to limit how often new rooms can be created; it is never stored. Cloudflare's technical logs of requests to our server, which can include an IP address, are deleted automatically within seven days. Legal basis: our legitimate interest in keeping the service available and safe (Article 6(1)(f)).
- Messages you send us: if you email us, including to report a snap or voice note, we use what you send to answer you and to act on the report. Legal basis: our legitimate interest in responding and in keeping LoveClock safe (Article 6(1)(f)). We delete these emails once the matter is closed.
- Purchases: Apple and Google process your payment as independent controllers, under their own privacy policies. The app checks your subscription on your device; we receive no purchase data.
We do not sell your data, and we make no decisions about you by automated means, including profiling.
Transfers outside Europe
Cloudflare, Apple and Google may process data outside the European Economic Area, including in the United States. These transfers rely on the EU–US Data Privacy Framework, in which all three companies participate, and on the Standard Contractual Clauses in their data processing terms. What leaves the EEA from our server is either end-to-end encrypted or technical data such as a push token or an IP address.
Your rights
Under the GDPR you have the right to access your personal data, to have it corrected or erased, to restrict its processing, and to receive it in a portable format. Where we rely on our legitimate interests, you can object at any time.
Because LoveClock has no accounts and our server cannot read what it stores, we usually cannot tell which data on it is yours. The simplest way to use these rights is in the app itself: everything you enter is on your phone, where you can view, change or delete it; unpairing removes your device from the room; and what is left on the server expires on the schedule above. You can also write to us and we will help as far as we can, though without information that only your phones hold we may be unable to find your data (GDPR Article 11).
You also have the right to lodge a complaint with a data protection authority, in particular in the EU country where you live or work. In the Netherlands, where LoveClock is based, that is the Autoriteit Persoonsgegevens.
Children
LoveClock is intended for a general audience and does not knowingly collect any personal information from anyone, including children.
Changes to this policy
If this policy changes, we'll update this page and revise the date above.
Who is responsible for your data
LoveClock is made by Pawel Szydlowski, an independent developer based in the Netherlands, who is the controller of the personal data described in this policy under the EU General Data Protection Regulation (GDPR). You can reach the developer at the email address below.
Contact
Questions about your privacy, or a request under the GDPR? Email pawels.apps@gmail.com.