On this page
Admins and owners can find and erase the logs that name one player, and delete the logs one key sent.
Erase one identifier or IP address
- Type one identifier with its type, such as
license:abc123. The types arelicense,license2,discord,steam,fivem,xblandlive. For an IP address, typeip:followed by the address. A bare value is refused. - The panel finds the matching logs and counts them.
- Confirm by typing the same identifier again.
What it matches
Every stored log of the team that names the identifier as the player or the target, in an attribute value, or as a whole word in the message. For an IP address, it matches the hashed token for that address wherever it appears. The address itself is never sent to storage.
How fast logs go
- From the moment you confirm, the matching logs no longer show in search or in any other read, including exports and alerts.
- The logs are then deleted, usually within minutes. It waits while logs from the delivery queue are being stored or another deletion is running.
- Deleted logs leave storage as it compacts, and older logs are cleared by a weekly maintenance run, so within about two weeks.
- Copies in the nightly backup (kept 8 days) and the hourly archive (kept 7 days) expire on those schedules. If a backup is ever restored, the erasures of the last 9 days are applied again from a list of deleted log ids that holds no identifier.
- Your team's unexpired exports are deleted too.
- Plan storage use does not go down after an erasure.
What is kept
The identifier itself is never stored. The erasure record keeps a keyed hash of it, who asked, when, and the counts, for 380 days.
Saved views and alert rules that mention the identifier are listed for you and are not changed. Remove the identifier from them yourself.
A team can run one erasure at a time, and 20 a day.
Export everything about one identifier or IP address
To see what the team holds about one player before you erase it, or to answer a player who asks, start a subject access export from the same place. See Exporting logs.
Delete every log one key sent
On the API keys tab, you can delete every log one key sent, or only those sent since a time you choose. Use it after a key leaked. It is the same job as an erasure.
Other ways logs are deleted
Retention, dataset deletion and team deletion keep deleting logs automatically; see fxvault Logs. There is no legal hold for logs. To ask for one, contact Clouduxe support; it is handled outside the panel, and deletion keeps running until then.