Privacy

What this notice covers

This notice describes argonav.ai, the website you are reading. It does not describe Argo or Itô, the products, which run under separate agreements with the firms that use them.

What you send us

The contact form asks for an email address and accepts a name, an organization and a message. Only the address is required. What you send lands in our own database, where our team reads it, and a copy reaches us by email when email delivery is configured.

The newsletter form asks for an email address and nothing else. The endpoint behind it also accepts a name and a list of topics, and no part of this site sends them.

A response on an article asks for a name and the response itself, and no email address. Both are published on that article, exactly as typed, once we approve them. Treat a response as public writing, because that is what it becomes.

What we record while you read

Articles carry a beacon. It records which article, how far down it you reached at 25, 50, 75 and 100 percent, how long you stayed, and which newsletter issue sent you when you arrive from one. It also records an identifier built from your IP address: we store a salted hash rather than the address, and the date sits inside the hash, so the identifier changes at midnight UTC and does not follow a reader across days. We do not call that anonymous. A hash made from an address is still made from it. The beacon does not run at all if your browser sends Do Not Track.

Every public form is rate limited, which stores a salted hash of your address with no date inside it.

When we send you the newsletter, our delivery provider reports whether the message was opened and which links were clicked, and we keep that against your subscription.

Signing in to the operator area, which is for our own team, writes an audit record carrying that email address and that IP address as given. No visitor has an account on this site.

What we do not collect

We do not store your browser or device string, and we do not store the page that sent you. This site sets no cookie for a visitor who never signs in, and the only thing it keeps in your browser is a single session key that stops the opening animation from playing twice.

Our typefaces are served from this domain, so no font network sees you.

No analytics service is running on this site. The code carries an integration that is switched off, verified against the live site rather than assumed. If we switch it on, this notice will name it.

Who else receives it

Vercel serves this site, so every request reaches them. Supabase holds the database and the files. Resend delivers email when we send you any.

Cloudflare Turnstile is wired into the forms and is not switched on. If we switch it on, your browser will contact Cloudflare when you use a form.

An article body can carry an image hosted somewhere else, and loading the article loads that image, which tells its host your address. We publish those bodies ourselves.

We do not sell personal information and we carry no advertising.

How long we keep it

Plainly: there is no retention schedule. The only data that expires on its own is the rate limiting table, where rows older than a day are removed opportunistically. Everything else stays until a person removes it.

What you can ask for

You can ask what we hold about you, ask us to correct it, and ask us to remove it. There is no self service for any of that. A person handles each request by hand.

The newsletter works differently on purpose. Unsubscribing takes effect immediately from the link in any issue, and we keep a row recording that you left, so a later import cannot add you back. Ask and that row goes too.

A published response can be unpublished on request.

How it is protected

Every table carries row level security. The key this site ships to your browser can write a submission and cannot read one back, which is the property that matters, because that key is public by design.

Traffic is encrypted in transit. We hold no security certification and this notice claims none.

How to reach us

Use the contact form. It is the route we can follow end to end.

The date at the top of this page moves when the text does. This version was written on 15 September 2026 from the code running that day.