Security & data
Your code is read in memory, in Denmark, and never kept.
Watchdog surveys your code automatically, and no person reads it. At every survey, your code is copied into memory (RAM), never onto a disk, and analysed there. When the survey ends, Watchdog keeps the report and deletes the copy, even if the survey failed.
No third-party AI ever sees your code, and nothing runs on someone else's cloud. Every claim on this page is written out in full, with its limits, in the security statement.
The short version
Four answers, before the paperwork.
Only the report stays
Watchdog gives each survey its own separate copy of your code, and when the survey ends, only the report and its measurements remain. Watchdog never uses your code to train an AI model, its own or anyone else's.
No third-party AI, no cloud
Watchdog runs its language model on its own servers in Denmark, along with the analysis, the database and the stored reports. No cloud provider is involved in any of it, and neither is any outside service for visitor statistics, error reports or content delivery (analytics, error tracking, CDN).
Read access only
Whichever host your code is on, whether GitHub, GitLab, Bitbucket or Azure DevOps, Watchdog asks only for read access to the code. It makes no commits, branches or edits, and the update messages your code host sends it (webhooks) carry no code. The one exception is optional and off until you turn it on: on GitHub, Watchdog can keep a single issue up to date that lists the open findings.
Publication is yours to choose
On every plan, the free one included, every report is private by default; publishing is an explicit opt-in. Once you publish, the public report always shows your latest survey, so anyone reading it sees the current state of your code.
One outside company handles your data, and only for payments
That company is Stripe Payments Europe, Limited, in Ireland, and it is the only name on Watchdog's list of outside processors (subprocessors). Stripe processes payments, so on the free plan no outside company handles your data at all. Everything else, including sign-in, runs on Watchdog's own servers.
Your code host is not on the list. GitHub, GitLab, Bitbucket, Azure DevOps or wherever else you keep your code is your own supplier, under your own agreement. Connecting a repository gives Watchdog read access to code you had already placed there. The security statement has the full table of what Stripe receives, why and where, and the legally binding version is annex B of the data processing agreement (DPA).
Leaving is self-service
You can leave without asking us.
Close the account yourself
Close your account from your settings, with no ticket and no email to anyone. For 14 days you can change your mind, and after that your personal details and your sign-in are erased for good.
Disconnect a single repository
Disconnect a repository and Watchdog stops surveying it for you straight away. Its reports and history are kept, so if you connect it again later, you still have its full history.
The documents themselves
Everything above, written out with its limits.
Security and data statement
The full account for a security review: what access Watchdog asks for, what happens to your code during a survey, where data is stored and how it is backed up, who can see a report, which outside company is involved, and which certifications Watchdog does not hold yet. Read the statement →
Data Processing Agreement
The contract for how Watchdog handles personal data on your behalf (GDPR Article 28): who is responsible for what, how long data is kept and how it is deleted, how it is protected, which outside company is involved, how you are told of a breach, your right to audit, and transfers outside the EU. Read the DPA →
Terms of Service
What the service does, what happens to your code, how the plans and their allowance of scanned code work, when a report is published, and how to close your account. Read the terms →
Try Watchdog on one repository, with read access only.
The first survey of every repository is free, with nothing held back, and no card is needed. By the time you open the report, Watchdog has already deleted its copy of your code.