Privacy — Modex

Website analytics

The Modex website uses Vercel Web Analytics to record aggregated page views. A page-view data point may include the page and referrer, approximate location, browser, operating system, and device information.

Vercel Web Analytics does not use third-party cookies. Vercel identifies visitors using a hash derived from the incoming request. The resulting visitor session is automatically discarded after 24 hours. See Vercel’s Web Analytics privacy documentation for more information.

The site sends page-view events only; it does not send custom analytics events.

The site itself is hosted by Vercel. Like any web request, loading a page reaches that host and appears in its standard request logs, which include the connecting address. Those logs are not joined to product telemetry and not used to build a profile of you.

Product telemetry

The Modex VS Code extension and Modex Desktop send a small amount of anonymous usage data so we know which editors, platforms, and languages to keep supporting. It is on by default and you can turn it off at any time.

What is sent is a fixed, closed set of events, and the two products do not send the same set. The VS Code extension sends one event: that the extension was launched. Modex Desktop sends that one and, because it runs the simulation and AI work itself, six more: the outcome of a simulation run, the outcome of an AI request, which public Modelica libraries a simulated model declares, the outcome of a Modelica compiler install, and — only when something goes wrong — the class of a startup failure and how the bundled server process stopped. Every value comes from a fixed list defined in the source. An AI request reports a provider and model family — never the model name you typed — and a library is named only when it is a public library Modex installed for you or ships with; anything else, including anything in your own workspace, is reported as a single placeholder word. Modex never sends your files, file paths, workspace or folder names, model content, prompts, completions, AI conversation content, error messages, stack traces, log lines, your name, email, account, or hostname. Every event also carries a flag marking whether it came from one of our own test machines, so that our testing does not get counted as your usage; on your install that flag is always false, and it describes us rather than you.

Events are tied to a random install ID generated on first run. It is not derived from you or your machine, and you can reset it. In VS Code, run the Modex: Reset Telemetry Install ID command. On the desktop, delete the telemetry state file in the Modex application-data folder — note that this also clears your on/off choice back to the default. Country and continent are derived from the connection that delivers the launch event, and only that event; PostHog is configured to anonymize the address, store no finer location, and retain no address of its own. Every other event is sent with geolocation switched off. Session recording, autocapture, and person profiles are off.

Telemetry goes to PostHog's EU host (eu.i.posthog.com) and is kept for 12 months.

To turn it off: in VS Code set modex.telemetry.enabled to false, or set VS Code's own telemetry.telemetryLevel to off — either one is enough. In Modex Desktop, open Help → About Modex and click Privacy at the end of the copyright line — that dialog states whether it is currently on, and switches it. Nothing else about the app changes.

Update checks

Modex Desktop asks modexai.io once a day whether a newer version exists. That request carries no usage data, account, or install ID, and it is separate from product telemetry. Being a web request, it reaches the same host as the website and appears in its standard request logs; those logs are never joined to telemetry. You can turn the check off under About.

Product data

The marketing website does not upload your model or simulation files.

Modex stores models, simulation outputs, figures, and documents locally. When you explicitly submit an AI request or use an external tool, selected context and tool results relevant to that request may be processed through the runtime or provider you chose — for example Anthropic, OpenAI, Google, or a runtime running on your own machine.

That traffic goes from the app to the provider you configured. It does not pass through a Modex server — the only modexai.io addresses in the shipped apps are this privacy page, opened when you ask for it, and the desktop update feed. The apps also have no Modex account: there is no sign-in, and we hold no email address, profile, or workspace of yours.

Who else processes this data

Two providers, and that is the whole list. We do not sell or rent your data, and there is no advertising network on this site or in the apps.

AI providers are not on this list because they are not our processors: you choose one, the app talks to it directly, and it operates under its own terms. Application downloads are served from GitHub Releases, the Visual Studio Marketplace, and Open VSX, which likewise operate under their own terms.

Legal bases (EEA/UK)

Website analytics, product telemetry, and update checks rest on our legitimate interests: knowing which editors, platforms, and languages to keep supporting, and keeping the software working. We are not asking for your consent for these, so it is worth being direct about the balance — that is why the data is a fixed set of events, carries no content of yours, is tied to a random install ID rather than to a person, and has profiles and session recording switched off.

You can object at any time, and the objection is the off switch: turning telemetry off stops it, with nothing else about the app changing. In VS Code the extension also honours your editor-wide telemetry.telemetryLevel, so a decision you already made there is not overridden.

Where you contact us, we process your message to answer it, which is a legitimate interest and, where you are asking us to act on your rights, a legal obligation.

International transfers

Product telemetry is sent to PostHog's EU host and stays in the EU. Website and update-feed requests are handled by Vercel, a company based in the United States, under its own data-processing terms; that is a transfer outside the EEA and the UK.

How long things are kept

• Product telemetry — 12 months.
• Website analytics — the visitor session hash is discarded after 24 hours; page-view counts remain as aggregates.
• Hosting request logs — kept by Vercel under its own retention, and not joined to telemetry.
• Email you send us — kept as long as needed to deal with it.

Your rights

Depending on where you live, you can ask for access to your data, correction, erasure, restriction, portability, or object to processing, and you can complain to your local data protection authority. Email support@modexai.io and we will answer within 30 days.

One practical note, because it decides whether we can act. Telemetry carries no name, email, or account — the only handle on it is the random install ID. Include that ID if you want your telemetry deleted; without it there is nothing in the data that identifies you as you, which is the point of collecting it that way, but it also means we cannot find your rows. On the desktop the ID is in telemetry-state.json in the Modex application-data folder. In VS Code it lives in the extension's global state and is not shown in the interface today — email us and we will tell you how to read it.

Resetting the ID is a different thing from deleting data. A reset (Modex: Reset Telemetry Install ID in VS Code, or deleting the desktop state file) stops future events being linked to the old identity, but what was already sent stays until it ages out or you ask us to remove it — so send us the ID before you reset it.

Children

Modex is not intended for children under 16, and we do not knowingly collect their information.

Changes to this page

When what we collect changes, this page changes in the same release, and the date at the top moves. If the change is material — a new category of data, a new processor, or a different default — we will say so in the release notes rather than leave you to notice the date.

External links and providers

This website links to software registries, GitHub, and Discord. Those services operate under their own privacy terms. AI runtimes, providers, and automation clients connected to Modex also operate under their own privacy terms. Review the privacy terms and settings for any external service you use or connect.

Contact

Modex is the controller for the data described on this page. For privacy questions, or to exercise any of the rights above, email support@modexai.io.