Privacy notice

ASysT is local-first. Your private customer data, SysML models, model elements, source text, saved renderings, model diagnostics and local logs are not uploaded by product diagnostics.

Data controller: Julien Cellier, entrepreneur individuel (sole trader) operating under the trade name asyst.rendering — 57 Rue Robert Desnos, Bât D1, 06600 Antibes, France — registered in France under SIREN 107 675 472 (R.C.S. Antibes) · asyst.rendering@gmail.com · full publisher details on the mentions légales page.

Optional product diagnostics

ASysT asks you to choose Share product diagnostics or Keep diagnostics off. Nothing is sent before you actively choose sharing. Refusing has no effect on the app. Under ⚙ Configuration → Privacy & diagnostics, startup/readiness, standard views, rendering workflow, named actions, duration buckets and coarse errors have separate switches. You can disable any category independently or withdraw with one click; disabling every category also deletes the local random installation ID. You can reset that ID separately at any time.

The purpose is to understand whether ASysT starts and renders successfully, which app channel and release are used, which of the eight standard SysML view families are opened, whether a rendering is saved, restored or deleted, whether an export, auto-layout, routing, filter or sort action completes, coarse duration bands and coarse failure categories. A view or action family is a fixed product value such as sequence; it is not a model element, element type, element name or model value. The legal basis is your consent (GDPR Article 6(1)(a)).

Each event contains only its event name and day, a random event ID, app version, VS Code or standalone channel, whether the build is production or development, coarse operating-system and processor families, a random installation ID, and the small allow-listed fields needed by that event. ASysT diagnostics never send model or source content, model elements or element names, source paths, raw clicks, pointer coordinates, filter queries, local action or error logs, diagnostic messages, stack traces, licence data, IP addresses, precise location, country, device names, account details or free-form text. An application error is converted locally to one fixed subsystem and one fixed error class before it can be queued. Audit the exact fields in the app's Privacy & diagnostics panel to see the complete allow-listed record shapes; unknown fields are rejected by the collector. A network address exists briefly in server memory only to rate-limit abuse; the diagnostics route does not log it.

Storage, recipients and retention

Consented events are sent over HTTPS to an ASysT service hosted by OVH in France. Access is limited to the controller. Raw failure events are kept for up to 14 days; other raw events for up to 30 days; pseudonymous daily rollups for up to 90 days; an exact aggregate summary for the current retained windows inside the password-protected operator dashboard; and minimum-five-suppressed backup summaries for up to 13 months. The service has a 20 GB total storage cap and stops collection before its reserve is exhausted.

A separate private GitHub repository backs up only sanitised summaries and their versioned schema. It never receives raw events, installation IDs, IP addresses, model names, paths or logs. The authenticated operator dashboard displays exact aggregate cells but exposes neither raw records nor installation IDs; before a summary enters the separate backup, cells based on fewer than five installations are suppressed.

Your choices and rights

Open ⚙ Configuration → Privacy & diagnostics in ASysT to review all six diagnostic switches, audit the fields, withdraw, reset the installation ID or copy the deletion ID. If you may want access to or erasure of already received events, copy that ID before withdrawing or resetting it, then email it to asyst.rendering@gmail.com. The ID is the only way to locate pseudonymous events; ASysT has no account that can identify you another way. You may request access, correction, erasure, restriction or portability where applicable, and may withdraw consent without affecting earlier lawful processing.

There is no advertising, sale of data, profiling or automated decision-making. A support request is sent only when you choose to create an issue in the public GitHub feedback tracker; it is not collected as diagnostics. Do not post confidential model information in a public issue.

If you believe your rights were not respected, contact the address above first or lodge a complaint with the CNIL, the French data-protection authority.

This website

The public website sets no advertising or audience cookies. It stores only your light/dark theme preference in your browser. Separate security access logs may contain IP address, requested page, time and browser information for up to about 15 days. They support service security and a basic aggregate traffic dashboard under legitimate interests (GDPR Article 6(1)(f)); they are not joined with app diagnostics.

Notice version 5 · last updated 29 July 2026 — the controller is now identified by its registered business details, matching the mentions légales.