Security at Guardian

Guardian is currently in the process of obtaining ISO 27001 certification. We're continuing to invest in formal security controls and operational processes to support enterprise security requirements.

Guardian uploads operational and usage data required to deliver product functionality, reporting, and performance insights. This may include information such as file names, file paths, model performance
metrics, and user activity data related to how Revit is being used.

Examples include metrics like time to open, time to sync, and which Revit commands are used.

Yes, project settings can be customized and automated based on conditions like file location, file name, and other model attributes. For secure projects, most firms disable Guardian's optional screenshot functionality. Firms have complete control over which projects are registered to Guardian.

Yes, we provide a standard DPA. View the DPA here.

All client data currently resides in US-based Azure servers. Data is replicated to regional Azure data centers based on client location. Learn more about Azure data center security.

Guardian is typically deployed by IT teams using standard enterprise software deployment methods. Most organizations first distribute the Guardian security certificate through Group Policy, then deploy the Guardian MSI using endpoint management tools such as Microsoft Intune or similar software deployment platforms.End users are not required to log in to Guardian. Instead, Guardian identifies users by capturing their Revit ID via the Revit API.

Not at this time. Guardian processes identifiable operational and usage data where needed to support product functionality, reporting, and administrative visibility. This enables client-specific insights such as project-level performance metrics, file-level reporting, and role-based administrative visibility.

Access to administrative controls is restricted by role, with support for company administrator and project administrator permissions.