HamPilot

Privacy Policy

Effective July 5, 2026

What we collect

Account basics (email, name, callsign, grid square), the radio data you enter (logbook, equipment, plans), and standard technical logs (IP, browser type) for security and debugging. Payment details go directly to Stripe — we never see or store card numbers.

What stays in your browser

Third-party service credentials you connect (LoTW username/password, QRZ Logbook API key) are stored only in your browser's local storage and sent per-request to perform the sync you asked for. They are never written to our database.

How we use it

To run the product: sync your data across devices, personalize predictions to your station, process payments, and send emails you've asked for (like band alerts). AI features send the relevant context of your request (like your gear list or location for a plan) to our AI provider (Anthropic or OpenAI) to generate the answer; it is not used to train their models under our API terms.

What we don't do

We don't sell your personal data. We don't show third-party ads. We don't share your data except with the processors that run the service (Supabase for the database, Vercel for hosting, Stripe for payments, Resend for email, AI providers for AI features) under their data-processing terms.

Public information

Callsign lookups display information already public in FCC license records. Your own public station page shows only what you choose to put on it.

Your controls

Export your logbook anytime (ADIF/CSV). Delete your account and your data is removed from production systems within 30 days. Email support@hampilot.com for access or deletion requests.

Cookies

Only what sign-in requires (Supabase auth session). No advertising or cross-site tracking cookies.

Changes & contact

Material changes announced in-app or by email. Questions: support@hampilot.com — Black Vector Technologies LLC, Arab, Alabama, USA.

See also the Terms of Service.