For IT departments: where the plugin connects
The Vitruvius plugin runs inside Revit on the architect's computer. All its connections are outbound (from the computer out), over HTTPS only. The code refuses any address that doesn't start with https://. There are no inbound connections.
A- Sheet
- I-01
- Title
- For IT departments: where the plugin connects
The addresses
I-01.1| Address | Why | When |
|---|---|---|
https://vitruvius-licensing.vitruviusecosystem.workers.dev | The licensing server: activating the licence and checking it periodically. | On activation, and from time to time afterwards. |
https://vitruviusecosystem.com/updates/manifest.json | Update check: a read-only JSON file with the latest version number. | When Revit opens. |
https://europe-west1-vitruvius-telemetry.cloudfunctions.net/recordEvent (and next to it /reportIssue) | Usage data and fault reports. | Usage data: on by default from version 0.5.0; the user can turn it off in the plugin's Settings and the sending stops at once (in earlier versions: only if the user turned it on in the plugin's Settings). The enabled field in %APPDATA%\Vitruvius\telemetry.config can only block it, never turn it on. Fault report: only when the user clicks "Send". |
https://account.vitruviusecosystem.com | The account area. Opened in the user's browser when they sign in to the account, not by a direct connection of the plugin. | On signing in to the account only. |
https://vitruviusecosystem.com | The site. Opened in the user's browser when they click a link, not by the plugin itself. | On a click only. |
Exactly what is sent on each connection, field by field, is set out in the Privacy Policy.
The VITRU bubble on the website (when it is switched on) is not part of the add-in: the question, the earlier messages of this conversation (up to 8) and the page address (without parameters) go to Microsoft's Azure OpenAI Service (Sweden Central, an EU region; processing and storage stay in that region) to write an answer. The conversation stays only in your browser tab, and Microsoft may keep, for a limited time, conversations its system flags as suspected abuse, for abuse review. It does not use them to train models or share them with OpenAI. Details are in the Privacy Policy.