HamClock is an amateur radio reference application that displays propagation data, solar conditions, world maps, and related information for licensed amateur radio operators. This policy describes what data the application and its backend service collect, why, and how it is used.
What is collected
When the application makes a request to backend servers (operated under the hamclock.com domain), the following information may be transmitted as part of normal HTTP requests and recorded in standard server access logs:
- Anonymous device identifier — a randomly generated numeric ID assigned by the application on first run. Used to distinguish concurrent client sessions. Not derived from any personally identifying information and not linked to a user account.
- Maidenhead grid square or geographic coordinates — entered by you in app Setup. Used to compute propagation paths, solar position, and other location-dependent displays.
- Amateur radio callsign — included in some requests (specifically PSKReporter propagation lookups) when you configure one in Setup. Used only for the lookup itself; not stored long-term or linked to user accounts.
- IP address — automatically associated with each request as is standard for any internet-connected service. Used for connection handling, abuse prevention, and aggregate traffic statistics.
- Application version and channel identifier — present in the request user-agent string. Used to identify which build is running.
What is NOT collected
- Real name, address, email, phone number, or other personally identifying information beyond the optional amateur radio callsign you choose to enter
- Persistent user accounts, login credentials, or authentication tokens
- Device contacts, photos, microphone, camera, or other device-level data
- Location data outside what you explicitly enter in Setup
- Browsing history, advertising identifiers, or third-party tracking data
How data is used
Data is used solely to provide the application's core functionality: rendering propagation maps, solar imagery, DX cluster spots, and related amateur radio information specific to your station configuration.
Aggregate, non-identifying access metrics (request counts, geographic distribution at the country level, error rates) may be reviewed for service health and capacity planning.
Data sharing
HamClock does not sell, rent, or share user data with third parties for advertising or marketing purposes.
The application connects to the following external services to retrieve public propagation and space weather data:
- NOAA Space Weather Prediction Center (public solar and geomagnetic data)
- NASA Solar Dynamics Observatory (public solar imagery)
- PSKReporter.info (public amateur radio propagation reports)
- VOACAP propagation modeling (computed locally on backend)
Your callsign and grid square are included in some of these public-data lookups in the same manner as any conventional HamClock client.
Data retention
Server access logs are retained for 90 days for operational and security purposes, then deleted. No long-term per-user profiles are constructed or stored.
Children's privacy
HamClock is intended for licensed amateur radio operators and does not knowingly collect data from children under 13.
Security
All connections between the application and backend are encrypted via HTTPS (TLS 1.2 or higher). Backend infrastructure is hardened against unauthorized access following industry standard practices.
Your rights
You may stop sharing data at any time by uninstalling the application. Because the application does not associate data with persistent user accounts, no account deletion process is necessary.
If you would like to inquire about data associated with your callsign, contact the operator below.
Changes to this policy
This policy may be updated as the service evolves. The "Last updated" date at the top of this page reflects the most recent revision.
Contact
HamClock is operated by HamClock.com
For privacy questions: contact@hamclock.com
HamClock is amateur radio reference software, originally created by Elwood Downey (WB0OEW). The current backend service and downstream applications are independently maintained.