Privacy Policy

hambot is operated by an individual amateur radio operator as a non-commercial hobby project. There is no company, no advertising relationship, and no revenue derived from your data.

Most hambot commands store nothing about you at all. Commands like /call, /dx, /cond, /muf, and /utc are answered and forgotten. No record is kept of which callsigns you looked up.

Data is only stored about you if you use the spot alert feature:

• Your Discord user ID and username — created the first time you set up an alert, so the bot knows where to send notifications.
• Your alerts — the callsign or prefix you are watching, the modes you selected, the data source, and when the alert was created and expires.
• Delivery records — which spots have already been sent to you, so you are not notified twice, and message identifiers so the bot can automatically delete its own alert DMs later.

Separately, the bot keeps a count of how many times each command has been used in each server. This is stored against the numeric Discord server ID only — no user IDs, no usernames, and no server names — and is used to understand which features are worth maintaining.

As of August 2026, hambot requests no privileged Discord gateway intents at all. This is a technical guarantee, not just a promise — Discord does not send the bot this data:

• Message content. The bot does not hold the Message Content intent and has no message listener. It cannot read what you or anyone else writes in a server.
• Member lists. The bot does not hold the Server Members intent. It does not enumerate, store, or track who is in a server.
• Presence. The bot does not hold the Presence intent. It cannot see your online status, activity, or what you are playing.

hambot also never collects email addresses, IP addresses, phone numbers, payment details, location data, or voice data. It does not read your direct messages; it only sends them.

• Alerts expire automatically 30 days after creation and are then deactivated.
• Alert DMs that hambot sends you are automatically deleted about one hour after they are sent. The records tracking those deletions are purged after seven days.
• Your user record persists while you have alerts, so the bot can keep delivering them. Deleting your alerts removes the associated alert and delivery data.
• Aggregate command counts are retained indefinitely. They contain no personal data.

Use /listalerts to see everything hambot has stored for you, and /removealert to delete an alert. Removing an alert also removes its delivery history, which is stored against the alert itself.

If you would like your user record deleted entirely, or want a copy of what is stored about you, open an issue on GitHub and it will be handled manually. Because the data set is small and consists of a user ID and the callsigns you chose to watch, these requests are straightforward to fulfil.

To answer commands, hambot queries public amateur radio data sources: HamQTH and Callook for callsign information, PSKReporter and DX cluster feeds for spots, and NOAA and associated services for solar and propagation imagery. These services receive the callsign or prefix being queried. They do not receive your Discord identity, and the bot does not tell them who is asking.

Callsign records returned by these services are public information published by national licensing authorities.

The bot and this website run on Railway with a PostgreSQL database. As with any hosted service, the hosting provider handles network traffic and may keep standard operational logs.

hambot.net sets no cookies, runs no analytics, and includes no advertising or third-party tracking scripts. The statistics shown on this site are aggregate totals — bot status, uptime, server count, and command usage counts — and contain nothing that identifies an individual.

Your data is not sold, rented, traded, or shared with third parties. It may be disclosed only if required by law.

hambot is not directed at children. Discord requires all users to be at least 13 years old, or older where local law sets a higher minimum age.

If this policy changes, the date at the top of the page will be updated. Material changes affecting how your data is handled will be noted in the bot's release notes.

Questions about this policy, or requests regarding your data, can be raised on GitHub: