Privacy Policy

Who we are

NavLog is a voyage-logging product consisting of a web dashboard, a mobile app, and an optional on-board device (“NavLogCore”). NavLog is provided by NavSuite Marine LLC. This policy covers these surfaces and access through connected assistants. NavLog is currently in private beta.

What we collect

Account data

When you create an account we store your email address, a securely hashed password (handled by our authentication provider), and the first and last name you provide. We use this to sign you in and to contact you about your account.

Vessel, trip & location data

We store the vessels you create, the trips you log, and the position, speed, heading, and related navigational data associated with those trips. Location data is the core of a logbook — it is recorded so you can review and export your own voyage history. We do not sell location data or share it with advertisers.

Telemetry

If you pair a NavLog Core, it uploads telemetry to your account so it can appear on your dashboard and in your trip records. Telemetry includes position, speed and heading, plus whatever your boat's instrument network broadcasts: depth, wind, engine readings, and battery and tank levels. Trip telemetry is kept at full resolution until you delete the trip or your account.

While you're away from the boat

A paired Core keeps reporting while no trip is running, so you can check on your boat from the app. About once a minute it records:

• battery voltage and current;
• tank levels;
• the boat's position;
• on/off states your boat's network reports;
• whether incoming AC power (shore or generator) is good, with its voltage and current.

It uploads them every few minutes. This is part of how a paired Core works and is on for every paired Core.

• Who can see it. Only the account the Core is paired to, and any assistant that account connects (see “Assistants you connect”). If the Core changes owners, data recorded before the new pairing is never shown to the new owner.
• How long we keep it. Readings recorded while no trip is running, including the latest ones and the boat's last reported position, are deleted automatically after 30 days.
• Position. While you're away, the app shows only the boat's latest position, not a track of its movements.
• How to stop it. Unpair or power off the Core. Readings already recorded are deleted on the same 30-day schedule.

This is not a security or alarm system. NavLog does not watch these readings for you or send alerts. They may be late or missing when the Core has no power or no internet.

Voice transcripts & AI processing

If you use voice log capture, your spoken audio is transcribed and the text is sent to an AI service to draft a structured log entry. We use this only to produce the draft you review before saving. Spoken content is kept distinct from device-measured data so you can tell them apart. Do not dictate sensitive information you would not want processed by a third-party AI provider.

Documents and email you give NavLog

You can give NavLog your boat's paperwork: files you upload, email you forward to your NavLog address (one address for all your boats), and — if you connect it — mail from your Gmail account. NavLog stores these with the boat they're about and reads them with an AI service to file them, record the maintenance an invoice or service report covers, note expiry dates, and answer your questions about your boats. Everything NavLog does with them is logged and can be undone.

• Connecting Gmail is optional and read-only. NavLog asks Google for permission to read your mail. It never sends, deletes, or changes your mail, and it never reads mail you've told it to leave alone.
• Only mail about your boats is kept. Depending on the setting you choose, NavLog either reads only mail you label “NavLog”, or goes through your mailbox to find mail about your boats, like an assistant you've put in charge of them. Going through the mailbox, it looks at the sender, subject line and one-line preview of each message from about the last two years (not spam, trash, chats, or Gmail's promotions and social tabs), and an AI service judges from those whether the message could be about your boats. Messages that could be are opened and read in full; the rest are not opened. Mail that mentions one of your boats' names, hull or registration numbers, or comes from companies and people you work on your boats with, is opened too. When a message turns out not to be about your boats, NavLog keeps only Google's message ID, so it doesn't look at it again, and deletes that ID after about 13 months.
• When you ask. If you ask NavLog about something in your mail (“when is the yard hauling her?”), it can search your connected Gmail for it — all of it, or only mail you label “NavLog” if that's the setting you chose — and read the messages it finds to answer you. Spam, trash and mail you've told it to leave alone are never searched. It keeps only messages that are about your boats; you'll see them in Settings › Connections › Email. Only NavLog's own chat searches your Gmail: assistants you connect to NavLog see only the mail it keeps.
• What NavLog picks out. From mail it keeps, NavLog notes visits and appointments, quotes, bills, orders and who owes a reply, so they show in Coming up. You can mark each one done or not needed.
• What is kept. For mail about your boats: the sender, subject, date, the text of the message, and its attachments, which are filed with the documents of the boat it's about. NavLog also keeps a list of the companies it has seen writing about your boats, and what you've told it to do with their mail.
• Mail from people you haven't approved. Mail from a sender NavLog doesn't know waits for you, with its attachments hidden, until you file or dismiss it. Mail left waiting is deleted after 30 days.

Google user data

NavLog's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Gmail data is used only to provide the features described above to you. It is not used for advertising, it is not sold, it is not used to train AI models, and people at NavLog do not read it except with your permission, for security, or where the law requires. It is shared with the service providers that run these features (our database host and our AI provider), which process it on our behalf. If you authorize a connected assistant, NavLog can also return boat-related mail and filed attachments in response to your requests, as described below. You can disconnect Gmail at any time in Settings › Connections › Email (Account › Email in the app), or remove NavLog's access in your Google Account. How we keep it safe is described under “How we protect your data”.

Assistants you connect

Connecting an assistant such as ChatGPT or Claude is optional. When you authorize a connection, that assistant can request information from your NavLog account. Responses can include boat and equipment details, crew and vendor contacts, maintenance schedules and service history, recent activity in NavLog, documents and temporary document download links, boat-related mail and what NavLog extracts from it (such as upcoming appointments, quotes, bills and amounts owed, and parts on order), trips, and recorded telemetry, including your boat’s latest position and readings. Answers from NavLog’s own assistant can also draw on notes it keeps about you and your boats, the address of a connected Gmail account, and the name and status of a paired NavLog Core. Available information depends on your account’s records and the request.

You choose what each connection may do: look things up (always), make changes, remove things, and search your Gmail. With changes, an assistant can record completed work and hour readings, add or change equipment, crew and maintenance tasks, change boat details, service records and documents, give NavLog documents to file, answer NavLog’s questions, save or forget the notes NavLog keeps about you and your boats, and pass your instructions to NavLog’s own assistant. With removing, it can take tasks, equipment, crew, service records, readings and documents off your record; removed items stay recoverable for 30 days. With Gmail, it can search and read the Gmail account connected to NavLog, within the limits you set there, and keep messages about your boats; it never sends or deletes mail. Changes appear in NavLog’s activity feed, where you can undo them.

NavLog stores connection and authorization records to authenticate this access, the instructions an assistant passes to NavLog’s own assistant together with the results, and the documents it sends. You can change what a connection may do or disconnect it in Settings › Connections › Assistants.

Information returned to an assistant is also handled under that provider’s terms and privacy practices. These can differ from the practices of the AI service NavLog uses internally. Revoking a connection stops future access; it does not remove information already returned or saved in an assistant conversation. To manage those copies, use the assistant provider’s controls.

Device identifiers & technical data

For paired hardware we store a device identifier derived at provisioning time, along with basic health and connectivity information (firmware version, uptime, last-seen time, sync backlog, and its latest position and readings) so we can tell whether a device is online and help you troubleshoot. We also process standard technical data such as IP address and request logs to operate and secure the service.

Cookies & local storage

NavLog uses only the cookies and browser storage it needs to keep you signed in — there are no advertising, analytics, or third-party tracking cookies.

• Session cookie — a first-party cookie that tells the dashboard whether you have an active sign-in session. It contains no personal data and expires with your session.
• Authentication tokens — our authentication provider stores your sign-in tokens in your browser's local storage so you stay signed in between visits. Signing out removes them.

Because these are strictly necessary for the service to function, we do not show a cookie consent banner. If we ever add analytics or other non-essential cookies, we will update this policy and ask for your consent first.

How we use your data

• To provide the logbook: storing, displaying, and exporting trips.
• To keep your boat's records: filing documents and email you give NavLog, and recording the maintenance they cover.
• To keep devices and accounts working and secure.
• To respond to support requests you send us.
• To diagnose problems and improve reliability during the beta.

Sharing & third parties

We rely on service providers to run NavLog — including a cloud database and authentication provider, an email provider that receives mail sent to your NavLog address, and AI providers (currently OpenAI and Anthropic) for voice transcription, drafting, reading documents and email, and answering you in NavLog's chat. They process data on our behalf under their own terms; our AI providers do not use it to train their models. If you connect an assistant, NavLog returns information to it at your request, as described under “Assistants you connect”; its provider handles that information under its own terms. We do not sell your personal data.

How we protect your data

We treat everything you keep in NavLog as sensitive: your boats' records and location history, and above all the email, documents and Google account access you give it. We protect it like this:

• Encrypted in transit. Data moving between the website, the app, a paired Core and our servers, and between our servers and Google or our service providers, travels over HTTPS (TLS). When a Core without internet passes its data through your phone over Bluetooth, that data is sealed end to end (AES-256-GCM). The website accepts only HTTPS connections.
• Encrypted at rest. Our database and file storage are hosted by Supabase, which encrypts stored data with AES-256.
• Your Gmail access is sealed. The token Google gives NavLog to read your Gmail is encrypted again by NavLog (AES-256-GCM) with a key kept only in our server functions' secret settings, never in the database or the apps, and it is bound to your account so it cannot be used for anyone else's. The website, the app and assistants you connect can never read it. Disconnecting Gmail deletes our copy of the token and asks Google to revoke it; you can also remove NavLog's access in your Google Account at any time.
• Other accounts can't reach your data. Every request is checked against the signed-in account before anything is read or changed, and the database itself refuses one account's rows to another. Files and email attachments are kept in private storage and opened only through links made for your account that expire after ten minutes.
• Least access. NavLog asks Google only to read your Gmail, never to send, change or delete it. Access to our production systems is limited to the people who run NavLog, and they do not read your email or documents except with your permission, for security, or where the law requires.
• Deletion. You can delete trips and documents yourself, and ask us to delete anything else or your whole account, as described under “Data retention” and “Your choices”.

No system is perfectly secure. If we learn of a security incident that affects your data, we will tell you as the law requires.

Data retention

Account, vessel and trip records are kept while your account is active. Trip telemetry is kept at full resolution until you delete the trip or your account. Readings your Core records while no trip is running are kept for 30 days. Deleting a trip deletes its telemetry, and deleting your account deletes all of it. Documents and email about your boat are kept until you delete them or your account; dismissing a message erases its text, and disconnecting Gmail stops NavLog reading it (what it already filed stays with the boat until you delete it). You can ask us to delete your data at any time.

Your choices — export & deletion

You can export trips from the web dashboard. You can delete individual trips yourself from the web dashboard or the app. Deleting a trip removes it and its telemetry from our servers; a trip recorded on a phone also keeps a copy on that phone. To request a full export or deletion of your account and associated data, email support@navlog.io from the address on your account. During the beta these requests are handled manually.

Beta status

NavLog is pre-release software. Data models, retention windows, and this policy may change, and we may occasionally need to contact beta testers directly about disruptive changes. Please don't rely on NavLog as your only record of a voyage during the beta.

Contact

Questions about privacy? Email support@navlog.io or visit our support page.