Rung Privacy Policy

Effective 5 August 2026

Rung is a local-first strength tracker made by Dan Yates (“we”, “us”). This policy describes what data the app handles and where it goes. It is deliberately short, because almost nothing goes anywhere.

Your training data never leaves your phone

Everything you record in Rung — workouts, sets, weights, reps, routines, custom exercises, personal records, settings — is stored in a local database on your device. Rung has no accounts, no sign-in, and no server of ours to send it to. The app makes no network calls with your training data, ever.

Analytics screens, weekly reviews, and progression suggestions are computed on-device from that same local data.

What IS shared: purchase processing

The statement above is a claim about your training data, not about the purchase transaction, and the two are different. If you buy Rung Premium (a one-time purchase made through Apple’s In-App Purchase system), payment is processed by Apple, and we use RevenueCat to validate and manage the entitlement. As part of that, RevenueCat receives transaction data: the product’s name and identifier, the price and currency, the transaction receipt, and an anonymous device identifier. This is the minimum needed to make your purchase work and to restore it on reinstall.

RevenueCat’s handling of this data is described in their privacy policy at revenuecat.com/privacy. Rung has no accounts, so it holds neither your name nor your email address and cannot send them to RevenueCat — and your training data is never sent to anyone.

Backups and export

Notifications

Rest-timer alerts and workout reminders are local notifications, scheduled and delivered on your device. No notification service of ours is involved.

What we don’t do

Support

If you email us at daniel.yates1@protonmail.com, we receive your email address and whatever you include in the message. We use it only to reply, and we don’t add it to any list.

Changes

If this policy changes, the new version will be posted at this address with an updated effective date.

Contact

Dan Yates — daniel.yates1@protonmail.com