Privacy
Privacy notice
The short version: the names you race stay on your device unless you sign in to sync saved lineups between devices. We measure how the site is used with our own anonymous counts and Google Analytics, and neither ever receives the names you race. The personal data we keep is what you choose to give us: an email address for the hosted-events list, and, if you sign in, your account and the lineups you save. You can delete either yourself.
Last updated October 17, 2026.
Race lineups and results
Names, choices, duck looks, winner messages, and results stay in your browser's local storage on your device. Duck Race Derby does not upload them to our servers. They leave your device only when you choose to:
- Save a race file. The
.duckderbyfile is downloaded to your device. Who you send it to is up to you. - Copy a setup link. The setup is packed into the part of the link after the
#, which browsers do not send to our server when the link is opened. Anyone who has the link can read the names in it, so the site asks you to confirm first. - Copy or share a result. The text goes to your clipboard or your device's share menu.
- Sign in to sync saved lineups. Lineups you save while signed in are stored in your account, as described in Accounts.
To remove locally stored lineups, use Clear and Delete in the game, or clear this site's data in your browser settings.
Usage counts
To learn which features help hosts, the site counts events such as "race started," "race finished," "race file saved," or "organization page viewed." Each count is stored only as a daily total, sometimes with a broad category such as the field size range (for example, 11 to 30 ducks), the course, or the race length. Counts never include names, messages, email addresses, IP addresses, or any identifier for you or your device, and no cookies are used for them.
If your browser sends a Do Not Track or Global Privacy Control signal, the page sends no usage counts at all.
Google Analytics
We use Google Analytics 4 to understand which pages people find and which race features they use. It records page views and actions such as "race started," "race file saved," or "signup form submitted," along with general details Google collects from your browser, such as device type, approximate location (country or city), and the page that referred you.
What we never send to Google:
- the names, choices, or messages in your race;
- your email address, or any confirmation or unsubscribe link;
- setup links: the part of the address that holds a lineup is removed before Google sees the page address.
Details we attach to actions are broad categories only, for example a field size range of 11 to 30 ducks, the course, or the type of event chosen on the signup form. Advertising features and Google signals are turned off, and the data is not used for ads.
Google Analytics sets first-party cookies (named _ga and _ga_...) to tell visits apart. Visitors in the European Economic Area, the United Kingdom, and Switzerland are measured without these cookies. Google Analytics does not load at all if your browser sends a Global Privacy Control or Do Not Track signal, and you can also block it with Google's opt-out browser add-on. Google describes its handling inhow Google uses information from sites that use its services.
The hosted-events email list
If you join the list on the organization events page, we store:
- your email address (required);
- anything optional you chose to give: organization name, type of event, approximate size, and timing;
- the consent wording you agreed to, its version, the time you agreed, and the page you signed up from;
- whether you have confirmed, and when we last emailed you.
Why: to email you about hosted organization events, meaning when they open and important changes before launch, and to understand, in total, how many organizations are interested and what kinds of events they run. We don't send general marketing to this list, and we never sell or rent it.
Confirmation: you are only on the list after you click the confirmation link we email you. Links work once and expire after 48 hours. Unconfirmed signups are deleted after 30 days. When you confirm, the site owner receives an email with the details you entered, so we can follow up about your event.
Leaving: every email has a link to unsubscribe or to delete your details completely. Unsubscribing stops all email; deleting removes the record. We keep confirmed signups until hosted events launch and for up to 12 months after, unless you leave first.
We don't ask for a phone number and we don't collect the names of anyone taking part in your event.
Accounts (optional)
Accounts exist so people who host races, such as teachers, team leads, and event organizers, can open their saved lineups on more than one device. Racing never requires an account, and students never sign in. Accounts are free. You can sign in with Google or with a single-use link sent to your email; there are no passwords.
If you sign in, we store:
- your email address, and your name if you sign in with Google and Google shares it;
- the lineups you save while signed in, including their names and choices, race name, course, duck looks, race length, and winner message;
- sign-in records: when you last signed in, and secure tokens for your active sessions (stored only in scrambled form).
We use this only to show your saved lineups on your devices. Lineups are not shared with anyone, are not used for analytics or advertising, and never appear in our usage counts or in Google Analytics. We suggest first names or nicknames for students. Lineups you race without saving are not stored.
Deleting: deleting a saved lineup removes its names from your account; a blank record remains so your other devices know to remove it too. Deleting your account on the account page permanently removes your account, sessions, and every synced lineup. Signing out on a shared computer can also remove your lineups from that computer.
Service providers
These companies process data for us, only to provide the parts of the service listed:
| Provider | What for | Data involved |
|---|---|---|
| Hostinger | Hosting the website and its server | Standard web server logs, which include IP addresses and are kept by the host for security and operations |
| Supabase | Database hosting | Hosted-events list entries and daily usage totals |
| Resend | Sending confirmation and update emails | Your email address and the email content |
| Google (Sign in with Google) | Optional sign-in | Your Google account email, name, and account identifier, shared by Google when you choose to sign in with it |
| Google (Google Analytics 4) | Website analytics | Page views, feature use, device and approximate location details, and analytics cookie identifiers, as described above |
Our server briefly uses your IP address in memory to limit repeated form submissions. It is not written to our database.
Cookies
The site uses Google Analytics cookies as described in the Google Analytics section. If you sign in to an account, a sign-in cookie keeps you signed in for up to 90 days on that browser. The site owner's private dashboard has its own sign-in cookie. The race stores your lineups in your browser's local storage, which is sent to us only if you sign in to sync them.
Children
Teachers use the race with students. Students don't create accounts or give us any information, and class lists stay on the teacher's device as described above. The hosted-events list is for adults organizing events.
Your rights and contact
You can ask to see, correct, or delete the information we hold about you, or object to how we use it. The unsubscribe link in any of our emails handles deletion instantly. For anything else, email hello@duckracederby.com. If we change this notice in a way that affects the email list, we will tell subscribers before the change applies.