Privacy Policy
Last updated 3 October 2026 · applies to ChronoSet for iOS
The short version. ChronoSet has no accounts or login. It does not ask for your name, email, GPS location, contacts or photos. When analytics delivery is enabled, it sends configuration snapshots to help improve the app. No account or persistent device identifier is attached, but combinations of settings and technical information may make records distinguishable or linkable. You can turn this off at any time in the app, under Settings → About ChronoSet.
Who we are
ChronoSet is an independent app developed by Dane Muldoon in Australia. For any privacy question, email hello@chronoset.app.
This website
This policy is about the ChronoSet app. The chronoset.app website itself sets no cookies, runs no analytics and loads nothing from third parties. It remembers your theme and language choice in your browser’s local storage, on your device only. The site is delivered by Cloudflare, which processes network information such as your IP address to serve and protect it. If you email hello@chronoset.app, your message and address are kept only to reply to you.
What we do not collect
- No account, sign-in, name, or email address.
- No location, contacts, photos, calendar, or health data.
- No advertising identifiers, and no third-party advertising or tracking SDKs.
- No free text you type (for example, custom dial text) ever leaves your device.
- No IP address is stored with the analytics record.
What the app sends
When enabled, configuration analytics are sent once, when the app launches. The numeric token contains the fields below, with no free text. The original numeric string is sent unchanged; identical strings are stored once. Up to 100 pending events may be held on the device, excluded from backups. Events older than seven days are discarded when the app next processes the queue; no background deletion is guaranteed. Usage analytics are on by default and you can turn them off at any time in the app: Settings → About ChronoSet → Share Usage Analytics. Turning them off stops anything further being sent and deletes any snapshots still waiting on your device.
| Category | Examples of what's included |
|---|---|
| App settings | Light/dark appearance and darkness level, selected face, countdown timer and beeps, digital-display mode, haptics, ticking, crystal and ceramic bezel settings, beat rate, Desk Stand Mode timeout, and your home time-zone's UTC offset. |
| Purchases | Which paid content packs have been unlocked (a yes/no per pack). No payment details — all purchases are handled by Apple. |
| Watch-face setup | Per face: chosen dial finish, colour and painting; hand style, metal and lume; markers; logo and dial-text options; bezel design, colour and lume; and enabled complications. Choices are encoded from fixed lists, not as free text. |
| Device & app | Device model and iOS version, app version and build, and your device language and region (for example en / AU). Not the precise city — only a time-zone offset. |
| Timestamp | The creation time, rounded down to the hour. The server also records its receipt time to the hour. |
Fixed choices limit what is collected, but do not guarantee anonymity. Detailed configurations combined with device model, software versions, locale, time-zone offset and timestamps may allow records to be correlated. We use these snapshots for aggregate analysis of how the app is used, not to identify anyone or to build individual profiles.
Why we collect it
To understand which faces, complications and options people actually use, to prioritise what to build next, and to spot problems (for example, an option that no one can find).
How it's handled and kept
- Delivery uses HTTPS and access-controlled Cloudflare D1 storage. Strings are decoded only locally for analysis.
- We do not store IP addresses with analytics or attach account, advertising or persistent device identifiers. Cloudflare processes network information, including IP addresses, to deliver and protect the service.
- Application request logging and tracing are disabled; operational messages exclude tokens and request headers. Provider security and account records have separate handling.
- Original strings with valid checksums are scheduled for deletion after 180 days; checksum-invalid strings after seven days. Purging runs every six hours; failures can delay deletion. Downloaded strings and local analysis databases follow the same retention policy.
- On the Free plan, Cloudflare recovery history can retain deleted data for a further seven days. Restored data is purged before ingestion resumes.
Purchases
In-app purchases (the Customisation and Complications packs, and Unlock Everything) are processed entirely by Apple through the App Store. ChronoSet never sees your payment information. Restoring purchases uses your Apple Account and Apple's servers.
Children
ChronoSet is not directed at children. The configuration analytics described above apply to all users; we do not collect an age field.
Your choices & rights
You can opt out. Turn off Settings → About ChronoSet → Share Usage Analytics at any time: nothing further is sent, and anything still waiting on your device is deleted. Records already received expire automatically (see above). For questions or requests about these records, contact hello@chronoset.app. Because we do not attach an account or persistent device identifier, we may be unable to locate records belonging to a particular person. We will assess requests rather than assume that no privacy rights apply.
Changes to this policy
If this policy changes materially, we will update the date above and, where appropriate, explain the change in the app.
This policy is published in English, French, German and Japanese. If a translation differs from the English version, the English version prevails.