NameboardBook a call
Menu

Privacy Policy

Nameboard S.L.

Last updated: 22 April 2026 · Version 1.0

1. Who we are and what this policy covers

Nameboard S.L. (“Nameboard”, “we”, “us”) sells fisheries-enforcement and maritime agencies a data service that gives each radar satellite detection inside a closed or protected fishing area a proposed vessel name, or the reason it has none. To build it we read free satellite scenes, AIS position reports, and the records an agency chooses to share with us: its license register and, where it decides to, VMS positions, patrol logs and port calls. This policy explains what personal data we handle when we do that, and why.

Registered at Rúa de Policarpo Sanz 22, Planta 3, 36202 Vigo, Spain.

We handle personal data in two different situations, and different rules apply to each:

Whose dataOur roleWhat applies
Part APeople who visit this website, ask about the service or write to usController: we decide why and how the data is usedThis policy
Part BStaff of our customers who hold accounts with us; and the owners and skippers of fishing and other vessels, where a vessel's name, registration number, AIS identity or position can be linked to a person, as it can for a small boat owned by one personSet out in B.1, because it depends on the dataThis policy and the data processing agreement we sign with each customer

If the data processing agreement (“DPA”) and this policy ever disagree about Part B, the DPA wins.

2. Part A: this website and our contact with you

This part covers the personal data we collect for our own purposes: running this website, answering requests, and staying in touch with people who are or might become customers.

A.1 What we collect

What you give us. When you send the form on this site, we collect what you type into it, such as your name, email address, phone number or company, and the fact that you agreed to be contacted. If you email or talk to us, we keep that correspondence and any contact details in it.

What is collected automatically. Our web server records the IP address a request came from, the browser used, the pages requested, the page you came from and the time. These logs exist to keep the site running and secure.

We don’t ask for sensitive data (the “special categories” in Article 9 GDPR) through this website, so please don’t send any through the form.

A.2 Why we use it, and what allows us to

WhyWhatLegal basis (GDPR Art. 6)
Answering your request and working out whether the service fitsWhat you sent in the form, our correspondenceArt. 6(1)(b): steps you asked for before a contract
Looking after customers, billing and supportContact details, correspondenceArt. 6(1)(b): carrying out a contract
Keeping the site running, secure and free of abuseServer logsArt. 6(1)(f): our legitimate interest in running a secure service
Contacting you about the serviceEmail address, companyArt. 6(1)(f): our legitimate interest in business-to-business marketing. You can object at any time
Meeting tax, accounting and legal dutiesBilling and contract recordsArt. 6(1)(c): a legal obligation

Where we rely on legitimate interest, we have weighed that interest against your rights, and you can ask to see the assessment.

A.3 How long we keep it

A.4 Your rights

If you are in the EEA or the UK, you can ask to see your data, correct it, have it deleted, limit or object to how we use it, get a copy you can take elsewhere, and withdraw consent where we rely on it. Write to [email protected] and we will answer within one month.

You can also complain to a data protection authority. If you are in the EEA, that can be the authority where you live or work.

3. Part B: data inside the service

This part covers the data that passes through the service itself: the records an agency shares with us, the AIS reports and satellite scenes we read for its areas, and the per-pass files, patrol lists and season reports we deliver.

B.1 What we handle, and in what role

For the records an agency shares, and for the files, lists and reports we deliver from them, we act as a processor, on the agency's instructions and under the data processing agreement; the agency decides which areas we watch and which of its records we read. For the AIS reports and satellite scenes we obtain ourselves, for our analysts' labels and for account details, we act as a controller. The service handles the following:

We take no photographs or video and receive none. Nothing in the service shows a face, a crew at work or the inside of a vessel.

We do not combine one agency's records with another's. A vessel on two agencies' registers is traced separately for each, and neither agency learns that the other asked about it.

We do not sell or share tracks, detections or agency records with insurers, shipping companies or anyone other than the agency that ordered the area.

B.2 What we do with it

Detection. Each radar scene covering a named area is cut to the area, and every target inside it is scored as vessel or not and measured by our radar model. Targets the model cannot settle are shown to one of our analysts, who sees the radar chip and nothing else. All of this runs on cloud infrastructure in N. Virginia.

Tracing. Each detection is compared with AIS tracks near the area, the license register, any VMS positions, patrol logs and port calls the agency shared, and the area's past seasons, by our own ranking model on cloud GPU capacity we control in N. Virginia. No person at Nameboard reads an agency's records while this runs.

Review and release. Every proposed name is shown to the agency's own officer in a review queue, with the signs behind it, and reaches the patrol only after that officer accepts it and releases the list. Our staff never accept, reject or release anything.

Support access. Two named support engineers can open an agency's records, and only when the agency asks in writing so that a fault can be fixed. Every opening is logged and listed in the agency's account.

No onward sale. We do not sell, rent or share agency records, detections, lists or reports. Subprocessors that host the service on cloud infrastructure in N. Virginia, supply licensed AIS, send our email and take payment are named on our subprocessor list. The AIS supplier receives only the area and time window we query, never an agency record.

B.3 AI models: where they run and what they learn from

Where models run. The radar model that decides which targets are vessels and measures them, and the ranking model that proposes which vessel a detection is, are models we trained ourselves, the first fine-tuned from an open-weight vision backbone, and both run on cloud GPU capacity we control in N. Virginia. No license register, VMS position, patrol log, port record, patrol list or report is sent to a third-party hosted model API at any point, and no such provider is on our subprocessor list. The plain sentences that state each sign are written by fixed templates, not by a language model.

Training. We do not train models on an agency's license register, VMS positions, patrol logs, port calls, patrol lists or reports. Two narrow uses are the exception. First, our analysts' labels: a radar chip cut from a public satellite scene and the label given, vessel or not and its length, sometimes taken from the stated length in that vessel's own public AIS broadcast; the pair carries no vessel name, AIS identity or agency identifier, is pooled across all customers because it contains public imagery only, and trains our radar model and nothing else. Second, an agency officer's accept or reject, with the signs the proposal rested on, adjusts the weights of the trace for that agency's own areas only; it is never pooled with another agency's decisions and is deleted with that agency's records.

Where a person decides. The models propose and people decide, at two points. A radar target the radar model scores between 0.35 and 0.75 as a vessel is checked by one of our analysts, who sees only the radar chip, before it counts as a detection; above 0.75 it counts, and below 0.35 it is listed in the pass file as a rejected target. A name is proposed only when at least two independent signs point at the same vessel, its score is 0.80 or more and the next vessel trails by at least 0.20; otherwise the detection is returned with no name and one of six fixed reasons. Every proposed name waits in the agency officer's queue and reaches the patrol only after that officer accepts it and releases the list. The service makes no automated decision with legal or similarly significant effect on any person: a name is a reason to go and look, and every boarding, case and sanction is decided by the agency's officers.

B.4 Where the data is kept

Every agency record, detection, per-pass file, patrol list and season report is stored and processed on cloud infrastructure in N. Virginia, in the United States. Backups are encrypted and kept in the same place. There is no option to keep data in the European Union.

Records from an agency in Spain, elsewhere in the EEA or in the UK reach N. Virginia under the European Commission's standard contractual clauses, which form part of our data processing agreement. Payment details are held by our payment provider and never reach our systems.

The suppliers that handle data in the service are named on our subprocessor list, which comes with the data processing agreement and which we send to anyone who asks: write to [email protected].

B.5 How long we keep it, and what deleting can’t remove

License register extracts, VMS positions, patrol log entries and port calls are kept for the season they serve and 90 days after, then deleted. An agency can have them deleted sooner by asking in writing; we do it within ten business days and confirm it in writing.

Per-pass files, patrol lists and season reports, with each officer's decision and reason, are kept for the life of the contract and 24 months after so that a report can be re-issued, or deleted earlier at the agency's request once it has exported them.

An analyst's label is kept as a pair: a radar chip cut from a public scene and the label given, which is vessel or not and its length. The pair carries no vessel name, no AIS identity and no agency identifier, and is kept for as long as the radar model it trains is in use.

Account details and the decision log are kept for the life of the account and 24 months after. Invoices and the books behind them are kept for six years from the last entry in the books, as Article 30 of Spain's Commercial Code requires.

B.6 Requests from people whose data is in the service

If you own or skipper a vessel and want to know what we hold about it, write to us. Most of what we hold is AIS reports and radar detections linked to the vessel's identity, and we will tell you what that is. Where the data came from an agency's records, we pass your request to that agency, which decides on it as the controller, and we tell you we have done so.

For everyone

4. Moving data between countries

Nameboard S.L. is a company in Spain, inside the EEA. Section B.4 says where the data in the service is kept. If any personal data we control ever has to leave the EEA, for example because a supplier named on our subprocessor list handles it elsewhere, it is protected by the European Commission’s Standard Contractual Clauses or another safeguard the GDPR accepts. You can ask us for a copy.

5. Security

We protect data in line with the risk. That includes encryption in transit and at rest, access limited to the people and systems that need it, each customer’s data kept separate from every other’s, and a log of every access to production systems.

If a personal data breach affects you, we tell you without undue delay, and at the latest within 36 hours of finding out, with the information you need to meet your own reporting duties.

6. Children

The service is sold to businesses and is not meant for children. We don’t knowingly collect personal data from anyone under 16.

7. Changes to this policy

We may update this policy. If a change matters, we email customers at least 30 days before it takes effect. The version number and date at the top of this page change every time.

8. Contact

Privacy questions and anything else: [email protected]
By post: Nameboard S.L., Rúa de Policarpo Sanz 22, Planta 3, 36202 Vigo, Spain

← Back

Your request has been received.

Expect a message from Nameboard. It goes to the address you gave.