Archery Timer
English

Privacy Policy

In short

This app collects no personal data. There is no account to create, no profile, and nothing about you is stored anywhere.

It does send a handful of anonymous counters, so we can tell whether the app is used at all and which parts of it are worth maintaining. They are plain totals (how many times the app was opened today, how many people pressed a particular button) added to a shared figure. Nothing identifies your device, nothing records what you did, and no two counters can be put back together into one person's session. The section below sets out exactly what is counted.

Those counters come from the app for iPhone, iPad and Mac, and from the app for Android phones and tablets. The Wear OS watch app and the Windows app send us nothing at all.

Everything else is unchanged: your settings never leave the device, and what the app sends to drive another screen goes only to your own devices, on your own local network.

The App Store privacy label says the same: Usage Data, Product Interaction, not linked to you and not used for tracking. The Data safety section on Google Play describes it in its own terms: App activity, and an installation identifier used only to prevent abuse, neither of them ever shared, both encrypted in transit.

What the app stores on your device

Your settings are saved locally, in the app's private storage:

The Wear OS watch keeps one thing only: whether it has already asked your permission to show its timer-running notification. On Windows, the settings are saved in a file in the app's folder, along with the window's position.

Apart from the counters described below, none of this is uploaded or backed up anywhere by us. It is deleted when you delete the app. Depending on your settings it may be included in your own iCloud or local backups (Apple devices) or in your Google Account backup (Android), which are yours and are governed by Apple's or Google's privacy policy.

What travels between your devices

The app lets one device drive a timer on others: a watch, a phone, a tablet or a computer controlling one or several screens. iPhone, iPad, Mac, Android and Windows all drive one another.

On the local network. Devices find each other over Bonjour, under the service name _archerytimer._tcp. Android and Windows use the same open standard (mDNS / DNS-SD) through their own system tools. What other devices on the network can see, and only while you have turned sharing on, is limited to: the name you gave the device, its kind (iPhone, iPad, Mac, Android, Windows), its random identifier, the protocol version, and whether a remote is already connected to it. Once connected, only what the timer needs travels: commands (start, pause, reset), the current phase, the time remaining, the end's settings, the display language, and, in arena mode, the letter assigned to each screen.

The link is end-to-end encrypted (TLS 1.2 with a pre-shared key derived from the four-digit code shown by the controlled device). A device without the right code cannot connect. TLS session resumption is disabled, so regenerating the code genuinely drops devices that were already connected.

The QR code and the pairing link. A shared device shows a QR code beside its code. That QR code holds a link to captarget-timer.web.app/l, followed by what it takes to connect: the device's random identifier, its four-digit code, its address and port on the local network, its name and its kind. All of that sits after the # in the link, the part a browser never sends to a server: neither we nor our host ever receive it. If the app is installed, the link opens it directly. If not, the page that opens reads that information in your browser only, to show the device's name and code and offer to install the app; it carries no tracker. The link is of no use outside your local network, and the code in it stops working as soon as it is regenerated. Share it only with people you would give the code to.

To read that QR code, the iPhone and iPad app uses the camera, only while the scanner is open: the image is analysed on the device, and no picture is kept or sent. On Android, reading it is left to the code scanner provided by Google Play services: the app then has no access to the camera and receives only the code's contents. On a phone where that scanner cannot run, the app opens its own camera screen instead, and asks for the camera only at that moment: the image is analysed on the phone, no picture is kept or sent, and the camera stops as soon as the screen closes. You can also scan the QR code with the system camera, or, on Windows, paste the link.

With no Wi-Fi network. Between Apple devices, the link can also run directly from device to device, with no access point at all. Android and Windows need a network: the club's, or a phone's hotspot. Either way, nothing goes over the internet and nothing reaches a server: we operate none.

With the Apple Watch. Communication with your paired Apple Watch uses the channel Apple provides between a watch and its iPhone. It stays between your two devices.

With a Wear OS watch. The watch talks only to the Android phone it is paired with, over the Wearable Data Layer that Google Play services provide between a watch and its phone. What travels there is the same as between two devices (commands, phase, time remaining, the names of the devices being driven). The watch has no network connection of its own and sends us nothing.

The anonymous counters

When the app opens, when it goes away, and on a few button presses, it adds one to a shared total. The whole of what is stored on our side is a date and a list of numbers:

Nothing beyond that. No identifier travels with a counter, no exact times are kept, and no record exists from which a day's total could be taken apart into individual sessions. We cannot tell that two of those presses came from the same phone, and neither can anyone else reading the database.

The two figures that look as though they would need to know who you are do not. Your own device decides, from a flag kept locally, whether this is its first launch ever and whether it has already been counted today; only the +1 leaves the phone.

Android. The Android app sends exactly the same counters, stored in a collection separate from the Apple devices' one, so that each platform's figures stay apart. Only the name of that collection says they came from Android.

Wear OS and Windows. The Wear OS watch and the Windows app send no counters, and no other data, to anyone. When a watch drives a session, it is the phone that counts it, once, among its own counters.

The anonymous account. So that nobody can inflate the totals, a write is accepted only from an app that has signed in anonymously. That account is created by the app itself: it holds no name, no email address and nothing you have typed, and it is never written beside a counter. Alongside it we keep one small record per installation, holding how many writes it has made on a given day, so that no single account can shout louder than one person. It says nothing about what was counted.

Checking the app. To make sure a write really comes from our app and not from a script, each one carries a verification token issued by the system: Apple's App Attest on iPhone, iPad and Mac, Google's Play Integrity on Android. That token vouches that the app is genuine and normally installed; it holds no information about you, is not kept with the counters, and is checked only at the moment of sending.

Who processes this. The counters are held by Google Firebase (Cloud Firestore, Authentication and App Check), acting on our instructions. Like any server, Firebase sees the connection's IP address; it uses it to protect the service against abuse, and we neither receive nor keep it. If your device has no connection, or you have turned on Low Data Mode (Apple devices) or Data Saver on a metered network (Android), nothing is sent at all and the count is simply lost. The timer is unaffected and says nothing about it.

What the app never touches

No location, contacts, photos, microphone, health or fitness data, calendar or address book. The camera is used only to read a QR code, as described above. The app reads no sensors. It plays sound in the background, because that is the point of a timer lying on the ground with the screen locked; on Android, that is why it shows a notification while a timer is running or shared. It records nothing.

The timer itself works entirely without an internet connection. Nothing it does on the shooting line needs one: with no connection the counters above are simply lost, and nothing else changes.

Links out

The settings screen offers a link to the store page for the CapTarget Archery app, and the star in the corner offers one to this app's own review page. Opening either takes you to the App Store or Google Play, where Apple's or Google's terms and privacy policy apply.

Presses on those two buttons are counted, as bare totals with nothing attached to them, because that is the only way to know whether they earn the space they take. We learn nothing about what you do once the store has opened.

What Apple, Google and Microsoft may pass on to us

We integrate no crash-reporting tool, no advertising, and no third-party tracker. The anonymous counters described above are the only measurement in the app, and we built them ourselves rather than adding somebody else's kit.

Apple may separately show us aggregate figures in App Store Connect (downloads, crashes, OS versions) if you have agreed to share that information with developers in your iOS settings. It reaches us aggregated and anonymous: it cannot identify you. You can turn it off in Settings > Privacy & Security > Analytics & Improvements.

In the same way, Google (in the Play Console) and Microsoft (in Partner Center) show us aggregate figures on installs and crashes, depending on your device's diagnostics settings. They cannot identify you either.

Children

The app collects no personal data, from children or anyone else. It contains no advertising, no user-generated content and no way to communicate with third parties. The counters described above are anonymous totals, and are no different for a child than for anybody else.

Your rights (GDPR)

We hold no personal data about you. The counters are anonymous totals. Once a +1 has been added to a shared figure, nothing remains that relates to you: nothing to disclose, correct or erase, and no way for us to find "your" entry even if you asked for it.

The one record kept per installation is the anti-abuse ledger described above. It holds a count of writes and a date, and is never joined to what was counted. Deleting the app ends it: the anonymous account lives on your device, and a new installation is a new account.

Everything else described here stays under your control on your device. To erase it, delete the app.

If you nevertheless believe your rights are not being respected, write to support@captarget-archery.com. You may also lodge a complaint with your national data protection authority; in France, the CNIL (www.cnil.fr).

Changes

If this policy changes, the date at the top of this page changes, and the current version is published at this address. Any change that widened what the app transmits would be announced in the release notes.

Contact

support@captarget-archery.com