The evidence log

On Studio and Scale, SenseGap seals each finished day of a site's AI bot visits. Open it from Evidence log in the site's sidebar.

What happens each day

1. Once a day, at about 03:20 UTC, every day that has ended in the site's timezone is sealed.
2. Each visit becomes one line: time, bot, verdict, the evidence behind it, method, path, status, user agent, anonymized IP and country.
3. The day's lines get a SHA-256 hash. That hash, the previous day's hash and the day's details form a header, which is signed with our Ed25519 key.

Raw visits are deleted after 90 days. The sealed days stay, for as long as the site is in your account. The first time a site is sealed, we also seal the visits from the last 89 days that we still have.

What it proves

• The records haven't changed since the day was sealed. Change one byte and the check fails.
• No day was removed, added or swapped later. Each day holds the hash of the one before it.
• SenseGap signed it. Our public key is at sensegap.com/.well-known/sensegap-evidence-key.

What it doesn't prove

• That a verdict was right. Verified, unverified and spoofed are the results of our checks at the time of the visit. Each line says which check was used and what it found. See verified, unverified and spoofed.
• Anything before a day was sealed. Integrity starts on the day of sealing.
• That we couldn't rebuild the whole chain. We hold the signing key. Keep the bundles you download, or just the latest hash shown on the page: every later bundle must contain them unchanged.

Download and check a bundle

Pick a day or a range, up to 366 days, and download a zip. It holds the day files, the chain with every signature, our public keys and a README.

Anyone can check it offline with the open-source verifier, no account needed (Node 22.18 or newer):

git clone https://github.com/tudortotolici/sensegap
node sensegap/packages/evidence/src/cli.ts sensegap-evidence-example.com-2026-10-01-to-2026-10-28.zip

To check against the key on our site rather than the copy in the zip, download it and add --keys keys.json. To confirm a hash you saved earlier, add --expect and the hash.

The code that checks it: packages/evidence on GitHub.