Skip to main content

Privacy Policy

Effective Date: February 11, 2026 Last Updated: July 14, 2026

Hamtrax ("we," "us," or "our") respects your privacy. This Privacy Policy explains how we collect, use, store, and share information when you use the Hamtrax application, website, and related services (the "Service").

1. Information We Collect​

Information You Provide​

  • Account information: Email address, name, callsign, country, and license class.
  • Profile information: Display name, nickname, and profile photo.
  • QSO logs: Contact records you create or import, including callsigns, frequencies, modes, dates, times, and notes.
  • Location data: Grid square, coordinates, or city — depending on the location mode you choose (callsign lookup, device GPS, or manual entry).
  • User-generated content: Photos, livestream URLs, folder cover images, station equipment images, and feedback submissions.
  • Billing information: If you subscribe to a paid plan, payment is processed by Stripe (web and Android) or by Apple via the App Store using RevenueCat (iOS). We do not store your credit card number or full payment details — these processors handle them directly. We store only your subscription status, plan type, and the customer ID issued by the relevant processor.
  • Station equipment: Rig and antenna profiles, including names, descriptions, and photos you upload.
  • Integration credentials: If you connect QRZ Logbook, you provide the API key for the specific QRZ logbook you choose. Other optional integrations may request their own credentials as described in their setup screens.

Information Collected Automatically​

  • Device information: Browser type, operating system, and device identifiers.
  • Usage data: Pages visited, features used, and interaction patterns within the Service. This includes tutorial and walkthrough completion state (so we can avoid re-running first-run flows you've already seen).
  • Analytics data: We use Google Analytics 4 (GA4) — in the app via Firebase and on our website and documentation site (docs.hamtrax.com) via Google's gtag — to collect usage metrics. These include page views, sign-up and login completions, and interaction signals such as scroll depth, expanding explanatory sections, and clicks on App Store badges. In the app, signed-in activity may be linked using a pseudonymous Firebase user ID; Hamtrax does not send your email address, callsign, or name as the analytics identity. This data helps us understand how the Service is used and where to improve. IP addresses are anonymized on the documentation site, and analytics data is processed according to Google's privacy policies.
  • Analytics location exclusion: Before the production or beta web app loads GA4 or Microsoft Clarity, it asks a Hamtrax Cloud Function whether the visitor's approximate IP location may fall within 30 miles of Kansas City, Missouri. At app startup, the Function sends the public IP address to GeoJS for an approximate location and returns only an exclusion decision to the browser; the browser caches only that decision for the tab. Hamtrax application code does not write the IP address or returned coordinates to its databases or application logs. Google Cloud and GeoJS process request metadata under their respective privacy policies. Sessions within the radius, sessions whose reported accuracy area overlaps it, and sessions whose location cannot be resolved are not sent to GA4 or Clarity. This is not continuous physical-location monitoring, and the exclusion does not apply to docs.hamtrax.com.
  • Cookies and similar technologies: Our website and documentation site use Google Analytics cookies (such as _ga) to distinguish visitors and measure usage. Because these cookies are shared across hamtrax.com subdomains, a visit to our documentation and a later sign-up may be recognized as the same journey. You can block or delete these cookies via your browser settings.
  • Referral and campaign data: When you arrive from a marketing link, we record the campaign parameters in the entry URL (for example, utm_source and utm_campaign) so we can understand which campaigns bring people to Hamtrax. This is retained for the browser session, attached to that session's analytics events, and is not linked to your identity.
  • Session replay: We use Microsoft Clarity to record session replays of how the Service is used — including page interactions such as clicks, scrolling, and mouse movement — so we can identify usability issues and improve the Service. Clarity may also collect device and browser information. For signed-in activity, Hamtrax may send the same pseudonymous Firebase user ID described above so activity can be linked without sending your email address, callsign, or name as the analytics identity. Recordings are processed by Microsoft and are subject to Microsoft's Privacy Statement.
  • Crash and error reports: When the app encounters an error, we record an anonymous report containing the device class (mobile, tablet, or desktop), platform, app version, environment, the feature area in use, the error message and technical stack trace, and a random per-session identifier. These reports contain no account ID, callsign, page URL, or browser user agent and are not linked to your identity. We use them solely to find and fix problems in the Service. On the iOS and Android apps, error reports are also processed by Firebase Crashlytics.
  • Authentication data: OAuth tokens and session information from third-party sign-in providers (Google, Apple).

Information from Third Parties​

  • Callsign lookups: We query external databases (HamQTH, QRZCQ, QRZ Digital, DMR/global callsign data, and the FCC ULS amateur database) to retrieve publicly available callsign registration data such as name, address, grid square, and license class.
  • Activity data: We aggregate data from public amateur radio services (POTA and the FCC amateur radio database) to power activity discovery features.
  • Location imagery: We use Flickr's public API to source geo-tagged nature photography for park and location displays.
  • Map imagery: When you zoom into the detailed map view, map tiles are loaded directly from OpenStreetMap's public tile servers. Like any web request, these tile loads send your IP address and the requested map area to the OpenStreetMap Foundation; their handling of that data is described in the OpenStreetMap Foundation Privacy Policy.

2. How We Use Your Information​

We use collected information to:

  • Provide, operate, and improve the Service.
  • Create and manage your account.
  • Display your profile and QSO statistics to other users (based on your privacy settings).
  • Power location-based features such as distance calculations and map displays.
  • Resolve callsign data and derive default settings (band plan, license privileges).
  • Perform third-party integration actions you request, such as importing contacts from QRZ Logbook or uploading Hamtrax contacts to it.
  • Send account-security communications you request and, while your account remains active, eligible activity and product emails. Before each non-transactional automated send, Hamtrax rechecks that the authentication account is active and that applicable stored email preferences allow delivery.
  • Detect and prevent abuse, fraud, or violations of our Terms of Service.

3. How We Share Your Information​

We do not sell your personal information.

We may share information in the following circumstances:

  • Public profile data: Your callsign, display name, and profile photo may be visible to other Hamtrax users depending on your settings.
  • Service providers: We use third-party services (Firebase/Google Cloud for hosting, storage, and crash and error reporting — including Firebase Crashlytics on the iOS and Android apps; Microsoft Clarity for session replay analytics) to host, store, and process data on our behalf. These providers are bound by their own privacy commitments.
  • IP geolocation provider: Hamtrax sends the public IP address to GeoJS to obtain the approximate location used by the analytics exclusion described above. GeoJS's handling of that request is governed by the GeoJS Privacy Policy.
  • Payment processors: If you subscribe to a paid plan on the web or Android, billing is handled by Stripe, Inc. and Stripe receives the payment information you provide during checkout; Stripe's use of your data is governed by Stripe's Privacy Policy. If you subscribe through the iOS app, billing is handled by Apple via the App Store and entitlements are mediated by RevenueCat, Inc.; their use of your data is governed by Apple's Privacy Policy and RevenueCat's Privacy Policy.
  • External services you connect: When Hamtrax checks a connected QRZ logbook's status, or when you request an import or upload, Hamtrax sends your API key and the data required for that operation to QRZ over HTTPS. QRZ handles that data under its own privacy policy. Hamtrax does not automatically import or upload QRZ contacts without an explicit user action.
  • Legal requirements: We may disclose information if required by law, regulation, or legal process.
  • Safety: We may share information to protect the rights, safety, or property of Hamtrax, our users, or the public.

4. Data Storage and Security​

  • Your data is stored using Google Firebase (Firestore, Firebase Authentication, and Firebase Storage for user-uploaded media) with encryption in transit and at rest.
  • A connected QRZ API key is additionally encrypted before it is stored in a server-only Firestore document. Client applications cannot read that document, and the stored key is never returned to the app after connection.
  • Certain data is cached locally on your device (IndexedDB and session storage) for offline access and performance.
  • We implement reasonable technical and organizational measures to protect your information. However, no system is completely secure, and we cannot guarantee absolute security.

5. Your Location Data​

For app features, you control how Hamtrax determines your location:

  • Callsign mode: Location is derived from your callsign registration address (publicly available data).
  • Device mode: Location is obtained from your device's GPS with your permission. We do not track your location in the background.
  • Manual mode: You enter a grid square, coordinates, or city of your choosing.

You can change your location mode at any time in Settings. Location data is used for distance calculations, propagation estimates, and map features.

The analytics location exclusion described above is separate from these profile settings. It uses only an approximate IP-derived location, does not update your Hamtrax location, and is not used for app features.

Separately, when you open the POTA activation setup screen, Hamtrax requests a one-time GPS reading -- regardless of your chosen location mode -- to auto-fill the nearest park. On iPhone this shows the standard iOS location prompt the first time. It is a foreground reading used only to fill in your park; we do not track your location in the background.

6. Data Retention​

  • We retain your account data for as long as your account is active.
  • Disconnecting QRZ removes the stored QRZ API key. Deleting your Hamtrax account also removes the server-stored integration-credential document.
  • Practice contacts generated by the in-app guided walkthrough are temporary and are deleted automatically by a server-side cleanup task -- they are not retained as part of your logbook.
  • If you delete your account, Hamtrax removes your authentication credentials, server-stored integration credentials, and the email address from the retained profile. Automated activity and product email delivery stops. Contact logs and other logbook/profile data are preserved and become inaccessible through that account; to export your data beforehand, use the ADIF export feature.

7. Your Rights​

Depending on your jurisdiction, you may have the right to:

  • Access the personal information we hold about you.
  • Correct inaccurate information in your profile.
  • Request deletion of personal information we hold about you, subject to applicable exceptions.
  • Export your QSO logs and data.
  • Object to certain processing of your information.

Settings can delete your login account as described above. To exercise rights covering retained profile or logbook data, contact us at info@hamtrax.com.

8. Children's Privacy​

The Service is not intended for children under 13. We do not knowingly collect personal information from children under 13. If we learn that we have collected information from a child under 13, we will delete it promptly.

The Service may contain links to third-party websites or integrate with external services (QRZ, HamQTH, POTA, etc.). We are not responsible for the privacy practices of these third parties. We encourage you to review their privacy policies.

10. Changes to This Policy​

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy with a new "Last Updated" date. Continued use of the Service after changes constitutes acceptance.

11. Contact​

If you have questions or concerns about this Privacy Policy, contact us at info@hamtrax.com.