Privacy notice
This notice covers what VIZid Next and VIZid Suite send to VIZid on their own, and what we keep when you contact us:
- Seat reports — small reports when a licence or trial changes state on a machine, or when the software's own licence records do not add up (the next two sections).
- What you send us yourself — support messages, an optional diagnostics text, and the getting-started tips you can opt into (the section "Support tickets, getting-started tips and the community").
It does not cover connections you start yourself — downloading an installer, or optional add-on packages the app offers to fetch from their publishers (for example an AI engine from GitHub) — nor the connections between VIZid programs on your own computer or your own render server. The software has no usage analytics: it does not report which files, projects, prompts or render content you work on, or your browsing.
What is sent, and when
A seat report is sent when you start a free trial, when you activate or deactivate a licence, at start-up while a trial stays ended (at most once a day), and at start-up when the software finds that its own licence records on a machine do not add up (see "Integrity signals" below; at most once a day for each set of signals, on trial and licensed machines alike). Each report contains only:
| Field | Example | What it is |
|---|---|---|
rk (Request Key) | VZRK-MXN5-2UTR-O7LN-SZ7Y | A pseudonymous hash (SHA-512) of the Windows installation's machine GUID (it changes when Windows is reinstalled). It cannot be reversed to a person, a name or an IP address; it does identify the same installation consistently, which is what lets us count seats. |
product | VIZidNext | Which product sent the report. |
version, build | 1.0.0-beta, a1b2c3d | The app version and build. |
os | Windows | The operating-system family (Windows / macOS / Linux). |
event | trial_start | One of trial_start, trial_end, activate, deactivate, tamper. |
nonce | 3f9a… | With trial_start only: a random id for that trial, so a trial that is reset on the same machine can be told from a new machine. |
signals | ["clock_back"] | With tamper only: short codes naming which of the software's own records did not add up (listed below). |
country | GB | A 2-letter country code, derived at the network edge — see below. |
Not sent / not stored: your name, email, IP address, precise location (region/city/GPS), hostname, user name, file paths, project or render content, a list of the software on your computer or the processes running on it, or any analytics about how you use the software. An automated test of VIZid Next's licence code inspects the reports the app builds for the user name, the host name and file paths, and fails if one is found.
The service keeps, per Request Key, the latest of these fields with first- and last-seen times, a report count, trial and integrity counters and the last 20 events with their times.
Integrity signals (tamper reports)
To keep the free trial fair, VIZid Next keeps a small signed record of when the trial started, in
a few places on the machine, and checks at start-up that those records, the system clock and the
application's own executable are as it left them. The check looks only at VIZid's own files,
registry entries and executable — never at other software, other files, or what else is running.
When something does not add up, the software sends at most one tamper report a day for that
set of signals, naming the signal codes, and on a machine without a licence it also limits
itself: for the first three signals below it asks for a licence code before opening a workspace.
A machine with a valid licence is never limited by these checks; the report is still sent.
| Signal | Meaning | Limits an unlicensed seat |
|---|---|---|
anchor_bad | A trial record on this machine failed its authentication tag (it was edited). | yes |
clock_back | The system clock is more than a day behind the last time the app ran. | yes |
binary | The application's code section differs from its build stamp. | yes |
unstamped | The executable carries no build stamp (reported only by builds that enforce the licence). | only in builds that enforce the licence |
anchor_mismatch | The trial records disagree about when the trial started. | no |
These checks never delete, disable or change anything outside VIZid's own records. At start-up the app updates its own trial records (the last-run time) and restores a missing or disagreeing copy; when a limiting signal is found it leaves them exactly as found. A false alarm (for example after restoring a backup or correcting the clock) is put right by support: send your Request Key and we will issue a code.
Where the software stores licence and trial state on your machine
%LOCALAPPDATA%\VIZid\license.json (the activation code), and the trial record in
%LOCALAPPDATA%\VIZid\seat.json, %APPDATA%\VIZid\seat.json, %PROGRAMDATA%\VIZid\seat.json and
the registry key HKEY_CURRENT_USER\Software\VIZid\Next\Seat. These hold the Request Key, the
trial start time, the trial id, the last time the app ran and the last licence code you entered
(so reactivating is one click). They are strictly necessary for the trial and licence you asked
for and are not used for anything else.
Support tickets, getting-started tips and the community (separate from the seat report)
When you write to support (email, the website form, or Help ▸ Contact Support… / Help ▸
Report a Problem… in the app) we keep what you sent — your email address, your name if you gave
it, your message, and any attachment — in VIZid's own support system, hosted in our Cloudflare
account. The app's forms always add this machine's Request Key, the product, version and
build, the operating-system family, the licence state and any current licence signal codes
(including trial_expired, and anchor_foreign for a trial record copied from another machine),
so that support can look the seat up without asking. A diagnostics text is added only while
the "Attach diagnostics" switch is on — it is on by default in Report a Problem… and off in
Contact Support… — and "Show what's attached" shows the exact text before you send. That text
holds the version, Windows version, CPU and memory figures, display sizes, the renderer's device
and last error, the licence state and the last 200 lines of the renderer's log, with your home
folder, user name and computer name replaced by placeholders; your documents are never read.
We use all of this to answer you (contract / legitimate interest). A ticket's contents are removed
two years after its last message. A support agent may ask an AI assistant to draft a reply from
your ticket and our documentation; a person reads and sends every reply. The support system looks
up your seat record by Request Key; it does not add your email to the seat record.
Getting-started tips during a trial are sent only if you ask for them, only after you confirm the address by clicking a link, and every email has a stop link. That list is separate from support and from the seat reports (consent, Art. 6(1)(a)).
The community lives on GitHub Discussions under GitHub's own terms and privacy policy. New threads may receive an automated first reply generated from our documentation, marked as such; it never asks for or repeats licence codes, Request Keys or email addresses.
How "country" works (no IP is stored)
The 2-letter country is determined by Cloudflare at the edge, from the connection, and is the only location signal recorded. The activation service's code never reads your IP address into the report and never stores it — only the coarse country code is kept. The connection itself is carried by Cloudflare's network under Cloudflare's own terms. This is deliberate data minimisation.
Why we collect it (legal basis)
The legal basis is legitimate interest (Art. 6(1)(f) UK GDPR / GDPR; Recital 47 names fraud prevention as such an interest): operating a paid product, offering a free trial, and preventing licence abuse. The data is the minimum needed to count live licences and trials, see the broad regions of use, and notice a trial that has been reset or a copy that has been altered. Because the machine identifier is pseudonymous and no IP or personal data is retained, the privacy impact is low. A transparency notice is shown in the software beside the button that starts the trial; the trial-start report is sent only after that button is pressed. An integrity report can be sent at start-up before any screen when the software's own records already do not add up.
Retention
Seat records are kept while a licence or trial is active and for a short administrative period after, then deleted.
Your choices
- Opt out of every report: set the environment variable
VIZID_NO_TELEMETRY=1before launching the software. Activation and the trial still work fully offline; only the reports — includingtamper— are skipped. (Intended for air-gapped / enterprise deployments.) - Object / access / erasure: because the only identifier is a machine hash, you can ask us to delete the record for your machine by sending us your Request Key (in VIZid Next: Help ▸ Licence & Trial…; in the VIZid Suite: VIZid Settings → Activation).
Contact
Data controller: VIZid (nstreamAI). To exercise any of the rights above, contact support@vizid.app with your Request Key.