Privacy

Watchgoose processes account, monitoring, and billing data needed to operate the service, including account credentials, project metadata, check configuration, alert delivery history, and billing contact details.

What We Collect

Account data includes your email address, authentication/session metadata, security settings, timezone, optional signup attribution responses, notification preferences, project membership, and support correspondence. Monitoring data includes check names, descriptions, tags, schedules, ping URLs, ping timestamps, status changes, logs, and alert delivery records. If you configure integrations, we store the integration settings needed to send alerts.

We do not need payment card numbers to operate Watchgoose. Paddle handles checkout, taxes, invoices, receipts, and payment details as merchant of record. We store billing identifiers, plan state, entitlement snapshots, invoice metadata, and webhook/audit records needed to keep your subscription in sync.

On selected anonymous public pages of watchgoose.com, we use GoatCounter to understand aggregate page visits and referral sources. We do not load analytics on authenticated, account, tokenized-link, error, or legal pages, or on staging and preview hosts. Before a pageview is sent, we remove all query parameters except short, restricted campaign values (ref and utm_*) and reduce external referrers to their origin. We disable automatic click tracking and do not send account identifiers, email addresses, form contents, or monitoring data. Aggregate metrics may include the page path and title, campaign labels, external referral origin, display size, browser, operating system, and approximate country. GoatCounter does not set analytics cookies or store persistent identifiers or raw IP addresses.

How We Use Data

We use data to provide monitoring, alerting, account administration, billing administration, abuse prevention, security logging, support, and service improvement. We may use aggregated or de-identified operational information to understand reliability, capacity, and product usage, but not to identify a customer publicly without permission.

Legal Bases

For users in the UK, EEA, or other GDPR-style jurisdictions, our legal bases are: contract, where processing is needed to provide Watchgoose; legitimate interests, where we secure, maintain, improve, and protect the service; legal obligation, where billing, tax, accounting, or lawful request records must be kept; and consent, where applicable for optional communications or settings you choose.

Processors and Third Parties

We use service providers for hosting, networking, email delivery, human support email, billing through Paddle, error/operational diagnostics, privacy-preserving aggregate web analytics through GoatCounter, backups, and security operations. These providers may process data only as needed to provide their services to us. A current subprocessor list or more detailed procurement information can be requested at support@watchgoose.com.

Retention

We keep account and project data while your account is active. Monitoring logs are retained according to your plan limits and service configuration. Billing, invoice, tax, entitlement, and security/audit records may be kept longer where required for accounting, fraud prevention, dispute handling, or legal compliance. Backups are overwritten on a normal rotation and are used for disaster recovery, not as an active archive.

Watchgoose sends operational email for sign-in links, monitoring alerts, email reports, and account lifecycle notices. Paddle sends billing invoices and billing receipts.

Your Choices and Requests

You can change notification settings and remove projects or checks from the product. Privacy requests, including access, correction, export, deletion, objection, or restriction requests, can be sent to support@watchgoose.com.

The service is not directed to children under 16. Do not use Watchgoose for special-category personal data, payment card data, health records, or other regulated sensitive data unless we have agreed to that use in writing.