Fox Sentinel — Privacy Policy
Transparency instead of secrecy
Fox Sentinel follows a simple principle:
If security depends on keeping the key hidden under a stone, then the key should not be hidden under the stone.
That is why we openly explain which data Sentinel processes, when this data is collected, what it is used for and who can see it.
This does not mean that internal security mechanisms or access credentials are published. It does mean that how the data processing itself works is described transparently.
1. Which data does Sentinel process?
Processing depends on whether you merely share a Discord server with Sentinel or actively use Sentinel.
1.1 Sentinel is on the same Discord server as you
If Sentinel is installed on a Discord server you are a member of, Sentinel can collect certain Discord data about you that is public or accessible to the bot.
This includes in particular:
- Discord user ID
- Discord username
- Discord display name
- Profile picture
- Server-specific nickname
- Roles on this Discord server
- Server membership
- Relevant changes to this information over time
This information can be collected without you actively using Sentinel.
The reason is Sentinel's fundamental function as a server-side security and moderation system.
Example:
You are a member of server A.
Sentinel is also on server A.
→ Sentinel can record your Discord identity for this server.
This alone does not mean that you have received a report, are suspicious or have done anything wrong. A Sentinel file is first of all an identity and history file, not automatically a criminal record.
2. If you actively use Sentinel
If you sign in or authenticate with the Sentinel dashboard or the Police Station, additional data may be processed.
This includes in particular:
- IP address
- Email address
- Discord connections
- Discord user ID
- Other Discord identity data required for sign-in
- Times of sign-ins and access
Discord connections
If you share your Discord connections through OAuth2 access, connected services can be detected, for example:
- Steam
- Spotify
- GitHub
- Xbox
- Other connections provided by Discord
This information can be relevant for identity, security and AccountGroup relationships. For example, Sentinel can detect that two Discord accounts have listed the same Steam connection. This does not automatically mean that both accounts belong to the same real person. A shared connection is a data point, not an automatic determination of identity.
3. IP addresses
If you sign in to the Sentinel dashboard or the Police Station, your IP address may be processed.
The IP address may be used, for example, for:
- Security checks
- Session and access security
- Abuse detection
- Auditing
- Technical error analysis
The actual IP address is not displayed as regular public Sentinel information.
4. Server-based IP verification
A Discord server can require additional verification before you are allowed to join it. If a server uses such a Sentinel verification, the server can request certain additional data from you.
Depending on the configured verification, this may include:
- IP address
- Email address
- Discord connections
You will be explicitly informed before or during this verification which data the server in question requests.
It is not supposed to happen secretly.
5. What does a server receive from your IP address?
If a server uses IP-based verification, that server never receives your actual IP address.
A hash value is used instead.
Example:
Your actual IP:
203.0.113.42
↓
SHA-256
↓
Hash:
...
The server only receives the hash value.
The actual IP address is not passed on to the server.
6. What can a server use an IP hash for?
A hash can be used in particular to determine whether two known values are identical.
Example:
User A
IP → SHA-256 → HASH_X
User B
IP → SHA-256 → HASH_X
If both values are exactly the same, the server can see that the same input value is behind them.
This allows the hash to be used, for example, for a comparison within the server.
The server itself decides how it uses the received hash within its own systems.
Sentinel does not release the original IP address.
Important
A hash is not magical anonymisation.
Hash values can be compared with each other and can be analysed under certain circumstances. That is why Sentinel continues to treat hash values as data worth protecting.
7. Connections are protected as well
The same basic principle applies to Discord connections.
Example:
Your Steam ID
↓
SHA-256
↓
Connection hash
A server does not receive the actual Steam ID or any other complete external account ID.
A hash can be transmitted instead.
This allows a server to determine, for example:
Connection A → HASH_X
Connection B → HASH_X
→ identical connection value
The original connection ID is not disclosed to the server.
8. What does a regular user see?
Sentinel follows a particularly strict principle here.
Your own data is shown to you uncensored in your file, as far as the system grants you access to it.
Other users do not receive these private values.
In particular, they are not simply shown:
- your real IP address
- your complete connections
- your email address
- private security data
Beyond that, it is not only the value that is hidden.
If a user has no permission for a private data field, the field is not transmitted to their client at all, on the server side.
So it is not merely:
<div class="invisible">
your-private-ip
</div>
The browser never receives this information.
9. Other users do not even see that private data exists
If a person has no permission for a particular type of private data, Sentinel does not merely try to hide the value.
Example:
Private record:
IP: present
Email: present
Connections: present
An unauthorised user does not receive:
IP: ********
Email: ********
Connections: ********
but only the non-private information.
Nor is the following shown unnecessarily:
IP present
Connections present
if the mere existence of this information is confidential.
10. Who may see complete data?
The complete personal data in your file is generally intended only for you and for explicitly authorised Sentinel access.
In particular, the two Sentinel Directors have access to correspondingly protected Sentinel data:
Sentinel Director
VECTORY Discord: vectory_owner ID: 1185587481140281569
Saro Discord: sarosychosis ID: 1510987812701208761
Access to private data remains technically protected by the Sentinel permission system and not merely by the user interface.
11. Servers never receive your real IP
For servers that use a Sentinel IP verification, the following applies explicitly:
The actual IP address is never passed on to the server.
The server only receives the intended hash value.
The same principle applies to external connections:
The actual external account ID is never passed on to the server when Sentinel provides a hash for it.
12. Why do we do it this way?
Sentinel is meant to enable security features without unnecessarily passing personal data on to other servers.
A server may, for example, want to determine:
"Have I already seen this value with another user?"
For that, the server does not necessarily need to know:
"Which specific IP address is this?"
Sentinel therefore provides a technical comparison value without passing the original information on to the server.
The same principle can be used for connections.
13. Data minimisation
Sentinel generally tries to process only the information required for the respective function.
The following applies:
Discord server
↓
Discord identity / server information
Dashboard / Police Station login
↓
IP + email + shared connections
Server requests verification
↓
only the data intended for this verification
Server needs IP comparison
↓
IP hash
Server needs connection comparison
↓
Connection hash
14. No automatic equating of identities
Sentinel can detect technical links.
For example:
Discord A
└── Steam Hash X
Discord B
└── Steam Hash X
This means:
Both accounts have the same technical connection value.
It does not automatically mean:
Both accounts definitely belong to the same person.
Likewise, an identical IP hash does not automatically mean that two accounts represent the same person.
Shared networks, households, VPNs, mobile networks or other technical circumstances can lead to identical or recurring values.
Such information must therefore always be considered in the relevant context.
15. A file does not automatically mean suspicion
The fact that Sentinel holds a file about you does not mean that you have done anything wrong.
Sentinel can also keep files for users who:
- have never been reported
- have not received any sanction
- are merely members of a protected server
- use Sentinel normally
- are entirely unremarkable
A file is primarily an identity, security and history structure.
16. Transparency about security features
Sentinel does not deliberately hide the basic workings of its data processing.
We want users to be able to understand:
- which data Sentinel processes
- when this data is collected
- when additional data is required
- which data a server receives
- which data is never passed on to a server
- which information is visible only to the affected user
- which information is specially protected
Security should therefore not depend on users not knowing the architecture.
Keeping access credentials and cryptographic keys secret is of course still required. How the privacy and permission system works is separate from that.
17. Summary
If Sentinel is merely on a Discord server with you:
Sentinel can record, among other things:
Discord ID
Username
Display name
Profile picture
Nickname
Server roles
Server membership
If you sign in to Sentinel:
The following may additionally be processed:
IP address
Email address
Discord connections
If a server requires a Sentinel verification:
You will be informed about it.
Depending on the verification, data such as:
IP
Email
Connections
may be requested and stored according to the function.
If a server wants to compare your IP:
❌ real IP
âś… SHA-256 hash
If a server wants to compare your connections:
❌ real external account ID
âś… hash value
Who sees the complete private data?
In principle:
You yourself
+
correspondingly authorised Sentinel access
Other users do not receive this private data and, on the server side, should not even be able to tell that such private fields exist.
18. Principle
Sentinel is meant to increase your security without unnecessarily exposing your private data.
For us, transparency does not mean publishing security vulnerabilities. Transparency means openly explaining which data is processed and how it is protected.
Your real IP stays your real IP. Your complete connections stay your connections. For corresponding comparison functions, another server only receives the intended hash value – never the original values.