Last updated: September 2026

Introduction

Hemna LLC ("we", "our", or "us"), the developer of APRS Chat, is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application and website (collectively, the "Service").

Information We Collect

Information You Provide

Account Information: When you create an account, we collect your email address and amateur radio callsign.
Support Requests: When you contact us for support, we collect the information you provide in your request (see "In-app Support" below).
Communications: Any messages or information you send to us.
Reports: If you report an abusive station or message from within the app, we collect the reported content and any context you provide so that we can review it.

Information Collected Automatically

Location Data: When you grant location permission, the app collects your device's precise GPS location (latitude and longitude). This includes foreground location access and, if you enable background beaconing, background location access. Location data is used to: (1) transmit your position to the APRS network as position beacons, (2) calculate distance and bearing to other stations, and (3) auto-detect your regional APRS server for optimal connectivity. Location data is transmitted over the public APRS network and is not stored on our servers. You can disable location access at any time through your device settings.
Device Information: Device type, operating system, and app version for support and diagnostics purposes.
Usage Data: How you interact with the Service (anonymized analytics).
APRS Data: Messages and position data transmitted through APRS networks (inherently public).
Crash Reports and Diagnostics: If you opt in, crash reports and diagnostic information are sent to our self-hosted crash reporting service (GlitchTip, using the Sentry protocol). These may include your device model, operating system version, app version, and a stack trace of the crash. Crash and analytics data is also processed by Firebase (Crashlytics and Analytics) when you consent.
Purchase Information: When you purchase a Premium subscription, payment is processed by the app store (Google Play or Apple App Store). We receive your subscription status and a purchase token so that our server can verify your subscription via the /api/v1/billing/verify-subscription endpoint. We never access your payment card details.
Backup Data: If you enable app backups, your app data may be backed up to your personal Google Drive (Android) or Apple iCloud (iOS) account. This data is controlled by your cloud account settings and is not stored on our servers.

How We Use Your Information

To provide and maintain the Service, including connecting to the APRS network using your callsign
To transmit your position to the APRS network (location data, when enabled by you)
To show your distance and bearing relative to other amateur radio stations (location data)
To auto-detect your regional APRS server for optimal network connectivity (location data)
To process in-app purchases, manage your subscription status, and verify your subscription against the app store
To provide in-app customer support (see "In-app Support" below)
To analyze crashes and usage in order to improve the Service, with your consent

APRS Data and Public Information

By using APRS Chat for amateur radio communications, you acknowledge that:

APRS is an inherently public communications system
Your callsign, messages, and position beacons are transmitted publicly
This data may be logged by APRS-IS servers, IGates, and other stations
Your amateur radio callsign is a matter of public record

Location Data

APRS Chat accesses and collects location data as follows:

What Location Data We Collect

Precise Location (GPS): Your device's precise geographic coordinates (latitude and longitude) via GPS and network-based location providers.
Approximate Location: Coarse location data used for regional server detection.
Background Location: If you enable background beaconing, the app collects location data even when not actively in use, in order to transmit periodic position reports to the APRS network.

How We Use Location Data

APRS Position Beaconing: To broadcast your geographic position to the APRS amateur radio network, enabling other operators to see your station location on maps.
Station Distance Calculation: To calculate and display the distance and bearing between you and other amateur radio stations.
Regional Server Detection: To automatically determine the best APRS-IS server for your geographic region.
Map Display: To show your position on in-app maps alongside other stations.

Location Data Sharing

Location data is transmitted to the public APRS-IS network when you enable position beaconing.
Once transmitted, your position is publicly visible on APRS tracking websites (e.g., aprs.fi) and to other amateur radio operators.
We do not store your location data on our servers.
We do not sell or share your location data with third parties for advertising or marketing purposes.

Your Control Over Location Data

Location access is optional — you can use the messaging features without granting location permission.
You can enable or disable location permission at any time through your device's system settings.
You can independently enable or disable position beaconing within the app settings.
Background location access requires separate, explicit permission that you can revoke at any time.

Data Sharing and Disclosure

We do not sell your personal information. We may share information in the following circumstances:

Service Providers: Third parties that help us operate the Service (hosting, email, crash reporting, analytics)
GlitchTip (Sentry protocol): Self-hosted crash reporting. When you opt in, crash and error reports are sent to our own GlitchTip instance to diagnose and fix issues. Reports may include device model, OS version, app version, and a stack trace.
Firebase (Google): Crashlytics and Analytics process crash reports and usage analytics when you consent. Firebase Remote Config may deliver configuration updates to the app. On iOS, Firebase Cloud Messaging is used to deliver push notifications. See Google's Privacy Policy.
Google Play Billing / Apple App Store: Process subscription purchases. The store receives your purchase information and provides us with your subscription status and purchase token. We never access your payment card details.
Google Drive / Apple iCloud: If you enable backups, your app data is backed up to your own personal cloud account. This happens through your device's standard backup mechanisms and is controlled by your cloud account settings.
Legal Requirements: When required by law or to protect our rights
Business Transfers: In connection with a merger or acquisition

Third-Party Services

APRS Chat does not display advertisements and does not use any advertising SDKs. The third-party services we use are listed below with the data each one handles:

GlitchTip (self-hosted, Sentry protocol): Opt-in crash and error reporting. Receives diagnostics such as device model, OS version, app version, and stack traces.
Firebase (Crashlytics, Analytics, Remote Config; Cloud Messaging on iOS): Crash reporting, usage analytics, remote configuration, and push notification delivery on iOS, with your consent. Firebase may collect app interactions and device identifiers (such as the Android Advertising ID, which you can reset or opt out of in your device settings).
Google Play Billing / Apple App Store: Subscription purchase processing. We receive your subscription status and a purchase token, and verify them through our server endpoint /api/v1/billing/verify-subscription.
Google Drive / Apple iCloud: Optional personal backups of your app data.

Because APRS Chat no longer contains advertisements, we do not use Google AdMob, the Google User Messaging Platform, or any other advertising or consent-management SDKs.

Data in Transit

APRS Network Data: Transmitted unencrypted via raw TCP sockets (port 14580), as required by FCC Part 97 amateur radio regulations. This includes your callsign, messages, and position beacons.
Billing & Purchase Verification Data: Subscription transactions are transmitted encrypted via TLS/HTTPS to Google and Apple. Purchase verification requests are sent encrypted via HTTPS to our server.
Support Chat Data: Transmitted encrypted via HTTPS to our server.
Map Tile Data: Loaded via HTTPS from OpenStreetMap tile servers.
Website & Support: All website traffic is encrypted via HTTPS/TLS.

In-app Support

APRS Chat includes an in-app support chat that connects you directly with the developer over the internet (not over APRS). This section explains what we store when you use it.

What We Store

Messages: The content of the messages you send and receive in the support thread.
Install ID: A random identifier generated on your device the first time you use support. It is used to associate your device with its support thread and cannot be used to identify you personally.
Diagnostics: Your platform (Android/iOS), app version, device model, operating system version, connection type, and — if you provide it — your callsign. The diagnostics line above the composer can be turned off at any time.
Attachments: Debug logs or images that you explicitly choose to attach to a message. Debug logs may contain callsigns, positions, and message text.
Authentication: Only a SHA-256 hash of your support thread token is stored on our server; the token itself is never stored.

Storage and Sharing

Support messages are stored on our own server. We do not share your support data with any third party. New support messages are relayed to us by email so that we can respond to you.

Retention

Support messages and associated data are retained for 12 months, after which they are deleted.

Deletion

You can delete your support history at any time from within the app ("Delete my support history"). This immediately deletes your support thread and all of its messages from our server. You may also request deletion by contacting us at aprschat@hemna.com.

Data Security

We implement appropriate security measures to protect your personal information. However, no method of transmission over the internet is 100% secure, and we cannot guarantee absolute security.

Data Retention

We retain your personal information for as long as necessary to provide the Service and fulfill the purposes outlined in this policy. Support data is retained for 12 months (see "In-app Support" above). You may request deletion of your account and associated data at any time.

Your Rights

You have the right to:

Access your personal information
Correct inaccurate information
Request deletion of your data
Object to processing of your data
Export your data in a portable format

Children's Privacy

Our Service is not directed to individuals under 13 years of age. We do not knowingly collect personal information from children under 13.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new policy on this page and updating the "Last updated" date.

Contact Us

If you have questions about this Privacy Policy or wish to exercise your privacy rights, please contact us:

Email: aprschat@hemna.com
Support: Report an issue on GitHub