AllMySat

Privacy Policy

Last updated: Aug 23, 2026

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.
  • The app uses your location on-device for pass prediction and tracking features.
  • 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 requested from our backend

The app connects to our backend to fetch operational data needed by app features.

These requests fetch public reference data only, with one exception: if you connect a QRZ.com account, your verified callsign is stored on our backend as described in the QRZ.com Integration section below.


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:

  • Your QRZ.com username and password are sent directly from your device to QRZ.com’s authentication servers to verify your account. AllMySat never stores your QRZ.com password. It is used once, in memory, to obtain a verification result, and is discarded immediately.
  • Once verified, your callsign is stored on our backend, linked to an anonymous, device-generated identifier, 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.

You can disable the QRZ.com integration at any time from the app’s settings, which removes your verified callsign from our backend.


Permissions and why they are used

PermissionPurpose
LocationCalculate pass predictions, tracking direction, and local visibility.
NotificationsSchedule satellite pass and launch reminder alerts.
CalendarAdd selected passes to your calendar.
CameraDisplay AR sky background in tracking mode.
MotionAlign AR view with device orientation.
Photos pickerChoose an optional cover image for custom lists.
MicrophoneRecord audio for satellite contacts in the logbook.

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.
  • 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.

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.