qFT8 Privacy Policy
This policy outlines how qFT8 handles the user's data, permissions, and communications. Its goal is transparency
and simplicity.
In short: qFT8 works on the user's device. It has no ads, no tracking and no analytics
libraries, and nothing is ever sold. Everything that sends personal data (callsign, grid, contacts) is
opt-in: it happens only after the user sets up a service, turns an option on, or presses a
button to send. On its own, qFT8 contacts the qFT8 developer's servers only to check for a newer version and to
download public data (propagation, POTA/SOTA activity, LQ8 calls on the air, satellite orbits); these requests carry no personal data, and all of them can be
turned off.
User Identity
The user must provide an amateur radio Callsign. This is required for the fundamental operation
of the app.
- This callsign personally identifies the user.
- It is broadcast via Radio Frequency (RF) when connected to a transceiver.
- It is encoded in audio signals for mock functionality when not connected to a transceiver.
Location Data
Optionally, the user can grant Location permission.
- It is used only to work out the user's Maidenhead Grid Locator (4 characters, e.g. "JN47",
about 100 x 100 km) to place the user on the app's map and, when needed, to set the clock from GPS time. The exact position never leaves the device.
- The grid is sent over the air as part of standard amateur radio messages. If the user types a 6-character
grid by hand, that grid is used in the user's own logbook uploads and WSPRnet reports (below).
Audio
- The app needs audio permission to receive signals, from a transceiver connected by USB or from the
microphone (demo mode, and the user's voice for SSB).
- Received audio is processed as it arrives and is not stored or sent to the developer or anyone else. SSB voice
memories the user records are kept on the device only.
- With the qFT8 bridge or the web remote turned on, audio travels between the user's own devices (below).
Bluetooth
- Only when the user chooses Bluetooth as the radio connection, the app asks for the Nearby devices
permission (Android 12 and later; the iPhone asks for Bluetooth) to talk to the radio the user picks from the
devices already paired with the phone. Only the radio's control (CAT) commands travel over that link; the app
does not scan for or track other devices, and the radio's name and address stay on the device.
Transmissions
When connected to a transceiver, the app tells the radio to transmit. Transmissions contain the user's callsign
and grid, as amateur radio rules require.
On the user's own network (off until turned on)
- Web remote: a web page to watch and control the app from another device on the same Wi-Fi/LAN.
Off by default. Access needs the private link or QR code shown in the app (its key never travels over the
network) and, if set, a password. The page is plain HTTP on the local network unless the user turns HTTPS on
(needed for the browser's microphone, which then carries the user's voice to the phone for SSB).
- qFT8 bridge: lets another qFT8 of the user's use a radio connected to this device (radio
audio and radio control). Off by default. Protected by a password that is never sent over the network, and
encrypted by default.
- qFT8 log: shares the logbook between the user's own qFT8 installations on the LAN. Off by
default; same password protection and encryption as the bridge.
- Logging programs on the network (off until set up): qFT8 can send each contact the user logs
to logging programs on the user's network (the address and port the user enters; plain, unencrypted network
messages, as those formats are), receive contacts that other programs on the network log (on ports the user turns
on), and answer logging programs that connect to it. Only contact data travels: callsigns, grids, date, time,
band, frequency, mode, reports and the user's notes on the contact.
- Logbook servers (off by default): qFT8 can act as a logbook server on the local network, so the
user's own logging programs can send contacts to it, and can show its logbook read-only in a browser. Plain HTTP
on the local network, protected by the key or password the user types on both ends.
- These features are found on the local network by a broadcast that reveals only a name, a port and a version.
They are never exposed to the internet by qFT8 and send nothing to the developer.
qFT8's own servers
- Update check (on by default; "Check for new versions on startup" in Settings): at most once a
day at start-up, the app asks the developer's server for the latest version number (data.qft8.com, a cached copy, or reports.qft8.com). It sends only the app version and
platform.
- Public data cache (on by default; "Use the qFT8 data cache" in Settings > Data sources, where each
download can also be turned off): POTA/SOTA activity, propagation and space-weather data are fetched from a copy kept by the qFT8
developer (data.qft8.com, or reports.qft8.com) instead of each public source. These requests contain no
personal data. With the cache off, the same public data comes straight from its source (POTA, SOTA, KC2G,
NOAA).
- LQ8 activity announcements (off by default): if the user turns on "Announce LQ8 activity to the qFT8 service",
each LQ8 transmission the radio actually sends (a CQ or any other over) is announced to the developer's server
(reports.qft8.com), at most once every 5 minutes per band. Transmissions made through the device's own speaker and
microphone instead of a radio are announced only if the user also turns on "Also announce it when communicating via
speaker/microphone" (off by default). An
announcement contains the user's callsign, the 4-character grid, the band, the dial frequency and audio offset, the mode
(LQ8), the time of the transmission and the app version. Its purpose is to let other qFT8 users see LQ8 activity on their
map. The server keeps only the latest announcement per callsign and band, in memory, and deletes it 10 minutes after it
arrived; the app version is checked and then discarded. The sender's IP address is used only for a moment to limit how
often announcements can be sent, and is never stored or logged. Turning the option off stops the announcements at once.
- Satellite orbits (only while the map's satellite layer or satellite mode is in use): the app fetches the
current satellite orbital elements from the qFT8 service (data.qft8.com, or reports.qft8.com), at most every 12 hours,
and keeps the last copy on the device. This is the same kind of request as the public data cache and sends nothing
personal.
- LQ8 activity on the map (on by default): "Download LQ8 activity from the qFT8 server" fetches the current list of
announced LQ8 activity (data.qft8.com, or reports.qft8.com) to show them on the map. This is the same kind of request as the public data
cache and sends nothing personal. It can be turned off in Settings > Data sources.
- Bug and crash reports (only when the user presses SEND): the description the user wrote, the
user's callsign and grid, an e-mail address only if the user gives one, and the app's logs and technical
details: the device and its operating system, the connected USB and audio devices (vendor and product
identifiers and drivers), the radio-control (CAT) messages of the first and last radio connection (any text
that could identify a person, such as CW text, memory names, call signs or the radio's serial number, is
removed), the last screens and buttons used (their internal names only, never what was typed), the audio and
radio-control settings, recent QSO steps and, after a freeze or crash, what the app was doing. Passwords, keys,
e-mail addresses inside logs, coordinates, serial numbers and internet (public) IP addresses, such as those of
devices that tried to reach the web remote, are removed; addresses inside the user's own home network are
kept, as they help to find network problems; pictures, the logbook and
certificates are never included. After a crash the app asks on the next start; nothing is sent without SEND.
A report that could not be delivered is retried for up to 14 days.
- Anonymous performance summary (off by default): if the user turns on "Send an anonymous daily
performance summary", about once a day, while the app is open, qFT8 sends technical performance data:
start-up time, screen smoothness, decoding, audio and radio-control timing, processor and memory use and
temperature throttling, anonymous error signatures (no message text), device model, operating system version,
processor cores and screen size, and, with a radio, its model (never its serial number), how it is connected,
the measured receive audio bandwidth and a log of the radio-control messages (times counted from the
connection, never the date or time of day; personal text removed), and, for a radio reached over Bluetooth or
the network, how that link behaved (connecting, logging in, drops and their timing; network and Bluetooth
addresses and user names removed), and, for each mode used, how many minutes it ran, how many messages,
characters or pictures it received, how many times it transmitted and how many QSOs were logged (numbers
only: never who, where, on which frequency or what was said). It never contains the callsign, grid,
location, logbook, settings values, passwords or any identifier, so a summary cannot be traced to a user or
linked to another. Turning it off stops it at once.
- Reports and summaries are used only to fix and improve qFT8 and are not shared with third parties. The developer
does not store the sender's IP address; like any internet service, the connection passes through Cloudflare
and other network services on its way.
Services the user chooses to connect (opt-in)
Nothing is sent to these services until the user sets them up. The credentials stay on the device and go only to
the service they belong to. Untick a service, or clear its credentials, to stop it.
- QRZ Logbook, Logbook of The World (LoTW), eQSL: once set up, each finished contact is
uploaded to the user's account: the user's callsign and grid, the other station's callsign and grid, date,
time, band, frequency, mode and reports. LoTW contacts are signed on the device with the user's own
certificate. qFT8 never deletes anything on these services.
- Club Log, HRDLog, HamQTH, World Radio League (WRL): once set up, the same contact data is
uploaded to the user's account on that service (clublog.org, hrdlog.net, hamqth.com,
worldradioleague.com), with the login, upload code or API key the user typed. qFT8 never deletes anything on
these services.
- Wavelog / Cloudlog: the same contact data, sent to the server address the user types in (usually
the user's own server), with the user's API key.
- POTA spotting (only when the user presses ANNOUNCE): the user's callsign, park, frequency and
mode are posted to POTA's public spot list (api.pota.app), and again every 30 minutes while that activation is
running, until the user stops it.
- PSKReporter and WSPRnet reporting (off by default): if turned on, the stations the app hears are
reported (their callsign and grid, frequency, mode, signal strength, time) together with the user's callsign
and grid (4 characters for PSKReporter). WSPRnet reports use plain, unencrypted HTTP, as that service
requires.
- Who heard me (map): while the user has the map open, the app asks PSKReporter and WSPRnet who
heard the user's callsign recently (it sends the callsign). "Download spots from PSKReporter / WSPRnet" in Settings > Data sources turn this off.
- Time: the app may ask public time servers (pool.ntp.org, time.google.com) for the exact time;
nothing personal is sent.
Data sent to a third-party service is handled under that service's own privacy policy.
Deleting data
- Bug and crash reports: to have a report you sent deleted, e-mail
hb9iph@gmail.com with your callsign and, if you have it, the report ID
(QFT8-XXXXX) or the date you sent it. The report is deleted from the qFT8 server and its archive, by hand,
within 30 days, and you get a reply when it is done.
- Anonymous performance summaries: they carry no callsign or other identifier, so a summary
cannot be traced back to a person, and cannot be found and deleted on request. Turning the option off stops
them at once.
- LQ8 activity announcements: they are deleted automatically 10 minutes after they arrive, and are not archived or backed
up, so there is nothing left to delete on request. Turning the option off stops them.
- On the device: everything qFT8 keeps for itself (settings, logbook, received pictures) is removed by
uninstalling the app or clearing its data in the system settings; copies you saved to the pictures folder or exported
stay where you put them.
- Third-party services: data you sent to QRZ, LoTW, eQSL, Club Log, HRDLog, HamQTH, World Radio
League, Wavelog / Cloudlog, PSKReporter, WSPRnet or POTA is kept by that service; ask that service to delete it, under its own privacy policy.
Data Management
The user can import and export logs and settings to/from files on the device at any time. A
settings export contains the service passwords and keys, so keep that file private. Uninstalling the app removes
everything it stored on the device.