Data & privacy
This page describes how the current RacePermit pilot handles information when you use its forms and workspace.
Pilot requests and feedback
Pilot requests collect your name and email, along with any optional event details and notes you provide. Feedback forms collect the message and optional contact details, and may include the project context shown in the workspace. These records are stored using Supabase. Pilot requests can also generate an email notification to the team through Resend.
Routes and project information
GPX files are parsed in your browser. Route analysis uses sampled course coordinates with Mapbox to suggest likely authorities; the map also uses Mapbox services. Workspace edits can be stored in this browser’s local storage. Choosing Save stores a project snapshot in Supabase, including route points, dates, contacts, document filenames, statuses, and notes.
Document contents and private links
Choosing a document records its filename; it does not upload the file contents. A private project link gives access to the saved plan. An editable link also allows changes. Share these links only with people you want to have that access.
Site measurement
The production site includes Vercel Web Analytics and Speed Insights to measure site usage and performance.
Questions about your information
For questions about information you have shared, or to request correction or deletion, contact racepermit@gmail.com. Include enough context to identify your request without sending private edit tokens or sensitive documents.