D2X Fitness Timer

Privacy Policy

Effective September 10, 2026 · Published by D2X Enterprises LLC

This Privacy Policy applies to the D2X Fitness Timer mobile app for iOS and Android.

Read this in another language

This Privacy Policy explains what D2X Fitness Timer (“the App”) does with your information. It is written by D2X Enterprises LLC (“we”, “us”, “our”), the publisher of the App.

The short version: this release has no server of ours, no account, and no analytics. Everything the App records — your timer configurations, your saved presets, your session history and your preferences — is written to storage on your own device and stays there unless you deliberately export it yourself.

The one exception is buying or restoring Pro. That goes through RevenueCat, which receives the store’s receipt and an anonymous identifier so it can answer whether you own the unlock. It never receives your training data. Section 5 says exactly what is sent.

1. Who we are

D2X Enterprises LLC
30 S 15th St Ste 1550 PMB 852931
Philadelphia, Pennsylvania 19102-4806, USA

Support: https://d2xenterprises.com/support/ · support@d2xenterprises.com

For users in the EEA or the UK, we are the controller for any personal data described in this policy.

2. What the App stores, and where

All of the following is stored only on your device, in the App’s own private storage area, under the namespace d2x.v1.:

Last-used configuration — The numbers you set for each clock (work seconds, rest seconds, rounds, and so on). Written when you press Start, not while you are editing.
Presets — Any configuration you save by name, with the date you saved it.
Session history — For each completed or abandoned run: a generated id, which clock it was, the title shown in history (for example “Interval 40/20”), the start time as an ISO 8601 timestamp with your local offset, total/work/rest/paused durations, rounds done, rounds planned, and whether it completed.
Preferences — Theme choice, sound on/off, haptics on/off, keep-awake on/off, voice cues on/off, and your chosen language.
Builder drafts — The track or pyramid you are building, so a run survives the App being closed mid-workout.
Consent flag — A single value recording that you have seen and accepted the in-app legal notice.
Pro cache — A single true/false flag recording the entitlement the store last reported, so the clock picker does not flicker while the store is queried.

There is no user account, no sign-in, no profile, and no server belonging to us. We do not operate a backend for this App, we do not receive a copy of any of the data above, and we cannot see, recover, restore or delete it for you.

No advertising. The App contains no advertisements and no advertising SDK. It does not collect an advertising identifier.

No analytics. This release contains no analytics, telemetry, crash-reporting or attribution SDK of any kind. Nothing about how you use the App is reported to us or to anyone else.

No location, contacts, camera, microphone, photos or files. The App does not request or use any of these. The only file access is the one you initiate yourself in Section 4.

Fonts and images are bundled. The App’s typeface (Zen Dots) and every icon and graphic ship inside the App. Nothing is downloaded at runtime, so no third-party host learns your IP address as a side effect of the App drawing a screen.

3. Does anything leave my device?

In normal use, no. The App has no server of ours to talk to and makes no network request of its own — you can train entirely offline. The only component that uses the network is the app store’s own billing module, and only when you open the unlock sheet or tap buy or restore (Section 5).

Data leaves your device in exactly four situations, and each one is something you start:

You export a backup or a CSV (Section 4).
You buy or restore Pro, or open the unlock sheet so it can show the store’s current price — in which case your device talks to Apple or Google and to RevenueCat, our purchase processor. Never to a server of ours, and never with your training data (Section 5).
You turn on writing workouts to Health, in which case data goes to your own device’s Health store (Section 6).
You open our support page from your own browser, at which point our support host sees the ordinary technical information any web server sees.

Full backup. “Export full backup” writes one JSON document — your sessions, presets, preferences and last-used configurations — into a .d2xtimer file in the App’s cache folder and hands it to your operating system’s share sheet. You choose what happens next: save it to Files or Drive, mail it to yourself, send it to someone. Once it leaves the share sheet it is governed by whatever service you sent it to, not by us. This feature is free, deliberately: your data should always be able to leave the phone.
History as CSV. “Export history as CSV” writes one row per session (start time, clock, title, durations, rounds, completed) to a .csv file and offers the same share sheet. This is a Pro feature.
Import. Importing a .d2xtimer file replaces what is currently on the device. The App asks you to confirm first, because import is destructive. The file you pick is read locally; it is not uploaded anywhere.
You are responsible for your exported files. A backup contains your full training history in plain readable JSON. Store and share it accordingly.

5. Purchases

The App offers D2X Pro, a one-time purchase — not a subscription — listed at $3.99 USD or the local equivalent under the product identifier com.d2xfitness.timer.prounlock. Pro unlocks six additional clocks, class mode, the builder, writing workouts to Health, and CSV export.

Payment is processed by Apple (App Store) or Google (Google Play) as merchant of record, under their own terms and privacy policies. We never receive, see, or store your payment card details, your billing address, or your store account identity.
Purchases are handled through RevenueCat. RevenueCat, Inc. is our processor for checking what you own. When you open the unlock sheet, buy, or restore, its SDK sends the store’s purchase receipt and a small amount of technical context — an anonymous identifier it generates on your device, the product identifier, the price and currency the store quoted, your storefront country, and your device model, OS version and app version — to RevenueCat’s servers in the United States. It sends back a single yes/no entitlement, which the App caches on your device and re-checks on every launch. If the entitlement is later gone — after a refund, for example — the App locks Pro again.
RevenueCat is not given your identity. The identifier is generated by the SDK and is not your name, your email, or your Apple or Google account. We do not send it your training data: your clocks, presets and session history are never part of a purchase check. RevenueCat processes this on our instructions and under its own privacy policy, at https://www.revenuecat.com/privacy/.
There is still no server of ours and no analytics on the purchase. We do not run a backend, and nothing about how you use the App is reported to us.
Because the App has no account, your Pro unlock is tied to the Apple or Google account you bought it with. “Restore purchase” re-activates Pro at no charge on any device signed in to that same store account. It cannot be moved to a different store account.
Refunds and any statutory cancellation or withdrawal rights are handled by Apple or Google under their policies and the consumer law of your country. We do not separately process payments or issue refunds.

What ships today. Store billing is wired in this release, through RevenueCat over StoreKit on iOS and Play Billing on Android. Purchases only work in a native build: in a preview build there is no billing module, every purchase path reports that the store is unavailable, and Pro is never unlocked locally. When you buy or restore, the question asked is whether your store account owns com.d2xfitness.timer.prounlock; the answer, and the store’s own localised price string, are the only things the App receives back.

6. Health data (Apple Health / Health Connect)

Writing your completed workouts to Apple Health (iOS) or Health Connect (Android) is designed as an optional Pro feature.

It is off unless you turn it on, and permission is requested at the moment you use it, never at launch. The App explains what will be written before the system prompt appears.
If granted, the App would write a workout record (start time, duration, workout type) to your device’s own Health store. It reads nothing from Health, and no Health data is ever sent to us — there is nowhere for it to be sent.
You can revoke the permission at any time in your system settings. Doing so never removes a session already recorded in the App.
Refusing is a valid answer and costs you nothing: the session is already saved locally by the time the question is asked.

What actually ships today. As of this release, no Health provider is installed, so isHealthAvailable() is always false, the Health row is hidden in Settings, and the App neither reads nor writes any Health data at all. No HealthKit or Health Connect permission is declared or requested. The section above describes the behaviour of a future build that installs a provider.

7. Notifications, sound, haptics and the screen

Notifications. While a clock is running, the App can post a local notification for the end of the current segment, so a lock-screen shows where you are. Android will ask for notification permission the first time this happens. These notifications are generated on your device and scheduled locally — there is no push server, no push token, and nothing is sent anywhere. If you refuse, the clock still runs normally. On Android, while a clock runs the App may also keep an ongoing notification in place: the system requires one for the service that keeps the clock running, and it clears when the clock stops.
Sound. Cue sounds are bundled with the App and play locally. The App ducks (lowers) other audio rather than stopping it. Cues are played by the App itself, so they are dependable only while the App is open and on screen. If you switch to another app or the screen locks, your device may suspend the App, and cues may be late or may not sound at all until you come back to it. It does not record audio and has no microphone access.
The spoken countdown. If you leave voice cues on, the App asks your device’s own text-to-speech to say the count and whether you are working or resting. On iOS that is entirely on-device. On Android it is handled by whichever text-to-speech engine you have installed, and some of those download a voice the first time they are asked for one — a request your device makes to that engine’s provider, not to us, and one that carries nothing about your training. We send it only the word to be spoken. Turning Voice countdown off in Settings stops this entirely; the tones and the vibration are unaffected.
Haptics. Vibration cues, controlled by a setting.
Keep awake. While a clock runs, the App can hold the screen on, controlled by a setting.

8. Children

The App is a general-audience training timer. It is not directed to children under 13 (or the equivalent age in your country), and we do not knowingly collect personal information from children — in this release we do not collect personal information from anyone, because there is no server to collect it. If a child uses the App on a shared device, everything they record stays on that device.

Physical training carries risk. Children and adolescents should train under adult supervision, and the App must not be used as a substitute for that supervision.

9. Your rights and choices

Because your data lives only on your device, you exercise most rights directly:

See it — everything is visible in the App: history, presets, settings.
Correct it — edit or delete any preset; delete any individual session.
Export it — “Export full backup” gives you a complete, portable copy in an open format, free of charge and without asking anyone’s permission.
Delete it — “Erase all data” removes everything the App has stored, including the consent flag, so an erase looks exactly like a fresh install. Deleting the App also removes its on-device data.

Depending on where you live you may have rights under the GDPR (EEA), the UK GDPR, CCPA/CPRA (California), and other laws such as Saudi Arabia’s PDPL or the UAE PDPL — including rights of access, correction, deletion, portability, objection, and withdrawal of consent. We hold almost nothing about you: your training data never reaches us, so the in-app equivalents above are the complete and immediate answer for it. The one record that exists off your device is the purchase record held by RevenueCat on our behalf, keyed to an anonymous identifier. Contact us at the address in Section 1 and we will action any request against it.

We do not sell or share your personal information, for cross-context behavioural advertising or for anything else. We have none to sell.

10. International transfers

If you only train, no data leaves your device, so there is no international transfer. If you buy or restore Pro, the entitlement check is processed by RevenueCat on servers in the United States, and the transaction itself is handled by Apple or Google as merchant of record, under their own terms, safeguards and international-transfer mechanisms — we are not a party to it and receive nothing from it. If you export a backup or a CSV, you choose the destination, and the transfer is yours rather than ours.

11. Security and retention

Your training data is protected primarily by the fact that it never leaves your device and is held in the App’s private storage, protected by your device’s own encryption and lock screen. We retain none of it, because we never receive it. The purchase record held by RevenueCat is kept for as long as the App is offered, so that a restore keeps working; it contains no training data. Exported backup and CSV files are written to the App’s cache directory and are plain text; treat them as you would any other copy of your personal records.

12. Changes to this policy

We may update this policy. When we make a material change we will update the date above and, where appropriate, note it in the App. The version bundled in the App and the version published on our website are the same document.

13. Contact

Questions, or a privacy request: https://d2xenterprises.com/support/ or support@d2xenterprises.com.