Legal

NautiQA privacy notice

This notice is for the NautiQA service. For this website and our business dealings, read the Privacy notice.

What we record when you use the service

We record your account details (name, work e-mail, organization and role), when and how you sign in, what you do in the service, and the questions you type into the assistant, together with your user name and organization. We use this to run and secure the service, to answer you, to prevent misuse, and to improve the service and its knowledge base.

Your organization's administrator can see account activity for the organization. We do not sell your data and we do not share it with other organizations.

How long we keep it depends on what it is:

  • Your account details, and what you and your organization save in the service (reports, files, assessments, records, messages and the like): for as long as the account exists. They are deleted when your organization’s administrator or we delete the account, and everything of an organization is deleted with the organization. Some work belongs to your organization and stays with it when a person leaves, as set out below.
  • The record of sign-ins and other security events (your user name, internet address, the kind of event and the time): 180 days, then it is deleted automatically.
  • The counters that limit password guessing: two days.
  • The questions you type into the maritime assistant, and the counts of how much the assistants are used: 30 days and 13 months, as set out under the AI assistants below.
  • The technical logs of our hosting provider (your internet address, the time and the page asked for): 90 days online and one year offline, under its data processing agreement.
  • Our backups: up to three months, then they are overwritten.

You can ask us for a copy, a correction or deletion at info@gatosconsulting.gr.

Our processors are Netlify, Inc. (hosting, and storage of the service's data), Cloudflare, Inc. (storage of files), Anthropic (the AI service behind the assistants, described below) and Resend (the e-mail the service sends: links to set or reset a password and, if you ask for it, a daily count of the messages waiting for you). All four are companies in the United States, so what they handle leaves the European Economic Area. This is where each of them keeps it, and what makes the transfer lawful:

  • Netlify, Inc. runs the service’s functions and keeps its stored data in the United States, in its US East (Ohio) region. Netlify is certified under the EU-US Data Privacy Framework. If that certification ends, the standard contractual clauses in its data processing agreement apply.
  • Cloudflare, Inc. keeps the files in its R2 storage, in its Eastern Europe (EEUR) region, which was set when our storage bucket was created. That region is not a guarantee that the files stay in a particular country or in the European Union. Cloudflare is certified under the EU-US Data Privacy Framework. If that certification ends, the standard contractual clauses in its data processing addendum apply.
  • Anthropic, PBC keeps what it receives, at rest, in the United States. The model that answers may run in other regions where Anthropic operates. The transfer rests on the standard contractual clauses in Anthropic’s data processing addendum, which forms part of its commercial terms with us.
  • Resend (operated by Plus Five Five, Inc.) stores its data in the United States, whichever region an e-mail is sent from, and keeps the content and the logs of the e-mails it sends for 30 days. The transfer rests on the standard contractual clauses in its data processing addendum, and on its participation in the EU-US Data Privacy Framework.

Each of them handles the data only for us, under a data processing agreement that forms part of its terms.

If your organization links to its verifier

A shipping company can link its organization to the verifier it has hired, when that verifier uses the service too. The administrators of both organizations must agree, and either can end the link at any time. The people of the company who may change data can then send the verifier what it needs to verify, with an optional note: one ship or the whole fleet, for one reporting year, as the emissions reporting files the service produces. Nothing is sent unless a person of the company sends it.

Before it opens anything, the verifier sees the company's name, the names and IMO numbers of the ships, the year, the note, the version, and who sent it and when. The files are kept in the service, in the company's own space, until the company withdraws the send or the link ends, and then they are deleted. We keep a record of each send: who sent it and when, what it covers, which person at the verifier opened it and when, and who imported it. The company can see when its send was opened and imported. The record stays while either organization has an account.

A verifier linked to a company can also ask it for papers, such as passage plans, SEEMPs, bunker delivery notes or logbook pages, with a short description and, if it likes, a ship and a year. The people of the company choose what to send for each request, or close it. A file sent for a request is kept in the company's own space and is deleted 24 hours after the verifier first opens it, and in any case 14 days after it was sent, so the verifier has to download what it needs in that time. We keep a record of each request and of each file (its name and size, who sent it and when, which person at the verifier opened it and when, and when it was deleted), but not the file itself once it is deleted.

When the verifier opens a send in its Verification Workbench, the ships become its own working papers, kept in its own space. They stay with the verifier if the company withdraws the send or ends the link, because a verifier has to keep its working papers. What the verifier does with them is governed by its own duties and its agreement with the company. Nothing is shared in the other direction, and nothing is shared with any other organization.

If you work as a verifier

The ships and reporting years you enter in the Verification Workbench, and the documents you add to them, are kept in your organization's own space on the service, so your colleagues can work on them from any device. Only people of your organization can see them: those with editing rights can change them, and those with viewing rights can read them. They are kept until someone with editing rights deletes them. Deleting a ship deletes its documents, and everything is deleted with your organization's account.

If your organization uses Vessel Reporting and its ships' sign-ins

An administrator can give each ship a sign-in of its own, and give people of the company access to the ships they work on, as manager, user or viewer. A ship sees only its own vessel. The ship and these people exchange reports and files through the service: the ship sends noon, arrival and departure reports, bunker delivery notes, safety reports, voyage plans and other documents; the company's people send files to a vessel, and may also send reports in the name of the vessel.

We keep what was sent (the report or the file), who sent it and when, who opened or downloaded it and when, who sent it on to Emissions, Outstanding or the approval of a voyage plan, and who deleted it. The people assigned to a vessel, and the administrator, can see its files; a viewer can read but cannot delete. A ship's sign-in is one for the whole crew, so we record the sign-in, not the person using it. When someone deletes a file, it moves to a Deleted folder, where it waits for 7 days. Nobody can open it there, and a report that was waiting for review is not reviewed. In that time a person who may delete files can restore it. The people concerned (the ship, the person who sent it, those responsible for it) are told. After 7 days, or at once if a person chooses Delete for good, the file is removed from storage and what the crew wrote in a report is cleared. A short record stays (what it was called, who sent it and when, who deleted it). The administrator can also set a rule that deletes files a number of days after they were sent. Everything is deleted with the organization's account.

Drafts. A report that is started and not sent is kept as a draft in the service, for the vessel, and not in the browser: the figures and the text written so far, who started it and who last changed it, and when. The ship's sign-in and the people who may write reports for the vessel can open, change, send and delete it, so that a report started on one computer can be finished on another. Sending the report deletes the draft. A draft nobody has changed for 30 days is deleted, and every draft is deleted with the organization's account.

Opened and taken back. We keep who opened a report or a file that was sent, and when. The person who sent something can take it back while nobody at the other end has opened it: it moves to Deleted for 7 days like a deletion, marked as taken back, and the people who were told that it was sent are told that it was taken back. A ship can look at everything it sent, as it was sent.

If your organization uses messages and Outstanding

Messages. Everyone who signs in to an organization has a mailbox in the service, behind the letter icon. People write to the other people of their own organization, and the service writes to a person when something needs them, for example an action given to them or a report waiting for their review. A message holds its subject and text, who wrote it and to whom, when, and a link to what it is about. Only the person whose mailbox it is can read it: the administrator cannot. We keep up to 300 messages for each person, the oldest read, deleted or sent ones going first. A deleted message waits in a Deleted box for a week, where the person can restore it or delete it for good, and is then removed for good. The text of messages is not written to our logs. A person's mailbox is deleted with their account, and every mailbox with the organization's account.

Outstanding. A shipping company keeps in Outstanding the records of its ships' accidents, incidents, near misses, observations, detentions and inspection and audit findings, and the actions that follow. A record holds its title and description, the ship, the dates, the severity, the area it is related to, who made it, comments and who wrote each, references, and a history of changes. An action holds its text, its owner, its due date, its state and who verified it. People write these in free text and may name third parties, such as crew, inspectors or auditors; they should name people only as far as the record needs. The administrator sees all the records of the organization. Other people see the records of the fleets and ships they are assigned to, as manager, crew or viewer, and a ship's sign-in sees only those of its own ship. A record is kept until a person with the right deletes it, which removes it for good after a confirmation, and is deleted with the organization's account. When a person uploads a list or an inspection report to make records, the file is read in the browser and only the records the person confirms are saved; the file itself is not kept.

The AI assistants

The service has two kinds of AI assistant, and both use an AI service provided by Anthropic. The maritime assistant in the library can be used by everyone who signs in. The AI assistants that read files and answer questions about a fleet and about the safety records are an optional module. They are off for an organization unless we switch them on, which we do when the organization asks, and we switch them off again when it asks. Nothing goes to the AI service unless a person asks a question or chooses a file to be read. No decision about a person is taken from what an assistant returns: a person checks and confirms the values read from a file before anything is saved, and an answer is for a person to read.

The maritime assistant. Your question and the recent conversation go to the AI service, with extracts of public regulatory text from the library and, when the library does not cover the question, the results of a web search, to be answered. We keep a log of the questions: your user name and organization, the question, how well the library covered it, what it lacked, the library pages and web pages used, and your thumbs-up or thumbs-down if you give one. We read the log to find what the library lacks and to improve it. We keep the log for 30 days and then delete it. If your account or your organization is deleted, the lines you asked are deleted with it.

Reading a file (optional module). When a manager asks the assistant to read a report or a bunker delivery note that a ship sent, or a person drops files in the bulk inbox, the content of the file goes to the AI service: the text of a PDF, a Word file or a sheet, or the pages of a scan, a photo or a PDF as pictures. The service's own templates are read without it. Nothing else goes with the content: not the name of the file, the ship, the company or the person. A file may name people, such as the crew, and those names go with the rest of its content.

Questions about a fleet (optional module). A question asked in Insights goes to the AI service with the figures that the assistant asks the service for in order to answer it, such as consumption, emissions, performance, costs and ports. The figures name ships and ports. The rows of the fleet and the free text in them do not go.

Questions about the safety records (optional module). A question asked in Outstanding goes with the figures that the assistant asks the service for: counts, dates, severity and status, by ship and type. When the question needs it, for example what the reports say, a corrective or preventive action, a next action or a safety campaign, the assistant also receives the titles and descriptions of up to 25 records at a time and, for one record, the text, state and due date of each action. Before they are sent, e-mail addresses, numbers that look like telephone numbers and links are taken out and each text is cut short. Comments, references, identifiers and the names of the people who made a record or who have an action are not sent. A description is free text and may name someone; the assistant is told never to repeat a name. A ship's sign-in cannot use this assistant.

We do not keep what is sent for reading or for the questions of the optional module, or what comes back, except the values a person confirms and saves. Anthropic handles what it receives under its commercial terms with us. Under those terms it may not use it to train its models. It deletes it from its systems within 30 days of receiving it or of generating the answer, unless it has to keep it longer: if its safety systems flag content as breaking its usage policy, it may keep it for up to two years (and the result of the check for up to seven), and it may keep what the law requires it to keep.

How much the assistants are used. For every request to an assistant we count it: who made it (the user name and the organization), the month and the day, which assistant, how much it used (the size of the request and of the answer, the number of web searches, an estimate of its cost) and the credits it used. We never keep the question, the answer or the file in these counts. The counts let your organization’s administrator see the use, let us apply the limits and the allowance of your organization, and let us invoice the AI. We keep them for 13 months. The counts of a person are deleted with the account, and those of an organization with the organization.

Maps, weather and your position

The service does not supply the maps, the weather, the tides or the storm tracks itself. Your browser fetches them straight from outside services: OpenFreeMap, OpenStreetMap and OpenSeaMap (map pictures and sea marks), GEBCO (seabed colours), NOAA (seabed depth, tides, and the wind forecast files that NOAA keeps on Amazon's servers), Open-Meteo (weather, sea state and the search for a place) and an ArcGIS-hosted feed of active storms. Each of them sees your internet address and the part of the map, or the place, that you ask for. If you search for a place, the words you type go to Open-Meteo. None of our cookies and no page address goes with these requests, and we do not tell these services who you are. We do not control what they keep: each has its own privacy terms. This is where they are, and where to read their terms:

  • OpenFreeMap: its privacy policy does not name where its servers are, and it may use Cloudflare as a content delivery network. Privacy policy.
  • OpenStreetMap (the map pictures and the place-name service): run by the OpenStreetMap Foundation. It keeps the personal data it stores in the United Kingdom and the Netherlands, with backups in the European Union, but the map pictures come from a worldwide network of cache servers. Privacy policy.
  • OpenSeaMap: its provider is in Germany. Legal notices.
  • GEBCO: hosted by the British Oceanographic Data Centre, in the United Kingdom. Privacy policy.
  • NOAA: an agency of the United States government. The wind forecast files are kept on Amazon’s servers. Privacy policy.
  • Open-Meteo: run by OpenMeteo GmbH in Switzerland, with servers in Europe and North America. Terms and privacy.
  • The storm feed: hosted on ArcGIS Online by Esri, a United States company. Privacy overview.

If you allow your browser to share your position, the Home page shows the weather, the sun and moon and the time where you are. Your browser sends your position, to about 100 metres, to Open-Meteo for the weather. The name of the town or village comes from our server, which asks OpenStreetMap's place-name service (Nominatim) using your position rounded to about a kilometre, so that service does not see your internet address; it is asked only for places on land. We keep those answers for 90 days, by square of about a kilometre and not by person, and we do not write your position to our logs.

Cookies

Only essential cookies, unless analytics are added. If they are, we will say so and ask first.

Changes to this notice

We update this page when something significant changes, and we show the date. This version was last changed on 5 November 2026.