EZbuild for Revit · Last updated: October 11, 2026
This policy covers EZbuild for Revit, the free Revit plug-in, in both its pyRevit and standalone editions. It is published by Pitayadesign, New Zealand. The EZbuild compliance-review web platform is a separate product with its own privacy policy.
EZbuild for Revit collects no personal information and sends nothing anywhere. It has no account, no telemetry, no update check and makes no network connections. Everything it does happens on your own computer.
None reaches us or anyone else. There is, however, one thing the plug-in records, and it records it inside your own Revit model: each table it imports carries a small source note on its drafting view, so that Refresh can find the spreadsheet again later. The note holds:
Only by the plug-in’s Refresh command, on your computer: the path and worksheet tell it where the table came from, the fingerprint tells it whether the spreadsheet has changed since, and the page number tells it how a long table was split. It is not used for anything else, and we never see it.
We share nothing with anyone, because we receive nothing.
The source note is part of your Revit model, though, so it goes wherever the model goes. If you send the model to a consultant, a client or a council, they can read it, and so can other Revit add-ins. To remove the note from a table, delete that drafting view — Refresh will then no longer be able to update it.
The plug-in opens the Excel file you choose read-only and never changes it. It reads its own settings file if you have created one. It writes no log files, temporary files or anything else to your disk.
The standalone edition bundles open-source libraries for reading spreadsheets and measuring fonts (ClosedXML and its dependencies); the plug-in uses them only to read the file you choose. The pyRevit edition runs inside pyRevit, which is a separate program with its own settings and terms that this plug-in does not control.
If a future version changes any of the above, this page will be updated, and the date at the top changed, before that version is released.
Questions about this policy: Pitayadesign, pitayadesign.nz@gmail.com. How the plug-in’s files are signed is set out in its code signing policy.