Privacy Policy

1. Controller identification

Controller: Jan Linhart (natural person)

Identification number (ICO): 75412551

City: Praha 6 - Ruzyne

This policy covers the Veetr mobile app and veetr.org.

2. What data we process

We process the data you provide in our contact forms, such as email address and message content. If ordering or shipping functionality is introduced later, we may process name, email, phone number, shipping address, and order history. We also process technical data collected via tracking, including IP address and device identifiers.

3. Purposes and legal bases

We process personal data for responding to inquiries, providing support, newsletter communication, analytics, service improvement, and legal obligations where applicable.

4. Tracking and cookies

We use a self-hosted Mautic instance for tracking and marketing automation. The data is stored on DigitalOcean servers located in Amsterdam, Netherlands. Analytics tracking is only enabled after you accept cookies in our cookie banner.

Cookie categories include essential cookies required for site functionality and optional analytics or marketing cookies used by Mautic. Optional cookies are disabled until you consent.

5. Data retention

We keep personal data only for as long as necessary to fulfill the purposes described above and to comply with legal obligations under EU and Czech law.

Typical retention periods are 3 years for support communications, until consent is withdrawn or 2 years of inactivity for marketing contacts, and 14 months for analytics data.

6. Recipients and processors

We use service providers including DigitalOcean for the self-hosted Mautic instance, Webglobe.cz for SMTP email delivery, GitHub Pages for website hosting, and other providers required to operate the site.

7. Your rights

You have the right to access, rectify, erase, restrict, or object to processing, and the right to data portability where applicable. You can also withdraw consent at any time where processing is based on consent.

To exercise your rights, contact us at [email protected].

8. Security

We take security seriously and use industry-standard safeguards to protect personal data. No system can be guaranteed fully secure.

9. Changes to this policy

We may update this Privacy Policy from time to time. The latest version will always be available on this page.

10. Optional Veetr app diagnostics

The Veetr mobile app offers optional diagnostic reporting to help investigate errors and tracking reliability. Automatic reporting is off by default and is enabled only when you choose “Share diagnostic reports” in Settings → Location & tracking. You may instead choose “Send diagnostic report” to authorize a single report without enabling automatic reporting. Tracking works regardless of this choice.

Reports contain app/build version, hardware model (not your device’s personal name), operating-system version, app foreground/background state, location-permission status, reported GPS accuracy, time elapsed since the last recorded fix and upload, upload-queue size, GPS restart counts, and fixed error categories. Android reports can also contain screen and power-saving state, location-provider availability, and bounded counters and timings for native location delivery, background jobs, service lifecycle, and recorder callbacks. They do not contain GPS coordinates, routes, names, email addresses, account or race identifiers, invitation links, authentication tokens, or unrestricted error/console messages.

While automatic diagnostic sharing is enabled, tracking reports can also include recent raw and filtered GPS speed/course values, reported position and speed uncertainty, delivery delays, a motion classification (quiet, moving or unknown), fixed filtering reasons and a filter version. These samples exclude coordinates, route copies and continuous raw accelerometer or gyroscope recordings. Each recorder retains at most 120 recent samples locally for up to seven days; a report includes at most 32 samples, subject to its size limit. This is a recent troubleshooting window, not a complete trip log. Disabling sharing deletes these unsent samples. A one-off report does not enable this extended collection.

Bluetooth diagnostics include recent connection stages, adapter and foreground/background state, connection and sensor timing, signal strength, firmware version, retry details and numeric error codes. They exclude Bluetooth device names and identifiers, raw error messages and sensor data. The app keeps up to 20 technical Bluetooth events in memory for up to six hours to include in a report you choose to send or in enabled automatic reports.

We process these reports based on your consent. Automatic reports use a random diagnostic identifier, separate from your account and race session, to relate technical events from the same installation. One-off reports use a separate random identifier. These reports are pseudonymous, not guaranteed anonymous. Supabase processes the reports on our behalf; authorized Veetr maintainers can inspect them. Normal hosting/network services also process connection information such as IP addresses to handle requests; our diagnostic report table does not store IP addresses.

Reports are removed from the active diagnostic database after 30 days by an hourly cleanup. Unsent reports are limited to 100 on the phone and expire after seven days. Native Android counters summarize up to 24 hours of activity and are collected only while automatic reporting is enabled. Turning off automatic reporting stops future automatic reports, cancels pending uploads where possible, and clears unsent reports, native counters, and the local automatic diagnostic identifier. Reports already received are subject to the retention period; turning off reporting does not recall them. Infrastructure logs and backups follow the hosting provider’s separate retention and security controls.

You can withdraw consent without affecting GPS tracking. For access or deletion requests, contact [email protected] and include the report ID shown after a one-off submission, if available. No reports are used for advertising or automated decisions about you.

Trips are private until their recorder chooses to share them. Sharing uploads the selected boat, trip title, timestamps, route and available sailing instruments. “Anyone with the link” allows anyone holding that link to view the trip; “Public” also lists it in Explore trips. Viewers do not need an account. Boat crew membership alone does not allow someone to publish another recorder’s trip.

Live sharing includes the route recorded so far and subsequent uploaded positions. Stopping sharing disables the link once the server confirms the request. When offline, the app shows that the change is pending. Ending a trip keeps your chosen sharing setting and the same link available for the finished route. You can stop sharing separately at any time. Disabling a link cannot remove copies that viewers already saved. Deleting the local recording does not delete an uploaded copy.

Phone GPS instruments and local trip recording do not require an account. With your permission, the app processes precise location, timestamps, speed, course and reported accuracy to display sailing data and record your route. Recording may continue while the screen is off or the app is in the background when you have enabled tracking and granted the necessary permissions. Optional connected instruments provide sailing measurements such as wind data. Local recordings remain on your device unless you choose an upload or sharing feature; map services still receive requests needed to display maps.

Account features process your email address, authentication information, account identifier and applicable boat or race memberships. Supabase provides account authentication and stores online account, trip and race data on our behalf. We use these data to provide the account and sharing services you request. Authorized maintainers can access data when necessary to operate the service or investigate a support request.

When you enable race location sharing, the app uploads your boat’s location, timestamps and available sailing measurements. Race participants, organizers and viewers with access to the race can see the information; public race views may be accessible without signing in. Recorded race positions may remain available for race history and replay after live sharing stops. Stopping tracking prevents future collection by that tracking session; it does not erase previously uploaded records. Account and uploaded sailing data are retained while needed for your account, saved trips and race history, unless you request deletion or a specific retention rule applies.

Map displays use third-party map services, including Google Maps on Android and Apple Maps on iOS, and map or overlay providers shown in the map attribution. Those providers receive technical requests, including connection information and the requested map area, under their own privacy policies. Veetr does not sell your location or use it for advertising.

Account and data deletion

You can request deletion of your account and associated personal data through our account deletion page or by emailing [email protected]. We verify ownership before acting. You can also request deletion of particular uploaded data without deleting your account. The deletion page explains the scope, local recordings, separately identified diagnostics, and possible retention exceptions. Signing out or uninstalling the app does not delete your online account.