Data Processing Agreement
Version of 2026-11-03. This Agreement is part of the Terms of Service and meets Article 28 of the General Data Protection Regulation (GDPR). The Portuguese version prevails in case of doubt.
1. Parties and roles
- Controller: the customer, owner of the FiveM server that uses SafeGuard.
- Processor: SafeGuard ("SafeGuard").
2. Subject, nature and purpose
SafeGuard processes data of the players of the customer's server only to protect the server against cheating and abuse: detect forbidden behaviour, compute risk, apply the punishments the customer configured, keep evidence and allow appeals. We use this data for nothing else.
3. Data subjects and data
Data subjects: players who connect to the customer's server and members of the customer's staff.
| Category | Examples | Notes |
|---|---|---|
| FiveM identifiers | license, discord, steam, xbl, fivem | Used to recognise the player across sessions and the customer's servers |
| IP address | — | Pseudonymised by default (keyed hash); the customer may choose not to store it or to store it in full |
| FiveM hardware tokens | — | Stored only as hashes |
| In-game name and sessions | join, leave, server | |
| Game telemetry | position, health, armour, speed, weapon, vehicle | To confirm detections; the customer can switch it off |
| Detections, risk, bans | type, confidence, technical evidence | |
| Screenshots and live frames | game screen | Screenshots kept per the customer's retention; live spectate frames are not stored |
| Replays | short picture sequences of the game screen, with health, armour and speed | Only if the customer turns them on. Created on serious detections, on bans or at staff request; they follow the screenshot retention |
| Text in screenshots | text read automatically from the image | Only if the customer turns on the menu search. Read on the API's servers, without third parties; the text is not stored, only the menu names found |
| Trust score | value from 0 to 100 and the factors used | Calculated from the data above. It only informs staff: it never decides punishments |
| Appeals | player's message, optional e-mail |
No special categories of data (GDPR Article 9) are processed.
Sharing between customers (optional). By default, one customer's data is never used for another. Two features can be turned on and off by the customer, and are the customer's instructions:
- Threat Intelligence, per organization: contributes aggregated data about a player and shows aggregated data from other participants, without revealing organization names.
- Ban network, per server: that server's automatic permanent bans count for other participants 24 hours after they are issued, and the player's FiveM account identifiers (license, license2, steam, discord, fivem, xbl, live) are compared with those of people connecting to participating servers. IP addresses, hardware tokens and manual bans are not used. Other participants see only how many communities banned the player; a refused player sees the ban reference and can appeal to the community that issued it. A revoked ban stops counting at once.
Each customer using these features decides about its own players, is responsible for its legal basis and must inform its players.
4. Duration and retention
For as long as the customer uses the Service. Retention periods are set by the customer in Settings (defaults: detections 180 days, evidence 90 days, screenshots and replays 30 days, inactive profiles 365 days) and applied automatically. When the contract ends, data is deleted within 30 days unless an export was requested before.
5. SafeGuard's obligations
- Process data only on the customer's documented instructions (the Service configuration and these Terms).
- Ensure people with access are bound by confidentiality.
- Apply appropriate technical and organisational measures (section 7).
- Help the customer answer data subjects' requests and with impact assessments, as far as possible.
- Notify the customer of a personal data breach without undue delay and at most 48 hours after becoming aware of it.
- Delete or return the data when the contract ends.
- Make available the information needed to show compliance with this Agreement and allow reasonable audits with prior notice.
6. Sub-processors
The customer authorises the subprocessors listed in the Privacy Policy (hosting, database, storage and e-mail). We give at least 30 days' notice before adding or replacing a subprocessor that processes player data; the customer may object and, in that case, end the contract. Subprocessors are bound by obligations equivalent to this Agreement.
7. Security measures
- Encrypted communication (TLS) and server requests signed with per-session keys.
- Sensitive identifiers pseudonymised or stored only as hashes; secrets and webhooks encrypted.
- Role- and permission-based access, with an audit log of every action.
- License and API keys stored only as hashes and revocable.
- Automatic retention and deletion per the customer's configuration.
8. Customer's obligations
The customer ensures it has a legal basis for the processing (usually the legitimate interest in protecting the server and other players) and informs players clearly, for example in its privacy policy or server rules.
9. International transfers
When a subprocessor is outside the European Economic Area, transfers rely on the European Commission's standard contractual clauses and/or the EU-US Data Privacy Framework.