Privacy Policy

Privacy Policy for OrbitDeck for iOS

Last updated: November 21, 2026

This Privacy Policy explains how OrbitDeck for iOS ("OrbitDeck," "the app," "we," "us") handles information. OrbitDeck is developed by Paul Stoetzer, N8HM ("the developer"). We are committed to protecting your privacy. In short: OrbitDeck does not collect, store, or transmit your personal information to the developer, and contains no advertising or third-party analytics or tracking. The developer runs no servers for the app. When OrbitDeck talks to an outside service, it connects directly from your device to that service, and this policy lists each one and what it sends.

Information we collect

The developer does not collect any personal information through OrbitDeck. OrbitDeck has no user accounts, no advertising, and no analytics or tracking SDKs. Your settings, favorites, saved sites, QSO log, recordings and cached data are stored locally on your device.

Location

OrbitDeck can use your device's location (only while the app is in use) to set your observer station, which is required to compute satellite pass predictions, look angles, and related information. Providing location is optional: you may instead enter your station manually as latitude/longitude or as a Maidenhead grid square. You can enable or revoke Location access at any time in the iOS Settings app.

Your station position is used on your device and is never sent to the developer. It leaves your device only in these cases:

Position beacons you choose to transmit over the radio with the Packet / APRS feature are broadcast publicly over the air, like any amateur-radio transmission; the packet setup's Position precision setting lets you send a less exact position.

Passwords, keys and certificates

OrbitDeck can optionally connect to third-party amateur-radio services if you choose to enter credentials for them. Secrets are stored in the device's secure iOS Keychain, as items available only on this device (they are not synced to iCloud Keychain), and are never sent to the developer:

Your LoTW callsign certificate (the .p12 file you import) is kept in OrbitDeck's private app storage on your device, protected by iOS data protection, not in the Keychain. Non-secret settings, such as your callsign, grid, QRZ and Space-Track user names, the Cloudlog address and station profile ID, and your LoTW station location, are stored in the app's preferences on your device.

Each secret is transmitted only to the corresponding service, and only when you use that feature. Your use of those services is governed by their own privacy policies. Settings → Saved credentials → Clear all saved passwords & keys removes every stored OrbitDeck password and key from the Keychain (Keychain items can survive deleting the app) and deletes the imported LoTW certificate; Settings → Reset can also remove them.

Third-party data services

To function, OrbitDeck downloads publicly available data from the following services. These requests are made directly from your device to each service and necessarily include your device's IP address, which those services may process according to their own policies. Except where noted, OrbitDeck does not send them your personal information.

OrbitDeck caches this data and limits how often it asks for it, following these services' usage policies.

Services that publish what you send

QRZ lookups

If you enter your QRZ XML login, OrbitDeck looks up callsigns you ask about and, with "Fill in names and states from QRZ" on (Log settings), the callsigns of stations you log, to fill in an empty name and a US station's state. OrbitDeck signs in to QRZ (xmldata.qrz.com) with your QRZ user name and password, then sends each callsign it looks up, all over an encrypted connection.

APRS-IS, DX cluster, ADS-B and telnet (Nearby & DX)

These connections are made only while you use the Nearby & DX screen (or, for the satgate, while the packet decoder runs with the satgate on):

APRS-IS, DX clusters and telnet are unencrypted protocols by design, so what OrbitDeck sends on them (including the satgate passcode) is not encrypted in transit.

Bluetooth and local network

If you use OrbitDeck's CAT (rig control) feature to Doppler-tune your transceiver, OrbitDeck communicates directly with your radio: over Bluetooth Low Energy (to a BLE serial adapter, or the built-in Bluetooth of an IC-705 or IC-905), or over your local network to an Icom network-capable radio or a Hamlib rigctld server. The rotator control feature works the same way, over Bluetooth Low Energy or to a rotator controller on your network (such as rotctld or PstRotator). The Packet / APRS feature can use a Bluetooth LE KISS TNC or a KISS TNC on your network (such as Direwolf). These connections are made only when you configure and connect a device, stay on your device and local network, and are never sent to the developer. iOS asks for Bluetooth and local-network permission the first time they are needed.

OrbitDeck can also run rigctld and rotctld servers so programs on your local network can share its radio and rotator connections. They are off by default, run only while OrbitDeck is in the foreground or a background audio session is active, and accept connections only on your local network (not over VPN or cellular). A new client must be approved by you (allow once, always allow, or deny; an unanswered request is denied after 30 seconds, and requests are denied while the app is in the background). Connections from the device itself are allowed, and you can turn the approval requirement off in the server settings. Keying your transmitter from the network is a separate opt-in. These server connections are not encrypted, so use them only on a network you trust.

Microphone and audio

iOS treats a USB audio interface as a microphone, so OrbitDeck asks for microphone permission to use one. OrbitDeck captures audio:

Audio is captured only while you record, decode, make a memo or talk. All decoding, including the DeepCW neural-network CW decoder (whose model is bundled in the app and runs on your device), FT4, SSTV and packet, happens on your device. Audio is never sent to the developer or to any online service. Pass recordings and voice memos are stored on your device until you share or delete them.

Logging, photos and calendar

The QSO log is stored on your device. Uploading sends QSOs only to the service you choose, LoTW (ARRL) or your own Cloudlog/Wavelog server, and only when you tap upload. LoTW uploads are signed on your device with your certificate and sent over HTTPS. Cloudlog/Wavelog uploads include your API key; OrbitDeck requires an https:// address unless the server is on your local network, where it allows http:// and warns you that the key is sent unencrypted on that network.

Decoded SSTV images are stored on your device and added to your photo library only when you export them (iOS asks for add-only photo permission then). Pass times are added to your calendar only when you choose to (iOS asks for write-only calendar access then).

PSKReporter reception reports (optional)

OrbitDeck can optionally upload the FT4 stations it decodes through satellites to PSKReporter (pskreporter.info), a public reception-reporting network, so that they appear on its public map. This feature is off by default and is only active if you enable "Upload FT4 reception reports" in Settings. When enabled, each report is sent directly from your device to PSKReporter and includes your callsign and grid square, the decoded station's callsign and (if heard) grid square, the downlink frequency, signal report (SNR), mode, and time. This information is inherent to amateur-radio reception reporting and is published publicly by PSKReporter under its own policies. Nothing is sent to the developer. You can turn this off at any time in Settings.

Notifications

OrbitDeck uses local notifications, created and delivered on your device, for pass alarms you schedule, reminders for activations you choose, and (if you use Packet / APRS in the background) alerts for messages to you, your watch list and your own packets being digipeated. iOS asks for notification permission when you first use one of these, or from the station readiness checklist. OrbitDeck does not use push notifications, and no notification data leaves your device.

Live Activities

The next-pass Live Activity on the Lock Screen, in the Dynamic Island and in the Apple Watch Smart Stack is computed and updated entirely on your device. It does not use a push server. With Background App Refresh on, iOS occasionally wakes OrbitDeck to update it from data already on the device. You can turn Live Activities off in OrbitDeck's Settings or in iOS Settings.

Files, backups and diagnostic logs

Notes are plain text files in OrbitDeck's folder in the Files app. A backup you export contains your settings, station details, log setup and activations (and, if you choose, your QSO log), and goes only where you save or send it; passwords, API keys and your LoTW certificate are never included.

OrbitDeck keeps an on-device diagnostic log (rig, audio, and network activity) to help troubleshoot problems. The log stays on your device and is never sent automatically. You may choose to share a log file with the developer, for example by email, when reporting an issue; only then does any log content leave your device, and only to the recipient you pick. You can disable logging or clear the logs at any time on the Diagnostics screen. The same applies to a log file that OrbitDeck set aside because it couldn't be read: it stays on your device unless you share it.

Analytics, advertising, and tracking

OrbitDeck contains no third-party analytics, no advertising, and no tracking. We do not track you across apps or websites, and OrbitDeck does not use the Advertising Identifier (IDFA) or request App Tracking Transparency permission.

Children's privacy

OrbitDeck is a utility for amateur-radio operators and is not directed to children. We do not knowingly collect personal information from anyone, including children under 13.

Data retention and deletion

Because OrbitDeck stores its data only on your device and the developer maintains no servers or accounts, there is no personal data held by the developer to retain or delete. You can remove OrbitDeck's local data with Settings → Reset or by deleting the app from your device; use Clear all saved passwords & keys in Settings (or the reset option that also removes them) to remove passwords and keys from the Keychain. Data you have sent to a third-party service (for example, uploaded QSOs, hams.at alerts, AMSAT reports, PSKReporter spots or gated APRS packets) is held by that service under its own policies.

Security

OrbitDeck's connections to web services use encrypted transport (HTTPS/TLS). Some amateur-radio protocols have no encryption: PSKReporter reports, APRS-IS, DX clusters, telnet, the rigctld/rotctld servers and clients, and the local radio, rotator and TNC links, as well as a Cloudlog/Wavelog server you reach over http:// on your local network. Credentials are stored in the iOS Keychain. No method of transmission or storage is completely secure, but OrbitDeck minimizes risk by keeping your data on your device.

Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected here with a new date.

Contact

If you have questions about this Privacy Policy or OrbitDeck's privacy practices, contact the developer at n8hm@arrl.net.