Legal · Anchormee Alarm

Anchormee Alarm Privacy Policy

Last updated: September 15, 2026

This policy applies to the Anchormee Alarm Android app (package com.chartermee.anchormee), the anchor-drag alarm companion to charterm.ee. It covers the version distributed on Google Play and the sideload version offered on GitHub.

Use of the charterm.ee website itself is covered by our separate website privacy policy.

1. Controller

The data controller responsible for the app and its backend service is MoLabs Ltd. ("we", "us", "our").

MoLabs Ltd.
25 Vitosha Blvd., floor 2
Sofia, Bulgaria

For privacy inquiries, contact us at privacy@charterm.ee or visit www.molabs.de.

2. In Short

  • No account, no ads, no analytics. The app has no login, shows no advertising, and contains no analytics or advertising SDK. We never sell personal data.
  • The anchor alarm works entirely on your phone. Your GPS position is evaluated on the device. The siren does not depend on a network connection, and your position is not sent anywhere for the alarm to work.
  • Track history stays on your phone. Recorded swing tracks are stored only in the app's local database and are never uploaded.
  • Data leaves your phone only for features you actively use: sharing a watch with a second device, remote alerts via email or Telegram, and loading the online map. Section 4 explains exactly what is sent.

3. Data Processed Only on Your Device

The following data is created and stored locally on your phone. We have no access to it.

  • Precise location. While an anchor watch is armed the app continuously reads your GPS position, including in the background and with the screen off, to compare it against the anchor position and alarm radius. Positions are used immediately and, unless you share the watch, are not stored beyond the track history described below.
  • Anchor watch data. Anchor position, alarm radius, optional sector, watch history (start/end times, alarms) and the current watch state.
  • Track history. Minute-by-minute swing-track points for each watch, stored in the app's local database.
  • Settings. Units, theme, alarm preferences, the remote-alert configuration you enter, and a random device identifier (see 4.1).

If Android Auto Backup is enabled on your phone, Android may back up the app's settings and local data to your Google account. That backup is operated by Google under the Google Privacy Policy; we cannot access it. Uninstalling the app deletes all local data from the device.

4. Data Sent to Our Servers

The app talks to our backend at dolphin.charterm.ee (operated by MoLabs Ltd.) only for the purposes below. All traffic is encrypted with TLS.

4.1 Device Registration

When the app starts it registers itself with our backend so that sharing and push notifications can work later. This registration contains:

  • A random device identifier generated by the app on first launch. It is not your Android ID, advertising ID, IMEI or any hardware identifier, and it cannot be linked to you by us.
  • A push-notification token issued by Google Firebase Cloud Messaging, used to wake a paired device quickly when the boat's state changes.
  • App version and language of your phone, used for compatibility and to send alerts in your language.
  • A launch-offer flag recording that this install is entitled to the free Pro features, so the entitlement can be restored if you reinstall the app.

The registration contains no location data and no personal details. If the backend is unreachable, the app continues to work fully offline.

4.2 Sharing a Watch with a Second Device

If you choose to share an active anchor watch (via QR code or link), the boat phone sends the current watch state to our backend for as long as the share is active, and the paired viewer device retrieves it from there. The shared state contains:

  • Watch status (searching, safe, warning, alarm, GPS lost).
  • Anchor position, current boat position, distance, alarm radius, bearing and GPS accuracy. This is precise location data of the boat.
  • Battery level of the boat phone and a low-battery flag.

The viewer device registers with its own random device identifier, push token and language so that it can receive alerts. A pairing code shown in the QR is valid for 10 minutes and single-use.

You can end a share at any time from the app; the session and its state are deleted from our servers immediately. Sessions that are closed or receive no updates are purged automatically after 7 days.

4.3 Remote Alerts by Email or Telegram

Optionally you can have alerts for a shared watch delivered to an email address or a Telegram chat. For this we store, linked to the session:

  • Email address you enter. Alert emails are sent through our email provider Resend (see section 7). The email contains the watch status and position.
  • Telegram chat identifier that Telegram passes to our bot when you link a chat or group. Status messages and alerts are sent through the Telegram Bot API. The Telegram commands you send to the bot (e.g. a status request or a periodic status timer) are processed by our backend.

4.4 Push Notifications

Fast-wake notifications for paired devices are delivered through Google Firebase Cloud Messaging. The push message carries only the session identifier and status; the viewer app then fetches the details from our backend. Google processes the push token and delivery metadata under the Firebase privacy terms.

4.5 Online Map

The Map screen can display an online basemap from Mapbox. When you open it with an internet connection, your phone requests map tiles for the area around your anchor directly from Mapbox's servers. Mapbox thereby receives your IP address, the requested map area and technical data collected by the Mapbox Maps SDK, as described in the Mapbox Privacy Policy. Without a connection the app falls back to its built-in offline map, which contacts no one.

5. Android Permissions and Why We Need Them

The app asks for the following permissions. You can revoke any of them in Android settings; the app then explains which feature stops working.

PermissionPurpose
Precise locationSetting the anchor position and measuring the distance from it. This is the core function of the app.
Background locationKeeping the anchor watch running overnight with the screen off or the app swiped away. Without it the alarm could not warn you while you sleep.
Foreground serviceRuns the watch as a persistent service with a permanent notification so Android does not stop it.
Notifications and full-screen alertsShows the watch status and the full-screen alarm that wakes the crew when the anchor drags.
Exact alarmsA watchdog timer that restarts the watch if the phone's battery manager kills it.
Ignore battery optimisation (optional)Requested from an explanatory banner so aggressive battery savers do not stop the safety-critical watch.
CameraOnly to scan the pairing QR code of another device. Images are analysed on the device and never stored or uploaded.
Internet and network stateSharing, remote alerts, push notifications and the online map. Not needed for the alarm itself.
Send and receive SMS (sideload version only)The GitHub-distributed version can send a drag alert by SMS to numbers you configure and answer status requests sent by SMS from those numbers. Messages are processed entirely on your phone and never reach our servers. The Google Play version does not contain this feature or these permissions.

6. Legal Basis for Processing

  • Performance of a contract (Art. 6(1)(b) GDPR): providing the features you actively use: device registration, sharing a watch, remote alerts and push notifications.
  • Legitimate interest (Art. 6(1)(f) GDPR): securing the backend against abuse, short-lived server logs, and restoring your launch-offer entitlement.
  • Consent (Art. 6(1)(a) GDPR): Android permissions such as background location and camera, which you grant in the system dialog and can withdraw at any time in Android settings.

7. Recipients and Third Parties

We do not sell your personal data. Data is shared with the following recipients only for the purposes described above:

  • Hosting providers: for running our backend and database in the EU.
  • Google LLC (Firebase Cloud Messaging): push-notification delivery. Google is certified under the EU-US Data Privacy Framework. Google Privacy Policy.
  • Mapbox, Inc.: online map tiles, only when you open the Map screen with a connection. Mapbox Privacy Policy.
  • Resend, Inc.: delivery of alert emails, only if you add an email channel. Resend Privacy Policy.
  • Telegram FZ-LLC: delivery of alerts and commands via the Bot API, only if you link a Telegram chat. Telegram Privacy Policy.

Where a recipient processes data outside the EU/EEA, the transfer relies on an adequacy decision (EU-US Data Privacy Framework) or the EU Standard Contractual Clauses.

8. Data Retention

DataRetention
Local data on your phone (settings, anchor history, tracks)Until you delete it in the app or uninstall the app.
Pairing code10 minutes or until used, whichever comes first.
Shared watch session and its state (positions, status, battery)Deleted immediately when you stop sharing; otherwise purged 7 days after the last update.
Email address / Telegram chat linked to a sessionDeleted when you remove the channel or when the session is purged.
Device registration (random ID, push token, app version, language)Deleted on request, or automatically 12 months after the device last contacted our backend.
Backend server logs (IP address, request path, timestamp)14 days.

9. Deleting Your Data

  • On your phone: clear the watch history in the app, or uninstall the app to remove all local data.
  • Shared sessions and alert channels: stop sharing in the app, or remove the channel. Deletion on our servers is immediate.
  • Device registration: uninstalling the app discards the random identifier on your side, and our backend automatically deletes device records that have not been seen for 12 months, together with any sessions they own. For earlier deletion use our data deletion request page or email privacy@charterm.ee; the registration holds no personal details, so we will work with you to identify the record, for example by the time of your last shared session.

10. Children

The app is a navigation and safety tool for skippers and is not directed at children under 16. We do not knowingly collect data from children.

11. Your Rights (GDPR)

You have the right to:

  • Access the personal data we hold about you (Art. 15).
  • Rectify inaccurate data (Art. 16).
  • Erase your data ("right to be forgotten", Art. 17).
  • Restrict processing (Art. 18).
  • Data portability (Art. 20).
  • Object to processing based on legitimate interest (Art. 21).
  • Withdraw consent at any time without affecting the lawfulness of prior processing (Art. 7(3)).
  • Lodge a complaint with a supervisory authority.

To exercise any of these rights, contact us at privacy@charterm.ee.

12. Data Security

All communication between the app and our backend is encrypted with TLS. Sessions are protected by short-lived tokens, pairing codes are single-use and expire after 10 minutes, and the backend is subject to access controls and regular security reviews. Please remember that an anchor alarm is an aid, not a substitute for a proper anchor watch.

13. Changes to This Policy

We may update this policy from time to time, for example when the app gains new features. The "last updated" date at the top reflects the most recent revision. Material changes will be announced in the app or on the website.