Privacy Policy

This policy explains what personal data MonoAdmin handles, why, how long we keep it, who can see it and what rights you have. It is written to follow the Data Privacy Act of 2012 (Republic Act No. 10173) of the Philippines and its implementing rules, and it gives people in the European Union, the European Economic Area and the United Kingdom the rights they have under the GDPR as well. You can reach our Data Protection Officer at hello@monoadmin.net.

MonoAdmin works with two groups of people, and the rules are different for each:

• Account holders: server owners and their staff, and anyone who visits our website or the panel. For their data, MonoAdmin decides why and how it is used. We are the “personal information controller” (the “controller” in EU and UK law).
• Players on servers that use MonoAdmin. For their data, the server owner decides what is collected, and we handle it for the owner. The owner is the controller and MonoAdmin is the “personal information processor” (the “processor”). See Players.

The Short Version

• We collect what we need to run accounts, sign-in, teams and billing, and what a server owner switches on for their players.
• We do not sell personal data. We do not show ads or build advertising profiles.
• This website sets no cookies of its own and has no analytics. Cloudflare, which delivers it, may set a strictly necessary security cookie. The videos on the home page and in the documentation load from YouTube only when you press play. The panel sets only the cookies it needs to keep you signed in.
• When something breaks, an error report goes to Sentry, with no account, no cookie and no tracking identifier. See Error Reports.
• We send service emails (security, billing, team and server notices), and occasional product news. Product news is on by default, and you can turn it off in Account > Notifications or with the unsubscribe link in any product news email. See Emails and Discord Messages.
• The panel has no button to delete your account or export your data. Write to hello@monoadmin.net and we answer within 30 days.
• MonoAdmin support can open a session as your account, for at most 30 minutes, only to help you or to look into abuse or a security problem. See below.

Who We Are

MonoAdmin is a cloud admin platform for FiveM game servers. There is no separate company name: MonoAdmin is the name we operate under. For anything about your privacy, including requests to see, correct or delete your data, write to hello@monoadmin.net.

What We Collect About You

Visiting This Website

The marketing website and the documentation set no cookies of their own and use no analytics, advertising or tracking scripts. They load no fonts or scripts from other sites. Apart from a video you choose to play (below), the one request they make to another site is an error report to Sentry, and only when a script on the page fails (see Error Reports). The site is served through Cloudflare, which may set a strictly necessary security cookie and, like any network that delivers web pages, sees your network address, your browser and the page you ask for. Prices on the pricing page are read from Tebex when we build the site, so nothing about you is sent to Tebex when you visit it.

The home page and the Quick Install page of the documentation each show a video that is hosted on YouTube. Until you press play, a video is a picture served from our own address, and nothing is sent to YouTube. When you press play, the player loads from YouTube’s privacy-enhanced mode (youtube-nocookie.com). From then on Google, which runs YouTube, receives your network address, your browser and the page you are on, may store data in your browser, and its own privacy policy applies. We do not control it.

Creating an Account

When you sign up we collect your display name, your email address and a password. The password is stored only as a salted argon2id hash, so nobody at MonoAdmin can read it. Sign-up is protected by a Cloudflare Turnstile check, which sends a challenge token and your network address to Cloudflare.

Until you open the link in the confirmation email, which works once and for 24 hours, your sign-up is held as a pending sign-up. If you never confirm, it is deleted after 24 hours.

An account also holds the choices you make: your theme, time zone, notification settings, and a profile picture. An uploaded picture is cropped and re-saved as a small 128 pixel image, and the original is not kept. If you do not upload one, your picture can come from the face of the game player you linked, from your Discord picture if you linked Discord, or from the Discord or Steam picture of that player. We keep our own small copy of it.

Signing In With Discord

If you sign in with Discord or link your Discord account, we ask Discord for your Discord ID, username, display name, email address, whether the email is verified and your avatar. We store your Discord ID, username and a small copy of your avatar. We use Discord’s access token once to read your profile and do not keep it. Signing up with Discord needs a verified Discord email, and your account is then created with that email address and the display name Discord gives us.

Two-Factor Sign-In

If you turn on two-factor sign-in, we store the secret of your authenticator app, encrypted, and your recovery codes, as hashes only.

Sessions and Security Activity

Each time you sign in we record a session with your network address, your browser and device description and the times it started and was last used. We also keep a security activity history of sign-ins, failed attempts, password and email changes, two-factor changes and Discord links, each with your network address and browser. You can see both in the panel.

When you sign in from a network you have not used for 90 days, we email you, and by Discord message if you chose that, with the time, the approximate place, the address and the browser. The approximate place comes from a location database file that our servers read themselves, so the address is not sent to any outside service.

Teams and Invitations

When an owner or manager invites someone, we store the invited email address and send an email to it, even if that person has no account. The invitation can be sent again, a few times an hour at most. An invitation works for 7 days. The invitation record, with the address, stays with the project until the project is deleted. The owner and members who can manage members can see the email addresses of the project’s members. A project also keeps the identifiers of a staff member’s game account if they link it for the in-game menu, the audit logs of their actions, with the address they came from, and daily totals of their activity for the Staff Activity report. A player who files a report in the game sees the display name of the staff member who answers it.

Your Game Server

The owner’s game server connects to MonoAdmin from a network address, which we store with the link. We also keep a record of each connection of the server, with the address, the resource version and the server’s name, for 180 days.

Payments

Paid plans are bought on Tebex’s own checkout, and Tebex collects your payment details. The checkout opens over the panel, but it is Tebex’s page in a frame: what you type in it goes to Tebex, and MonoAdmin never sees your card number. When the owner starts a checkout, we send Tebex the plan, a reference to the project and a single-use checkout code, the pages to return to and the buyer’s network address. Tebex then asks the buyer to sign in with a Cfx.re account before checkout. Tebex tells us about each payment, refund and dispute. We keep: the Tebex transaction ID, the plan, the amount and currency, the email address used to pay, whether it was a renewal, the dates, and the subscription’s reference. Tebex’s full notices are kept for 1 year. The payment records are kept for accounting, with no fixed end date, even after a project is deleted, no longer attached to the project. Checkouts that were never paid are deleted after 30 days.

Getting the Resource

The MonoAdmin resource is a free package on our Tebex store, and Cfx.re delivers it. To claim it, you open our store’s page for it (the panel’s Claim on Our Store links there), sign in at Tebex with your Cfx.re account and go through Tebex’s checkout, under Tebex’s own privacy policy. MonoAdmin sends Tebex nothing about you for a claim. Cfx.re then adds the resource to that account’s granted assets on portal.cfx.re, where you download it. When your server starts the resource, Cfx.re checks that the server’s license key belongs to the same account. That check happens under Cfx.re’s own privacy policy, and MonoAdmin takes no part in it. MonoAdmin is not told who downloads the resource or which servers run it, apart from the servers you link to a project (see Your Game Server). When Tebex sends us a notice of a claim, as it does for orders on the store, the notice holds the details Tebex has for the buyer: name, email address, network address, country and Cfx.re username. We act on nothing in it and keep it for 1 year, like every other Tebex notice.

Emails and Discord Messages

We send service emails: sign-up confirmation, password reset, security alerts, team invitations and changes, billing notices and server notices (for example when a server goes offline). You cannot switch these off, because they keep your account safe and working.

We also send occasional product news by email: new features and offers. It is on by default for every account. You can turn it off at any time in Account > Notifications, or with the unsubscribe link at the end of any product news email. Turning it off stops only product news, and service emails keep arriving. Product news is the only marketing we send, and we send no other newsletters.

Our emails are sent from a mail server that MonoAdmin runs itself. If you link Discord, we also send some of the service notices as Discord messages, which you can turn off at any time in Account > Notifications. We keep a record of each message sent for 30 days. A record of each product news email sent (the address, the campaign and when) is kept for 1 year, so that unsubscribe links keep working.

Customers of Our Earlier Service

We hold the email address, and a name if we had one, of customers in the customer records of the earlier MonoAdmin service. These people may have no account with this MonoAdmin. We use the address only to send product news. Every one of these emails has an unsubscribe link, and an address that unsubscribes is kept only as a do-not-email record, so that it is not emailed again. To have your address deleted from this list, write to hello@monoadmin.net.

When You Write to Us

If you write to hello@monoadmin.net, we keep your message, your address and our replies for as long as we need to deal with your request and any follow-up.

Our Own Logs

Our servers write an operational log of requests, whether they come from the panel, from a game server or from a player’s game: the time, the address requested, the result, the network address, and account or project IDs when known. Warnings and errors are also saved in a database table, which staff use to fix problems and which is cleared after 30 days. We do not use these logs for anything but running and securing the service. The plain log files are kept for 30 days, then deleted. Errors are also sent to an error-reporting service, as the next section says.

Error Reports

When something fails, a report goes to Sentry (run by Functional Software, Inc., in the United States) so that we can find the fault and fix it. Reports come from four places: the panel and this website, in your browser, when a script on the page fails; MonoAdmin’s own servers; and the resource on a customer’s game server, which sends its errors through MonoAdmin’s servers (the resource holds no address or key for Sentry). A report holds:

• the error message and its stack trace;
• the page address, without anything after a ? or #, and with the secret part of a link, such as a password reset or an invitation, replaced;
• the type of browser and operating system, and the version of MonoAdmin;
• for errors in the panel, on our servers and in the resource, the project’s number (its internal ID, not its name), and for the resource also the versions of the resource and of the 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 reports player names, identifiers or chat, and it does not report an error in a project’s own revive code.

We attach no account, email address or name to a report. The report script is served from our own address, sets no cookie and keeps nothing in your browser. Nothing else is sent: no analytics, page views, recordings of your screen or performance measurements. Sentry does not store IP addresses, or the place it would work out from one, and its data scrubbers are switched on. It keeps reports for up to 90 days.

Why We Use Your Data

What we do	Why	Our legal basis
Create and run your account, sign you in, run projects and teams	To give you the service you asked for	Contract
Take payments, keep payment records, handle refunds and disputes	To sell and account for paid plans	Contract and legal obligation
Send security, billing, team and server notices	To keep your account safe and keep you informed	Contract and legitimate interests
Keep sessions, security activity, logs and rate limits, check sign-ins with Turnstile	To protect accounts, find abuse and keep the service working	Legitimate interests
Send error reports to Sentry	To keep the service working and fix faults	Legitimate interests
Let our support staff help you and look into abuse	To answer you and protect other people	Legitimate interests
Link Discord, use a profile picture you upload	Because you chose to	Consent, which you can withdraw
Send some of these notices as Discord messages once you link Discord	To tell you what is happening in the channel you linked	Legitimate interests. You can turn them off at any time
Send product news, to accounts and to customers of the earlier service	To tell you about new features and offers	Legitimate interests. You can object or opt out at any time
Follow the law and respond to lawful requests	To meet our legal duties	Legal obligation

In the Philippines these map to the criteria for lawful processing in the Data Privacy Act. Under the GDPR they are the legal bases of Article 6.

Players

This section is for people who play on a FiveM server that uses MonoAdmin, and for people who apply to such a server’s whitelist. You do not have a MonoAdmin account and you did not choose MonoAdmin, so please read it.

Who Is Responsible

The owner of the server decides which MonoAdmin features are on, which kinds of Server Logs are kept, who on the team can see what, and what the whitelist asks. For the data about players that results, the server owner is the controller and MonoAdmin is the processor. We store and handle the data for the owner, on the owner’s instructions, under our Data Processing Addendum. We do not use it for advertising, we do not sell it, and we use it for our own purposes only to run and protect the service.

What Can Be Processed

What is collected depends on the owner’s settings and on the framework the server runs. At most, it is:

• Identifiers. The name a player uses, and the identifiers FiveM provides: Rockstar license, Steam, Discord, Cfx.re and Xbox or Microsoft IDs. Also hardware tokens, which are identifiers FiveM derives from a player’s device (they carry no name). They are used for sticky bans and to find linked accounts. The Discord ID is the one the player’s own Discord client reports.
• IP addresses. Stored with each visit, and shown in full only to the project owner and roles with the View Player IPs permission. Everyone else sees them masked, and the in-game menu never shows them. We look an address up against a location file that our servers read themselves, so the address is not sent anywhere. The owner sees counts per country and city, not names. No MonoAdmin feature uses an address to identify a player, link accounts or match a ban. 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. An address is cleared from a visit after 90 days at the latest. A player’s own game also connects to MonoAdmin, so the address appears in our request log and in Cloudflare’s, and in the Player Monitor relay while a stream runs. See Our Own Logs.
• Visits. When a player joined and left, for how long, the reason the game gave and the last position.
• Positions and routes. Where the player was, from the game server’s own snapshots: place, heading, whether in a vehicle, what they were doing and the routing bucket. While a player is online their own game also reports position, health, armour, vehicle and activity.
• Pictures. A picture of the player’s character’s face, captured in the game when the player joins, and refreshed about once a week, and the Discord or Steam profile picture that we fetch for a player who has no face picture. These are used as profile pictures in the panel.
• Screenshots. Staff with the permission can capture what a player’s game shows. A player who opens the /report window can attach a screenshot, and it is sent only if they keep the option on and send the report.
• Player Monitor. A live view of the player’s game, sent from the player’s game to a staff member’s browser through a relay that MonoAdmin runs. It is not recorded and not stored.
• Server Logs. Connections, disconnects, kicks, staff actions, chat messages, commands with their arguments, item events, money events, public phone posts and ended calls (the numbers, the length and whether it was answered), and the lines the owner’s own scripts post to a webhook. A log line holds no IP address. Private phone messages are never logged.
• Moderation. Notes, warnings, bans, kicks, mutes and community service, with the reason and who gave them, and reports with their messages and attachments.
• Discord tickets. If the owner uses the ticket bot, the messages written in ticket channels, with the author’s Discord name and ID, attachments and edits, and a transcript. A transcript can also be posted to a channel in the owner’s Discord server and sent by Discord message to the person who opened the ticket. The bot can send ticket messages to a player who has no MonoAdmin account.
• Whitelist applications. The Whitelist ID, which is tied to the player’s Rockstar license, and the answers to the questions the owner wrote. The request also keeps the player’s name, their Discord ID if the game reported one and the account identifiers shown at the last attempt. MonoAdmin’s form does not ask for a name, email or Discord. The owner’s questions might.
• Analytics. Job changes and money going in and out on ESX, QBCore and Qbox, what players were doing over time, and how many players, vehicles and objects the server had.
• Imports. If the owner imports a txAdmin backup, the players, bans, warnings, notes and whitelist in it.

Character, inventory and owned-vehicle data is not copied to MonoAdmin. It stays in the owner’s own game database, and MonoAdmin reads and edits it through the resource when staff with the permission open it. When staff delete an owned vehicle, MonoAdmin keeps a backup of that vehicle’s record for 60 days so the deletion can be undone.

Where It Comes From

From the MonoAdmin resource on the owner’s game server and from the player’s own game; from the staff using the panel or the in-game menu; from Discord, for tickets when the owner uses them and for public profile pictures; and from Steam’s public profile pictures. Players are never asked to create an account.

Who Sees It

The server owner and the team members the owner gave a role that allows it. MonoAdmin staff see it only when needed to support the owner, to look into abuse or to keep the service safe. Looking up an address needs a recorded reason.

What Players Are Told

MonoAdmin does not itself tell players in the game that they are tracked, that their face was captured, or that a staff member may take a screenshot or watch the screen. The only privacy line we put in the game is one in the /report window. The server owner has to tell their players what is collected, and our terms and the Data Processing Addendum say so.

How Long It Is Kept

Data	How long
Player records, identifiers, hardware tokens and linked accounts	Until the project is deleted
Pictures of a player (face, Discord, Steam)	With the player record, until the project is deleted
Punishments, notes, reports and their messages	Until the project is deleted
Discord ticket files and transcripts	Until the project is deleted
Approved whitelist entries	Until the project is deleted or staff remove them
Whitelist requests that were never approved	90 days after the last attempt
Visits	At least 60 days and at most about 90 days
IP address on a visit	Cleared after 90 days at the latest
Positions and routes, Analytics, Server Logs, audit logs, webhook logs, Player Locations	Readable for the owner’s plan history, and deleted for good about 60 days after they were recorded. They are removed in batches, so a record can outlast that by a few days
Screenshots and report attachments	Deleted when they expire, between 7 and 60 days depending on the owner’s plan when they were uploaded, or sooner if staff delete them
Backups of deleted vehicles	60 days
txAdmin backup file uploaded for an import	Deleted when the import finishes or is discarded, and after 24 hours if never started
Player Monitor video	Not stored

The owner can delete staff notes and files. MonoAdmin has no screen for erasing one player’s record. All of a project’s data is deleted when the project is deleted. The Plans and Limits page lists each plan’s history, and Data, Privacy and Retention in the docs describes the same rules for owners.

Your Rights as a Player

Start with the server’s owner: they decide what is kept and can answer your request to see, correct, delete or restrict your data, or your objection. Use the way the server contacts its players, such as its Discord or its website.

If you cannot reach the owner, or you are not sure who it is, write to hello@monoadmin.net. Tell us the name of the server and your name in the game, and your identifiers if you know them. We pass your request to the owner and help them answer it, and we tell you what we can do ourselves. Because there is no screen for erasing a single player, we help the owner by hand. An owner may have a lawful reason to keep a ban or a record of what happened. We answer within 30 days and tell you what we did, or what we could not do and why. MonoAdmin has no appeal process of its own; appeals are for the server’s staff.

Sticky bans work on identifiers and hardware tokens: a ban on one account can also block accounts that share an identifier, or two or more hardware tokens, with it. The owner chooses to use bans, and the staff decide who is banned.

Whitelist Applications

The public application page, at app.monoadmin.net/apply, shows the owner’s server name and logo and the text “Powered by MonoAdmin”. It is protected by a Cloudflare Turnstile check. The owner decides the questions. A request that was never approved is deleted 90 days after the last attempt.

Children

GTA V and FiveM are not made for children, and we do not know a player’s age. The server owner is responsible for who plays on their server and for the rules that apply to the data of young players.

When MonoAdmin Staff Look at Your Account

MonoAdmin support can open a session as your account for at most 30 minutes. It does this only to answer your support request or to look into abuse or a security problem. Opening one needs a recorded reason.

• Such a session cannot change your password, email, two-factor, Discord link, sessions or billing, and cannot send invitations. It can do support work inside a project, such as reading settings and seeing players.
• MonoAdmin staff sign-ins as your account are recorded in MonoAdmin’s staff log with the reason given, and so is every change staff make in the back office and every address lookup. Changes made inside such a session appear in the project’s Audit Logs under your account’s name, and the staff member behind them is recorded for MonoAdmin’s own use. Apart from address lookups, looking at data is not logged.
• It is not shown in your Sessions list or your security activity, and you are not notified each time.

MonoAdmin staff work in a separate back office. Every sign-in needs a password and an authenticator code, and every change they make in the back office is recorded with a reason. Staff can see accounts, projects and their settings, sessions and the addresses seen, and player visits with IP addresses masked, and can reveal one only with a recorded reason.

Who We Share Data With

We share personal data only with:

• The people on your project, as the owner’s roles allow.
• Service providers that help us run MonoAdmin: Cloudflare, Backblaze (storage for screenshots and other files), Discord (for sign-in, tickets, messages and profile pictures), Steam (profile pictures), Sentry (error reports) and the provider that runs our servers. The Sub-processors page lists them.
• Tebex, which sells paid plans to you as reseller and merchant of record and is responsible for your payment data under its own privacy policy. It also hands out the free package you claim the resource with. It is an independent provider, listed apart from our service providers on the Sub-processors page. What we send it is under Payments, and what a claim involves is under Getting the Resource.
• Authorities, when the law or a valid legal request requires it, or to protect people from harm.
• A successor, if MonoAdmin is taken over, who must keep to this policy.

We do not sell personal data and we do not share it for advertising.

How Long We Keep Account Data

Data	How long
Pending sign-ups that were never confirmed	24 hours
Ended sessions	7 days
Security activity of an account	180 days
Records of emails and Discord messages sent	30 days
Records of product news emails sent (the address, the campaign and when)	1 year
Mailing list entries of customers of the earlier service	Until you ask us to delete the address. After you unsubscribe, only as a do-not-email record
Game server connection records	180 days
Audit logs	Readable for the project’s plan history, and deleted for good about 60 days after they were recorded. They are removed in batches, so a record can outlast that by a few days
Our request log files	30 days
Staff Activity daily totals	365 days
Warnings and errors in our own log	30 days
Error reports, held by Sentry	Up to 90 days
Payment records (transaction, plan, amount, email used to pay)	Kept with no fixed end date, for accounting, also after a project or account is deleted
Tebex notices	1 year
Checkouts that were never paid	30 days
Invitation records	Until the project is deleted
The account itself	Until you ask us to delete it
Our staff log, which records what MonoAdmin staff change	Kept

We do not delete inactive accounts automatically.

Backups. Data you delete, or that we delete for you, can stay in our backups for up to 30 days before it is overwritten.

Deleting Your Account and Getting a Copy of Your Data

The panel has no button to delete an account or to export your data. Write to hello@monoadmin.net from the email address of the account. We answer within 30 days and tell you what we did, or what we could not do and why.

What deleting an account removes. Every project the account owns is deleted, with everything in it, including its player data. The account leaves every team. Its sessions, security activity, pictures, game identifiers and pending sign-ups are deleted, and the email address, display name, password, Discord link, two-factor secret, time zone and theme on the account are cleared, so the account shows as “Deleted user”.

What it keeps. Display names that were already copied into logs and moderation records, such as an audit entry or a punishment, stay and are not rewritten. Audit entries about you in other projects also keep the address you acted from until they are deleted, about 60 days after they were recorded. Payment records stay. Our staff log, which records what MonoAdmin staff did, stays. The entry for the deletion keeps only a masked address, but earlier entries about the account, such as a changed email address, can hold it in full. Platform bans on email addresses and Discord accounts are kept as hashes; a ban on a range of network addresses is kept as the range.

If you want to keep a project, ask us to move it to someone else before you ask us to delete your account. Deleting an account does not cancel a Tebex subscription: cancel it at Tebex first.

A copy of your data. We send you, as a file, the data in your profile, your sign-in sessions, your security activity, your project memberships and your payments. For a project, the panel can export reports as an HTML page, JSON or a ZIP with their files. For anything else about a project, ask us.

Your Rights

Under the Data Privacy Act of 2012 you have the right to:

• be informed about how your data is processed;
• object to the processing of your data;
• access your data;
• have wrong data corrected;
• have your data erased or blocked, when the law gives you that right;
• data portability: to receive your data in a common format;
• be compensated for damage caused by data that is inaccurate, unlawfully obtained or misused; and
• file a complaint.

If you are in the EU, the EEA or the UK you also have the GDPR rights: access, rectification, erasure, restriction of processing, objection, portability, and withdrawing consent at any time, which does not affect what was done before.

How to use them. Write to hello@monoadmin.net. We may ask you to reply from your account’s email address, or to give details, so we are sure it is you. It is free. We answer within 30 days and tell you what we did, or what we could not do and why. For data about players, see Players first.

Complaints. You can complain to the National Privacy Commission of the Philippines at privacy.gov.ph, or, if you live in the EU, the EEA or the UK, to your local data protection authority. We would like the chance to fix it first, so please write to us too.

How We Protect Your Data

• Passwords are stored as salted hashes. Sign-in sessions and other long-lived secrets are random tokens, and we store only a hash of them. A password reset or sign-up link, and a one-time code, also sit in our outgoing mail queue, in full, until the record is deleted 30 days after it was sent; each of them stops working long before that.
• Two-factor secrets and the tokens of a customer’s own Discord bot are encrypted.
• Connections to the panel, the game gateway and the website use HTTPS.
• Each project’s data is kept apart from every other project’s, and roles are checked on every request.
• IP addresses are masked for people who should not see them.
• Screenshots, attachments and Discord ticket files are stored under long random addresses that cannot be guessed, and the panel gives an address only to staff allowed to see that file. Anyone who has an address can open the file until it is deleted or expires, so staff should share it with care. Files that are not images are always downloaded, never opened as a page.
• MonoAdmin staff need a password and an authenticator code, and what they change in the back office is recorded with a reason.

How MonoAdmin Is Secured describes this in more detail. No system is perfectly secure, and we cannot promise that nothing will ever go wrong.

Data Breaches

If a breach of personal data happens and the law requires us to tell people, we tell the affected people and the National Privacy Commission, within 72 hours of knowing about it. We tell affected customers (server owners) without undue delay, so they can meet their own duties.

Moving Data Across Borders

You and the players on a server can be anywhere in the world, and the providers we use, such as Cloudflare, work in many countries. The files we store (screenshots, attachments, Discord ticket files and txAdmin uploads) are kept with Backblaze in the United States, and error reports are held by Sentry in the United States. Your data can therefore be handled in countries other than your own. Where the law requires a safeguard for this, we put it in place. Ask us if you need to see it.

Children

You must be at least 16 to create a MonoAdmin account. We do not knowingly keep an account of someone younger, and we close or delete it when we learn of it. For players, see Players.

Cookies

The website sets no cookies of its own, though Cloudflare, which delivers it, may set a strictly necessary security cookie. The panel sets only strictly necessary cookies. The Cookie Policy lists each of them, and the browser storage keys the panel uses.

Changes to This Policy

We may update this policy. For a material change we post it on this page and email the project owners at least 14 days before it takes effect. The date at the top of this page says when it was last changed.

Contact

Write to hello@monoadmin.net for anything about this policy or your data.