Privacy policy
How Good to Go and Flight Logbook collect, use and protect information.
Last updated 22 September 2026
Calendar access is read-only. Your saved logbook is stored in your account, and you can export your entries or contact us about your data.
Who we are
Good to Go provides Flight Logbook, a personal pilot logbook at log.goodtogo.nz. The service is operated by Joel Wilkinson in New Zealand. This policy covers the public website at goodtogo.nz and the Flight Logbook application.
For privacy questions, access, correction or deletion requests, contact motoxcrazy@gmail.com.
Information we collect
- Account information: your Google account identifier, email address and basic profile information, supplied by Google when you sign in.
- Calendar information: event identifiers, titles, descriptions, locations and times from the roster calendar you configure. The app reads recent and upcoming events to identify flights.
- Logbook information: entries, flight and simulator times, aircraft details, routes, crew details, comments, imports and settings you provide. Flight details you choose to log from Calendar are stored in your logbook.
- Connection information: Google authorization credentials and app session information needed to keep you signed in and retrieve Calendar events.
- Technical information: hosting and request logs may include IP addresses, browser or device information, request paths, response status and timings.
- Support messages: information you send when contacting the operator.
Please only include crew or other people's information when you have an appropriate reason to record it, and avoid unnecessary personal details in comments or support messages.
How we use information
We use information to authenticate you, associate your records with your account, display roster flights, store entries, calculate summaries, produce exports, answer support requests and maintain the service's reliability and security.
Google Calendar information is used for the roster and logbook features you choose to use. We do not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Information is not routinely inspected by people; access for support or security is limited to what is necessary and permitted by Google's policies.
Google access
The current sign-in flow requests openid, email, profile and calendar.events.readonly. Basic identity permissions enable sign-in. Read-only event access lets the app display roster information. It does not let the app create, edit or delete Calendar events.
Google grants this event permission across calendars you can access. The app retrieves events from the calendar ID you enter in Settings; Google does not offer a per-calendar OAuth permission for this flow. The app does not request Google Drive or Google Sheets access.
Flight Logbook's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
You can revoke access in Google Account connections. Doing so stops future authorized Google access but does not automatically delete saved logbook records. If you connected before the permissions were reduced, remove the old connection and sign in again to replace the earlier grant.
You can browse this public website without signing in. Account access requires Google sign-in. Calendar roster features require Calendar permission and a valid calendar ID; manual entries do not require a roster calendar to be configured.
Storage, sharing and security
Supabase provides authentication and stores account information, logbook records, settings and encrypted Google refresh credentials. Vercel hosts the website and server endpoints. Google provides sign-in and Calendar APIs. These providers process information needed to deliver their services. Information may be processed outside New Zealand; the current Supabase database is hosted in Japan.
We may disclose information where required by law or where necessary to investigate abuse or protect the service, consistent with applicable law and Google's data-use restrictions. We do not publish your logbook as part of this website. Exports you download, email or otherwise share are under your control.
The service uses HTTPS, account access controls, encrypted server-side Google refresh credentials and protected session cookies. Ordinary database requests are restricted to the signed-in user's records. Authorized administration may be needed for support, security and data requests. No online service can guarantee absolute security.
Retention and deletion
We retain saved logbook records and settings while they are needed to provide your account, until you delete records or request account-data deletion. Google connection credentials remain until removed or replaced. Support correspondence and operational information may be retained as needed to address the request, operate the service or meet applicable obligations.
Deleting a live entry does not necessarily immediately remove copies from historical migration archives, operational logs or provider backups. These copies are handled separately. When requesting deletion, you can ask us to include archived records and stored Google credentials and explain any remaining retention.
There is currently no self-service button to delete an entire account. Email the operator to request account deletion. We may need to confirm your identity before providing information or making changes.
Your choices and rights
You can review and edit entries, delete individual entries, and download PDF or complete CSV exports in the app. You can also contact us to request access to or correction of personal information, ask for deletion, or raise a privacy concern.
If you are concerned about our response, you can contact the New Zealand Office of the Privacy Commissioner. Your rights depend on applicable law; this policy does not limit those rights.
Changes and contact
We may update this policy as the service changes. The date at the top identifies the current version. Material changes to how Google information is used will be reflected in this policy and any required consent process.
Privacy contact: Joel Wilkinson
motoxcrazy@gmail.com