Privacy

Your rhythms are yours alone. Here is exactly what we know, why we keep it, and how long we hold onto it.

What we collect

When you sign in with Apple, we receive your Apple subject ID (a unique identifier Apple gives us), your email address, and optionally your display name. That is how we know who you are. We keep the email address Apple provides with your account so the application operator can identify and support it. We do not collect your phone number or personal information beyond what Apple shares.

We store your device type (iPhone or Apple Watch) and a push notification token so we can alert you when your partner sends a rhythm. We also track which Apple account you paired with, your subscription status, and how many rhythms you send each day (to enforce the free-tier limit of 3 per day).

The rhythm itself — the pattern of taps and any label you attach — is stored only between you and your partner. We never read it, share it, or use it for any purpose other than delivering it to them.

If a Couple Plus member chooses Heart, the Apple Watch reads one current heart-rate sample through HealthKit to create a one-time seven-pulse rhythm. The raw heart rate stays on the Watch only in memory for this send and is never saved or sent; only the derived private rhythm is delivered to the paired partner. Kindred Beat is not medical monitoring or an emergency feature.

What we do not collect

We do not use Google Analytics, Firebase, or any third-party tracking. We do not collect your location, browsing history, contacts, photos, or microphone access. We do not sell your data, show ads, or build a profile about you. There is no feed, no audience, and no public profile.

Where your data lives

Everything is stored in a single database on our Windows server. No external databases, no cloud storage, no third-party data services. The only data that leaves our servers is what is necessary to talk to Apple: verifying your sign-in, delivering push notifications, and checking your subscription status.

Push notifications contain only a generic message — "Your partner sent you a rhythm." — no patterns, labels, or names.

How long we keep things

Rhythm messages are cleared immediately after your partner plays them. We keep your account identity, including the email address Apple provides, until you delete your account. Pairing invitation codes expire after 10 minutes. Security logs, push delivery records, and session data are purged after 30 days.

Product analytics

We log a small set of events — like when the app opens, a pair is created, or a rhythm is played — to understand how the app is used and where things break. These events contain no rhythm content, no labels. They are associated with a protected account ID and stored only in our own database, never sent to an analytics provider.

Deleting your account

You can delete your account at any time from the app. When you do, we revoke your Apple credentials, end all pairings, delete all your rhythm messages, and erase your personal identifiers. A small anonymous record is kept only to prevent your account from being accidentally recreated. Your analytics events are anonymized — we keep the event names and timestamps, but strip your identity.

For paid subscribers, your paid status will be lost too and is not possible to recover.

Encryption

All communication between the app and our servers uses HTTPS. The production server uses restricted service-account access for data at rest. Apple refresh tokens are additionally encrypted with ASP.NET Core Data Protection. Refresh tokens and pairing codes are stored only as one-way hashes — we cannot recover the original values even if the database is compromised.

Who can access your data

Only the application operator can access the database. There is no admin panel, no employee access, and no third-party access. Apple receives only what is necessary for authentication, push delivery, and subscription verification — never your rhythm content or who you are paired with.

Contact

If you have questions about your data, reach out through the Support page.

Last updated: November 2026