Privacy Policy

TL;DR

The app collects, transmits, and stores no personal data. It runs on your iPhone and, if you use one, your Apple Watch. There are no analytics, no crash reporting, no advertising SDKs, and no Splits server. Your heart-rate and workout data stay on your devices unless you choose to write them to Apple Health or share a summary card yourself. This website has no forms and no sign-ups, so it collects nothing either.

What Splits is

Splits is an iOS workout timer that records a continuous heart-rate session alongside structured training blocks (EMOM, Intervals, AMRAP, For Time) and reports your splits with heart-rate zones. It takes heart rate from a standard Bluetooth chest strap, or from an Apple Watch running the Splits watch app. In version 1.0 the entire app is local code. There is no Splits backend that your installation talks to.

Data we collect

None. Not in the app, and not on this site.

No analytics, telemetry, crash reporting, advertising SDKs, or third-party data services are integrated. Splits does not create or use an account, does not ask for your name or email address, and does not request location, microphone, camera, or contacts access. The app makes no network requests of its own. Its one outside contact is the App Store, through Apple's StoreKit. The app asks it at every launch whether the unlock is owned and what it costs, and again when you buy or restore the unlock. Cloud sync is being built, but it is compiled out of the App Store build, so the version you install contains none of it.

This site is the same story. There is no form on it, nothing to sign up for, and no analytics, tracking pixels, or advertising scripts. The only way to reach us is to send an email yourself, and then we have whatever you chose to put in it.

Heart-rate and workout data

• Heart rate from your strap. Splits connects to your chest strap over Bluetooth using the standard Heart Rate Service that every compliant strap exposes. No vendor SDK is involved. Readings are written to a database inside the app's own storage on your iPhone. They are never transmitted anywhere.
• Heart rate from your Apple Watch. If you use the watch app instead of a strap, the Watch reads your pulse and sends each reading to your iPhone over WatchConnectivity, Apple's direct link between a Watch and the phone it is paired to. The readings end up in the same local storage as strap readings. The Apple Health section below explains exactly what the watch app asks for and why.
• Your sessions. Workouts, blocks, rounds, splits, and the heart-rate timeline behind them live in local app storage on your device. Deleting a session in Splits deletes it. Uninstalling Splits removes all of it.
• Your strap's identifier. So the app can reconnect to the same strap next session, its Bluetooth identifier is remembered on-device. Forgetting the strap in Settings removes it.
• Your profile. You enter it yourself: your birthday (month and year), and optionally your weight and sex. The birthday gives your age, which sets your heart-rate zones. Weight and sex are used only to estimate calories. All three are stored on-device in app settings. Splits does not read any of them from Apple Health, and does not write them there.

Splits never uses heart-rate or health data for advertising or marketing, never sells it, never shares it with third parties, and never discloses it to data brokers or information resellers. There is no mechanism in the app that could do any of these things.

Apple Health

Splits can save a finished workout to Apple Health, including its heart-rate samples, so it appears alongside the rest of your activity. This is controlled by the Save to Apple Health toggle in Settings and by the iOS permission prompt, which appears the first time you end and save a session.

The iPhone app only writes to Apple Health. Its read set is empty, so it cannot see any health data already on your device. Deleting a session in Splits also removes the workout it wrote to Apple Health. Turning the toggle off stops future writes and leaves existing entries alone.

The watch app is the exception, and it has to be. watchOS gives an app the wrist sensor only through Health, so the watch app asks for read access to heart rate. That is a separate Health permission request from the one on your phone, and it is the only read permission anywhere in Splits. It is used for one thing. While a workout is running, the watch app reads heart-rate samples recorded from the moment that workout started, keeps only the ones this Watch itself recorded, and forwards those to your iPhone. It asks to read no other health type, reads nothing dated before the workout, and reads nothing at all when no workout is running. It also starts a workout session on the Watch, which is what lets watchOS keep the app running with your wrist down. watchOS requires permission to write a workout before it will start one, so the watch app asks for that too, and then never uses it: the watch never saves a workout. Your iPhone is the only thing in Splits that writes to Health.

None of this goes anywhere else. Neither app sends health data off your devices.

Data written to Apple Health is governed by your device and iCloud settings, not by Splits.

Photos

When you share a workout summary card you can optionally compose it onto one of your own photos. Splits uses the standard iOS photo picker, which hands the app only the single image you select. It grants no access to the rest of your library. The card is rendered on your device and handed to the iOS share sheet. Where it goes from there is your choice, and is governed by whichever app you share it to. Splits does not upload it anywhere.

Payment

Splits has one purchase, the unlock. Apple processes it under Apple's Privacy Policy. Splits never sees your payment method or billing address, and receives no personal information from the transaction.

The app keeps two things on your device, in its standard app settings. One is whether the unlock is active. The other is a record of an unfinished purchase: which product it is for and since when. It is written when a purchase waits for approval, such as an Ask to Buy request, or when leaving the app interrupts a purchase. It stays until the purchase completes or you dismiss it. A declined approval sends the app no notice, so in that case only dismissing clears it. Deleting the app removes both.

None of this is sent to Splits or to anyone else. The app has no server to send it to. Whether you own the unlock is checked with Apple through the App Store, not through us.

Third parties

None. No analytics providers, advertising networks, social-media SDKs, or data brokers receive information from Splits. The app ships with no third-party runtime dependencies. Apple sells the unlock through the App Store, as described under Payment, and receives nothing from Splits in doing so.

Children's privacy

Splits is not directed at children under 13. Because the app collects no information, no children's data is processed by Splits.

International (GDPR, CCPA, and similar)

The app collects no personal data and talks to no server of ours, so there is nothing for us to export, correct, restrict, or delete on request. Deleting a session removes it from your device; uninstalling Splits removes everything the app held. Data you chose to write to Apple Health is managed through the Health app.

If you have emailed us, that message sits in our mailbox like any other email; ask at support@splits.fit and we will delete it.

Changes to this policy

We will update this page if Splits ever introduces data collection. The effective date at the top will reflect the change, and material changes will also appear in the App Store release notes for the version that introduces them.

Contact

Privacy questions: support@splits.fit