Data, Privacy and Retention

To moderate a server, MonoAdmin has to remember things about the people on it. This page lists what is stored about your players and about your staff, who can see IP addresses, how long each kind of data is kept and how to remove a project’s data. The limits in the retention rules come from your plan only where the page says so. For how the data is protected, see How MonoAdmin Is Secured. The legal side is in the Privacy Policy, which also covers players on your server.

What MonoAdmin Stores About Your Players

• The player record. The name the player last used, when they were first and last seen, and their total playtime.
• Identifiers. The identifiers FiveM provides for a player: the Rockstar license, Steam, Discord, Cfx.re account and Xbox or Microsoft identifiers. Also hardware tokens, identifiers FiveM derives from a player’s device (they carry no name). They are used to find linked accounts and for sticky bans. See Sticky Bans and Linked Accounts.
• Visits. Each time a player joins and leaves: when, for how long, the reason the game gave and their IP address.
• Where they went. The Tracking route: position, heading, time, whether they were in a vehicle, what they were doing and their routing bucket. The points come from your game server’s own snapshots, not from the player’s game. See Server Map and Player Tracking.
• Activity and economy. What players were doing over time and, on ESX, QBCore and Qbox, job changes and money going in and out. These feed Analytics.
• Moderation. Punishments with their reason and who issued them, and staff notes. Linked accounts are worked out from the identifiers above, and the Linked tab shows which kinds two accounts share, not the values.
• Reports. Reports, their messages and attachments, and Discord tickets with their files and transcripts.
• Server Logs. Connections, disconnects, kicks, staff actions, chat, commands, items, money and a copy of the lines your scripts post to webhooks. You choose which of these are recorded on Features and Modules.
• Screenshots. When staff capture a player’s screen, and the screenshot a player attaches to a report they file in game.
• Pictures. The face captured from a player’s character in game, or the Discord or Steam picture MonoAdmin fetched for them.
• Server numbers. How many players, vehicles, NPCs and objects your server had over time.

Character, inventory and owned-vehicle data is not copied. It stays in your own game database, and MonoAdmin reads and edits it through the resource when staff open it. The exception is deleted vehicles: a backup is kept so a deletion can be undone. MonoAdmin does not store Player Monitor video or voice.

What MonoAdmin Stores About Your Staff

• The account. Email address, display name, theme, time zone, the Discord link, and a profile picture if they uploaded one. Passwords are stored as hashes and two-factor secrets encrypted.
• Sessions and security activity. The browser, IP address and time of each sign-in, and a history of sign-ins and security changes.
• Game identifiers. The identifiers a staff member verified by linking their game account, which the in-game menu uses to recognise them.
• Audit logs. Every staff action: who, what, to whom, the result, the time and the IP address it came from.
• Staff activity. Daily totals of actions, time in game and reports handled, from which the score is worked out. See Staff Activity and Scoring.
• Messages sent. Records of the emails and Discord messages MonoAdmin sent them.

IP Addresses

IP addresses are stored in four places: on a player’s visits, on a staff member’s sessions and security activity, on audit log entries, and with your game server’s link and connections.

Your game server’s address. The address your game server connects from is stored with its link. MonoAdmin also keeps a record of each connection of your game server, with that address, the resource version and the server’s hostname, for 180 days. The Audit Logs entry “Server link used from another address” holds both addresses involved.

Who sees a player’s full address. The project owner, and anyone whose role includes the View Player IPs permission. Everyone else sees it masked, with the last two parts hidden, as in 203.0.x.x. The masking happens on the server, so the full address never reaches a browser that may not show it. The in-game menu never shows player IP addresses, whatever the role.

Who sees a staff member’s address. Audit log addresses are masked for everyone except the project owner.

How long they are kept. A player’s address is cleared from their visits after 90 days at the latest, and the visit records themselves are removed on the schedule described below. Game server connection records are kept for 180 days.

What they are not used for. No MonoAdmin feature uses an IP address to identify a player, to link accounts or to match a ban. Bans and sticky bans use identifiers and hardware tokens only. MonoAdmin staff can look up an address, with a recorded reason, to see which accounts, servers and players were seen from it when they look into abuse.

Player Locations. The Dashboard’s Player Locations card turns addresses into counts per country and city (“Counts only, nobody is named.”). MonoAdmin looks addresses up in a location database file it downloads and reads itself, so no address is sent to an outside service. A player who cannot be placed, for example on a local network, counts as Unknown. Because a city comes from an address, members without the View Player IPs permission see countries, and only cities of at least 5 players from visits that ended before today (The Dashboard has the details).

MonoAdmin’s own staff can look up an address only with a reason, and each lookup is recorded. The Player Monitor streams through a relay so the viewer and the watched player never see each other’s address.

How Long Data Is Kept

Two numbers matter. Your plan’s history decides how far back the panel will show time-based data, and it is different for each plan. A fixed limit of 60 days applies to every plan: time-based data is removed for good once it is that old. Plans and Limits has the history for each plan.

Time-Based Data

These kinds can be read for as long as your plan’s history, and are deleted for good about 60 days after they were recorded:

• audit logs;
• Analytics data: players, activity, entities, the economy and jobs;
• Server Logs;
• Tracking positions;
• webhook delivery logs;
• Player Locations.

MonoAdmin removes them in batches, so a record can outlast the limit by a few days.

Visits are different. They are stored and deleted in 30-day batches, so a visit is kept for at least 60 days and at most about 90 days, whatever your plan. The disconnects and crashes in Analytics come from visits and follow the same rule. A player’s IP address is never kept longer than 90 days.

Files

Screenshots and report attachments are deleted when they expire. A file’s expiry is set when it is uploaded, from your plan’s history at that moment, and counted from the upload. Staff with the Delete Files permission can delete one sooner. Files from Discord tickets never expire. They stay until their report goes, and reports stay until the project is deleted. See Files.

Imported Backups

A txAdmin database backup that the owner uploads to import is kept only so that the import can run. It is deleted when the import finishes, and also when you discard it. An upload that is never started is deleted after 24 hours. What the import wrote, the players, bans, warnings and notes, is ordinary data and is kept like the rest, until the project is deleted. See Move From txAdmin.

The Token of Your Own Discord Bot

If you run Discord Tickets through your own bot, MonoAdmin has to keep the bot’s token so the bot can run. It is stored encrypted, the panel never shows it again after you save it, and it is not written to the Audit Logs. It is kept while the bot is paused, and deleted for good when you remove the bot and when the project is deleted. MonoAdmin keeps the bot’s name and application ID next to it, because the panel shows them.

Other Kinds

Data	Kept for
Backups of deleted vehicles	60 days
Whitelist requests nobody acted on (waiting or denied, with no application waiting)	90 days after the last attempt to join
Staff Activity daily totals	1 year
Security activity of an account	180 days
Ended sessions	7 days
Game server connection records	180 days
Records of sent emails and Discord messages	30 days
Records of product news emails sent (the address, the campaign and when), kept so that unsubscribe links keep working	1 year
Sign-ups not yet confirmed, and pairing codes	24 hours
Checkouts that were never paid	30 days
Payment notices from Tebex	1 year

Payment records themselves, with the plan, amount, transaction ID and the email used to pay, are not deleted when a project is. They stay, no longer attached to a project. A checkout that was paid stays with its project, for billing, until the project is deleted.

Kept Until the Project Is Deleted

These have no expiry. They stay for as long as the project exists:

• player records, identifiers and linked accounts;
• punishments, notes and reports with their messages;
• members, roles and settings;
• the whitelist’s approved list;
• Discord ticket files and transcripts.

There is no screen for erasing a single player’s record. A staff note or a file can be deleted by someone with the matching permission, but punishments, reports and player records stay until the project goes.

Error Reports

When MonoAdmin’s own code fails, a report goes to Sentry, a service in the United States, so that the fault can be found and fixed. Reports come from the panel and the MonoAdmin website in your browser, from MonoAdmin’s servers, and from the resource on your game server. A report holds the error message and its stack trace, the page address without its query, the type of browser and system, and MonoAdmin’s version. For errors in the panel, on MonoAdmin’s servers and in the resource it also holds your project’s number, and for the resource the versions of the resource and your framework.

The resource reports only when MonoAdmin’s own code fails: the name of the part that failed, the message and a few fields such as the error text, a code or a method name. It never sends player names, identifiers or chat, or an error from your project’s own revive code. It sends nothing from a player’s game or from the in-game menu, and it does not contact Sentry itself: it hands the errors to MonoAdmin over the link it already has, and it starts only when MonoAdmin’s side has error reports switched on. There is no setting for it in the panel or in server.cfg.

No account, email address or name is attached to a report. Sentry does not store IP addresses, or the place it would work out from one, and keeps reports for up to 90 days. The Privacy Policy and the Sub-processors page say the same.

Deleting a Project

Among the people on a project, only the owner can delete it, from Settings > Delete Project. It is deliberately slow.

1. Choose Delete Project. The dialog “Delete {name}?” explains that everything is deleted for good, for you and every member.
2. Choose Email Me the Code. You may be asked to confirm it is you.
3. Enter the 6-digit code from your email under Confirmation Code. It works for 15 minutes.
4. Choose Delete Project Forever.

Deleting removes the project’s players, punishments, notes, reports, logs, tracking, analytics, roles, members and settings, and the token of your own Discord bot if you saved one. The linked server stops working with MonoAdmin. It cannot be undone. Staff members’ own accounts are not deleted, they only lose access to the project.

Deleting does not cancel a Tebex subscription. Cancel it on Tebex first. See Paying and Renewing.

MonoAdmin can also suspend or terminate a project. A suspended or terminated project has its pages and game server link switched off. A terminated project is deleted 14 days later, unless MonoAdmin restores it, and the panel shows the date.

There is no way to delete your own account from the panel, and no self-service ownership transfer. Only MonoAdmin staff can do either, so contact MonoAdmin support at hello@monoadmin.net. The Privacy Policy says what deleting an account removes and what is kept.