Product Data Handling Overview
This page explains how TiMBIM Manage works with project information, local settings, and licensing details as part of its normal Revit workflow.
Privacy Principles
Local-first workflow
Most day-to-day processing happens inside Revit and local settings files.
User control
Users choose when to preview, apply, save, refresh, or remove project-related data.
Scope
This page describes the behavior of the TiMBIM Manage Revit add-in. Website analytics, ecommerce checkout systems, contact forms, or other services used on the TiMBIM website should be covered separately in the main site privacy policy where relevant.
Information Processed By The Add-In
TiMBIM Manage works with the Revit model information needed to support the selected workflow. Depending on the workspace, this can include family names, type names, material names, categories, parameter values, view details, sheet data, title blocks, legends, revisions, and classification values.
- Project information is read so previews, filters, and rules can be evaluated
- User selections are used to decide which items are included in a given operation
- Locally saved rule or settings files can include names, parameters, templates, and layout options chosen by the user
Licensing and Validation
TiMBIM Manage checks licensing before the main workspaces open. As part of that access check, the add-in sends the licensing details needed to validate the installation against the TiMBIM licensing service. This includes the licensed email address entered for the seat, the Autodesk user identifier reported by Revit, the add-in version, the product key, the Autodesk app identifier, and a machine fingerprint used to recognize the workstation.
The current machine fingerprint is derived from active network adapter MAC addresses and is sent as a one-way SHA-256 hash, not as a plain-text hardware list. This information is used for licensing, seat validation, access control, offline grace handling, and related support processes.
Local Storage
The add-in can store local settings that support workflow continuity between sessions. Examples may include saved rule libraries, cached interface preferences, and licensing cache data stored on the workstation.
For licensing, the local cache can include the saved license email, the Autodesk user identifier tied to the most recent check, the last validation status and message, license type, product details, expiry information, and the time of the last successful validation. Local settings are intended to make the add-in easier to use on the same workstation, including short offline grace periods after a valid check.
Support Contact
If you have questions about TiMBIM Manage data handling or licensing-related processing, contact support@timbim.eu.