What ZeroLog.ai does with your data.

This page describes what the service holds, what it does not, and the cookies this website can set. It is written against what the software does today. The full privacy notice and the sub-processor list are published at launch.

Very little, and never the content.

Your account exists so you can sign in and so we can count what you spend. Nothing in it records what you asked or what came back — not in a log line, not in a table, not for a moment while the answer streams.

What we hold

Your email address and the password you set.
An active sign-in session.
A usage counter: tokens spent, requests made.
A 90-day log of sign-ins, sign-outs and password resets.

What we never hold

What you asked, in any form.
What the model answered.
Any record linking your account to either — not even briefly.
Your files. A PDF you attach is read on your device and stays there.

Your conversations are stored on your own device.

They live in your browser, on the device you used. There is no permanent server-side copy, which also means that clearing your browsing data for this site deletes your history. You can export everything to a file at any time.

Content cannot get into our server logs.

We keep operational logs, and they are built so that content cannot reach them. Every log line goes through a single seam that drops content fields, and the tests fail if content appears in one. A request is correlated by a random identifier that is created for that request and never stored beside your account.

ZeroLog.ai sets no cookies of its own.

Your sign-in is held in your browser's own storage, not in a cookie. The only cookies this website can set belong to Microsoft Clarity, which shows us how people move through it. While we are testing, that includes the app itself: Clarity records what you do there, never what you write. None of them are set unless you accept.

Clarity does not act on a Do Not Track signal, and we would rather say so than let you assume otherwise. It does act on Global Privacy Control. Microsoft publishes its own list of the cookies Clarity uses, and we link to it rather than paraphrase it on Microsoft's behalf.

In the app, the masking is written into the page rather than set as a preference we could change later. Every part of the app carries an instruction telling Clarity to mask it, and masked content is never sent to Microsoft.

What Clarity records

Which pages you open, and in what order.
Where you click and scroll, and how far down a page you get.
A replay of that activity, which we can view for up to 30 days.
Not the text on these public pages: masking is set to strict, so text is redacted.
Not your messages, their titles, or the names of files you attach. The app is masked in full.
Nothing at all from the sign-in screens. It does not run there.

The cookies it sets

_clck, which holds a Clarity user id for this website.
_clsk, which joins several page views into one recording.
Cookies on Microsoft's own domains, which Microsoft names in its list.
No advertising cookie: we deny advertising storage, which is what governs it.

Microsoft's list of Clarity cookies

Your choice on this device.

Still to be published.

The parts of a privacy notice that are legal commitments rather than descriptions of software are written by the operator of the service and published at launch. They are not drafted on this page, and their absence here is not a claim about them.

Who operates ZeroLog.ai, and how to reach us.
The legal basis for each thing we hold.
Your rights, and how to exercise them.
How long each record is kept.
The sub-processor list.
Which parts of the service run in which country.

Sketch note — this page is not the privacy notice. Nothing above commits the operator to a legal position, and the sections listed here are unwritten.