Evidence security
Uploads are content-validated, executable formats are blocked, archives are quarantined, and preserved files use AES-256-GCM encryption.
Chain of custody
Every preserved file is recorded with a SHA-256 hash in an integrity manifest. Case decisions and exports carry an auditable timeline.
Independent review
Serious findings, developer ownership claims, deny policies, and upheld appeals require separate reviewers where configured.
Scoped integrations
FiveM and service clients use individual HMAC secrets, route scopes, server binding, timestamps, and one-time nonces over HTTPS.
Privacy boundary
Public lists contain masked identifiers and two-reviewer findings only. Customer records, evidence, reporters, and reviewer identities stay private.
Two-reviewer authority
Signals and matching scores stay advisory. Only a supported verified leak/theft case with two distinct approvals can trigger bans in Discord servers that explicitly opted in.
Found a security issue?
Share it privately with support. Do not include unrelated personal data or public proof-of-concept abuse.