Custom image stays local
Homepage image data stays on your device.
Privacy Policy
What PilotCB stores on your device, what it does not collect, and how aviation data flows through the product.
01 · Overview
Privacy at a glance
Presentation preferences stay in your browser. Account and Early Access records are held server-side to provide and protect access.
Public page-view analytics
Vercel Web Analytics provides aggregate public-page usage statistics without third-party analytics cookies.
One PilotCB account
Registration, Early Access, and Admin use the same managed authentication service and secure session cookies.
Local preferences only
Lightweight settings are stored in your browser.
Aviation source requests
Official and selected supplemental sources provide aviation data.
02 · On your device
Custom background and local preferences
Your background image and lightweight preferences remain browser-local in the current architecture.
01 · SelectYour image
JPEG, PNG, WebP, or AVIF.
02 · ProcessYour browser
The image is handled on your device.
03 · StoreIndexedDB
Local storage where available.
Not uploaded to PilotCB servers.
When you upload a custom background image for the PilotCB homepage, the image data stays on your device. PilotCB does not upload, store, or serve custom image bytes from its servers.
The image is saved in your browser's IndexedDB where available. A lightweight theme and focal-point preference may be kept in localStorage. These are browser-local values only.
Custom images do not synchronize across devices. If you clear your browser or site data, the custom image will be removed. If IndexedDB is unavailable in your browser, the image may persist only for the current session.
Accepted formats are JPEG, PNG, WebP, and AVIF. Other file types are not uploaded or processed.
Local settings
Local preferences and settings
PilotCB stores lightweight settings in your browser's localStorage. This includes your selected homepage image, last visited airport, favorite airports, recent airports, and Pro Workspace preferences such as basemap mode, waypoint visibility, and ETOPS parameters.
No personal identifying information is stored. The data exists only in your browser and is not transmitted to PilotCB servers except as part of operational API requests you initiate, such as airport or flight lookups.
Browser data handling
Cookies
Essential secure cookies carry the managed session and request-protection state. Preference and settings data use localStorage and IndexedDB instead.
Analytics and tracking
PilotCB includes Vercel Web Analytics for aggregate public-page usage statistics. It does not use third-party analytics cookies. PilotCB removes query parameters and fragments from tracked page URLs and does not load this integration on the private Pro workspace, Precision Queue, or Admin routes.
No custom events containing account identities, email addresses, user identifiers, or flight data are instrumented. Hosting and network infrastructure may process ordinary technical request information such as IP address and request metadata needed to deliver and protect the service.
See Vercel Web Analytics privacy information for the service's data handling.
Aviation data sources
PilotCB retrieves weather, airport, and operational information from official and selected supplemental sources. FAA and official aviation data form the core. Selected third-party sources add context where useful without replacing authoritative aviation data.
PilotCB uses FAA data and other authoritative aviation sources. Data is requested from those sources when you open a page or trigger a lookup. PilotCB does not maintain a separate record of your queries beyond what is stored locally in your browser.
Accounts and current release
Accounts and submitted information
Supabase Auth processes registration, sign-in credentials, email confirmation, and authenticator verification. PilotCB stores the stable account mapping, profile preferences, Early Access requests, confidentiality acknowledgement version and timestamp, entitlements, and administrative audit records. PilotCB does not store account passwords.
Authorized administrators can review registered accounts and requests and manually grant or revoke access. Early Access does not collect payment information or start the future commercial trial.
Privacy contact
For privacy questions and data requests, contact [email protected]. Do not include passwords or authenticator codes.
Changes to this policy
Changes to data collection, storage, or tracking practices will be reflected in an updated page before the change goes live.