Cookie Policy

1.What this policy covers

This policy explains how MaritimeMentor uses cookies and similar browser storage technologies. It should be read alongside our Privacy Policy, which covers what we do with your data more broadly.

2.Cookies vs local storage

Cookies are small files that websites store in your browser, typically to remember login state or track usage. Local storage is a similar browser feature that lets a site keep data — like your chat history — on your own device.

Both are stored locally in your browser, and both can be cleared through your browser settings. The difference that matters here: cookies are sent to the server with each request, while local storage stays on your device unless the site explicitly sends it.

3.What we use today

MaritimeMentor uses a small number of cookies, all essential to running the service — none for advertising or profiling:

• Sign-in cookies — keep you signed in to your account (set by Supabase, our authentication provider; HttpOnly and Secure)
• "mm-anon-count" — a signed, HttpOnly cookie that counts the three free preview messages for signed-out visitors

We also use local storage for chat history while you're signed out ("maritime-mentor:conversations") — so conversations survive a page refresh until you sign in, at which point they move to your account and the local copy is cleared.

4.Third parties

Cookies are set by us and by Supabase (authentication). Email delivery runs through Resend. We do not embed advertising or social media trackers, and the service does not currently use an analytics provider. If that changes, this page will be updated before any such tool is switched on, together with any consent choice required by law.

5.Managing your preferences

You can clear or block cookies and local storage through your browser settings — clearing site data removes everything at once, including your sign-in. Blocking cookies signs you out and disables the free preview; blocking local storage stops chat history persisting between visits.

6.Changes to this policy

As features arrive — payments being the next likely one — we will update this page and, where required, ask for your consent first. The "last updated" date at the top always reflects the current version.