Privacy Policy
Who we are
Holt Racing Limited is registered in England and Wales (company number 12633258), with registered office at Hockford Cottage, Ash Road, Pirbright, Woking, Surrey, GU24 0DE. Privacy enquiries can be sent to privacy@tailendcharlie.app.
Information kept on the device
Depending on the features used, the app may store a display name and app-generated identifier; vessel and app preferences; precise GNSS positions, routes, tracks and voyage events; crew state and quick messages; MOB events; imported or created GPX files; optional contact, emergency and medical details entered by the sailor; downloaded maps and forecasts; and configuration for a boat-local AIS/NMEA receiver.
Local voyage records remain until the sailor deletes them, the voyage lifecycle removes short-lived material, app storage is cleared or the app is uninstalled. Android backup is disabled.
Information that can leave the device
- Forecasts and web maps: opening relevant views sends the requested area and ordinary network information to named providers such as Open-Meteo and OpenFreeMap. The app shows source and limitations beside marine data.
- Nearby crew: when the sailor creates or joins a shared voyage and grants permission, accepted nearby devices can receive selected position, route, crew and message data over an encrypted connection.
- Optional internet relay: a tester build configured with the relay can exchange the same voyage coordination data with people holding the private voyage capability. Live positions expire after no more than 30 minutes, optional contact and emergency shares after no more than two hours, and other voyage relay data after no more than 72 hours. Ending a voyage shortens retention.
- Planner codes: choosing to create a short web-planner code sends the plan to the relay. It is encrypted at rest and expires after no more than 30 days.
- User-directed hand-offs: GPX export, QR scanning, telephone, messaging and website actions use the destination deliberately chosen by the sailor. QR images are processed on-device.
Optional Android notifications may use Firebase Cloud Messaging when a tester build is configured for it. A boat-local AIS feed is not uploaded as public vessel history. Tide and Seek does not scrape or sell vessel positions.
Choices, security and rights
Permissions can be refused in the operating system, although the related feature may then be unavailable. Leaving or ending a voyage stops new sharing; a private invitation should be treated like a password and shared only with the intended crew. Network requests use HTTPS and supported nearby transfers are encrypted, but no system is guaranteed to be completely secure.
UK and EEA rights may include access, correction, erasure, restriction and objection. Because Tide and Seek has no accounts, we may need a voyage or link identifier to locate relay data and must avoid disclosing another sailor’s information. Contact privacy@tailendcharlie.app. You may also complain to the UK Information Commissioner’s Office.
Children and changes
Tide and Seek is intended for adult sailors and is not directed at children. We may update this policy as the field-test product changes; the effective date identifies the current version.