Dahdio

Policy · Dahdio

Privacy policy

Last updated 28 September 2026

In short

The app listens to your radio’s audio (through a USB audio interface or a cable, or the microphone) to decode Morse code and keeps your contact log, does all of that on your phone, and sends nothing anywhere unless you export something yourself.

This privacy policy explains what Dahdio (dahdio.com) does with your data when you use the app.

What data do we collect?

None. Dahdio has no accounts, no analytics, no crash reporting and no advertising identifier. Decoding happens entirely on your device and never needs a connection. The app does have permission to use the internet, and uses it only for things you ask for, such as downloading an optional decoding model. Those requests carry no personal data; as with any web request, the server can see your IP address.

Audio input

Dahdio decodes Morse code from your radio’s audio. That audio usually arrives through a USB audio interface or a cable into the phone’s headset or line input; with nothing connected, it comes from the phone’s microphone. Android calls every audio input a microphone, so the app asks for the microphone (“record audio”) permission whichever input you use. While you are listening, audio from the input in use is processed in memory on your phone to produce the decoded text you see on screen. The audio is not recorded to a file, not kept after it has been decoded, and never transmitted. Audio is only captured while Listening is switched on; pressing Stop ends it.

The decoded text stays on screen until you clear it or close the app. It is not sent anywhere. Two things you choose to use keep a little of it on your phone: alert mode’s history (see below), and anything you enter in the log.

If you choose a Bluetooth headset as the input, Android 12 and later ask you for the “Nearby devices” permission. The app uses it only to switch the headset’s microphone on while you are listening and off again when you stop. It does not scan for, list, pair with or remember Bluetooth devices beyond the input you chose in Settings, and the headset’s audio is handled exactly like any other input’s: decoded in memory, never recorded or sent. Refusing the permission only means the headset may not connect.

Data stored on your device

The app keeps the following in its own private storage on your phone:

  • Your settings: sending speed, sidetone pitch and volume, layout, decoder preferences, the name of the audio input you chose, your callsign, your stored messages and the callsigns or phrases you asked alert mode to watch for.
  • Alert mode’s history, if you use alert mode: for each alert, what matched, the line of decoded text around it, the time and the audio frequency.
  • Your QSO log, if you use the logger: the contacts you log (the other station’s callsign, date and time, band and frequency, signal reports, the exchange such as name, location, serial number or reference, and your notes), the details of each logging session (your callsign, operator, the event and your exchange), and a copy of any callsign database (MASTER.SCP) you import.
  • For the free version’s daily allowance, the date and the number of seconds decoded that day.
  • If you buy Dahdio Full, the status of your purchase as Google Play reported it: which product, when it was bought, Google Play’s order number and purchase token for it, and when the app last checked it with Google Play. This lets the app work offline.

None of this leaves your device on its own, and it is deleted when you uninstall the app or clear its data.

Log exports

When you export your log (for example as an ADIF or Cabrillo file), the app writes the file and hands it to where you send it: on Android, the app you pick from the share sheet; on a computer, the place you choose to save it. What happens to it after that is up to you and the app or service you sent it to. On Android the app also keeps a copy of each export in its own files folder (dahdio-log), which you can see over USB or with a file manager and which is deleted when you uninstall the app.

Purchases and ads

Dahdio Full (a subscription or a pass) is bought through Google Play. Purchases are handled entirely by Google Play under Google’s privacy policy: your payment details, name, email address and Google account never reach the app or us. The app receives only the purchase status from Google Play on your phone (which product, when it was bought, whether it is active or pending, and Google Play’s order number and purchase token), keeps it on your device as described above, and checks it with Google Play when the app starts. It is not sent to us or to anyone else; we have no server. To do this the app uses Google’s Play Billing library and the “billing” permission (com.android.vending.BILLING) it adds; like other Google Play components, that library may itself report diagnostic information to Google. Subscriptions are managed and cancelled in Google Play, and Google Play is where refunds are handled.

This version contains no ads. If a future version offers an optional “watch an ad for more minutes” reward, this page will be updated to describe exactly what the ad provider receives before that version is released.

What are your data protection rights?

Dahdio sends us no personal data about you: your settings and log stay on your phone, so we hold nothing to access, correct, erase, restrict or transfer. You remain entitled to ask us to confirm this, and to the rights to access, rectification, erasure, restriction of processing, objection to processing and data portability. If you make a request, we have one month to respond. To exercise any of these rights, contact us:

Contact us

Cookies

The app does not use cookies. This website does not set any.

Privacy policies of other websites

This page contains links to other websites. Our privacy policy applies only to our app and website, so if you click on a link to another website, you should read their privacy policy.

Changes to our privacy policy

We keep this privacy policy under regular review and place any updates on this web page. This privacy policy was last updated on 28 September 2026.

How to contact us

Questions or complaints about this privacy policy, or about how we have handled your data: email [email protected].