Last updated 30 August 2026
The short version: the add-in runs entirely on your computer and does not send your model, your findings, or anything else to us or to anyone else.
Before you read further. This policy describes how the software behaves today, and we have written it against what the code actually does rather than what a template says. If a future version transmits anything, this page will say so before that version ships.
Plumbline is a Revit add-in. It reads the model open on your machine, evaluates it against rule packs stored alongside the program, and shows the results in a window. All of that happens locally. The add-in makes no network requests: it does not phone home, it carries no analytics or telemetry, and it has no mechanism for uploading a model, a finding, or a report.
| What | Where | Why |
|---|---|---|
| Audit settings | %AppData%\NccChecker\settings.json |
Remembers which subject areas you have switched off so you do not re-do it each session. |
| Licence details | %AppData%\NccChecker\licence.json |
Records the licence holder and expiry so the add-in knows it may run. |
| Reports and remediation logs | Wherever you choose to save them | Written only when you press Export, to the location you pick. |
Nothing in these files is sent anywhere. You can delete them at any time; the add-in will recreate the settings file with its defaults on the next run.
Your Revit model never leaves your machine because of Plumbline. We do not receive a copy, we cannot see your findings, and we have no ability to reconstruct your project from anything the add-in produces. If you send us a model or a report in the course of asking for support, we treat it as confidential, use it only to answer your question, and delete it when the question is resolved.
The site is a set of static pages served from Google Cloud Run. It sets no cookies, runs no analytics, embeds no trackers, and includes no third-party scripts. The only external request a page makes is to Google Fonts, to fetch the two typefaces used in the design; that request reaches Google and is governed by their privacy policy.
The web server keeps ordinary access logs — the requesting IP address, the time, the page requested, the response status and the browser's user-agent string. These are used to keep the site working and to see whether it is being abused. We do not use them to build a profile of you and we do not combine them with anything else.
Builds sit behind a password. When you sign in to download, the server records the request in the same access log described above. The password is shared with people we have given access to; it does not identify you individually.
The Australian Privacy Principles under the Privacy Act 1988 (Cth) inform how we handle personal information. In practice we hold very little of it: an email address if you have written to us, and server logs. You may ask what we hold about you, ask us to correct it, or ask us to delete it, and we will do so unless we are required to keep it. If you are unhappy with how we have handled a request you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
If this policy changes we will update the date at the top. A change that affects what the software transmits will be described here before the version that makes it is released.
Privacy questions go to the address on the terms of use page.