Privacy policy
What checkride.io collects, how we use it, where it lives, and what you can do about it. Plain language first; we'll cite the formal pieces where it matters.
Summary
- We collect what we need to audit your logbook and operate your account: the logbook file you upload, the parsed flight rows, your email and name (via Clerk), and standard product analytics.
- Your logbook file and parsed entries are stored in our infrastructure (S3-compatible object storage and a managed PostgreSQL database). We do not sell or rent any of this data.
- You can request export or deletion of your account, files, and audit results at any time by emailing privacy@checkride.io.
What we collect
Account data
When you create an account we collect your name, email address, and authentication identifiers. Authentication is handled by Clerk; their privacy policy governs the credential side of the flow.
Logbook files and audit results
When you upload a logbook (CSV exports today; OCR for scanned PDFs is on the roadmap), the file is stored in S3-compatible object storage and the parsed flights, audit requirements, and results are written to PostgreSQL. We retain these so you can re-open your audit and a future DPE can verify the underlying data.
Product analytics
We use PostHog, Google Analytics, and Vercel Analytics & Speed Insights to understand which parts of the funnel work and where users get stuck. These collect standard pageview, click, and performance signals along with a hashed visitor identifier.
What we don’t collect
We don’t collect payment information today (the audit is free during beta). We don’t access third-party flight-tracking, ForeFlight, or MyFlightbook accounts — you export the file yourself and upload it.
How we use it
- To run the audit you asked for and return the result.
- To let you re-open and re-share your audit and report later, including with a DPE.
- To operate, debug, and improve the service.
- To email you about your account or material changes to the service. We do not send marketing email without explicit opt-in.
Where it lives
Application infrastructure runs on Vercel (United States). The database is managed PostgreSQL; uploaded files live in S3-compatible object storage. Authentication runs on Clerk. Analytics events are sent to PostHog, Google, and Vercel.
Who we share it with
We share data with the infrastructure subprocessors above only to the extent required to operate the service. We do not sell or rent your data to third parties. We will disclose data when legally required (subpoena, court order, or other valid legal process) and will, where permitted, notify you first.
Retention
Logbook files and audit results are retained for as long as your account is active. If you close your account or email privacy@checkride.io with a deletion request, we delete uploaded files and audit results within 30 days, and remove them from backups within the next backup-rotation cycle.
Your choices
- Access & export. Request a copy of the data tied to your account at any time.
- Correction. Update profile data directly in your account, or email us for anything you can’t edit yourself.
- Deletion. Delete your account, all uploaded files, and all audit results.
- Opt-out of analytics. Use a Do-Not-Track signal, uBlock Origin, or your browser’s privacy controls. We honor Global Privacy Control where the browser sends it.
Email privacy@checkride.io for any of the above. We respond within 30 days, typically much sooner.
Children
Checkride.io is not directed to children under 13 and we do not knowingly collect data from them. The minimum age to hold a Student Pilot Certificate is generally 16 (14 for glider/balloon), and our service is designed for that audience and older.
Changes to this policy
We’ll update the “Effective” date above when we make material changes and, where appropriate, notify account holders by email. Older versions can be requested at the privacy email below.
Contact
Privacy questions, requests, and disputes: privacy@checkride.io. For anything else, see the contact page.