Trust

Privacy & data handling

Exactly what the scanner reads, what leaves the PC, how players are pseudonymised and how long reports are kept.

DUXAC is designed so that a player can agree to a PC check knowing exactly what it involves. The formal notice is on the privacy page; this page explains the mechanics.

Nothing is scanned before the player accepts the consent screen. It shows the community's name, its request note and consent text, and every check with the data it reads (the "Reads" lines in the Checks reference). Declining ends the scan and notifies the staff member who created it.

What the scanner reads locally#

Each check reads only what its consent line states: for example the list of running programs, file names in specific folders, execution history records, driver and service lists, DNS cache and browser-history domains, and system security settings. Reading happens on the PC.

What leaves the PC#

Only two things are uploaded, over HTTPS with signed requests:

Findings: indicators that matched a signature or a check rule. Each has its check, signature id, category, severity, confidence, a short title and detail, a small evidence object (at most 4 KB of JSON, for example the matching path and a timestamp) and when the artefact was observed.
Minimal system information: Windows version and build, uptime, administrator status, CPU, GPU and RAM summary, whether it is a virtual machine, whether FiveM is installed or running, the local clock, and the hardware reference described below.

Never uploaded: file contents, documents, photos, messages, passwords, browsing history beyond matching domains, or full process lists.

Paths in findings are reported with the Windows user name removed: C:\Users\alex\AppData\Roaming\... becomes %APPDATA%\..., and other paths under the profile become %USERPROFILE%\....

The hardware reference#

To let a community recognise the same PC across scans, the scanner computes HMAC(hwidKey, hardware identifiers) on the PC. The key (hwidKey) is derived per workspace by the API. As a result:

the hardware identifiers themselves are never sent;
the same PC yields the same reference within one community, so its scan history can be linked;
the same PC yields a different reference in another community, so players cannot be tracked across communities.

Who can see a report#

The members of the workspace that created the scan, according to their role, and DUXAC administrators with the scans.read permission for support and abuse handling. Actions in a workspace are written to its audit log.

Retention#

Each report gets a deletion date when it completes, based on the workspace's plan. Staff with the right capability can delete a scan earlier.

Nothing stays behind#