Privacy policy
Effective date: October 5, 2026
Last updated: November 19, 2026
Apex Derby ("we," "us," "our") is race-day software made and run by Dave Wilson in Canada. It is for Pinewood Derby events. This policy says what information the service collects, why, where it is stored, who can see it, how long it is kept, and how to have it corrected or removed. It applies to the website at apexderby.com and the web application (there is no separate mobile app).
If you run a derby with Apex Derby, you are the one adding other people's information (your racers and their families). Section 6 says what that makes you responsible for.
1. Who this applies to
- Organizers: the people who create an account and run an event (owners and the organizers invited to help).
- Racers and their families: the children and adults entered in an event. They don't have accounts; the organizer enters their details.
- Spectators: anyone who opens a parent link or sees the display screen. They don't sign in. If they vote for design awards on a phone, we keep the name they type and their votes, which the event's organizers can see, and a scrambled (hashed) form of their internet address that only shows whether two ballots came from the same connection that day. Voter names are replaced 30 days after the event.
- Visitors to the public website.
2. What we collect
2.1 Your account
- Email address and the display name you choose.
- If you sign in with Google or Microsoft: they tell us your name and email address, and confirm the email is yours. We ask for nothing else: not your contacts, files, calendar or password.
- If you add them in Settings: your phone number and date of birth. Both are optional, and people on your team can't see them.
- Whether you've asked for reminder and news emails, and a record of each yes or no (section 9).
- For each event you make: who is hosting it (a name you type), what kind of group runs it if you say (Scouts or youth club, church, school, community group or something else), its contact email if you give one (families never see it), and the names and emails of the team members you invite.
- If you answer it: how you heard about Apex Derby (asked once, optional). We use it only to know which places bring people to Apex Derby.
- Your password is stored only as a one-way hash, so it can be checked but never read back. We never see it. If you use Google or Microsoft, we have no password for you at all.
- Event Pass purchases: Stripe handles payment and keeps the card details. We keep a record of what was bought, when, and the Stripe identifiers for it. Card numbers never reach us.
2.2 Your event
Everything you enter to run a derby:
- Racers: name, group (den, class, division), car name or number, weight, the owner or guardian's name, an optional email address, check-in status, and an optional photo or avatar you upload for the racer card.
- Car photos and cartoon icons: if you add a car photo, we may turn it into a cartoon icon of the car. That is done by Cloudflare Workers AI. Cloudflare already hosts the website and your event's data, so the photo isn't sent to any other company. Once the icon is made, parents' phones show the icon and not the photo, and the photo is shown only on organizers' screens, with two exceptions for design awards: the car showcase on the event's TVs shows each car's photo, and while phone voting is open the voting page on a parent's phone shows the photos so families can see what they're voting for. (The display screen's other views show the icon, unless an organizer chooses to show the photo.)
- Races: heat schedules, lane assignments, times, places, standings and awards.
- Timer readings from a connected finish-line timer, and any times typed in by hand.
- Settings: track and timer details, race formats, what the parent link shows.
- Files you import (a roster spreadsheet) and files you export (results, certificates, a backup of your event).
2.3 How the service is used
- Server logs: our hosting provider records the usual web-server details for each request (address, browser, time, page) for a short period, for security and troubleshooting.
- Our own activity and error log: when something goes wrong in the app, or a significant action happens (an event created, a pass used, a site admin viewing an account), we record an entry with identifiers and counts, not racer names. This lives in our own database. Apart from the cookieless visit counter below, we don't use an outside analytics or tracking service inside the app.
- Timer logs: when you connect a finish-line timer, the app records what the timer sends (lane numbers, times and its own messages) and the questions the app sends it, with the timer brand you picked, the cable's USB ids and your browser, and sends that record to us so we can support more timers. It holds no racer names.
- Website visits: Cloudflare Web Analytics counts visits to every page of the site, including the app, parent pages and the display screen, so we can see how many people use it and which pages are slow. It sets no cookies, doesn't identify you, doesn't follow you to other websites, and its numbers are only ever totals.
- How you found us: the first time you open a page on a visit that came from an ad, a link with tracking tags (like utm_source) or another website, we save a small cookie of our own (apex_src, kept 90 days) with where you came from: the ad or site, the campaign tag, the page you landed on and the date. When you create an account we keep that note with the account so we know which ads and links bring people to Apex Derby. It holds no name or email, it isn't shared with anyone, and we don't set it when a visit gives no hint of where it came from.
- Advertising measurement: we advertise on Meta (Facebook and Instagram) and may also advertise on Google and Reddit, and we use their tags to measure whether our ads work. On our public pages, the sign-up pages and the billing page only (never on an event, a racer, a parent page or the display screen), those companies may set their own cookies and receive your visit to the page, the ad or page you arrived from, and, when you create an account or buy an Event Pass, that event (the Event Pass price is sent, a racer's name never is), along with your IP address, browser details and a one-way scrambled (hashed) version of your email address. Where you are in Quebec, the European Union, the European Economic Area or the United Kingdom, we ask first and use none of this unless you click Accept. Elsewhere it is on until you turn it off, and the notice that appears has a button to do that. Either way you can change your mind at any time with "Cookie settings" at the bottom of our public pages; your choice is remembered for 12 months. Each company handles what it receives under its own privacy policy. Apex Derby is a service for adults (organizers and parents), and our advertising is not directed at children.
2.4 On your own computer
To keep working when the hall's Wi-Fi drops, the app keeps a copy of your event in your browser's storage on the race laptop (IndexedDB and local storage), along with a queue of changes waiting to be sent to the server and up to 30 automatic and 20 manual backups of your event. These stay in that browser until you clear its site data or delete the event. Sign-in uses the usual session cookies; the app itself sets no advertising cookies.
2.5 Messages
- Invitations and trial links you ask us to send, and who they went to.
- Feedback you send from the Feedback button, and your replies to the short survey we email the morning after a race.
- Anything you email us at hello@apexderby.com.
3. What we use it for
- To run your event: schedules, timing, the display screen, the parent link, results and certificates.
- To sign you in, send you receipts, invitations, trial links, and the morning-after survey.
- To support you. If you ask for help, a site administrator (Dave) can open your account in a "view as" mode. Every action taken that way is logged, billing can't be touched, and the account owner is emailed a notice.
- To find and fix problems, using the error log described above.
- To meet legal obligations and keep the service secure.
We don't sell or rent personal information, we don't build advertising profiles, and we don't send marketing email lists. We may publish totals and averages across all events (how many derbies ran, typical heat counts) that identify nobody.
4. Where it is stored
Apex Derby runs on services based in the United States:
| Service | What it does | Where |
|---|---|---|
| Cloudflare | Hosts the website and application, the database, sign-in, live updates and uploaded files, sends our email, and makes the cartoon car icons (Workers AI) | Database in eastern North America; pages served from Cloudflare's worldwide network |
| Stripe | Payments | USA |
| Resend | Sends our email when Cloudflare can't, and replies from our support inbox | USA |
| Google, Microsoft | Sign-in, only if you choose "Continue with Google" or "Continue with Microsoft" | USA |
If you are in Canada, this means your information, including your racers' names and results, is stored and processed outside Canada, mainly in the United States, and may be subject to United States law. Canada's privacy law (PIPEDA) allows this when you are told, which is what this section is for. Data is encrypted in transit (HTTPS) and at rest by these providers, and each account's data is walled off from every other account's by access rules checked on every database request.
5. How long we keep it
| What | Kept until | Why |
|---|---|---|
| Your account | You delete it, or ask us to | So you can come back next year |
| Your event's results, car names and settings | You delete the event (Dashboard → Data), or your account | They're your records |
| Racers' names and parent emails | 60 days after race day the owner is emailed; 14 days later they are locked: encrypted, with the racers shown as "Racer 1", "Racer 2", and the key emailed to the event's owner. Pressing "Keep names longer" waits another 60 days; typing the key puts them back for another 60. Deleted with the event or your account | So you can look back without us keeping children's details readable |
| A race, round or racer you deleted | A recovery copy stays with the event so you can undo the deletion for 7 days, then it is deleted; it also goes when the event is deleted | So an accidental deletion can be undone |
| An event you deleted | Gone from the app straight away. A recovery copy (with its car photos) is kept for 7 days so you can undo it, then deleted for good | So an accidental deletion can be undone |
| The parent link | Closes 3 or 7 days after race day (your choice); you can also switch it off at any time | Families follow the race, then it's over |
| Restore points of an event | A full copy of the event, taken while it changes and before big changes, kept 7 days and then deleted; they also go when the event is deleted | So a mistake on race day can be rolled back |
| Purchase records | 7 years | Tax and accounting rules |
| Our activity and error log | Until we clear it; deleting your account removes your name from it | Fixing problems |
| Timer logs | Until we clear them; deleting your account removes the link to you | Supporting more timers |
| Hosting and email delivery logs | A short period set by Cloudflare and Resend | Security and troubleshooting |
Deleting an event in the app removes it straight away, apart from a recovery copy kept for 7 days in case it was a mistake; after that the copy and the event's car photos are deleted for good. To delete your account, email hello@apexderby.com: we delete your account and your events within 30 days and tell you when it's done. Purchase records are kept for the time in the table above.
6. Running a derby with other people's information
As the organizer, you are the one collecting your racers' details, and you are responsible for having a basis to do so. For a pack, church, school or club, that is normally your registration form or your group's existing permission. In particular:
- Tell families that results, car names and car pictures (a cartoon icon of each car, or the photo if you add one and choose to show it) will appear on the display screen in the room and on the parent link, and that car photos appear on the TV's car showcase and on the voting page while phone voting is open. Keep people out of the car photos.
- The parent link shows full names by default, and you can switch to first name and initial ("Dave W.") or to no names at all (cars only) in Event details. Switch unless you have permission for full names.
- Don't enter more than you need. The optional email and photo fields can be left blank.
- Children never create accounts or sign in. Apex Derby does not knowingly collect information directly from a child under 13 (COPPA, USA) or a minor; everything about racers comes from the organizer.
7. Who can see what
- Your team: the owner and the organizers on an event see everything in it.
- The parent link: off until you turn it on. While it's on, anyone with the link or QR code sees the schedule, live times, standings, car names, a cartoon icon of each car (the photo only until its icon is made), and racers' short or full names as you've chosen. It never shows email addresses, weights or anything else from the roster, it is not listed by search engines, and it carries no advertising and nothing that identifies or follows visitors (only the cookieless visit counter in section 2.3).
- The display screen: whatever is on the TV or projector in the room, with the same name rule.
- Apex Derby staff: for support, as described in section 3, logged and notified.
- Our providers in section 4, only as needed to run their part of the service.
- The law: we will disclose information if legally required, and we will tell you unless we are not allowed to.
8. Your choices and rights
Wherever you live, you can:
- See what we hold about you or your event: much of it is in the app; email us for the rest.
- Correct it: edit it in the app, or ask us.
- Export it: results as CSV and a full backup of your event as JSON, from Dashboard → Data.
- Delete it: delete an event from Dashboard → Data, or ask us to delete your account.
- Ask on behalf of a racer: if you're a parent and want a racer's details corrected or removed, contact the organizer first (they hold the roster); if that doesn't work, email us and we'll help.
Email hello@apexderby.com. We answer within 30 days, usually much sooner. Canadian residents may also complain to the Office of the Privacy Commissioner of Canada; California residents have the rights in the CCPA, and we do not sell or share personal information as that law defines it.
9. Email
Most email we send is about your account or your event: sign-in and password messages, receipts, invitations and trial links you requested, a notice if a site admin views your account, and one short survey the morning after a race. Canada's anti-spam law (CASL) treats these as transactional messages. If you'd rather not get the survey, reply and say so.
Reminders and news. A few times a year at most, we may send a reminder or an announcement: for example, a note in the fall to book this year's derby, or word that Event Pass checkout is open. We send these only if you said yes: the box when you sign up or set up your account (never ticked for you), or the News emails switch in Settings. We keep a record of each yes or no, with the address it was for, where you gave it, the words you were shown and when, so we can show that you asked; it is deleted with your account.
Every reminder or news email says it's from Apex Derby, includes our mailing address and a way to reach us, says why you're getting it, and has an unsubscribe link. The link works without signing in and takes effect straight away (the law allows up to 10 business days); your mail app's own Unsubscribe button works too, and so does turning News emails off in Settings or replying to ask. Unsubscribing never affects the account and event emails above. We never send on anyone else's behalf or share your email address.
10. Security
- All traffic is encrypted (HTTPS), and our providers encrypt stored data.
- Passwords are stored only as one-way hashes.
- Every database request is checked against access rules, so one account cannot read another's data unless it was invited to that event, even by mistake in our code.
- Key race-day moments (a race started, heats built, an emergency reset) are logged with the account that made them.
- Site admin access to your account is logged and triggers an email to you.
No system is perfectly secure. If we learn of a breach affecting your information we will tell you as the law requires. Please report anything that looks wrong to hello@apexderby.com.
11. Changes to this policy
When this policy changes we update the dates at the top and post the new version here. For changes that matter to you (new uses of data, new providers), we also email account holders.
12. Contact
Apex Derby
Dave Wilson
hello@apexderby.com
Canada
We aim to answer privacy questions within 30 days.