Legal · Effective 11 November 2026
Privacy Policy
Stingray is built so that as little of your data as possible ever leaves your machine. This page describes, precisely, what is processed, where, and why — and the rights you have over it.
1. Who we are
The data controller for Stingray (stingraynav.com) is Tommaso Laterza, reachable at tommasoltrz@gmail.com.Stingray is developed in collaboration with Kontiki S.R.L. (Genova, Italy), which is not the operator of this service.
2. Two roles: your account data vs. your case data
For the data that makes your account work — your email, your profile, waitlist signups, usage counters, analytics — we are the controller.
For the case data you upload and produce — recordings, decoded vessel tracks, notes, audio clips, chart overlays — you (or your organisation) are the controller, and Stingray acts as a processor: we store it on your instruction, we never read it, analyse it, or share it, and it is technically isolated to your account (row-level security, verified by policy audit). Maritime traffic data can contain personal data (vessel names, MMSIs of small craft, voice recordings) — assessing the lawfulness of analysing it in your case is your responsibility as its controller.
3. What never leaves your machine
The following processing and storage stay on your machine. Cloud project data is described in §4.
- Serial recordings and recorder logs are parsed locally in a background worker. The complete files are not uploaded. Recorder media can retain local folder access and in-memory source copies for later playback. Recorded screen pictures remain in the source folder; their indexes and source metadata can be saved with a cloud project.
- Audio and image filesyou attach or import stay on your device. A project keeps each file's name, size and fingerprint so the original can be found and checked again. A cloud project does not receive the file.
- Exports (MP4 videos, Rhino 3DM models, CSV files, PNG and SVG images) — generated locally and saved directly to your disk. Nothing is rendered server-side.
- Local projects. When you save a project as a local file (a
.stingrayfile on your disk), the saved project data stays on your machine. Recorder audio and recorded screen pictures can still need the original folder; they are not embedded in the file. (Cloud projects, the default, are stored in your private workspace as described below.)
4. What we process, and why
| Data | When | Purpose / legal basis |
|---|---|---|
| Account identity (email, optional name) and beta invitation details | When an invitation is created or claimed, and at signup | Operating your account (contract, Art. 6(1)(b)) |
| Project data (decoded tracks, settings, notes, source names, relative paths, hashes, capture indexes and audit records, media filenames and fingerprints) | When you save a cloud project | Storing your work at your instruction (contract; we act as processor — see §2). Hosted in the EU, readable only by your account. New audio and image files are not uploaded. Audio and image overlays uploaded to a cloud project before 11 November 2026 stay stored with it until you remove the attachment or delete the project. |
| Waitlist email | When you request access | Notifying you when Stingray opens — nothing else (consent, Art. 6(1)(a)) |
| Vendor configuration document and optional sentence samples (AI-assisted decoding) | Only when you explicitly upload one to the optional “draft with AI” feature. Bounded observed sentence samples are included only if you separately select that option | Drafting decode rules (consent per use). Sent to Anthropic for processing; never stored or logged — we keep only token counts for rate limiting. |
| Usage and diagnostics (normalized routes, feature use, operation outcomes, performance, sanitized error categories, device class and country) | Browsing the site and using the app | Understanding usage and improving reliability (legitimate interest). Cookieless, without account identity or private case data, reported through our own domain. |
| Hosting logs (IP address, requested URL) | Every request | Security and operation of the service (legitimate interest) |
5. Who receives data (processors)
- Supabase (database, storage, authentication) — hosted in the EU (Ireland, eu-west-1). Holds account data and saved project data.
- Resend (transactional email) — receives recipient email addresses and the contents of account confirmation, password reset, and waitlist confirmation emails. Project data is not included in these emails.
- Vercel (hosting) — processes requests and logs; transfers to the US are covered by its EU–US Data Privacy Framework certification and standard contractual clauses.
- We run Umami on Vercel for usage and diagnostics, with an analytics database hosted by Neon in Frankfurt, EU. It receives normalized page routes, feature use, tab selections and preset display choices for maps and charts, active display settings at workspace open, AI draft usage and timings, operation outcomes, playback controls and speed, aggregate playback statistics, preparation and viewer load timings, browser performance measurements, and sanitized error categories through our own domain. Error reports may include an application code location, but exclude raw messages and full stack traces. Recordings, vessel and project identities, filenames, coordinates, audio and anything you type are excluded. No tracking cookies, account identity, session replay or cross-site identifier are sent.
- Anthropic (AI-assisted decoding) — receives the vendor document you explicitly upload and bounded observed sentence samples if you separately opt to include them. US-based. Never used unless you choose to.
- Map tile servers (OpenStreetMap, Carto, ArcGIS, OpenSeaMap) — an unavoidable property of using third-party basemaps: when you pan the map, your browser requests tiles for the viewed area directly from these servers, which therefore see your IP address and the map region you are looking at. No case data is included in those requests.
We do not sell data, and there is no advertising of any kind.
6. Cookies and local storage
Stingray sets no tracking cookies. The only cookies are the strictly-necessary session cookies that keep you signed in. Local interface preferences such as panel sizes are kept in your browser's local storage. Analytics is cookieless. Browser Do Not Track signals do not disable usage, performance or error telemetry. The private-data exclusions described above apply to every telemetry payload.
7. Retention
- Account and project data: until you delete a project or your account (see §8).
- Waitlist emails: until you are notified of launch or ask to be removed, whichever comes first.
- AI-usage counters (never content): as long as needed to enforce usage limits.
8. Your rights
Under the GDPR you can request access, rectification, erasure, portability, or restriction of your personal data, and object to processing based on legitimate interest. To exercise any of these — including full deletion of your account and all stored data — email tommasoltrz@gmail.com. Requests are honoured within 30 days.
You also have the right to lodge a complaint with a supervisory authority — in Italy, the Garante per la Protezione dei Dati Personali (garanteprivacy.it), or the authority of your own EU member state.
9. Changes
If this policy changes materially, the effective date above is updated and registered users are notified by email. The current version always lives at this address.