Privacy Policy

1. Scope and contact

This Privacy Policy describes Chocks Pilot logbook, the CHOCKS iOS and Android application, and the static flychocks.com website. CHOCKS is operated by Danish Yashin Dhamaskar, an individual based in India. Privacy questions may be sent to privacy@flychocks.com.

2. Records on your device

The app stores flights, duties, aircraft, people and crew details, certificates and qualifications, notes, imported source rows and a signature in local SQLite storage. These records can include licence, medical or other sensitive details you choose to enter. The core logbook works offline. The app does not continuously sync the full logbook to a CHOCKS server.

You can choose a local or Google Drive backup and export files through your device's sharing controls. Those copies leave the app when you choose a destination. A portable backup includes many logbook and settings tables, but excludes the pilot signature, portal connection and temporary weather cache. Review exported files before sharing them.

3. Connected services

Account and sign-in

Supabase handles email and password authentication and account records. Apple or Google may be involved if you choose their sign-in option. The app stores session tokens in device secure storage. The operational provider for authentication email delivery is not yet confirmed.

Optional roster connection

With your consent, the backend stores a crew-portal address and username and an encrypted password. It uses them to retrieve roster and report data on your behalf. Pending results can remain until fetched and cleared, overwritten, or the portal or account is deleted. You review imported results before saving them locally. CHOCKS is independent of crew-system operators and airlines.

Other connections

Google Drive receives backups you choose to upload. AviationWeather.gov receives requested airport identifiers for METAR and TAF retrieval; network metadata may accompany requests. RevenueCat and the Apple App Store or Google Play handle subscription offerings and purchases. The audited app receives subscription status and expiry information, not payment card numbers. Support email you send is handled by the email services involved in delivery.

Website and diagnostics

The static website source includes no analytics or advertising tracker. No third-party analytics or crash-reporting SDK was found in the audited app code. Hosting providers, operating systems, app stores and connected services may handle technical logs under their own arrangements; their retention is not established here. The audited app schedules local notifications rather than registering a remote push token.

4. Retention and deletion

Local records remain until you remove them, delete the app, or complete in-app account deletion. Portal credentials and backend records persist until the connection or account is deleted. Pending roster results are cleared on retrieval, overwritten, or deleted with the connection or account. Hosting log and backup retention periods require confirmation.

The in-app account deletion flow requires an export first. After backend deletion of portal records and the Supabase account succeeds, the app attempts to erase its local database and session. If local erasure fails, records may remain on the device and the app offers a retry. Account deletion does not cancel an app-store subscription or remove files you exported or uploaded to your Drive. See account deletion for current instructions.

5. Choices and rights

You can use the core logbook without signing in, choose whether to connect a portal or Google Drive, review imports and export records. You may request access, correction or deletion of service-held information, subject to applicable law, at privacy@flychocks.com.