Skip to content
Vitruvius Ecosystem

Updated: 20.10.2026

Privacy Policy

The Hebrew version prevails in case of discrepancy.

This Privacy Policy (the “Policy”) sets out the personal information that is collected and processed when you use the site vitruviusecosystem.com, your account area and the Vitruvius plugin for Revit (together, the “Service”), the purposes of the processing, the parties to whom the information is transferred, and your rights under the Privacy Protection Law, 5741-1981, as amended by Amendment 13 (in force from 14.8.2025) (the “Law”). Every data field is listed in this Policy by its technical name, so that you can verify exactly which data leaves your computer.

Who is responsible for the information

The controller of the database, being the person who determines the purposes for which the information is used, is the business trading under the name VITRUVIUS ECOSYSTEM (“Vitruvius”, “we” or “us”). The business’s full details are provided in the disclosure document sent with the purchase confirmation. Any privacy question or request may be addressed to contact@vitruviusecosystem.com, stating “Privacy” in the subject line. Section 11(2A) of the Law requires the identity of the controller and its contact details to be stated. The service providers that process information on our behalf are “holders” within the meaning of the Law, and they are listed in the section “Who the information goes to”.

The Service is intended for businesses and professionals aged 18 or over.

What is collected

Under section 3 of the Law, “personal information” means data about an identified person or a person who can be identified, including by means of an “online identifier”. The installation ID and the short computer fingerprint are online identifiers of this kind. Accordingly, all the usage data that the plugin sends is personal information, and we process it as such.

Account and purchase. An e-mail address and a name, as passed to us by the sign-in provider (Google, Microsoft or a code sent by e-mail); the subscription plan, its start and end dates, and invoices. When making a purchase you will be asked to provide the name to appear on the invoice and, at your choice, a company number or an authorised-dealer number and an address. These details are kept in our database and are transferred, together with the purchase details, to Morning (Green Invoice, “חשבונית ירוקה”) for the purpose of issuing a tax invoice as required by law. Morning acts as a holder on our behalf and processes the details solely under our instructions. Credit card details are provided to Cardcom and are kept by it alone, and we do not receive them; the only item we keep is a token received from Cardcom, for the purpose of renewing the subscription at the end of its term. When a coupon is redeemed, the e-mail address it was redeemed with is kept as a sale record. It is kept while the licence is active and is deleted on your request.

Ideas from the partners form. If you send an idea through the partners page of our site, we keep the name, e-mail address, office name and the content of the idea as you gave them, and the time it was sent. There is no legal obligation to provide them, but without an e-mail address and the content of the idea we cannot handle the request.

Licensing (required for the licence to function, and sent regardless of usage data). When a licence is activated, the plugin sends the licensing server: office (the office name), architect_name, architect_email, fingerprint (the full computer fingerprint), client_hash, install_id, nonce and ts. On a periodic licence check it sends client_hash, install_id, fingerprint, nonce and ts. When you sign in to an account from the plugin it also sends code and code_verifier (a one-time sign-in code) and device_name, which is the computer name as set in Windows. The server issues the computer a device_id and a device_token, and the plugin sends the device_token when it renews the licence and when it counts seats, together with lease_id and seq. When a former key licence is moved to an account, the plugin also sends legacy_key_hash (a hash of the former key); and when you choose to replace an existing computer or to move the licence to this one, it sends the flags displace and force. The licence activation details (the office name, the architect’s name and e-mail address, and the computer fingerprints) are held on the licensing server as long as the licence exists, and are deleted on your request or when the account is closed. A copy of them in the usage-statistics system is deleted 90 days after the licence was last used.

Usage data from the plugin (on by default from version 0.5.0; you can turn it off at any time in the plugin’s settings). Every event is sent with a fixed envelope: event, schema_version, install_id, app_version, revit_year, license_key_id, device_id, language, fingerprint_short, ts. device_id is the identifier of the device on which an account licence was activated, and for a key licence it is sent empty. It is used to link a report to the licence activated on that computer, and is kept for the same period as the rest of the usage data. In addition, each event may carry only the fields defined for it in advance:

  • DWG file scan: link_count, file_count, shx_font_count, shx_fonts, dxf_entity_count_bucket, had_hebrew, duration_ms, reason_code
  • Fonts and mapping: font_name, recommended_ttf, had_recommendation, mapping_count, new_count, merged_count, overridden_count, shx_font, suggested_ttf, chosen_ttf, restored_mapping_count
  • Fixing and layers: stage, links_fixed, links_failed, entities_reversed, top_entity_type, layers_affected, scope, xrefs_shown, xrefs_hidden, field_changed, is_xref_layer
  • Commands and errors: command, success, exception_type, where, stack_hash
  • Licence and usage: result, tier, is_first_session
  • Once, upon licence activation, and only if usage data is on: key_index only. The office name, the architect’s name and the architect’s e-mail address are sent to the licensing server at the activation itself, as described above, and are not sent as usage data.

Technical diagnostics (part of usage data, switched off together with it). To diagnose faults remotely, since we have no on-site support, the plugin also sends technical data linked to an installation id; it contains no names, paths or drawing content. Because the installation id is tied to a licence and an account, this data can be linked to them. It is divided as follows:

  • Technical environment: the plugin version; the Revit version, build and language; the Windows build, language and regional settings; the .NET version; the number of processors; memory and free disk space, as ranges only; installed AutoCAD products and their versions, without installation paths; the licence state and the number of trial uses left; the Windows code page; 32-bit or 64-bit; which AutoCAD product the plugin uses and whether a manual choice was set (without a path); the state of the usage-data switch; the update channel. Fields: plugin_build, revit_build, revit_lang, win_build, win_ui_lang, win_locale, codepage, dotnet, bitness, cpu_count, ram_tier, disk_tier, acad_state, acad_year, acad_trueview, acad_choice, license_state, consent_mode, channel.
  • Operation diagnostics: stage durations, error codes and reason codes, converter exit codes, counts of entities and links, whether the user cancelled or the operation failed, and the outcome of Undo; the name of the plugin command that ran; font codes (without font names); the format version of the DWG file and its text encoding; the size of the converter output, as a range; and the number of Revit warnings and errors in our operations, with Revit’s own failure identifier (GUID), and classified output codes of the converter. Fields: outcome, stages, convert_exit, convert_ms, convert_timeout, output_size, tail_codes, entity_tier, link_tier, dwg_version, encoding, font_codes, undo_outcome, user_cancelled, warnings, errors, failure_guid.
  • Errors: the exception type and code, a hash of the stack trace, the type of the inner exception, and method names from the plugin’s own code only. Error messages, paths and file names are not sent. Fields: hresult, inner_type, frames (method names from the plugin’s own code only, up to 12).
  • Health: the length of the working session, samples of the plugin process memory, load times, the number of slow responses of the window, and network failure codes together with the server we were contacting (licensing, update or usage data). Fields: session_min, mem_tier, load_ms, slow_ui_count, target (the server type only: licensing, update or usage data), http_status.
  • The diagnostic data carries random session and operation identifiers (session_id, op_id), and is held in a local queue file on your computer, telemetry-queue.jsonl in the folder %LOCALAPPDATA%\Vitruvius. The file exists only while usage data is on, and is deleted when it is switched off.
  • The plugin log is sent only if you tap it yourself in the fault report window, as described below.

We do not collect names of files, folders, projects, offices or people, e-mail addresses or drawing content. Diagnostic events, fault reports and their log attachments, and the daily activity of each installation are deleted after 90 days. After that we keep only daily totals that carry no identifier. You can switch diagnostics off at any time in the plugin settings, with the same switch that turns off usage data.

The plugin blocks any value that appears to be a file path. An event that carries a field not on this list is not sent at all. The content of a drawing is never sent. SHX font names are sent as they are; where a font has been given the name of a project, that name will be sent.

Fault report (only when you send one). Sent: message (the text you wrote), reporter_name, reporter_email, category, severity, license_key_id, install_id, app_version, revit_year, language, and also diagnostics. This is the plugin log, and it is sent only if you tick the box to attach it in the report window (unticked by default). You see a preview before sending; names (of files, people, offices, links, layers and views) and paths are removed from it, and it is cut to at most 400 lines. In a licensing fault report the log is always attached, after the same removal of names and paths.

The site and the plugin’s connections. IP address, the browser or software type (User-Agent) and the pages viewed. These data are exposed to the infrastructure provider upon every visit to the site, and also upon every call from the plugin: licensing, usage data and the update check. The infrastructure provider logs them for security purposes only. The site contains no advertising cookies and no third-party tracking tools.

Required or optional, and what happens if you do not agree

There is no legal obligation to provide us with any information, and providing it is entirely voluntary; however, some of the information is required for the Service to function. Under section 11(1) of the Law, we inform you of the consequences of not providing it:

  • Without an e-mail address an account cannot be opened, and without an account a subscription cannot be purchased and a licence cannot be activated.
  • Without an office name, a name and an e-mail address a licence cannot be activated. The activation window in the plugin requires all three.
  • On an account licence, without a device identifier (device_id) seats cannot be counted, and the plugin will therefore operate in trial mode only.
  • Usage data: the default and turning it off. From version 0.5.0 the switch is on by default, and in earlier versions it is off until you turn it on. If usage data was off before you updated to version 0.5.0, it stays off. On the first run of version 0.5.0 the plugin shows a notice with the switch. Turning the switch off in the plugin’s settings stops the sending immediately: events waiting to be sent are deleted and are not sent, and the plugin continues to operate in full. The value enabled:false in the telemetry.config settings file also blocks the sending.
  • A fault report is sent only when you click “Send”.

Why the information is collected

We use the information only for the purposes listed below, and for no other purpose (section 8(b) of the Law):

  • Activating the licence, counting seats and preventing double use.
  • Billing, issuing invoices and giving notice of the renewal date.
  • Responding to inquiries and faults.
  • Improving the plugin, for example in order to identify the fonts that most users lack and the actions that fail.
  • Usage data from the plugin: improving the tools and finding faults.
  • Reviewing ideas sent from the partners form, replying to the sender and sending an acknowledgement.

We do not sell information, do not use it for advertising, and do not train artificial intelligence models on it. An idea sent from the partners form is kept confidential, and only we have access to it. Upon the launch of Vitru, requests addressed to it will not be stored by us; they will be passed directly to the AI provider you have chosen.

Who the information goes to

The information is transferred only to service providers that process it on our behalf and in accordance with our instructions (section 11(3) of the Law):

  • Cloudflare: hosting the site and the licensing server, and protection against attacks.
  • Google Firebase: signing in to the account.
  • Google Cloud (Firebase): receiving usage data (unless you turned it off) and fault reports (only when you click “Send”), on servers in the europe-west1 region (Belgium, EU).
  • Cardcom: processing the payment and keeping the card details for the purpose of renewing the subscription.
  • Morning (Green Invoice): issuing tax invoices, on the basis of the name, the company or dealer number and the address you provided.
  • Resend: sending e-mail messages on our behalf (purchase confirmations, renewal reminders, seat invitations and acknowledgements), using only the e-mail address and the content of the message.
  • VITRU (the site’s bubble): when you ask a question, the question, the earlier messages of this conversation (up to 8) and the page address (without parameters) are sent to Microsoft’s Azure OpenAI Service (region: Sweden Central, an EU region; processing and storage stay in that region) to write an answer from the site’s own content only. The conversation stays only in your browser tab; we do not store it or link it to you, and we keep only aggregate usage counts, with no content. 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.
  • Microsoft or Google: only if you chose to sign in through them.

With each provider there is an agreement that sets out what it may do with the information, for which purposes, for what period, and how the information is returned or destroyed at the end of the engagement (regulation 15(a) of the Information Security Regulations). We will disclose information to an authority only if required to do so by a court order or by law.

Transfer outside Israel

Some of the providers store and process information on servers located outside Israel, mainly in the United States and the European Union. Among them, Resend, our e-mail delivery provider, stores the message details (the recipient’s address, the sender’s address, the subject and the content of the message) on servers in the United States. Regulation 1 of the Regulations on the Transfer of Information to Databases Outside the State’s Borders permits such a transfer only subject to certain conditions. We transfer information only to a provider whose data processing agreement (DPA) obliges it to protect the information and to use it solely in accordance with our instructions, as provided in regulation 2(4). Regulation 3 requires a written undertaking from the provider that it takes sufficient measures and that it will not pass the information on to any other person. Large providers use sub-processors, and we therefore verify that their agreement binds the sub-processors on the same terms. We retain these agreements. As regards information stored in the European Union, the transfer is also permitted under regulation 2(8). Should the law require a different basis for the transfer, we will request your consent (regulation 2(1)).

The right to inspect information

Every person is entitled to inspect the information about them that we hold (section 13 of the Law, and section 11(4)). Most of it can be viewed directly in your account area: the account details, the devices, the subscription and the invoices. To obtain a full copy, including the usage data sent from your plugin, write to contact@vitruviusecosystem.com. The copy will be sent in Hebrew, Arabic or English (section 13(b)), within the period prescribed by law.

Correction and deletion

If you find information that is incorrect, incomplete or not up to date, you may request that we correct or delete it (section 14 of the Law). Where we agree to the request, we will also update every provider to which the information was transferred. Upon the closure of an account, the usage data, the details of the devices linked to the account and the licence activation details are deleted. The identifier of a revoked device is kept in the revocation list only, until its local licence expires (up to 14 days). Tax invoices are retained for the period that the tax laws require, including the customer details recorded in them. Our payment records are kept under a replaced identifier and not under your account. An idea sent from the partners form will be deleted on your request.

Security and confidentiality

We, and every provider that holds information on our behalf, are responsible for its security (section 17(a) of the Law). We use encryption in transit (HTTPS). The licence is cryptographically signed, and access to the data is limited to those who require it. Every employee, manager or provider that holds information on our behalf is bound by confidentiality (section 16). Every event that raises a concern of harm to the information is documented and handled, in accordance with regulation 11(a) of the Information Security Regulations, and where the law so requires we will notify you and the Privacy Protection Authority. The security level that applies to us under the regulations is the basic level.

Changes to this Policy

Should the activity of the Service pass to another company or body, the information will pass with it for the same purposes only, and we will give you advance notice.

We will give notice of any material change to this Policy by e-mail and on the site before it takes effect. The date of the last update appears at the top of the page.