Log2Go MobileAmateur radio logging

Privacy Policy

Plain-language public posting generated from the Log2Go public document draft. Final legal review is recommended before production launch.

Log2Go Mobile Privacy Policy

Draft for review

Last updated: 2026-07-10

This Privacy Policy explains how Log2Go Mobile handles information when you use the app and related Log2Go backend services.

This draft is prepared for Google Play submission and public posting. It is not legal advice. Final text should match the production app, backend, SDKs, and Google Play declarations before publication.

Operator and contact

App name: Log2Go Mobile

Developer / operator: Will Sherman - KE5ZQV

Website: https://log2go.ke5zqv.net

Support and privacy contact: support@ke5zqv.net

Information Log2Go collects

Log2Go is an amateur-radio logging app. Depending on the features you use, Log2Go may collect and store:

  1. Account information
  • Callsign.
  • Username.
  • Email address used for registration, verification, security notices, support, or recovery.
  • Device registration identifier for each app installation.
  • Account status and security events such as registration, login, device verification, password reset, account changes, and account deletion requests.
  1. QSO and station information
  • Callsigns, dates, times, bands, modes, frequencies, signal reports, notes, and other QSO fields entered by the user.
  • Station profile information such as station callsign, grid square, county, state, city, country, operating status, rig, power, and default operating settings.
  • Log upload and confirmation status for supported services.
  • Imported records from connected online logbook services while the Log2Go account is active.
  1. Location information
  • GPS coordinates, location accuracy, timestamp, grid square, county, state, and city when the user chooses to capture location for a QSO or station profile.
  • Log2Go uses foreground, user-triggered location capture only. Log2Go does not use background location tracking.
  • GPS coordinates may be sent to a geocoding or reverse-geocoding provider so Log2Go can derive county, state, city, or related station-location fields.
  1. Connected-service credentials and service metadata

If you connect amateur-radio services, Log2Go may store encrypted credentials or tokens for:

  • LoTW.
  • QRZ.com.
  • eQSL.cc.

Log2Go may store non-secret service metadata such as service name, callsign, account nickname/label, verification status, last sync/import status, and related service history.

When a connected service is manually disabled or deleted, Log2Go deletes that service's stored credentials immediately. Historical QSO/service status records may remain as part of the user's logbook unless the user deletes the account or QSO data.

  1. NetLogger and net participation data

Log2Go may display or interact with NetLogger-style net data, including active nets, check-ins, roster details, monitor lists, and AIM/chat messages. Net mode may allow AIM/chat send and receive.

Third-party net data and AIM/chat content can include user-generated text from other operators. Log2Go plans basic abuse reporting/blocking later. A full moderation system is not part of the launch scope unless it is separately implemented before release.

  1. Diagnostics and crash reports

At launch, Log2Go plans to use Firebase Crashlytics for crash reporting only. Crash reports may include device/app diagnostic details needed to diagnose crashes. Log2Go does not plan to use general analytics at launch.

  1. Push notifications

Log2Go may send account/security notifications and sync/status notifications.

How Log2Go uses information

Log2Go uses collected information to:

  • Provide account registration, login, device authorization, and account recovery.
  • Save and sync QSO records.
  • Provide local logging and manual ADIF export.
  • Provide paid backend sync/storage when subscribed.
  • Import, upload, and check status with connected amateur-radio logbook services when enabled by the user.
  • Calculate grid square and station-location fields from user-triggered location capture.
  • Display net information and support Net/AIM/chat workflows.
  • Send account, security, sync, and status notices.
  • Diagnose crashes and app errors.
  • Protect accounts and prevent abuse.

Sharing and disclosure

QSO records are not public by default. QSO data leaves Log2Go only when the user uploads, exports, syncs, imports, or otherwise uses a feature that sends data to Log2Go backend services or connected third-party services.

Log2Go may send information to:

  • Log2Go backend services for account, sync, storage, and processing.
  • LoTW, QRZ.com, and eQSL.cc when the user connects those services and uses related import, upload, or status features.
  • NetLogger-related services when the user uses Net mode features.
  • A geocoding or reverse-geocoding provider when the user captures location and Log2Go needs derived station-location fields.
  • Firebase Crashlytics for crash reporting, if enabled in the production build.
  • Service providers needed to operate hosting, email, security, and app distribution.

Log2Go does not sell personal data. Log2Go does not include ads at launch.

Data retention

  • Active account data and server-side QSO records are retained while the account is active, unless the user deletes data or deletes the account.
  • Imported LoTW, QRZ.com, and eQSL.cc records are stored while the Log2Go account is active.
  • Server logs and security events are retained for 90 days unless a longer period is required for security, legal, or operational reasons.
  • If a backend sync/storage subscription remains unpaid for 90 days, the subscription is treated as expired. During non-payment, paid backend syncing is disabled, but encrypted connected-service credentials may be retained so service can resume if payment is resolved. After the 90-day non-payment period, Log2Go notifies the user and schedules server-side data deletion. If payment is not resolved within 7 days after that notice, all user data stored on the server, including encrypted connected-service credentials, is deleted.
  • When a user deletes a Log2Go account, all server-side QSO data for that account is deleted.

Account deletion

Users can delete their Log2Go account in the app. In-app deletion takes effect immediately after confirmation.

Users can also request account deletion outside the app by contacting support@ke5zqv.net or using the public deletion page when available. Outside-the-app deletion requests are completed within 7 days after the user verifies ownership.

See the Account Deletion Policy for the exact steps:

https://log2go.ke5zqv.net/account-deletion

Security

Production Log2Go backend services will use HTTPS only. Connected-service credentials are stored encrypted on the server. Users should keep their passwords and connected-service credentials private.

No system can guarantee perfect security. If Log2Go detects a security issue affecting an account, Log2Go may notify the user by email or push notification.

Children and minors

Log2Go Mobile is not child-directed and does not focus marketing on children. The app is built for amateur-radio operators and radio hobbyists.

Children can hold amateur-radio licenses. Minors may use Log2Go with parental approval. If Log2Go learns that a child has provided personal information without appropriate consent, Log2Go will delete that information after verifying the request.

NetLogger attribution

NetLogger is credited to its respective authors and rights holders. NetLogger 3.x is copyright © 2015-2018 John Marvin, AC0ZG, All Rights Reserved; NetLogger 2.4 is copyright © 2001-2009 N1HWQ. The NetLogger 3.x license credits Chris Gearhart for the initial NetLogger application/server software and John Dean, K0JDD, for NETLOGGER server software. Log2Go is an independent project and is not affiliated with, endorsed by, or sponsored by NetLogger.org or the NetLogger authors.

Changes to this policy

Log2Go features, pricing, integrations, and policies may change over time. When material privacy changes are made, Log2Go will update this policy and may notify users through the app, email, or other reasonable means.

Contact

For privacy, support, or account deletion questions:

support@ke5zqv.net