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.

The Feedback button

The ASysT application carries a Feedback button in its top bar, beside Export, that opens a short form. Nothing leaves your computer until you press Send; then the ASysT program running on your computer passes the message on to this server. A message keeps exactly four things: your text (at most 1000 characters), your e-mail address only if you typed one, the version of ASysT you are using and the time. It is anonymous unless you add an e-mail, and it never sends your model, your files or their names. The server keeps no IP address, browser information or cookie for it, and its route is left out of the access logs; a network address exists briefly in server memory only to limit how many messages one connection can send.

The same button works in the Live preview. There the copy of ASysT that passes your message on runs on this server rather than on your computer, so it hands the server your network address along with the message, only so that the same limit applies to you and not to every visitor together; that address is held in memory in the same way and is never stored. The message keeps the same four things, with the version marked as coming from the Live preview.

The purpose is to read and, when you ask for it, answer what you wrote, and to improve ASysT — legitimate interests (GDPR Article 6(1)(f)). Messages are stored on the same OVH server in France, are readable only by the controller, are never published or shared, and are deleted within 12 months. To have a message deleted early, e-mail the address above with roughly when you sent it and a few of its words. Please do not put confidential model information in it.

Live preview: error reports

The Live preview page, and the ASysT Modeler running inside it, send a short error report to this server when something breaks in your browser: an error in the page's code, a request that got no answer at all, or a preview frame that is still empty after 30 seconds. Nothing is sent when nothing breaks, no other page of this site sends anything, and at most ten reports leave one page load. A report keeps exactly: what kind of error it was, the error's message (at most 300 characters, with anything shaped like an e-mail address and every web-address query removed), the program file and line it came from, the path of the page or request (never its query) and the time. No cookie, IP address, browser information or model content is kept with it; a network address exists briefly in server memory only to limit how many reports one connection can send, and the report route is left out of the access logs. An error message can quote a name you typed into the example model, so please do not type personal information there.

The same failure log also records, from the server's own logs, what went wrong on the server side for visitors — a refused or failed request in the Live preview with its status and the sandbox number (1 to 10, not your session), a page or file of this site that was not found, the server answering with an error, and how often the feedback form refused a message and why (never the message itself). These records carry no IP address or browser information either. The purpose is to find and fix what fails for visitors — legitimate interests (GDPR Article 6(1)(f)). The log stays on the same OVH server in France, is readable only by the controller, is never published or shared, and is deleted after 90 days.

So that one visitor counts once rather than once per refused request, each Live preview sandbox also leaves one visit record when it is reclaimed: how long it was open, how many changes were made in it, and a visit tag — eight characters derived from your sandbox session, which cannot be turned back into it and changes whenever the preview server restarts. Refused requests of the same sandbox carry the same tag. The server's own log sees your browser's identification string so that robots and scripts can be recognised: their requests are then dropped, not stored, and only counted per day; this log never keeps that string. If the site's owner has named one of their own devices on their private dashboard, that device's records carry the name chosen for it (for example “owner-phone”); a visitor's records carry no name.

What you do in the Live preview is recorded, step by step. The Modeler keeps a log of each action you complete — for example “Renamed groundLed to groundLead” or “Ran Auto-layout on CrisisSystem” — with the time since your sandbox opened and, when an action was refused or failed, the reason it gave, plus the Modeler's own technical notes about what it did on screen. Each step also carries a few measurements that hold no name or text: its number in the sequence, the model's and the layout's revision, how many boxes and relations were on the board, the zoom, which part of the layout file was written, the kinds of the two elements a relation joined, and — a quarter of a second after you move or resize a box — where that box sits on screen and where the layout records it. A step the Modeler refused is also listed, with its reason, in the failure log described above. It is the same log the installed Modeler writes on its user's computer. That log is kept with your visit record (same visit tag, at most 2000 lines) so the author can see how the tool is really used and fix what gets in people's way. Like the rest of this log it carries no IP address, cookie or browser information, stays on the same server, is readable only by the controller, and is deleted after 90 days; the legal basis is the same legitimate interest. A step can quote a name you typed into the example model, so please do not type personal information there. The installed Modeler (Windows, Linux, VS Code) sends none of this.

A blank model you start in the Live preview is kept with your visit. The Live preview lets you start a model from nothing. It is a preview, not a workspace: nothing is saved for you after your session, exports are disabled, and your sandbox is deleted when the session ends (after 2 minutes without activity, or when you press Reset demo). Just before that, the text of any model you started there — its SysML files, its layout files and its manifest — is added to the log of your visit described above, beside every step you took. ASysT Rendering may use it to improve the product. It is kept like the rest of that log: no IP address, cookie or browser information, the same server, readable only by the controller, deleted after 90 days, on the same legitimate interest. You are told this, and asked to confirm it, before the model is created. Please do not type personal or confidential information into it.

Notice version 12 · last updated 1 November 2026 — each Live preview step carries name-free measurements, and refused steps are listed in the failure log. Version 11 (1 November 2026) — the text of a blank model started in the Live preview is kept with the visit. Version 10 (1 November 2026) — the steps of a Live preview visit are recorded. Version 9 (31 October 2026) — one record per Live preview visit, robots dropped, and the owner's own devices told apart. Version 8 (31 October 2026) — the Feedback button in the Live preview. Version 7 (31 October 2026) added the Live preview's error reports and the site failure log. Version 6 (30 October 2026) added the application's Feedback button and what it keeps. Version 5 (29 July 2026) identified the controller by its registered business details, matching the mentions légales.