# Privacy

> Wake is built so that the data it holds cannot identify a person or a machine. This page says who we are, what is kept, what is never kept, and what you can ask. Version `2026-11-10`.

## Who we are

Wake is operated by Agent Observatory, the research project behind the public sensor at agent-observatory-sensor.nolimit-observatory.workers.dev. Contact: the email address in the footer of [the site](/wake/). For sites that process visitor data under the GDPR, the [Data processing addendum](/wake/docs/dpa) describes our role as processor.

## Kept, per site

- Coarse events from your collector: timestamp, method, page class, status code, operator family (a label such as `anthropic`, `openai`, `curl`), identity tier, country code, the network operator name where the edge knows it (an ASN organisation such as `Amazon.com, Inc.`, never an address), and a **daily nickname**.
- The nickname is an HMAC computed from an opaque hint that your collector derives from the client address with **your** secret, folded again with the UTC day and your site id on our side. The same machine tomorrow is a new nickname. Nothing in Wake can be joined back to an address.
- Your email with the hostname, the SHA-256 hashes of your keys, an AES-GCM-sealed copy of the ingest key so the install kit can be reopened, the verification method and time, and your listing plan.

## Never kept

Raw IP addresses, user-agent strings (read in transit to label the operator family, then discarded), query strings, request bodies, prompts, outputs, page content, cookies, referrers, tool arguments, fingerprints, precise location.

## About you, the account holder

Your email, a password hash (scrypt) or your Google account id with its verified email, the hostnames on the account, when you accepted the terms, and, once you subscribe, Stripe's customer and subscription ids. Stripe holds the card; we never see it. We email you about the desk: alerts you set, the end of the trial, invoices, a password reset you asked for, and changes to these pages. No marketing list, no third-party pixels on the desk.

## Retention

Agent visits are kept **90 days** on the edge and on the desk, then deleted. Per-site event files keep the newest records (compaction). Revoking an API key takes effect immediately. Rotating the collector keys restarts nicknames. Removing a site or deleting the account deletes its visits, labels and keys at once, including the rows on the edge. Daily backups of the desk ledgers follow the same 90 days.

## Sub-processors

Cloudflare (edge database and Worker), Railway (the desk), Stripe (payments), Resend (email when configured), and PostHog only if you connect your own project. The [DPA](/wake/docs/dpa) lists what each one sees.

## Your rights

Export the desk as JSON from Settings at any time. Delete the account from Settings; it is immediate and complete. Ask us by email to correct your account data or to send you what we hold about you, and we answer within 30 days. If you are in the EU or UK you can also complain to your data protection authority. A visitor to your site cannot be identified from what Wake holds, so a visitor's request cannot be matched to a row; we confirm that in writing when asked.

## What the API and MCP expose

Exactly what the desk shows: the rows above, aggregated. There is no endpoint that returns anything finer than a page class and a status code, so no key can leak more than that.

## Learning across sites

Wake learns the weight of each piece of evidence from sessions across every site, nightly. The training rows are evidence bits (a declared operator, a missing browser bundle, a burst, a scripted pointer), the address block operator's name, and a label: a verified signature, a page that reported a person, or a site owner's confirmation. No row carries an address, a user agent, a nickname that outlives the day, or the site it came from. The learned weights never flip the direction of a piece of evidence and replace the hand-set ones only when they predict held-out sessions at least as well.
