Your data should be as clear as the runway.

Information shown in the directory

DPE names, locations, authorizations, public contact details, and source links may come from public aviation directories or public professional listings. This is directory information about aviation professionals, not information collected from a pilot's device. Designation and authorization can change, so users should always confirm current status with the FAA before scheduling.

Mobile app

The mobile app stores saved DPEs, pending pilot-report drafts, hidden-report choices, a random installation identifier, per-report editing credentials, and missing-directory tips locally on the device. A completed pilot report is queued locally when offline and transmitted to Checkride Radar when a connection is available. Once accepted, that report becomes visible on the shared DPE profile and contributes to its public summary. Device-only preferences can be removed by clearing the app's storage or uninstalling the app.

Reports submitted to the current test data environment and future production reports are stored separately. A production launch can therefore begin with clean public ratings without deleting later production reports or mixing them with prelaunch submissions.

When you tap a phone number, email address, FAA locator link, or public directory link, the app hands that action to your phone, email app, or browser. The destination service then operates under its own privacy policy.

Website accounts and submissions

The mobile app sends a random installation identifier with pilot-report, contact-attempt, helpful-vote, and moderation requests. The server stores a one-way hash of that identifier to limit duplicate reports and abuse; it is not used for advertising. This installation identity is not a durable cross-device account: clearing app data, reinstalling, using Expo Go instead of an installed build, or using another device can create a different identifier. For new mobile reports, Radar also stores a random editing credential on the submitting installation and only a one-way hash on the server, so normal app updates retain edit access without allowing name or device spoofing. Clearing app storage, reinstalling, or switching app sandboxes can still remove that access; this is not authenticated cross-device recovery, and duplicate enforcement remains not reinstall-proof. When you sign in on the website, Checkride Radar receives an account identifier and basic account details needed to recognize you. The site may store DPEs you save, private outreach-tracker records, factual contact-attempt episodes, directory correction and missing-DPE tips, pilot reports, helpful votes, and reports of objectionable content. Contact-attempt episodes contain dates, selected contact methods, and an outcome; Checkride Radar does not collect message contents, screenshots, or the DPE's contact details in that record. Public profiles show only combined Contact Responsiveness statistics and reported-count wording, while the submitting user can retrieve their own current episode to edit or withdraw it. Missing-DPE tips are kept in a verification queue until checked. Public pilot reports display the checkride details and experience you submit, but do not publicly display your account identity. Public report data includes a separate pseudonymous contributor key derived from the server-side identity hash so another user can hide all reports from the same contributor without learning who that contributor is. For abuse prevention, the service may process a network address supplied by the hosting platform and store only a secret-keyed one-way hash in daily request-count buckets. The raw network address is not stored in the application database. Pilot reports and contact-attempt records also store the Terms and Privacy Policy versions accepted at submission.

Private disputes and owner decisions

A DPE, representative, or other affected person may privately submit a dispute concerning profile information or a pilot report. The dispute stores the claimant's name, email address, optional phone number, relationship to the DPE, disputed information, requested correction, and an optional public supporting-source link. This information is visible only to the owner and service providers needed to deliver the submission. A dispute does not verify the claimant's identity and does not automatically change public content. The service retains the owner's decision, note, and audit history for consistent moderation and dispute handling.

How information is used

• Provide and update DPE search, contact, and comparison features.
• Save private preferences and outreach status for signed-in users.
• Publish eligible pilot reports and calculate aggregated ratings and fee signals.
• Calculate separate, rolling Contact Responsiveness statistics from attested contact attempts.
• Screen written submissions, prevent duplicate or excessive submissions, investigate abuse, let users block report contributors, and moderate reported content.
• Maintain service security, diagnose failures, and comply with legal obligations.

A structured pilot report may include the practical-test type and date, initial or retest status, completed or discontinued status, category ratings, oral topics, flight tasks, approximate timing, neutral checkride-style observations, optional fee and scheduling facts, and an optional written gouge. Checkride Radar does not ask for a public pass/fail result. Structured selections are combined into checkride-specific Radar summaries that show sample size and recency; small samples are described qualitatively instead of being presented as statistically established conclusions.

Checkride Radar also records limited first-party product events such as search, profile and Radar views, report-flow start, step reached, completion, abandonment, and profile sharing. These events may include a pseudonymous account or installation identifier, DPE record number, checkride type, report-flow session, and step number. They do not include search text, precise location, aircraft, written gouge content, phone numbers, email addresses, or message contents. They are used to improve report completion and diagnose the service, not for advertising.

Access roles and future subscriptions

Checkride Radar is free to download, and all published pilot reports and gouges are free to read at initial public launch. The service stores an access mode and may store account-level roles or entitlements needed to provide administrator-approved complimentary access, verified instructor or flight-school access, contributor rewards, or a future Premium subscription. These records may include a pseudonymous account or installation identifier, role and verification status, entitlement source, status, start and end dates, and a store transaction reference. The launch app does not process a paid subscription and does not contain an advertising SDK. If paid digital access is introduced, purchases will use Apple's or Google's in-app billing system on the applicable mobile platform, and this policy and the store disclosures will be updated before activation.

Sharing, advertising, and sale of data

Checkride Radar does not sell personal data. The current mobile release does not contain ads or advertising trackers. Hosting and authentication providers may process limited technical and account information to deliver and secure the service. Information may also be disclosed when required by law or necessary to protect users and the service.

Retention and deletion

Device-only data remains until you remove it or uninstall the app. Synced pilot reports, pseudonymous installation hashes, contact-attempt episodes, helpful votes, moderation reports, and prior versions of edited or withdrawn reports remain on the server while needed to operate the service, preserve the integrity of community ratings, resolve disputes, meet legal obligations, or prevent abuse. You may request access, correction, or deletion through the developer contact displayed on the Checkride Radar app-store listing. Some records may be retained in de-identified form or when required for safety, fraud prevention, or legal compliance.

Security and children

Data transmitted to Checkride Radar is protected in transit. No online system can guarantee absolute security. Checkride Radar is intended for aviation applicants and professionals and is not directed to children under 13.

Questions or corrections

Email dperadar@gmail.com for privacy questions, data requests, or corrections to a public DPE profile. This policy will be updated before advertising or any materially different data handling begins.