Privacy policy

Last updated · Edition 1

Draft 2026-11-01, pending owner review. Not legal advice; the owner reviews this before it is relied on.

This policy describes what Watchtower does with personal data. It covers two roles. For your account, Watchtower is the controller. For telemetry that you send to a project, the customer organization is the controller and Watchtower is its processor under the data processing agreement.

Account data

  • Name, email address and sign-in identifiers, held by Atlas (our account provider) and mirrored in Watchtower as your user record.

  • Organization memberships, roles, API key and token hashes, sessions (a hashed session token and its timestamps), and an audit log of actions taken in your organization. Secrets are stored only as SHA-256 hashes and never written to logs or audit events.

  • Support messages if you use the chat, and referral information if you use the referral program.

Customer telemetry (as processor)

Customers choose what they send. It can include traces, logs, metrics, error reports, profiles, uptime results and, if a project turns it on, browser events and session replays. Telemetry can contain personal data if the customer's software puts it there, for example user ids or IP-derived country.

  • Browser events and replays: replay is off until a project admin enables it and masks all text and inputs by default; password, card and one-time-code inputs are never recorded; user ids are reduced to a salted hash in the browser; cookies, Authorization headers and request or response bodies are not collected.

  • Every project is pinned to one data plane at creation, and its data stays there.

  • Retention is set per project (defaults: logs 30 days, metrics 90 days) and enforced by database expiry; replay objects are removed on expiry or when a project or session is deleted. Backups and message queues follow their own, shorter retention.

  • Customers can request deletion of telemetry matching a filter or a user; a second administrator approves it by default.

Who processes data for us

Processor

What for

Data

Atlas

Accounts and sign-in

Account data

Cookie Munch

Cookie consent and data-rights requests

Consent choices, rights requests and the email used to make them

Forumulate

Docs, community, blog and changelog

Reader accounts and posts if you sign in to the community

Chatly

Support chat and its knowledge base

Chat messages and the identity you are signed in with

Referalli

Referral program

Referral codes and sign-ups attributed to them

Seolyticize

Cookieless page counts of the landing page

Page address and coarse, non-identifying visit counts

OVH

Hosting of the servers that run Watchtower

All data stored by the service

The full list is on the subprocessors page.

Cookies and browser storage

See the cookie policy.

Your rights

Depending on where you live you may access, correct, export or delete your personal data, restrict or object to its processing. Use the data-rights form: https://cookiemunch.net/r/${COOKIEMUNCH_CBID}. We confirm your email address before acting. Erasing an account removes your sign-in and anonymizes your user record; if you are the only administrator of an organization that has other members, the request is rejected until another administrator exists, so that the team is not orphaned. For personal data inside a customer's telemetry, contact that customer; we assist them.

Changes

Changes are announced in the changelog.

All documents