Using Cadence on Android? Read the Android Privacy Policy. The iPhone information follows below.
Cadence Privacy Policy
Effective date: September 22, 2026
Operator: Mustafa Onur ILGAZ (individual developer)
Privacy contact: mustafaonurilgaz@gmail.com
This policy covers the Cadence: Contraction Timer app for iPhone, including TestFlight beta builds, and these web pages.
Your records
Cadence works without an account. Contraction times, durations, intensity ratings, notes, breaks, kick counts and session history are stored locally on your iPhone. The app uses this local store to show timer information in its widgets and Live Activity. Cadence does not upload your records to a Cadence server.
PDF and CSV exports are created on your iPhone and go only to the destination you choose in the system share sheet.
Saved sessions remain until you delete them. Ending a session keeps it in History. You can delete completed sessions and individual records in the app; record deletion includes a short Undo period and local cleanup. This is not a promise that every storage or device-backup copy is immediately erased.
Optional usage and crash reporting
The setup screen explains the usage and crash reporting choice. You can change it in Settings > Privacy without losing access to the timer. Its initial position depends on your device region: off in the EU, UK and EEA, and when the region is unknown; on elsewhere. Collection starts only after setup is completed with this choice enabled. When upgrading from an earlier build without a saved choice, reporting stays off until you enable it in Settings.
When enabled, Google Analytics for Firebase receives app-use events, such as setup completion, your selected rule preset, contraction session start/end, kick-counting session start, screen visits, feature use, display preferences, Pro screen visits, price availability, purchase and restore outcomes, report export and share outcomes, and review-request attempts. We cannot see whether Apple displayed its review prompt or what rating you chose. Because Cadence is a pregnancy and labor app, these events can indicate pregnancy or labor. Our custom events do not include individual contraction timestamps, durations, counts, intensity values or notes. We do not record your screen, text input, exported report contents or share recipients. Standard SDK app-use events may also be collected.
With reporting enabled, Cadence also asks Apple whether an Apple Ads campaign led to the app download. Our lookup sends a temporary attribution token only to Apple. If Apple returns a match, our custom Analytics event includes campaign, ad group and keyword identifiers so we can measure campaign performance. That custom event excludes the token, raw response, ad interaction dates and ad location. Firebase may also collect its standard Apple campaign attribution, including source, medium and keyword identifiers, under the same reporting choice. Turning reporting off cancels our request where possible, clears our locally saved campaign information and resets local Analytics data. We do not send your app activity or health records back to an ad platform for targeting.
Analytics uses app/device identifiers, including an app instance identifier and Apple's identifier for vendor, plus app/device information and approximate location derived from the network connection. Cadence does not use Apple's advertising identifier, does not ask for tracking permission, does not set a named user ID and does not use these reports for personalized advertising. Google processes connection information, including IP addresses; this policy does not claim that all Google services ignore or immediately erase every IP address.
Firebase Crashlytics receives crash traces, installation identifiers, crash times, app/OS versions and device diagnostics to help us fix failures. Analytics activity may appear as crash-report breadcrumbs. We do not attach your notes or record history as custom crash logs. Google also processes operational service data, which can include IP addresses. These services may process information outside your country.
Turning reporting off stops new Cadence analytics events after a final opt-out event and resets local Analytics data. It does not delete information already received by Google. Crash reporting changes can take effect on the next app launch; previously queued reports may remain on the device and may be sent if reporting is enabled again. An upload already in progress cannot be promised to stop immediately.
Purchases
Cadence Pro is a single one-time purchase made through Apple. Apple handles payment and StoreKit transactions; Cadence does not receive your payment-card details.
To confirm the purchase and unlock Pro, including Restore Purchases and Family Sharing, the app uses the RevenueCat SDK. It sends the App Store transaction and product information for your purchase to RevenueCat together with a random, anonymous app user identifier created on your device. Cadence does not send your name, email, Apple Account or advertising identifier to RevenueCat. The RevenueCat SDK also sends technical request information with each request, including Apple's identifier for vendor, device model, OS version, preferred languages and App Store country, which RevenueCat uses to process purchase checks. RevenueCat processes this information to validate purchases and to show us purchase history and aggregate charts; we do not use it for advertising. If RevenueCat cannot be reached, the app checks your purchase locally with Apple's StoreKit so Pro stays unlocked. This purchase check is part of the purchase feature and is not controlled by the usage and crash reporting switch. See RevenueCat's privacy policy.
TestFlight, support and this website
If you test a beta through TestFlight, Apple automatically collects usage and crash information and shares it with us; it may include your name and email address. Feedback you submit can include text and screenshots. The Cadence reporting switch does not control Apple's TestFlight collection. See Apple's TestFlight privacy notice.
If you contact support, we receive the contact details, message and attachments you send and use them to answer your request and investigate problems. Please avoid sending personal health details or screenshots containing them.
These pages are hosted on Cloudflare Pages. Cloudflare processes technical request information, such as IP addresses, to deliver and protect the site. The pages use no cookies, analytics, scripts or third-party content.
Retention and your choices
Cadence's Google Analytics retention settings are currently 2 months for event-level data and 14 months for user-level data. The user-data retention period resets with new activity. These settings apply to the data covered by Google Analytics retention controls; aggregated reports may follow a different schedule. Firebase states that removal of crash traces and associated identifiers from live and backup systems begins after 90 days; this is not a guarantee of complete deletion on day 90. RevenueCat keeps purchase information under its own policy. We keep support emails while they are needed to handle your request, and you can ask us to delete them.
Email mustafaonurilgaz@gmail.com about access, correction or deletion requests concerning information we hold. We will explain what can be located and handled. Records stored only on your iPhone are not available to us, because there is no Cadence account; you can delete them in the app. You can withdraw optional reporting consent in Settings > Privacy. Depending on where you live, you may have further rights under local data protection law, including the right to complain to a data protection authority.
Read more about Firebase's data handling and Google Analytics retention. We will update this policy and its effective date when Cadence's data practices change.
Not medical advice
Cadence is a timing tool. Its rule matches are timing patterns you chose, not medical advice. If anything worries you, call your care team.
See our Terms of Use for app licensing and purchase information, or contact support for help.