Data and AI
Where your data lives, and what AI is allowed to do with it
SSA holds video and audio of identifiable people, and a programme’s confidential numbers. Two questions decide whether that is acceptable, and both are answered in full on this page rather than in a policy nobody reads.
Everything stays in the EU
Not “EU-friendly” or “EU-available”. Every subprocessor below is an EU region, and there is no US fallback.
| Who | What for | Where |
|---|---|---|
| Supabase | Database, authentication, file storage | Ireland (eu-west-1) |
| Bunny.net | Video transcoding and delivery | EU edge storage |
| Scaleway | All AI inference — transcription and summarisation | France |
| Vercel | Application hosting | EU region |
| Open-Meteo | Weather forecasts (venue coordinates only — no personal data) | EU |
Video and photographs of identifiable crew are personal data under the GDPR, and so is a debrief recording of someone’s voice. A data-processing agreement is part of the contract rather than something to ask for afterwards, and this list is the subprocessor schedule to it. If it changes, you are told before it changes.
What AI does, and what it is not allowed to do
Debrief recordings are transcribed and summarised by a model. That is the single most sensitive thing SSA does, so here is the whole of it.
No third-party AI vendor ever receives your data.
All inference runs inside SSA’s own account at Scaleway, a French provider, on European hardware. Your crew’s voices and your team’s words are never sent to OpenAI, Google, Anthropic, Meta or any other model vendor. This is an architectural constraint, not a setting — there is no code path that would send a recording anywhere else.
What runs
- Whisper large-v3 — turns a recording into text.
- Mistral Small 3.2 (24B) — tidies the text into your own vocabulary and drafts a summary.
- Both hosted by Scaleway. Open-weight models, not a vendor’s private API.
What it is given
- The recording you chose to process, and nothing else.
- Your team’s glossary — sail names, crew names, class jargon — so it transcribes A2 and gybe rather than guessing.
- No other team’s data is ever in the same request. There is no shared context between teams.
The rules it runs under
- Nothing is trained on. Your recordings and text are not used to train or fine-tune any model, by us or by Scaleway. Improving SSA’s analysis uses sailing data — tracks, wind, manoeuvres — and only with the separate permission described below.
- AI only runs when a person asks it to. Nothing is transcribed in the background. A coach presses record, or picks a file, every time.
- A person approves the output before it is saved. The draft is shown for review and editing first. It is a good assistant and a bad witness, and the product treats it that way.
- It cannot reach across teams. The model is given one team’s material in one request. It has no index of everyone’s seasons to draw on and cannot leak one team’s day into another’s summary.
- Everyone in the room has to agree first. The team debrief recorder does not run until every sailor and coach on the team has ticked the consent box in their own profile. It is asked at signup, it defaults to no, and anyone can withdraw it at any time — which stops the recorder for the whole team until they agree again. Owners, consultants and guests are not counted, because they are not in the debrief.
- You can switch it off. A team that does not want AI transcription simply does not use it; every note can be typed. Nothing else in SSA depends on it.
Who can see what
Access is per team and per boat, enforced in the database rather than in the interface.
| Admin | Everything, across all teams. That is one person: the founder. |
| Team manager | Everything for their own programme, including rig and tuning. |
| Coach | Everything for the boats they coach. |
| Sailor | Their boat’s days, media, analysis and debriefs. |
| Consultant | The same as a coach, but only inside a date window you set. Access ends by itself. |
| Guest | The most recent day only. |
| Share link | Exactly one clip. No account needed, revocable at any time. |
Squad sharing is opt-in, per category. When boats from different owners share days, you choose what goes: tracks and analysis, photos, video. Rig settings and tuning are off by default and stay off until you turn them on.
Debriefs are never shareable. Not to a squad, not to a partner boat, not by link. What a team says about its own performance stays inside that team, and there is no setting that changes it.
It is your data
Export whenever you want, including on the way out. We will not hold a season hostage to a renewal.
Deletion is real. Ask and it is removed from the database and from video storage, not flagged as hidden.
Consent is recorded and revocable. Agreeing to be recorded is a tick box in your own profile, dated when you set it, and untickable at any time without asking anyone.
A crew member can ask for their own data. Access, correction and erasure requests go to the team manager or straight to us, and we answer within a month as the GDPR requires.
Improving the analysis needs your separate permission.It is its own clause in the contract, it covers de-identified sailing data only — never video, audio or debrief text — and you can decline it and keep everything else.
What is not settled yet
A privacy page that claims everything is finished is the one you should not believe.
- There is no automatic retention schedule. Data stays until you ask for it to go. Some programmes want a fixed deletion horizon; if you need one, it is a contract term today rather than a switch in the app.
- No formal certification. SSA is not ISO 27001 or SOC 2 certified, and saying otherwise would be a lie. What exists is EU-only hosting, a DPA, database-level access control and the AI constraints above.
Questions your legal team needs answered?
Send them straight over. A federation’s data-protection officer asking hard questions is a good sign, not an obstacle, and the answers above are the ones we would give them.