Privacy Policy

Last updated October 9, 2026

What we store

• Your pair — a random pair ID, the first names or nicknames you enter, your shared tap count, streak, and chosen theme.
• Delivery tokens — the Apple Push Notification tokens for your devices, used solely to deliver a tap to your partner. They’re rotated by iOS and are useless to anyone else.
• A device identifier — a random ID generated on your device to tell the two of you apart within your pair.
• Product analytics — events such as first open, onboarding progress, demo and paywall interactions, taps, widget state, and purchase status. These may include app and OS version, device model, language, locale, time zone, App Store country, install time, a random installation and session ID, and an anonymous RevenueCat customer ID.
• Ad attribution — when available, Apple’s AdServices attribution token so we can tell whether an install came from an Apple Search Ads campaign. Apple supplies this token without requiring the App Tracking Transparency prompt.

What we do NOT collect

• No message content — a tap is just a tap.
• No contacts, photos, microphone, or health data, and no precise location. Location is limited to the city each of you may type for the distance between you, and the approximate country, region and city described under Analytics.
• No advertising identifiers and no third-party tracking or profiling across other companies’ apps or websites.
• No account, no email, no password (sign-in is optional and handled by Apple).

Analytics

Anonymous usage counts (from version 1.1.0). Love Taps also sends anonymous usage events to our own server (growth.tundra.industries, run by Tundra Industries on Cloudflare) so we can see which features are used. Each event is one of these:

• the app was opened, a session started or ended (with its length in seconds), and the first launch after install
• which screen was opened (welcome, pairing, home, the demo, Settings, themes, dates, distance, widget setup, the unlock screen)
• a tap or mood was sent (from the app, a widget, the Lock Screen control or a notification reply), a tap was received, and which of the built-in moods was used
• widgets on the Home or Lock Screen (by size), whether notifications were allowed when iOS asked, and actions such as setting or clearing your city or start date, opening the distance card, sharing a card, and creating, joining or completing a pair
• onboarding steps reached, including whether you came from an invite, whether you chose to invite, join or try the demo, whether you tapped “I have a code”, and whether you sent the request asking your partner to set it up
• that the app asked iOS to show the App Store rating request (not whether it was shown or what you chose; Apple does not tell the app)
• the unlock screen was shown and closed (and for how long), which plan was started, and whether a purchase or restore succeeded, was cancelled, is pending or failed (with the error number)

Each batch of events also carries: a random install ID created by the app (not your Apple ID, not the advertising identifier), the app version and build, iOS version, device model (for example iPhone17,1), language and region setting, time zone setting, the App Store country, and whether the app is a release, TestFlight or development build. Our server records the approximate country, region and city that Cloudflare derives from the connection; the IP address itself is not stored. On first launch on a real device the app also sends Apple’s AdServices attribution token.

Usage counts never include your names, your partner’s name, your city, pair or invite codes, or anything you type. They are not linked to your identity and are not used for advertising or tracking. Raw events are kept for up to 400 days.

We use RevenueCat to understand subscription and purchase events. We use this information for product and conversion analytics. It is associated with random or anonymous identifiers rather than your name, email address, Apple ID, or advertising identifier, and it is not used for advertising or cross-app tracking.

Where it lives

Pair data is processed on Cloudflare’s edge network (Workers, Durable Objects, and D1) to deliver taps quickly. Apple Push Notification service delivers notifications. Our own usage-count server (on Cloudflare) processes product analytics, and RevenueCat processes purchase and subscription status. These providers receive only the information needed for those services.

Payments

Love Taps+ is sold through Apple’s App Store and managed via RevenueCat for receipt validation and subscription status. Purchase events are also used in our product analytics. We never receive or store your card or other payment details — Apple handles all billing.

Your choices

Usage events are deleted after 400 days. You can unpair or delete the app at any time, which stops all processing. To request deletion of your pair’s data, email us and we’ll remove it.

Children

Love Taps is not directed to children under 13 and we don’t knowingly collect their data.

Changes

If this policy changes, we’ll update the date above and, for material changes, note it in the app.

Contact

Questions? [email protected]
Tundra Industries · Hawaii, USA