Privacy

What CountWatch stores, for how long, and your rights.

Draft, not yet in force. This text waits for legal review. Text in [brackets] is still to be filled in.

Last updated: [date of publication]

Who we are

CountWatch is run by [legal name of the company or person, address]. Questions and requests: hello@countwatch.com.

What CountWatch stores

CountWatch watches numbers you send it and tells you when they spike, drop or stop. To do that it stores:

• Your account: its name, its plan, when it was created, and the e-mail addresses of its owner and members.
• Your sign-in: the e-mail address you sign in with. The addresses a sign-in link went to are kept for 24 hours, to limit repeat sends.
• Agents you connect: the agent's name and its access, until you disconnect it in Settings.
• API keys and the webhook URLs you make for sending counts: only as one-way hashes. We cannot read one after we show it to you once.
• The counts you send: metric names, labels and counts per 5 minutes, and for 24–48 hours the point ids and batch ids you attach (to ignore repeats).
• Webhook URL hits: the last 50 hits of your webhook URLs, for up to 7 days: the time, the metric, its labels and the outcome. Never the caller's address, headers or body.
• What CountWatch makes from them: the rules for each watch, alerts, the feedback and notes (up to 200 characters) you give on an alert, and events you report (such as a deployment).
• Where alerts go: webhook URLs and their signing secrets, Slack webhook URLs, PagerDuty routing keys, and a record of each delivery (time, status code).

Please do not put personal data in metric names or labels. CountWatch is built for counts such as orders or sign-ups, not for data about people. Send signups=1, not an e-mail address.

What CountWatch does not store

• We do not log request bodies, keys, secrets or webhook URLs.
• We do not store IP addresses. To limit how many accounts one network can create in a day, we store a keyed hash of the network (an IPv4 address or an IPv6 /64) under a random key that changes every day; keys and counts are deleted after 2 days, after which a hash can no longer be linked to an address. Cloudflare's rate limiter also uses your network address for a few seconds to stop floods; we keep no copy.
• No trackers, no advertising, and we do not sell or share your data. No AI model reads your data.

Cookies and your browser

CountWatch sets two cookies, both needed to sign in, so we do not ask for consent:

• a session cookie for the dashboard, for 30 days or until you sign out;
• a sign-in step cookie, for 10 minutes while you sign in.

The home page keeps your best score in its small game in your browser's storage; it never leaves your browser.

On our public pages (not the dashboard or sign-in), Cloudflare Web Analytics counts page views. It sets no cookies, stores nothing in your browser and builds no profile of you.

Logs and metrics

Our logs contain only these fields: a request id, the route, method, status, duration, your account id, watch ids and counts of points accepted. They are kept for 7 days. Per-request metrics (route, method, outcome, status, duration, no account data) are kept by Cloudflare Workers Analytics Engine for 3 months.

Why we process it (legal basis)

• To run the service you asked for (GDPR Art. 6(1)(b)): your account, the counts you send, alerts and deliveries.
• Our legitimate interest in keeping the service safe and available (Art. 6(1)(f)): rate limits, the per-network account limit above, and logs.
• Your consent (Art. 6(1)(a)) for alert e-mails, which you turn on and can turn off in every e-mail.

Where your data is

CountWatch runs on Cloudflare. Your account record and every account store are created in Cloudflare's EU jurisdiction, which keeps that data stored and processed in the European Union. Cloudflare runs our code in data centres worldwide to answer requests quickly, and Cloudflare's own billing logs, which contain internal object ids but not your counts, may be outside the EU. Cloudflare, Inc. is a US company; transfers to it rely on its data processing addendum ([verify: the EU-US Data Privacy Framework and the Standard Contractual Clauses it names]).

How long we keep it

• Counts, alerts, notifications and delivery records: 90 days.
• Your e-mail address: as long as you own the account or are a member of it.
• When the owner erases the account in Settings, all its data is deleted at once. Cloudflare's point-in-time recovery keeps a restorable copy for up to 30 more days; we do not restore erased accounts.

Who processes your data for us

• Cloudflare, Inc.: computing, storage, logs and e-mail sending (sub-processor).
• Slack and PagerDuty receive alert content only when you add them as a destination; your agreement with them applies to what they receive.

E-mail

We e-mail only addresses you give us: the sign-in links you ask for, a confirmation before alert e-mails start and, if you turn them on, alert e-mails (every one has a link to turn them off). E-mail comes from alerts@mail.countwatch.com; reply to reach us.

Your rights

You can read your data in the dashboard and through the API, export it in Settings, change it, and erase your account. If you are in the EU or UK you also have the rights the GDPR gives you, including to complain to your data protection authority. Write to hello@countwatch.com; we answer within one month.

Children

CountWatch is a tool for businesses and developers and is not meant for children under 16.

Changes

We announce changes to this notice on this page and, for important changes, by e-mail at least 14 days before they apply.