Privacy: HamTalk QSL
This policy applies to the HamTalk QSL app on iPhone, iPad and Mac. You do not need an account with us.
Our principle
Your cards belong to you. Your QSL cards and photos are stored on your device and, if your device is signed in to iCloud, in your own private iCloud space. We do not run a server for this app and receive no data from the app.
- No ads, no analytics or tracking services, no telemetry in the app.
- No cookies in the app.
- We do not sell your data.
This does not mean that nothing ever leaves your device. If you use iCloud, eQSL.cc, HamQTH or AI reading, the data needed for that goes to Apple, to these services or to Anthropic. Details are below.
In short
- Nothing reaches us. The app has no server of its own.
- iCloud (Apple) receives your cards and photos automatically as soon as your device is signed in to iCloud.
- Anthropic (processing also in the USA) receives card photos only if you have agreed, switched on AI reading, entered your own API key and have a card read with AI.
- eQSL.cc (USA) receives data only when you upload or fetch something there with your own account.
- HamQTH receives a callsign read from a card only if you switch on the lookup and enter your own account.
Publisher and contact
The app is published by Christoph Kopetzky, Homburger Straße 59, 66424 Homburg (Saar), Germany. We receive no data from the app. We are the controller within the meaning of the GDPR only when you write to us (see Contact by email). Privacy questions: [email protected].
"We" and "us" in this policy mean Christoph Kopetzky.
What stays on your device
The app stores your cards in a database in the app's protected area on your device. A card contains, for example:
- details of the contact: the other station's callsign, date and time (UTC), band, frequency, mode, reports, and your own callsign used for the contact
- details of the other station as printed on the card: name, QTH, country, locator, DOK, QSL manager, remarks
- the QSL status (received, sent, route and date) and markers such as a star or a note for an award
- the photos of the front and back
QSL cards often contain personal data of other radio amateurs: callsign, name, postal address, locator and signature.
Photos. The app stores new card photos as a new, smaller JPEG file. The extra camera data, including the location where the photo was taken, is dropped. The app never asks for your location.
Text recognition. Your device reads the text on the photos itself, using Apple's text recognition. Nothing goes online for this. The app also works out the country of a callsign on the device, using a bundled country list.
Your details in Settings. Your name, your callsigns, your locator, your DOK, your QTH and your greeting for DigiQSL and eQSL. They are stored on the device and synced with iCloud (see below). All other switches stay on this device only.
Credentials. The passwords for eQSL.cc and HamQTH and the API key for AI reading are stored only in this device's keychain. They are not synced with iCloud and are not included in backups.
Stays on the device only: the imported DIG member list (callsign and DIG number only), background images for DigiQSL and the print template, saved contests, a log of iCloud sync errors and the status of the connection with HamTalk Logbuch.
We cannot access any of this.
Camera and photos
The app uses the camera only when you take a photo of a card yourself, and opens your photos only when you pick a photo yourself. You can withdraw these permissions in your device settings.
iCloud
If your device is signed in to iCloud, the app also stores your cards and photos in your own private iCloud space (CloudKit) and syncs them between your devices. Your details from Settings (name, callsigns, locator, DOK, QTH, greeting) are synced through the iCloud key-value store. The app chooses this by itself; there is no separate switch in the app. You can switch off iCloud for HamTalk QSL in your device's iCloud settings. The cards then stay on the device only.
The provider is Apple, and Apple's privacy policy applies. How Apple protects the data in iCloud is described in Apple's information on iCloud security. We have no access to your iCloud space.
Connection with HamTalk Logbuch
If you also use our HamTalk Logbuch app with the same iCloud account, the two apps exchange data. This runs only through your private iCloud space; no other service is involved.
- From the logbook to this app: HamTalk QSL reads the contacts from your logbook and adds them here as logbook entries or completes existing cards.
- From this app to the logbook: When you mark a checked paper card as received or sent, HamTalk QSL writes this into the paper QSL fields of the matching contact in the logbook, with route and date. The app changes nothing else in the logbook.
The connection is on as soon as both apps use the same iCloud account. You can switch it off in Settings under "HamTalk Logbuch".
AI reading
AI reading is optional. The app works without it. It uses Claude, an AI model made by Anthropic (processing also in the USA). Claude is software, not a person, and what it reads may be wrong. That is why you check every card before saving it.
When data is sent. Only if all of the following apply: you have agreed to the privacy notice in the app, switched on AI reading in Settings, entered your own Anthropic API key, and have a card read with AI. Checking the key in Settings also contacts Anthropic, but no photos are sent.
Which data.
- the photos of the card being read (front and back), reduced to at most 1600 pixels on the longest side, without location data
- a fixed instruction on how to transcribe the card
- your API key, the chosen model and the identifier "HamTalk QSL/1.0"
- your IP address, which is part of every internet connection
The photos often show details of other radio amateurs, such as callsign, name, postal address, locator and signature. The app does not send your own details from Settings, but they are often printed on the card, for example your callsign after "To Radio".
Other people's details on the cards. You are responsible for the details of other radio amateurs on the cards you send to Anthropic. You decide which card you have read with AI. If a card shows something that should not go to Anthropic, read it on the device only.
The route. Your device sends the data encrypted directly to Anthropic (api.anthropic.com). Our server is not involved, and we receive nothing. The app does not retry a failed request by itself and does not cache anything.
Anthropic. For AI reading, you enter into your own agreement with Anthropic when you get an API key. Anthropic's commercial terms (Commercial Terms) apply to this. If you live in the European Economic Area, your contracting party under these terms is Anthropic Ireland, Limited. Under these terms, Anthropic may not use the data to train its models. According to Anthropic, it deletes inputs and outputs within 30 days. Longer retention applies where the law requires it or where it is necessary to enforce its usage policy. The data may be processed in the USA, outside the EU. The level of protection there may be lower, and authorities may be able to access the data. The transfer is governed by the terms between you and Anthropic.
The terms you agree with Anthropic apply to your API key. Anthropic bills the cost to your key. Anthropic's privacy policy is available at anthropic.com/legal/privacy.
Before you create a key. Anthropic offers API keys under commercial terms. Whether you may use them as a private individual is for Anthropic to decide. Please read the terms before you create a key.
Agreement and withdrawal. On first launch the app asks on each device whether you agree to AI reading. The app asks you beforehand so that you know what happens, and unlocks AI reading only after you agree. Without your agreement it stays locked. Your agreement is stored with its date on this device only. You can withdraw it at any time in Settings under "KI-Lesung (Claude)". After that nothing more is sent to Anthropic.
You may use AI reading only if you are 18 or older.
eQSL.cc
The app talks to eQSL.cc only when you do something there with your own account:
- Upload: for the QSOs of a card, the other station's callsign, date, time, band or frequency, mode, report, your greeting and, if set, your QTH nickname at eQSL go to eQSL.cc, together with your callsign and password for signing in. eQSL then sends electronic QSL cards.
- Fetch: when you fetch received eQSLs, your callsign, your password and, if set, your QTH nickname go to eQSL.cc. For a card image, the details of that QSO are sent as well.
The password is stored only in this device's keychain. The connection uses HTTPS, without caching and without cookies. The operator is Air Wave Productions, LLC, Texas, USA. The data is therefore processed in the USA. eQSL.cc decides on its own processing; its terms and privacy policy apply.
HamQTH callsign lookup
The HamQTH lookup is off at first. If you switch it on and enter your own free account at hamqth.com, the app asks HamQTH who a callsign read from a photo belongs to. For this, your user name and password for signing in, the callsign read and the app's identifier go to hamqth.com. The app compares the name and place in the reply with the card on the device only. The password is stored only in this device's keychain. The operator is Petr Hlozek, OK2CQR, Neratovice (Czech Republic). According to him, the server is located in Germany. HamQTH stores data until you ask for it to be deleted. HamQTH decides on its own processing; its terms apply.
Links
Some buttons open a page in your browser, for example a callsign on QRZ.com, the rules of an award or contest, or Anthropic's privacy policy. From then on that page's privacy policy applies. The app itself sends nothing in doing so.
Notifications
Reminders for cards that have not come back and for saved contests are created by the app on the device. They do not go through a server.
Sharing, backups and files
The app creates backups, tables, ADIF files, PDFs, labels, calendar files and DigiQSL images only when you ask for them. You decide where to save them and whom to send them to. A backup contains all cards with photos and your details from Settings, but no passwords and no key.
Purchases and App Store
In-app purchases. You download the app for free and can try it for 7 days. After that you unlock it with a one-time in-app purchase. Apple handles the purchase and payment; Apple's terms and privacy policy apply. Whether you have bought the app or are in the trial period is checked only on your device via Apple. We receive neither your name nor your payment details. The app contains no statistics of its own. If you have agreed in your device settings to share with app developers, Apple may provide us with its own app analytics and crash reports.
Contact by email
If you write to us, we process your message and address to reply (Art. 6(1)(b) and (f) GDPR). We delete them once the matter is settled and no retention obligation applies.
Deletion
You delete a single card in the app. If you delete the app, your device also removes its data on the device; keychain entries may remain depending on the system. You remove the data in iCloud in your device's iCloud settings. Data at eQSL.cc, HamQTH or Anthropic is deleted there. There is nothing to delete on our side.
Obligation to provide data, automated decisions
You do not have to provide any data. Without iCloud the cards stay on the device only; without your agreement only AI reading stays locked. There is no automated decision with legal effect under Art. 22 GDPR.
Your rights
You have these rights against us for the data we hold, that is, your emails. For data held by Apple, Anthropic, eQSL.cc and HamQTH, please contact them.
You have the right of access, rectification, erasure, restriction of processing and data portability. You can also lodge a complaint with a data protection authority, for example the Unabhängiges Datenschutzzentrum Saarland.
Objection. You can object at any time, on grounds relating to your particular situation, to processing based on Art. 6(1)(f) GDPR: [email protected].
As of: 16 November 2026
This policy is available in German and English. In case of differences, the German version prevails.