1. Data controller
Controller: Raúl Palacios Castillo.
Contact for any privacy matter, including requests to delete your data: privacy@harborcues.com.
[REVISAR: data protection officer, if any]
2. What data we keep and why
We keep only what the service needs:
- Account (if you create one): email, first name, country (optional), user identifier, sign-up date, plan and trial or plan dates, and the version and date on which you accepted the terms. Your password is handled by our sign-in provider (Supabase) and we never see it.
- Devices: a random identifier that works as a key, a name (the one you type, the one on your invitation or, with an account, "system - browser"), language, the alert role you choose in the app (pilot, surveyor, barges, tugs, agent or other; it is only stored and does not change which alerts you get), creation and last-use dates and the associated session. They make the app work, power the "My devices" list and provide security.
- Ships you follow and pending follows (by MMSI, IMO or name), and a log of follows added and removed.
- Alerts for the ships you follow and the status of their delivery to your device, and a technical log of notification delivery attempts.
- Push notification subscription: the address and keys given by your browser's notification service.
- Alert preferences.
- Acceptance of the terms and the policy in the app: when you accept them we keep the version accepted and the date and time of acceptance, linked to the device, so that we can prove it. They are deleted with "Delete my data".
- Mobile app notifications: the identifier given by the phone's notification service (Google's Firebase Cloud Messaging on Android), the platform and the dates it was added and changed. It is used to send alerts to the app; it is deleted when you sign out of the app or delete your data there. In addition, on the phone, the Firebase Cloud Messaging library generates a Firebase installation ID that Google uses to deliver notifications; our server does not store it.
- Invitations: the invited person's name, a digest of the code (never the code), the dates of creation, expiry, redemption or cancellation and a shortened identifier of the device that redeemed it. They give access and show who uses each device. For demo access (for app store reviewers), also how many times the code has been used and the maximum allowed; each use creates its own device whose key expires with the access.
- Mobile app: a digest of the device's access key and of the installation identifier (never the key or the identifier), its creation and last-use dates, the revocation date and reason if it is withdrawn, and the app platform and version. For each attempt to activate the app: date, result, platform, version, the app or browser identifier (user-agent) and the IP address shortened (IPv4 without its last number; IPv6 only its network prefix). They give access, provide security and help detect abuse.
- Your ratings of alerts (right / wrong) with their optional comment, and the comments you send from Settings.
- Error reports ("This is not correct" / "Confirm"): the ship, the alert they refer to if any, the chosen reason, the optional comment, the date and the ship's last known position at that time. They are used to measure and improve alert accuracy.
- Log of admin actions (administrators only): date, action and the administrator's IP address.
In your browser's local storage we keep: the device identifier, the language, the account session and your recent searches. We do not use advertising cookies or analytics tools.
In the mobile app the phone's secure storage keeps: the access key, the installation identifier, the notification identifier, the language, the map filters and layers and the alerts you have already reported.
If you tap "Go to my location", the app uses the phone's location, with your permission and only while you are using it, to center the map and show your position. Your location is not sent to our server or stored.
Ship positions are public AIS data about vessels, not data about users, and are kept for 30 days.
3. What we use it for and on what basis
- Providing the service (account, alerts, map): performance of the contract.
- Sending you push notifications: your consent when you turn them on; you can withdraw it at any time.
- Security and preventing abuse (request limits, session control): legitimate interest.
- Improving the accuracy of alerts with your ratings and comments: legitimate interest.
[REVISAR: legal bases]
4. How long we keep it
- Your account data, for as long as you have the account. When you delete it, it is removed immediately.
- Logs of follows added and removed and of notification deliveries: 90 days at most (and removed when you delete the account).
- Finished invitations (redeemed, expired or cancelled): 90 days at most (and removed when you delete the account).
- Attempts to activate the app (with the shortened IP and the user-agent): 90 days at most.
- What we keep about a mobile app device (ships you follow, preferences, alert role, comments, reports and notification identifier): until you delete it with "Delete my data" or ask us by email to delete it.
- If you delete your data from the app, only a minimal record without any name is kept: the dates the device was added and removed and, for its key, the digest, dates, platform, version and reason for removal. It is kept for security and to know that the invitation was used. [REVISAR: how long this record is kept]
- History of acceptances of the terms and this policy (versions and dates): kept also after "Delete my data", within the minimal record, as proof of consent. [REVISAR: how long it is kept]
- Deletion code to ask for deletion by email (only a digest, never the code): valid for 30 days and deleted 30 days after it is used, cancelled or expires.
- Abuse limits (the IP and the device, stored as a digest that cannot be read back): 1 hour at most.
- Closed sessions, as opaque identifiers to stop them being reused: up to 30 days.
- Database backups: the 7 latest daily copies are kept, so deleted data may remain in them for up to 7 days.
- AIS positions: 30 days.
5. Who else receives data
- Railway: hosting of the server and the database.
- Supabase: account management and sending verification emails; if enabled, storage of backups.
- The push notification services of your browser or phone (Google, Apple, Mozilla or Microsoft): they receive the alert content in order to deliver it.
- Google (Firebase Cloud Messaging): in the Android app, it receives the notification identifier, the Firebase installation ID and the alert content in order to deliver it.
- OpenStreetMap: when you view the map on the web your browser requests tiles from their servers and they see your IP address.
- Stadia Maps: when you view the map in the mobile app the phone requests the style and tiles from their servers, which see your IP address and the area of the map being shown (your position's area if you have centered the map on it). They do not receive your location.
We do not sell your data or use it for advertising. Our server does not keep a log of visits; the hosting provider may keep its own technical logs.
6. Transfers outside the European Economic Area
Some of these providers may process data outside the European Economic Area. [REVISAR: Railway and Supabase regions; Google and Stadia Maps; applicable safeguards such as standard contractual clauses]
7. Your rights
You can exercise your rights of access, rectification, erasure, objection, restriction and portability:
- Access and portability: on the web, "Download my data" in Settings gives you a file with what we keep about your account. In the mobile app, "Download my data" in Settings > My account and plan gives you a file with what we keep about that device.
- Erasure: on the web, "Delete my account" in Settings deletes your account and your data. In the mobile app, "Delete my data" in Settings deletes the ships you follow, your preferences and alert role, comments, ratings, reports and notifications, removes the name of the device and of its invitation and withdraws its access key. Without the app, you can ask by email: see the "Delete my data" page (/borrar-datos).
- Rectification and the other rights: write to us at privacy@harborcues.com.
If you think we are not handling your data properly you can complain to the Spanish Data Protection Agency (www.aepd.es).
8. Security
Passwords do not pass through our server. We validate every session on the server, secret keys only exist on the server and the connection is encrypted. No system is infallible: if a breach affects you we will tell you as the law requires.
9. Minors
HarborCues is not aimed at children under 14 and we do not knowingly create accounts for them. [REVISAR: minimum age]
10. Changes to this policy
This is version 2026-11-borrador-3. If it changes significantly we will tell you in the app.