Last updated: 2026-11-18. This agreement is between you, the customer who signs up an organization in WatchLog Cloud, and WatchLog, which runs WatchLog Cloud. It is a plain-language draft: a lawyer is reviewing it, and the final version will replace this page before Cloud opens. Questions: [email protected].
Roles
For the personal data in your organization's monitoring data and settings, you are the controller and WatchLog is the processor: we process it only to provide WatchLog Cloud to you. For your own account (your email address, sign-in and billing), WatchLog is the controller, as the privacy policy describes.
What we process, and why
- Purpose: collecting, storing and showing the monitoring data your agents send, alerting on it, and keeping it for your plan's retention. Nothing else: we don't sell it, mine it or use it to train anything.
- The data: metrics, summaries of Kubernetes objects and Docker containers, events, network connections between services, and applications' metrics. They can contain personal data by accident: a host, pod, container or label named after a person, an IP address, an email address in an alert channel. Container log lines are streamed when you open them and never stored. The agents never read Secrets, ConfigMap data, environment variables or request payloads.
- Whose data: the members of your organization, and anyone whose data appears in the names, labels or addresses your systems report.
- How long: while your organization exists, within your plan's retention (3 days on Free, 30 on Pro).
Your instructions
The settings you choose in WatchLog Cloud are your instructions: what you install, what you connect, who you invite, where alerts go and when you delete. If we're ever asked to process your data in another way, we will tell you first, unless the law forbids it.
Confidentiality and staff access
Only WatchLog staff who run the service can reach your data, and only through a support session: read-only, at most an hour, with a recorded reason, announced by email to your Owners and listed in Settings › Security with the pages it opened.
Security
The measures in place today are on the security page: isolation between organizations enforced by the database, encrypted connections, secrets encrypted at rest, tokens stored as hashes, encrypted backups, two-factor sign-in, and the read-only support sessions. We don't hold certifications such as SOC 2 or ISO 27001.
Subprocessors
The services that process data for WatchLog Cloud are listed on the subprocessors page. We will update that page, and tell Owners by email, before a new subprocessor starts processing your data. (The notice period is to be set in the final version.)
Helping you with requests
An Owner can export the organization's configuration and metrics, and delete it, in Settings › Data. For a request from a person whose data you hold that the product can't answer, write to us and we will help.
Incidents
If a breach affects your data, we will tell your Owners by email without undue delay, with what we know and what we're doing about it.
When it ends
When you delete your organization, an Owner can undo it for 7 days; then its data and metrics are deleted. Encrypted backups expire within 30 days. We keep only a record that the deletion happened.
Where
Where WatchLog Cloud's servers and backups are hosted, and the transfers that involve, will be named here once the hosting and backup providers are confirmed.