Privacy Policy

A Clear Commitment

AllMySat is built to track satellites, not people. This policy explains what the app processes, what is stored locally on your device, and what is requested from our backend. It is written to reflect the current implementation of the mobile app.

At a glance

• No account is required to use the app.
• Your location is used on your device for pass prediction and tracking. It leaves your device only for the weather forecast, rounded to about 1 km, and as a grid square when you submit an AMSAT report.
• The backend serves public satellite, transmitter, launch, and space weather data.
• We do not use third-party analytics SDKs, ad SDKs, or third-party crash reporting SDKs in the mobile app.

Data sent to our backend

The app connects to our backend to fetch public reference data such as satellites, transmitters, launches and space weather. Beyond these requests, only the following leaves your device.

• Weather. To show the local forecast, the app sends your position rounded to two decimal places, about 1 km. Our backend asks MET Norway for the forecast at that rounded position and keeps it in a cache keyed by the rounded position only, with nothing that identifies you.
• QRZ.com verification. If you connect a QRZ.com account, your login passes through our backend once to verify your callsign, as described in the QRZ.com Integration section below.
• AMSAT reports. When you submit a satellite activity report, our backend sends AMSAT your verified callsign, the satellite, mode and status, and your Maidenhead grid square computed from your location. AMSAT publishes these reports on its public live status page. Our backend keeps a record of each submission (callsign, satellite, mode, status and time) and never stores your location or grid square.

Maps on Android

On Android, maps are displayed with Mapbox. To show them, Mapbox receives technical information such as your IP address, as described in Mapbox's privacy policy. From version 2.2.0, AllMySat turns off Mapbox's collection of map usage and location data, and Mapbox only receives an anonymous count of active users.

QRZ.com Integration

AllMySat offers an optional integration with QRZ.com, a third-party amateur radio callsign database, used for two purposes: enriching logged contacts with callsign information, and verifying your callsign to enable submitting satellite activity reports to AMSAT.

If you choose to connect a QRZ.com account, here is what happens.

• To verify your callsign, your QRZ.com username and password pass through our backend to QRZ.com once. They are used in memory to obtain the verification result, then discarded. They are never stored or logged on our servers.
• Once verified, your callsign is stored on our backend, linked to an anonymous identifier created by the app, not to your name, email, or any other personal information. This is used solely to confirm that satellite activity reports you submit through the app are attributed to a callsign you have proven ownership of.
• To look up the callsigns of your logged contacts, the app keeps your QRZ.com login on your device, encrypted (in the iOS Keychain, or with the Android Keystore), and contacts QRZ.com directly from your device.

You can disable the QRZ.com integration at any time from the app’s settings. This removes your verified callsign and the record of your AMSAT submissions from our backend, and your QRZ.com login from your device.

Garmin watches

If you connect a Garmin watch, the app sends it your upcoming passes, computed on your phone, with the chosen frequencies and Focus Mode settings. This goes through Garmin's Connect app on your phone to the AllMySat app on your watch. Your location is not sent to the watch, and nothing goes through our backend. Garmin handles this connection as described in Garmin's privacy policy.

Permissions and why they are used

All permissions are optional and can be managed in your device Settings at any time.

Purchases

In-app purchases are handled through the platform’s native billing system (Apple StoreKit on iOS, Google Play Billing on Android). Payment processing, billing, and refund handling are managed by the respective platform provider.

iCloud Sync (Apple only)

On iOS, AllMySat uses Apple CloudKit to optionally sync your custom lists, and favorites across your devices via your personal iCloud account. This data is stored in your private iCloud container and is not accessible by the AllMySat backend or any third party.

Storage and retention

• App preferences are stored locally using the platform’s standard preferences storage.
• Satellite and related datasets are cached locally in the app container for performance.
• Calendar events you choose to create are saved in your own calendar database.
• On Android, your settings, favorites, custom lists and their cover photos can be included in the backup Google makes to your Google account, if backup is turned on in your Android settings. It lets you restore them on a new phone and is not accessible by the AllMySat backend.
• Deleting the app removes app-container data stored locally on your device.

Your controls

• You can manage permissions at any time in your device Settings.
• You can disable notifications, location usage, and optional features from app settings and system settings.
• You can remove your favorites, custom lists, and local notification schedules directly in the app.
• To delete your data, follow the steps in Delete your data below.

Changes to this policy

We may update this policy when the app changes materially. The latest version is always published on this page.

Contact

If you have privacy questions, contact us at contact@allmysat.com.