Last updated: 2026-11-18. This policy covers the website at watchlog.io and WatchLog Cloud at cloud.watchlog.io, run by WatchLog.
The website
- Server logs. Like any web server, ours records each request: your IP address, the page, the time, the browser's user agent and the referring page. We use these logs only to keep the site running and secure, and delete them after 14 days.
- Cloudflare. Requests to watchlog.io pass through Cloudflare, which delivers the site and protects it from attacks. Cloudflare processes your IP address for that purpose; see Cloudflare's privacy policy.
- Analytics, only if you accept. Fonts, images and the site's own script are served from watchlog.io itself. Until you accept analytics, loading a page makes no requests to anyone else; if you accept, the pages also load Microsoft Clarity, described below.
Analytics
With your consent, we use Microsoft Clarity to understand how the site is used (which pages people read, where they click, how far they scroll, what doesn't work on a phone) so we can improve it. We don't use it for advertising.
Only if you accept. A bar at the bottom of the page asks once. Until you choose Accept, and after you choose Decline, Clarity doesn't load: nothing is sent to Microsoft and it sets no cookies.
What Clarity collects once you accept: the pages you view and the page that sent you to us; clicks, taps, scrolling, mouse movement, text selection and window resizing; how the page looked as you used it (its layout and text), which lets us replay a visit as a recording and build heatmaps; page performance and script errors; your device type, operating system, browser, screen size and language; and your approximate location (country or region), which Clarity derives from your IP address. See what Clarity collects.
What it doesn't see: the waitlist form and everything typed into it, your email address included, are masked: recordings show placeholders instead. Clarity never runs on the waitlist pages that the links in our emails lead to, nor on any address that carries a link token.
Cookies: with your consent Clarity sets two cookies on watchlog.io: _clck, which keeps a random Clarity user ID for a year, and _clsk, which links the pages of one visit into one session for a day. Microsoft's own servers (clarity.ms and bing.com) can also set their cookies, such as CLID, MUID, MR, SM and ANONCHK, which Microsoft uses to recognise browsers across sites that use its services, unless your browser blocks third-party cookies (Safari and Firefox do by default). See Clarity's cookie list. We tell Clarity that we don't consent to ad storage.
Your choice: Analytics settings, at the bottom of every page, opens the bar again. Decline after an Accept and Clarity deletes its cookies on watchlog.io and stops; later pages don't load it. We remember your answer in your browser's local storage (watchlog-analytics-consent), not in a cookie. Your browser can do more: blocking third-party cookies in its settings keeps Microsoft's cookies away even after an Accept, a content blocker that blocks clarity.ms stops Clarity from loading at all, and you can opt out of Microsoft's tracking through the Digital Advertising Alliance.
Microsoft: Clarity is a Microsoft service. The data goes to Microsoft and is stored in Microsoft's Azure cloud. Microsoft keeps recordings for 30 days (a random sample, and recordings we mark as favourites, for up to 9 months) and uses the data as described in the Microsoft Privacy Statement and Clarity's terms. We see the recordings, heatmaps and aggregate reports in Clarity's dashboard; we don't receive your IP address.
The live demo
The live demo at demo.watchlog.io is a read-only WatchLog dashboard on a sample cluster. The demo itself doesn't load Clarity or any other analytics script, and its only cookie is the session cookie that lets you in.
What its server logs: for each page and request the demo answers: the time, your IP address, the country Cloudflare derives from it, the address you opened and the answer's status, the page that sent you there, and your browser's user-agent. Files such as scripts, styles and images aren't logged.
What we keep: we don't keep these lines. Our server groups them into visits: when the visit began and ended, your IP address, the country, the kind of device and browser (taken from the user-agent, which isn't stored), where you came from (our site, another site, or directly), which demo pages you opened and in what order, and which changes you tried that the read-only demo refused. Bots and our own monitoring aren't counted.
AI assistants (MCP): if you connect an AI assistant to the demo with its public token, its requests are logged the same way, as a visit of its own. We also keep which tool it called (for example get_problems) and which kind of client it was (for example Claude Code). Your questions, the tools' arguments and their answers aren't logged.
Why: to see whether the demo works for people and what they look at, so we can improve it and WatchLog.
How long: your full IP address is kept for 30 days, then shortened (IPv4 to its first three numbers, /24; IPv6 to its /48), so it no longer points to you. The shortened visits are kept to compare the demo's use over time.
Where: on our own server, readable only by the WatchLog team through the admin panel (password and two-factor authentication). None of it is sent to anyone else. Requests to the demo pass through Cloudflare like the rest of watchlog.io.
To ask for your demo visits or their deletion, write to [email protected] with your IP address and roughly when you visited.
The Cloud waitlist
When you join the waitlist we store:
- your email address;
- when you signed up, and when you confirmed it;
- where you came from: the
utm_source,utm_mediumandutm_campaignof the page you signed up on, and the address of the page that linked to us, without its query string; - a salted hash of your IP address, never the address itself. It limits how often one visitor can sign up and helps us spot abuse;
- hashes of the confirmation and unsubscribe links in our email.
Why: to send you one email to confirm your address now, and one when WatchLog Cloud opens. Nothing else: no newsletter, and we never sell or share your address. The source tells us which posts brought people to the waitlist.
Where: in a database on our own server, readable only by the WatchLog team through an admin panel behind a password and two-factor authentication. Email goes out through our own mail server.
How long: an address that isn't confirmed is deleted after 30 days. A confirmed one stays until you unsubscribe or ask us to delete it. Nightly backups are kept for 30 days, so a deleted address is gone from them within 30 days too.
Unsubscribe or delete: every email has an unsubscribe link, which removes your entry at once. To ask for your data or its deletion without the link, write to [email protected].
You agree to this when you confirm your address, and you can withdraw at any time by unsubscribing.
WatchLog Cloud
WatchLog Cloud, at cloud.watchlog.io, runs WatchLog for you. Two kinds of data are involved: your account, which we hold to run the service for you, and the monitoring data your agents send, which your organization decides on and we process on its behalf, as the data processing agreement describes.
Your account:
- your email address, and the id of your GitHub or Google account if you sign up or sign in with one;
- your password as an argon2id hash (never the password itself); when you choose a password, only the first 5 characters of its SHA-1 hash are sent to Have I Been Pwned to check it against known breaches;
- if you turn on two-factor sign-in, its secret, encrypted, and your recovery codes as hashes;
- your sessions, each with its IP address and browser user agent, so you can see and end them in Settings › Security;
- the organizations you belong to, your role in each, and their audit events (who changed what, and when).
Your monitoring data: what your agents send: metrics, summaries of Kubernetes objects or Docker containers (names, labels, images and states), events, the network connections between your services (addresses and ports, never the traffic itself), and the metrics of the applications you connect. Container log lines are streamed to your browser when you open them, redacted first, and never stored. The agents never read Secrets, ConfigMap data, environment variables or request payloads: the security page lists everything they can access.
What you set up: clusters, alert rules, channels (a channel's secrets, such as a bot token or a Slack URL, are encrypted), the people you invite, applications and API tokens (kept as hashes).
How the product is used: to see where signing up and getting started go wrong, Cloud records a few events in its own database, such as "signed up", "first data received" or "alert channel connected", with the organization, the user and the time. No third-party analytics run on cloud.watchlog.io, and nothing is recorded during a staff support session.
Cookies on cloud.watchlog.io: only the ones signing in needs, all HttpOnly and Secure: the session cookie wl_session; wl_mfa (10 minutes) during two-factor sign-in; wl_oauth (10 minutes) during GitHub or Google sign-in; and wl_support, which only WatchLog staff get in a support session. No analytics or advertising cookies. On sign-up, password reset and "send a new link", Cloudflare Turnstile checks that you are a person; Cloudflare processes your IP address and browser signals for that, as its privacy policy describes.
Email: account emails (verifying your address, password resets) and service notices (a staff support session started, a plan limit reached, an organization about to be deleted or suspended, a payment problem, and 14 days' notice before billing starts) go to the people they concern. In their first 30 days, Owners also get a few emails to help them get started (welcome, help installing, the first alert explained, tips, close to a Free limit): at most one a day, each with a one-click unsubscribe link that works at once.
Support sessions: when you ask us for help, a WatchLog staff member may open a support session on your organization: read-only, at most an hour, with a recorded reason. Its Owners get an email when one starts and can see each one in Settings › Security: who, when, why and which pages it opened.
Payments: once billing starts, payments go through Stripe: you enter card details on Stripe's own pages, and they never reach our servers. We keep the Stripe customer and subscription ids for your organization.
How long:
- monitoring data: 3 days on Cloud Free, 30 days on Cloud Pro; after a change to a smaller plan, older data stays until its earlier retention runs out;
- your account and your organization: until you delete them;
- a deleted organization: an Owner can undo the deletion for 7 days; then its data, its metrics and the accounts that belong to no other organization are deleted, and we keep a record that the deletion happened (the organization's name and id, when and by whom it was asked, how many clusters and series it had);
- a Free organization without data for 30 days gets an email, and is suspended 7 days later if still no data arrives; nothing is deleted then: sign in to reactivate, export or delete it;
- backups: encrypted copies of the database are kept for 30 days and metric snapshots for 7, so deleted data leaves the backups within 30 days.
Who else processes it: the services on the subprocessors page, and nobody else. We never sell your data.
Your rights in Cloud: an Owner can export the organization's configuration and metrics, and delete the organization, in Settings › Data. You can manage your sign-in methods, two-factor sign-in and sessions in Settings › Security. For anything else, write to [email protected].
The WatchLog software
When you self-host WatchLog, it sends nothing to us: no telemetry and no usage data. Agents send metrics, summaries of Kubernetes objects or Docker containers, and events only to your own WatchLog server. They never read Secrets, ConfigMap data, environment variables or request payloads. The security page lists everything the agent can access.
WatchLog Cloud runs the same software for you; what it holds is described above, under WatchLog Cloud.
Your rights
You can ask us what we hold about you (server logs, your waitlist entry if you joined, and your Cloud account), and ask us to correct or delete it. For the analytics, Decline stops Clarity at once. Clarity's data is held by Microsoft: write to us and we will help, or contact Microsoft as its privacy statement describes. Write to [email protected]. If you are in the EU or the UK, you can also complain to your data protection authority.
Changes
When this policy changes, the date at the top changes too.