# Data processing addendum

> For customers who process their visitors' data under the GDPR, the UK GDPR or a similar law. This page forms part of the [Terms](/wake/docs/terms). Version `2026-11-10`.

## Roles

For the events your collector sends, **you are the controller** and **Wake (Agent Observatory) is the processor**. For your own account data (email, password hash, hostname, billing) Wake is the controller; see [Privacy](/wake/docs/privacy).

## What is processed

Per request that reaches your site from a client the collector forwards: a daily nickname (an HMAC of the client address computed on your side with your secret, folded again with the UTC day and your site id on our side), timestamp, method, page class, status code, operator family, identity tier, country code, the network operator's name, and evidence bits (for example "proof-of-work answered", "pointer looked scripted"). The user-agent string is read in transit to name the operator family and is not stored. No IP address, user-agent, URL, query string, body, cookie, referrer, prompt or page content is ever processed by Wake.

Because the nickname cannot be joined back to an address and changes every day, the events are at the edge of personal data. We still treat them as personal data under this addendum.

## Instructions

Wake processes the events only to produce the desk, the API, MCP, the alerts and the fixes for your site, and, in anonymised form (no site id, no nickname that outlives the day), to learn the weight of each piece of evidence across sites. Your documented instructions are these terms, the settings on your desk, and anything you ask by email.

## Sub-processors

| Who | What | Where |
|---|---|---|
| Cloudflare | Edge database (D1) and Worker that receive and store the events | EU and US data centres, Cloudflare's choice |
| Railway | Hosts the desk and its ledgers | US |
| Stripe | Payments; sees your billing email and card, never events | US, EU |
| Resend | Sends alert and account emails when configured | US |
| PostHog | Only if you connect your own PostHog project; events are forwarded to your project | Your choice |

We tell account holders by email 30 days before adding a sub-processor.

## Security

Events are coarsened before they leave your infrastructure. Keys are stored as SHA-256 hashes; the ingest key copy that lets you reopen the install kit is sealed with AES-GCM. Access to the production stores is limited to the operator. Account passwords are scrypt hashes. Ledgers are backed up daily; backups follow the same retention.

## Retention and deletion

Agent visits are kept 90 days, then deleted on the edge and on the desk. Removing a site or deleting the account deletes its events, labels and keys at once, including the edge rows. The export under Settings gives you the data in JSON at any time.

## Your rights and your visitors' rights

Wake cannot identify a visitor from what it holds, so a request from a visitor cannot be matched to a row; tell us anyway and we will confirm that in writing. We help you answer authority requests and carry out an impact assessment with the facts on this page.

## Transfers

Data may be processed in the United States by the sub-processors above under their standard contractual clauses. Tell us if you need EU-only storage; the edge database region can be pinned.

## Breach

We tell you by email without undue delay, and within 72 hours of learning of it, about any breach affecting your events, with what we know and what we are doing.

## Audit

Once a year, on request and at reasonable notice, we answer a written questionnaire and share this page's evidence (collector source, retention jobs, access list).

## Contact

The email address in the footer of [the site](/wake/).
