This notice describes the personal data that riSim Studio (the Visual Studio Code extension, the command line tools and the simulator toolchains, the “Software”) processes. The controller is xq-Tec GmbH, Harztaler Str. 5, 67693 Fischbach, Germany, info@xq-tec.com. Your rights, including the right to object and to complain to a supervisory authority, and the backups of our license server are described in sections 11 to 13 of our privacy policy.

1. What stays on your computer

The Software simulates your designs on your computer. Your designs, simulation results, waveforms and logs stay there; the Software sends none of them to us, and sends them elsewhere only where you set this up yourself (section 5). It contains no telemetry, usage statistics or crash reporting, and it doesn’t check for updates by itself.

2. Downloads of toolchains

The Software connects to our download server dl.risim-studio.com only when it downloads a toolchain: when you install or update riSim with its installers or its command line tools, and when the version of riSim that you select, or that a workspace you work in requires, isn’t installed yet. In that case, the command line tools and the Visual Studio Code extension install that version and tell you so; in workspaces you haven’t trusted in Visual Studio Code, the extension doesn’t run. You can also configure the Software to download nothing; its documentation explains how. A download transmits your IP address, the time, the files requested (which show the version and your platform) and the version of the Software. We don’t keep logs of downloads; AWS processes this data only to deliver the files and to determine your country from your IP address, so that deliveries to countries and regions under sanctions can be refused (see clause 11.3 of the license terms).

The download server is operated for us by Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg (“AWS”), as our processor (Art. 28 GDPR). The files are stored in Frankfurt, Germany, and AWS delivers them from a location near you, which can be in Europe, Israel, Türkiye, the United States, Canada or Mexico, and occasionally elsewhere. A request may therefore be processed outside the EU, in particular in the United States. For the United States, Amazon Web Services, Inc. is certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR); for the United Kingdom (Implementing Decision (EU) 2021/1772, as renewed by Implementing Decision (EU) 2025/2574 until 27 December 2031), Switzerland (Decision 2000/518/EC), Israel and Canada, adequacy decisions of the European Commission apply (Art. 45 GDPR); otherwise, the EU standard contractual clauses in our data processing agreement with AWS apply (Art. 46(2)(c) GDPR), of which you can request a copy from us.

The legal basis is Art. 6(1)(f) GDPR: our legitimate interest in delivering the Software you request securely and reliably, and, for determining your country, in not providing the Software in countries and regions where this would expose us to penalties under export control and sanctions law (see clause 11.3 of the license terms). You don’t have to provide this data, but without it the Software can’t download toolchains. Storing the downloaded toolchain on your computer is part of the installation you request (Section 25(2) No. 2 TDDDG).

3. License activations

Without a license key, riSim Studio doesn’t contact our license server. When a paid plan or a trial is activated on a machine, in Visual Studio Code, on the command line or automatically, for example on a build server, the Software reads the machine id that the operating system assigns to the machine and the machine’s host name. It then sends the following to our license server license.risim-studio.com, which runs on our server at Hetzner Online GmbH in Germany, as our processor (Art. 28 GDPR; sections 3 and 10 of our privacy policy):

  • the license key;
  • a fingerprint of the machine, computed from the machine id and the host name; the machine id can’t be recovered from it, but the fingerprint identifies the machine for as long as its machine id and host name stay the same;
  • the machine’s name: its host name, unless you choose another name when you activate the machine;
  • the platform of the Software (its operating system and processor type) and its version.

Where the operating system has no machine id, the Software creates a random one on activation and stores it on the machine. The Software also stores the activation on the machine. While the Software runs, it renews the activation once a day; on a floating license, it also reports every few minutes which simulation threads the machine uses. A machine whose license has ended keeps contacting the license server to renew it while the Software runs, until you deactivate it on the machine, for example with the command line tools; this continues after the license server has deleted the machine’s data.

The license server stores the activated machines, the time of their last contact and, on a floating license, the threads in use. Your IP address is processed for each connection; it is stored only in the server’s technical logs, with the time and the request, for 14 days, to detect and fix errors and attacks (Art. 6(1)(f) GDPR). The license server also determines your country from your IP address, so that it can refuse requests from countries and regions under sanctions (Art. 6(1)(f) GDPR, with our interest as in section 2). The license server is source-available software that we run ourselves on that server; no data goes to the software’s developer or to other third parties.

We are the controller of this data. We process it for our own purposes: to enforce the limits of the license (the number of machines and, on a floating license, of threads), to protect the Software against unlicensed use, and to show the activated machines to the license holder, so that it can manage them. We don’t process it on behalf of the license holder.

The legal basis is Art. 6(1)(b) GDPR where you yourself are the license holder. Where the license holder is your employer, your client or another organization, it is Art. 6(1)(f) GDPR: our legitimate interest in enforcing the license terms and protecting our copyright, and the license holder’s interest in using its license on the machines you use. You don’t have to provide this data, but without it a license key can’t be activated; the Software then runs only on the free plan, which doesn’t cover virtual machines and containers (clause 3.2 of the license terms).

Reading the machine id and the host name, and storing the activation and, where needed, the generated machine id on the machine, are strictly necessary for the activation you request (Section 25(2) No. 2 TDDDG). The free plan neither sends anything to the license server nor stores anything for it. On every plan, the Software stores on the machine which version of the license terms you have accepted, and whether it has pointed you to their current version; it sends this nowhere.

The Software shows a link to this section when it activates a license and where it shows the license status, on the command line and in Visual Studio Code; its installers show a link to this notice. If someone else, for example your organization’s IT department, activated the Software on a machine you use, the license holder has also undertaken to make this information available to you. Host names can contain names of persons; you can choose a neutral machine name when you activate the machine.

Right to object (Art. 21 GDPR). You may object at any time, on grounds relating to your particular situation, to any processing described in this notice that is based on Art. 6(1)(f) GDPR. We will then stop that processing, unless we demonstrate compelling legitimate grounds for it that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defense of legal claims. For a machine’s activation, this generally means that we deactivate the machine, so that only the free plan applies on it, and tell the license holder that the machine was deactivated, without naming you unless you agree.

A machine’s data is deleted when the machine is deactivated, 7 days after its license ends, and on a floating license within 30 minutes after its last contact. You can deactivate a machine with the command line tools, which also deactivate it when they uninstall riSim; uninstalling only the Visual Studio Code extension doesn’t deactivate the machine. The license key’s data is deleted with the data of the trial (section 7 of our privacy policy).

4. Visual Studio Code Marketplace

When you install or update the extension from the Visual Studio Code Marketplace, Visual Studio Code connects to Microsoft. Microsoft is responsible for this, under its privacy statement (https://privacy.microsoft.com/privacystatement). We receive statistics of installations from Microsoft, and see the reviews and questions you post publicly there.

5. Connections you configure

If you configure the Software to export its logs and traces to a server of your choice, it sends them there, not to us. If a proxy is set in the environment in which the Software runs, through the usual proxy environment variables, downloads and connections to the license server go through that proxy. If you use remote development in Visual Studio Code, where the Software runs on another computer or in another environment, Visual Studio Code forwards the connection between the extension and the Software, under the terms of the remote environment you use.

6. AI assistants

If you use an AI assistant in Visual Studio Code, it can call the Software’s tools, for example to run a test case or list the problems found in your design. Their results go to the assistant you use, under its provider’s terms; the Software itself sends them nowhere.

7. Changes

If a version of the Software adds a network connection, we update this notice before that version is released.