Terms of Service.
These Terms govern your use of SentinelFX — the Discord bot, the FiveM FXServer resource, the dashboard at sentinelfx.net/dashboard, and the public website at sentinelfx.net. By using any of them, you agree to these Terms. If you don't agree, don't use the service.
- About these Terms
- Eligibility
- The service
- Accounts & authentication
- Server operator responsibilities
- Acceptable use
- Network reports & bans
- Automated & AI-assisted decisions
- Appeals
- FiveM resource terms
- Service availability
- Suspension & termination
- Intellectual property
- Disclaimers
- Limitation of liability
- Indemnity
- Changes to the service
- Governing law
- Contact
01About these Terms
These Terms are a binding agreement between you and the SentinelFX Team ("SentinelFX", "we", "us"). They work alongside — not in place of — the Privacy Policy, which explains what data we handle, and the separate rules of third-party platforms you reach us through (notably Discord's Terms of Service, its Community Guidelines, and — for FiveM operators — Cfx.re's Terms).
If anything in these Terms conflicts with a platform's own rules on that platform, the platform's rules take precedence there.
02Eligibility
You may use SentinelFX only if you meet the minimum age required to use Discord in your country (13 years old in most places; higher in some). By using the service, you confirm you meet that requirement and are legally able to enter into these Terms. If you're under the age of majority where you live, you confirm a parent or guardian has reviewed and agreed to these Terms on your behalf.
SentinelFX is not directed at children under 13. We don't knowingly collect information from them — see the Privacy Policy for detail.
03The service
SentinelFX is a community-operated network-protection service. The parts of the service we currently offer are:
- A Discord bot providing real-time moderation, raid protection, verification, threat scoring, and network-wide ban enforcement.
- A FiveM FXServer resource (the SentinelFX resource) that extends the same ban list into FiveM game servers through identifier-keyed connect-time checks.
- A web dashboard for server operators and the SentinelFX Team.
- A public website and any supporting APIs or status endpoints.
The service is provided free of charge. We don't sell it, we don't sell your data, and we don't run ads. We may add, change, or remove features at any time.
04Accounts & authentication
We don't create traditional accounts. You sign in to the dashboard using Discord OAuth. Your Discord account remains yours and is governed by Discord's own terms. We don't receive or store your Discord password.
- You're responsible for everything that happens under your Discord account while signed in to SentinelFX.
- Keep your Discord account secure (MFA, strong password, don't share tokens).
- If you believe your account has been compromised, revoke the SentinelFX OAuth authorization in Discord's user settings and contact us.
05Server operator responsibilities
If you add SentinelFX to a Discord server or register a FiveM resource on your FXServer, you're the operator of that server for the purposes of these Terms. By doing so, you confirm that:
- You have the authority to add the bot or install the resource on that server.
- You will operate the server in compliance with Discord's and (if applicable) Cfx.re's rules.
- You'll configure SentinelFX honestly — don't give a Moderator role to people who aren't moderators to game the threshold system.
- You understand bans you issue in-server may be escalated to the network by your staff via
/report, and that FiveM in-game bans may be forwarded to us depending on the ban mode you select (see §10). - You're responsible for notifying your members that SentinelFX is in use — our Privacy Policy explains what data flows where.
06Acceptable use
Whether you're a regular member, a moderator, or an operator, you must not use SentinelFX to:
- Break Discord's Terms, Community Guidelines, or any applicable law.
- Harass, doxx, threaten, or target individuals — including through reports, appeals, staff notes, or dashboard comments.
- Submit knowingly false reports, brigade the report queue, or coordinate reports to punish a user for something that wasn't actually a rule-break.
- Evade a network ban (alt accounts, HWID spoofing, identity laundering) or help someone else evade one.
- Interfere with the service — probing for vulnerabilities outside our security.txt disclosure policy, scraping at abusive rates, reverse-engineering to extract secrets, or attempting to bypass rate limits and authentication.
- Upload malware, token grabbers, phishing URLs, or other malicious payloads to any SentinelFX surface — including report evidence fields, appeal statements, or staff notes.
- Impersonate SentinelFX, its staff, or the operators of other network servers.
- Resell, sublicense, or incorporate SentinelFX into a commercial product without our written permission.
- Use the service to build a competing ban-sharing network, or to export or mirror our ban list for use outside the network.
07Network reports & bans
Server moderators can submit users to SentinelFX for network-wide review via /report. Approved reports result in a network ban that applies across every connected Discord server and every FXServer running the resource (regardless of its ban mode — the mode controls outbound, not inbound).
- Not every report is approved. The SentinelFX Team reviews the evidence and can deny, request more information, or approve.
- Approval decisions are at our discretion, based on the evidence presented, the reported user's prior history, and the severity and plausibility of the behaviour described.
- Network bans are applied at the identifier level (Discord user ID; and for FiveM — license, Steam, Discord, FiveM, xbl/live, and HWID fingerprints). Ban evasion through any of these is itself a violation (§6).
- False or bad-faith reports may result in the reporter — and in serious cases, the operator whose staff filed them — being removed from the network.
08Automated & AI-assisted decisions
SentinelFX operates a hybrid auto-action engine. A deterministic rule engine — which we control end-to-end — scores every report against objective signals; on reports it can't decide on its own, a structured case summary may additionally be reviewed by an AI sub-processor (currently Anthropic) for a second opinion, under strict safety rails. Full technical detail, including the exact data sent and the confidence thresholds required before any action is taken, is in our Privacy Policy (§7).
- No action is final without a human option. Every network ban — including AI-influenced auto-bans — is appealable, and every appeal is reviewed by a human staff member, never by the AI.
- AI recommendations are not binding. The rule engine and safety rails always have priority: the AI cannot override protective gates, cannot recommend a ban on insufficient evidence, and cannot raise an action above the rule engine's floor without high-confidence agreement.
- You can request a human-only review. State this in your appeal and we will honour it. Your right under applicable law not to be subject to a purely automated decision with legal or similarly significant effects is preserved.
- The AI layer is kill-switchable. Network admins can disable the AI judge at any moment from the dashboard; the rule engine keeps operating as before.
- The AI's reasoning is logged. Every AI-influenced action records the model used, its confidence, and its written rationale to the audit trail. That reasoning is available to reviewing staff and, on request, to the affected user through the appeal thread.
09Appeals
If you receive a network ban, you can appeal it via /appeal in any SentinelFX-protected server you still share with the bot, or through the dashboard if you don't share a server with us. Appeals are reviewed by the SentinelFX Team, and the decision (approve or deny) is final for that appeal.
- Only one active appeal per ban at a time.
- Appeals must be made by the banned user. Third-party appeals aren't accepted.
- Repeatedly submitting identical appeals, or using the appeal field to abuse or threaten staff, is grounds for denial and may extend the ban.
10FiveM resource terms
If you install the SentinelFX FXServer resource, the following apply in addition to the rest of these Terms.
Distribution
The resource is distributed exclusively through Tebex / CFX Asset Escrow, free of charge. The CFX runtime checks at boot that the Cfx.re account behind your server's licence key owns an entitlement to the asset; you must claim the asset on Tebex while signed in to the same Cfx.re account that owns your licence key. The entitlement attaches to that account permanently and cannot be transferred. Re-distributing or re-uploading the resource elsewhere is not permitted.
Ban mode
You pick one of three modes when you register your server:
- Off — your FXServer enforces network bans but doesn't send its own in-game bans to us.
- Review (default) — in-game bans are sent to SentinelFX for review by network admins before any network-wide action.
- Auto — in-game bans from your FXServer are trusted and propagate network-wide immediately. Available at our discretion, and revocable at any time.
Secrets & identifiers
- Each FXServer gets a unique signing secret, generated on the SentinelFX dashboard and shown to you once. You paste it into the resource's local config file on your FXServer host. Keep it private — don't commit it to public repositories, paste it into screenshots or support tickets, or share it outside your ops team. If you suspect it has leaked, rotate it from the dashboard immediately.
- The resource transmits player identifiers (licence, Steam, Discord, FiveM, xbl, live, HWIDs) and event metadata. It does not transmit chat logs, file contents, or gameplay data. The full list is in the Privacy Policy.
- All outbound traffic from the resource is cryptographically signed. If you modify the resource in ways that break signing or tamper with the identifier set, we may revoke your server key and suspend the connection.
Fail-open behaviour
If SentinelFX is unreachable, the resource is designed to fail open — it will not block real players because of an outage on our side. Only confirmed, verified network-ban matches cause a connect to be rejected.
11Service availability
We aim for high uptime and publish live status at sentinelfx.net/status, but the service is offered on a best-effort basis. We don't guarantee uninterrupted availability, fixed response times, or that every feature will remain available forever. Maintenance, outages, third-party dependencies (Discord, Cfx.re, our hosting provider), and emergencies can all affect the service without notice.
12Suspension & termination
We can suspend, restrict, or terminate your access to any part of SentinelFX — for a user, an operator, a server, or a FiveM resource — if we reasonably believe you've breached these Terms, put the network or its users at risk, or are using the service in bad faith. Where practical we'll tell you why, but for active abuse we may act first and explain after.
You can stop using SentinelFX at any time: kick the bot from your Discord server, remove the FiveM resource from your FXServer, and revoke the OAuth authorization in Discord's settings. Data retention after you leave is covered by the Privacy Policy.
13Intellectual property
The SentinelFX name, logo, website design, dashboard UI, bot code, and FXServer resource are our intellectual property (or licensed to us). Nothing in these Terms transfers ownership to you.
- You get a limited, revocable, non-exclusive licence to use the bot and resource for their intended purpose on servers you operate.
- You may not rebrand, redistribute, or create derivative services based on SentinelFX without our written permission.
- Content you submit (reports, evidence, appeal statements, staff notes) remains yours. By submitting it you grant us a licence to use it as needed to operate, review, and enforce the network — including sharing relevant portions with the servers and users involved.
14Disclaimers
To the fullest extent permitted by law, SentinelFX disclaims all warranties, whether express, implied, or statutory — including merchantability, fitness for a particular purpose, non-infringement, and any warranty arising from course of dealing or usage of trade. We don't warrant that the service will be error-free, secure, uninterrupted, or that any defect will be corrected. We don't warrant that it will catch every bad actor, prevent every raid, or stop every ban evader.
15Limitation of liability
16Indemnity
You agree to defend and hold SentinelFX harmless from any claim, demand, or expense (including reasonable legal fees) brought by a third party arising out of: (a) your use of the service; (b) content you submit (reports, evidence, appeals); (c) your breach of these Terms; or (d) your violation of any law or third-party right. We'll tell you promptly about any such claim and cooperate reasonably with your defence at your expense.
17Changes to the service & Terms
We may update these Terms as the service evolves. When we make material changes, we'll bump the version number and effective date at the top of this page, announce it through the SentinelFX HQ server or dashboard, and — where the change expands our rights or reduces yours — give you reasonable notice before it takes effect. Continued use of the service after changes take effect means you accept the updated Terms.
Minor edits (typo fixes, clarifications, reformatting) may be made without announcement.
18Governing law
These Terms are governed by the law of the jurisdiction in which the SentinelFX operators are resident at the time a dispute arises, without regard to conflict-of-laws principles. You and we agree that any dispute arising out of or in connection with these Terms or the service will be resolved in the courts of that jurisdiction. Nothing in this clause removes any mandatory consumer protections available to you under the law of your place of residence.
19Contact
The fastest way to reach us is through our Discord support server. For formal legal notices, write to legal@sentinelfx.net. For privacy matters, see the Privacy Policy contact section. For security vulnerabilities, use the responsible-disclosure channel in our security.txt.