Terms of Service

Last updated 27 September 2026 · Version 2026-09-27 · Operated by Canine Development (registered company, Denmark). By signing in you accept these terms.

Terms. Each heading is a permanent link, so a clause can be cited in a contract or a review.

• 1. What Watchdog does
• 2. Your code
• 3. Plans, LoC-scan budgets and billing
• 3.1 Fair use
• 3.2 Community plans: what they ask in return
• 4. The public open-source corpus
• 5. Your reports: publication is opt-in
• 6. Scheduling
• 7. Acceptable use
• 8. No warranty; limitation of liability
• 9. Closing your account
• 10. Changes
• 11. Contact

Watchdog performs a deep, periodic architecture-and-health audit of the repositories you connect and produces a report at the cadence you choose. It is a governance and planning tool: it runs on a schedule (not on every commit) and gives you an updated report for retrospectives and sprint planning, even when nothing changed.

For every scan we make a temporary, isolated clone of your repository, run the analysis, store the report, and delete the working copy. We do not retain your source beyond serving the report, and we do not train models on your code. You must have the right to connect each repository you connect.

Detector quality assurance: we may occasionally run additional internal analyses, to confirm a suspected detection gap or verify a fix. These are handled like any scan, produce no report, are never published, and never count toward your LoC-scan budget or your bill.

Watchdog is offered as four plans, each at one fixed price: Community free, Community unlimited and Professional, billed monthly, and Enterprise, a self-hosted licence billed yearly. Every plan may be used for commercial work (see §3.2 for what "Community" means). Each plan covers an allowance of LoC-scans: codebase size (production lines of code, measured by the first free scan) × scan frequency. We meter lines scanned, not repositories or seats; every active repository (public or private) counts. The pricing page is authoritative and may change.

Each plan's allowance is stated on the pricing page as LoC-scans a month (Enterprise: a year). A LoC-scan is one line of code read in one scan, so your monthly total is the size of your code multiplied by how often it is scanned: a 250,000-line codebase scanned every week uses 1,000,000 LoC-scans a month. The first full report on any newly connected repository is free on every plan and does not count.

Community free stops at its allowance: a scan that would exceed it does not run until the month resets. On Community unlimited and Professional, scans keep running up to 150% of the allowance: you get a notice at the first LoC-scan over it, and again at every further 5%. At 150%, new scans do not run until the month resets. A scan that does not run is recorded as a failed run with an explanation and an upgrade link; other scans are unaffected, and the daily security watch runs throughout.

Enterprise licences are a hard limit per licence year (the unlimited licence has none); the installation's owners are warned when a month runs past a twelfth of it.

Automated agents: you may connect agents via the Watchdog agent API or MCP to act on findings. An agent-triggered verification re-scan counts toward your LoC-scan budget; it is off by default and enabled per repository by its owner. (Internal detector-QA is separate and never billed.)

"Community" refers to the Watchdog community: the members who make the product better by helping classify noise. It does not mean non-commercial, and both Community plans may be used for commercial work. Community free is for one account; Community unlimited has unlimited accounts. Agent and MCP keys are unlimited and never count as an account.

Both Community plans are paid for partly in judgement. The people who lead engineering in your organisation (engineering managers, tech leads and architects, or the owners when nobody holds those roles) get one noise question a day about a finding in someone else's code, and at most 15 wait at a time; past that the oldest drops off and counts as unanswered. If your organisation answers fewer than 30% of its questions over the last 30 days, billable scans pause until it catches up; the daily security watch keeps running. Below 50% in each of three whole months, your contributors and owners are warned. These rules count questions offered from 1 November 2026.

The answers are what our published noise figures are checked against. Those sent to the Code Assurance Index are filed under a pseudonymous id and declared as compensated, never as independent. How agreement is measured, and how to dispute an item, is in the contributor terms. Professional and Enterprise ask for none of this.

Watchdog also surveys a corpus of public open-source repositories on its own account, to validate the engine and to publish comparable figures. Those reports are public: the scores, findings and evidence at the commit that was scanned, and the repository's presence in aggregate figures such as per-language noise rates. Nothing is published about the people who wrote the code beyond what the repository already makes public. A maintainer can ask for a repository to be removed from the corpus and from future publications; figures already published stay published.

This is separate from your plan: no plan publishes your reports automatically (§5).

On every plan, including Community free, reports are private by default. You may publish a report (your quality stamp) by explicit opt-in. Reports that regress below a previously published report are never published.

Scans run in off-peak windows and may be moved. Some packages let you choose your own schedule and a more frequent cadence. Scheduled scans are best-effort and may be queued during peak load.

Connect only repositories you are authorised to analyse. Do not disrupt the service. Do not circumvent plan limits.

Reports are provided "as is" for informational and planning purposes. They are not a guarantee of security, correctness, or fitness for any purpose, and do not replace human review. To the maximum extent permitted by law, Canine Development is not liable for indirect or consequential damages.

You can close your account at any time from your settings. Deletion happens after a 14-day grace period (during which it can be undone), then becomes permanent: we erase your personal data and login, and purge your reports. We retain invoices for bookkeeping and anonymised, non-identifying aggregate metrics (see the DPA). Cancelling a subscription (keeping the free plan) is separate from closing the account.

We may update these terms. Material changes are shown on your next sign-in for re-acceptance; continued use constitutes acceptance.

Questions about these terms: contact us. See also Security & data handling and the Data Processing Agreement.