Privacy notice

Cadence is run by one person, with no company behind it. That person is the data controller, who answers for your data under UK data protection law, and "we" below means them.

Email hello@cadencerange.com

For your account: your email address, an account ID, how you sign in, and when you joined and last signed in. If you sign in with Google, it also passes on your name and a link to your profile picture. Apple may pass on your name the first time, and lets you hide your real email address from us.

From your training: what you enter in the app. That means your profile (name, experience, dominant hand, disciplines, goals and preferences), clubs and ranges, your kit (firearm type, make, model, calibre, optic and notes), ammunition stock, sessions, strings, shot times and scores, drills and templates you make, matches, plans and checklists.

A firearm serial number, if you add one, stays on the device you typed it on and is never uploaded. Signing out removes it, so save a backup file first if you want to keep it.

From signing in: Supabase, which runs our sign-in system, records your IP address and device or browser details against each sign-in session.

From the website: GitHub, which hosts it, logs visitors' IP addresses for security, whether or not they sign in.

From feedback: whatever you send with Send feedback. The message carries the app version and your device details, you can read it before it goes, and it travels through whichever app you choose to send it with.

About testers: a list of who is testing, with your name, email address, which phone you use and which timer you own.

From TestFlight, if you test on an iPhone: Apple shows us the email address you were invited with, the name we entered for you, how many times you used each build, your device model and software version, and crash logs. If you send feedback through TestFlight we also see your comments and screenshots. Apple's TestFlight notice has the full list.

The app does not collect your location or contacts, and it has no analytics, tracking or advertising. It uses Bluetooth only to connect your shot timer.

We use your account and training to run the app and keep your training on every device you sign in on. The legal basis is that this is needed to provide what you signed up for (a contract).

We use sign-in records to keep the service secure, and feedback, the tester list and TestFlight data to run the beta and fix what goes wrong. The legal basis for these is our legitimate interest in doing those things.

Cadence suggests drills and sessions from your own record. That happens inside the app, and we make no automated decisions with a legal or similarly significant effect on you.

You need an account to use Cadence, and an account needs an email address, given directly or through Apple or Google. Setup also asks for a name, which can be any name you like, the disciplines you shoot and a range. Everything else is up to you.

Supabase Pte. Ltd., of Singapore, runs the database and the sign-in system and sends the sign-in codes by email. It is our processor, so it acts on our instructions.

Apple and Google handle your sign-in if you choose them, under their own privacy policies. Apple also runs TestFlight, and GitHub hosts the website.

We do not pass your data to anyone else unless the law requires it.

Your account and training are stored with Supabase in Ireland, and each device you sign in on holds a working copy. Ireland is in the European Economic Area, where UK law allows personal data to go.

Our agreement with Supabase covers any transfer beyond the UK and the European Economic Area with standard contractual clauses and the UK Information Commissioner's approved addendum. GitHub, Apple and Google may handle data in other countries, including the US, under their own terms.

Your account and training stay until you delete the account. That removes them from the database at once, and Supabase's daily backups can hold a copy for up to seven days after.

When you delete a single record its contents go, and a marker with its ID and the time stays until the account is deleted, so your other devices know it has gone.

We keep feedback and the tester list while the beta runs, and delete what we no longer need when it ends. Apple keeps TestFlight feedback for a year. Supabase and GitHub set their own periods for their logs.

To delete your account, go to Profile, then Account, then Delete my account. It removes the account and every record in it, and takes your training off that device. It cannot be undone. Any other device you were signed in on returns to the sign-in screen within about an hour, and its copy stays until someone signs in there again, or you remove the app or clear the site's data.

You can ask us for a copy of your data, and ask us to correct it, delete it or limit how we use it. You can also object to uses based on legitimate interests, and ask for your data in a form you can move elsewhere. We have one month to reply.

Much of this is in the app. You can edit your training directly, and Profile has Save a backup file and Export strings as CSV.

You can complain to the Information Commissioner's Office, the UK regulator, at ico.org.uk/make-a-complaint.

When this notice changes, the date at the top changes too, and we will tell testers about anything important.