Hamer 中文

Hamer Privacy Policy

Updated October 2026

Hamer is provided by an individual developer ("Hamer" or "we"). We collect only what the service needs and store it in mainland China.

Without an account

You can use Hamer without signing in. Your log then stays on your phone and we receive nothing.

What we collect and why

  • Phone number: to sign you in and keep your account safe. Codes are sent by Alibaba Cloud's number verification service and carry its sender name, not Hamer's.
  • Email address: to sign you in and keep your account safe. When you sign in with email or link an email, we email you a code.
  • If you sign in with Apple or link an Apple Account on an iPhone, only the identifier Apple provides, to recognise your account. Hamer doesn't ask Apple for your name or email.
  • If you sign in with Google or link a Google account (outside mainland China), the account identifier and email address Google provides, to recognise your account. Account and security shows the email only partly hidden.
  • Station details you enter (callsign, license class, grid, location, rig, power).
  • Repeaters you add. After you sign in they are backed up to your account and synced to your other phones; no one else sees them.
  • Your log. After you sign in it is backed up to your account and synced to your other phones. Private notes are never uploaded to online logbooks.
  • Device name, sign-in times and IP address, to keep you signed in and prevent abuse.
  • Location, only when you tap "Use my location" to work out your grid. It is used on the phone and never uploaded.
  • Callsign lookups: when you look up a US callsign, your phone asks callook.info for that callsign's entry in the FCC's public license database. Only the callsign you looked up is sent.

Online logbooks, including overseas ones

You can upload your log to QRZ.com, HamCQ Echo, LoTW and others. Your phone sends the data directly using your own account. Each platform needs your separate consent, which you can withdraw at any time. We record when you gave or withdrew consent.

Services we use

  • Brevo (Sendinblue SAS, Paris, France; data protection contact dpo@brevo.com) emails sign-in codes, so it receives your email address and the email. This sends personal information outside China, and happens only when you choose email, see the note on the sign-in screen and ask for a code. You can exercise your rights with Brevo at that address, or ask us to.
  • Sign in with Apple and Google sign-in (Google LLC, USA), only when you choose them. Google sign-in happens between your phone and Google; Hamer receives only the account identifier and email Google returns.
  • callook.info (USA) for the FCC's public license data on US callsigns.

SDKs inside the app:

  • Alibaba Cloud captcha (Alibaba Cloud Computing Ltd.): the human check before a sign-in code is sent, run in a web view inside the app. It processes device and network details, such as your IP address, and how you complete the check. Android and iOS.
  • Google sign-in SDK (Google LLC): GoogleSignIn on iOS; Credential Manager and Google Identity Services on Android. It runs only outside mainland China, when you sign in with or link a Google account, and handles that account's identifier and email.
  • Google Play services location (Google LLC), Android only: after you tap "Use my location" and allow it, phones with Google Play services get the position from it, following your phone's location settings; other phones use the system's location service. Hamer uses the position only on the phone, to work out your grid.
  • Sign in with Apple (Apple Inc.) is built into iOS, not an SDK bundled with the app, and runs only when you choose it.

The other libraries in the app are open-source code that runs on your phone and doesn't send your information anywhere by itself. We update this policy before adding an SDK or service.

Storage and security

Our servers are in mainland China (Tencent Cloud). Before sending a code we may show Alibaba Cloud's captcha, which checks device and network details such as your IP address, and how you complete the check. Traffic is encrypted, sign-in tokens are stored only as hashes, and provider tokens are encrypted.

Your rights

Export your log as ADIF at any time, correct or delete entries, withdraw consents, link or unlink sign-in methods under Account and security (keeping at least one; unlinking Apple also revokes Hamer's access with Apple), and delete your account (15-day cooling-off period, after which everything is deleted).