Data processing agreement
Last updated · Edition 1
Draft 2026-11-01, pending owner review. Not legal advice; the owner reviews this before it is relied on.
This agreement applies when a customer sends telemetry containing personal data to Watchtower. The customer is the controller; Watchtower is the processor.
What is processed
Subject matter: storing, querying, alerting on and displaying the customer's telemetry (traces, logs, metrics, errors, profiles, uptime results, browser events, replays, audit events).
Duration: while the customer's projects exist, plus the retention windows in the privacy policy.
Data subjects and types: whatever the customer's software emits, such as end users' ids, IP-derived location and error context.
Our commitments
Process the data only to provide the service and on the customer's documented instructions (the API and console settings).
Authenticate every request and isolate tenants: tenant identity comes only from credentials; telemetry cannot claim another tenant. Inaccessible resources answer as if they do not exist.
Store secrets only as hashes. Encrypt data in transit.
Keep each project's data in its pinned data plane.
Support deletion requests through the deletion API (with second-administrator approval by default) and legal holds, and delete project data when a project is deleted.
Use only the subprocessors listed, and announce changes in the changelog.
Help the customer answer data-subject requests, and tell the customer without undue delay after learning of a personal-data breach.
To be completed by the owner
Security-measures annex, audit rights, international transfer mechanism, liability and signature details.