Account information. Your email address, used to sign you in via a magic link. Until you add an email, you can use the app under an anonymous session; that session's data lives on your device and in our database until you sign in, which claims it. If you never sign in, that data simply stays until you ask us to remove it.
Everyday Ultra status. If you redeem an Everyday Ultra access code, we store the fact that you're a coached athlete so the app stays free for you.
Race planning data. The plans you build: race and course details, GPX files you upload, aid stations, pacing goals, supplies, playbook tasks, and the names and roles you enter for your crew. You are responsible for having your crew's permission to add their names.
Race-day activity. Check-ins, arrival times, task completion, and notes logged by you or by crew members using your share link.
Location (optional). On the course map you can choose to share your location, which uses your device's GPS to show where you are on the course. This happens entirely in your browser — your location is never sent to our servers, stored, or shared with the runner or other crew.
Technical basics. Standard server logs (including IP address), the cookies needed to keep you signed in, and plan data cached in your browser's local storage so the app works quickly and survives a refresh. We do not run advertising or cross-site tracking.
Solely to run the product: storing your plans, computing your pacing model, syncing live race-day updates to your crew, and sending you login emails. We do not sell your data or share it with advertisers.
Vercel hosts the app and processes the requests your browser makes, including server logs. Supabase hosts our database, authentication, and file storage — your account, plans, and uploaded GPX files live there. Mapbox renders the course maps; when a map loads, your browser requests tiles from Mapbox directly. Resend delivers login emails and sees the address they're sent to. Each provider processes data only to provide its service. Data is stored and processed in the United States.
A race plan's share link grants access to anyone who has it — your crew sees the plan and can log check-ins, tap tasks, and add notes without creating an account. Treat the link like the credential it is, and share it only with your crew. If a link is shared further, we can't tell the difference.
If you're a crew member who arrived via a link: the runner who invited you controls this plan and can see everything you log in it. We collect what you enter (check-ins, task taps, notes) and standard technical basics. We don't create an account for you or contact you. If you want your name or entries removed, ask the runner who shared the link, or email us.
If you publish a course to the course library, that course copy — stations, coordinates, elevation, GPX track — becomes public for other runners to clone. Your playbook, crew, supplies, notes, and pacing goals are never included.
We use industry-standard measures to protect your data, including encrypted connections and access controls that restrict each account to its own data. No system is perfectly secure, and we can't guarantee absolute security.
You can view and edit your plans in the app at any time. To request a copy of your data, correct it, or delete your account and everything associated with it, email us at andrew.redden.94@gmail.com and we'll respond within 30 days. Deleting a plan removes its aid stations, playbook, crew list, supplies, notes, and check-ins.
Crew Angel isn't intended for anyone under 13, and we don't knowingly collect their information.
If this policy changes materially, we'll update the date above and note the change in the app.
Questions about privacy: andrew.redden.94@gmail.com