Privacy policy

1. Your journal and files

QSO records and station profiles are stored on your device. They can contain callsigns, names, QTH, grid locators, UTC dates and times, radio parameters and notes. The app also keeps local recovery copies for import and restore operations. We do not operate a server that receives your journal as a cloud backup.

ADIF exports and journal backups contain the data you choose to export. Copies saved or shared through Files, a cloud drive or another app are handled by that destination. Device backups may also contain app data, depending on your Apple settings.

2. Analytics, diagnostics and purchases

The app contacts these services, including when no purchase is made:

Google Analytics for Firebase

Receives feature-use events, screen names, session information, app/device identifiers, technical information and general geographic information. We use these data to understand usage and improve the app. Custom events include operation outcomes, counts, band and radio mode; optional app feedback records a like/dislike response. They exclude callsigns, names, journal text, QTH, grid locators and raw coordinates. We do not assign a custom analytics user ID. Firebase privacy information; Google Privacy Policy.

Firebase Crashlytics

Receives crash reports, stack traces, installation identifiers, app/OS versions and device information to diagnose failures. These reports are separate from the journal. Firebase privacy information.

Apple and RevenueCat

Process purchases, receipt or transaction information, purchase history and entitlement status. RevenueCat uses a generated app user ID and technical information to provide purchase functionality and metrics. We do not give it a custom user ID or journal content. Payment details are handled by Apple; we do not receive your full card details. RevenueCat privacy information; Apple Privacy Policy.

Identifiers used by these services are pseudonymous identifiers, not a guarantee that no personal data are processed. Network requests also disclose an IP address to the receiving service.

3. Optional device location

If you select Use current location, the app requests iOS location permission and calculates a six-character Maidenhead grid locator on the device. This feature does not upload your raw coordinates to our analytics. The locator is saved in your station profile only when you save that profile, and may then appear in records or exports. You can enter it manually instead and revoke location permission in iOS Settings.

4. Online callsign lookups

When you enter a valid contact callsign in the new-QSO editor, the app can automatically query HamDB and/or HamQTH to fill station information. The requested callsign and ordinary network metadata, including your IP address, reach those services. Offline estimates and previous-contact suggestions are calculated locally.

If you connect a HamQTH account, its callsign and password are sent to HamQTH over HTTPS to sign in. Credentials are saved in this device’s Keychain and excluded from journal backups. HamQTH receives the queried callsign and authenticated requests. Disconnect HamQTH removes the app’s saved login. These services handle their own records under their policies: HamDB and HamQTH privacy information.

5. Advertising and tracking

Logbook does not display third-party ads. We do not use Logbook data for targeted advertising or cross-company advertising measurement, or share it with data brokers. Analytics and purchase identifiers are still collected as described above; this is not a “no data collected” service.

6. Controls, retention and deletion

• You can edit or delete journal entries in the app. Recovery copies, exported files and device backups may retain earlier data. Removing the app normally removes its local app data, but does not remove exports or copies held elsewhere.
• Use Disconnect HamQTH before uninstalling if you want to remove its saved login. iOS Keychain items can outlast app deletion. Removing the login does not delete your HamQTH account or its public callbook record.
• Analytics and crash collection are enabled automatically. The current app does not have an in-app switch to disable them. Revoking location permission does not disable analytics.
• Service data are retained for app operation, diagnostics, purchase handling and legal obligations, subject to provider retention settings and policies. Uninstalling does not automatically delete data already sent to providers. Contact us about deletion requests; additional information may be needed to locate pseudonymous records.

7. Website requests

The website uses no browser analytics scripts, analytics cookies or persistent visitor IDs. Its server counts page requests and fixed App Store redirects, including day, language, button position, referring hostname and bot/prefetch flags. The dedicated measurement log excludes IP addresses, full user agents and persistent identifiers. Separate server operational/error logs may contain network information for reliability and security. This website behavior is separate from the app’s Firebase and RevenueCat processing.

8. Contact and privacy rights

Depending on applicable law, you may have rights to access, correct or delete personal data, object to or restrict processing, withdraw consent where it applies, and complain to a relevant data protection authority. Send requests to devenlprm@gmail.com. We may need to verify the request and identify relevant records. Do not send passwords or a complete journal unless specifically necessary for a support request you choose to make.

If you contact us by email or Telegram, we receive the details and content you provide so that we can respond. Those communication services also apply their own policies.

9. Security and international processing

Online service requests use HTTPS; HamQTH credentials use device-only Keychain storage. No method of storage or transmission is absolutely secure. Our service providers may process data in countries other than yours, under their applicable terms and safeguards.

10. Children

Logbook is not directed to children under 13. We do not knowingly collect their personal data. A parent or guardian who believes a child has provided such data can contact us so we can investigate and address the request.

11. Policy changes

We will publish updates at this address and change the date above. Where required, material changes will receive additional notice. This policy describes data practices; it does not replace any consent required by applicable law.