Privacy & data handling
This policy explains what the SafeNet Secure public website exposes, what it deliberately keeps private, and how lookups are protected against abuse.
Public lookup results are intentionally limited
The public lookup service returns only a small, explicitly approved set of fields: the Discord ID, its type, flag status, category, public reason, date flagged and — where SafeNet Secure has marked it public — the risk level. No other data is ever included in a lookup response.
Sensitive investigation information is never exposed
Internal moderation notes, private evidence, reporter identities, staff identities (unless explicitly marked public), investigation history and internal risk scoring are never returned by the public API. These details remain exclusively within SafeNet Secure's private systems.
The website cannot modify SafeNet Secure records
The website is strictly read-only. It has no endpoints capable of creating, editing, resolving, expiring or deleting flags, and it is designed to operate using read-only database permissions. All changes to flags happen through the SafeNet Secure bot and private management infrastructure.
Abuse prevention and rate limiting
Lookups are subject to per-IP rate limiting and burst protection to prevent scraping and automated bulk access. Exceeding these limits temporarily blocks further requests. We may log security-relevant events — such as lookup timestamps, lookup type, whether a public record was found, and rate-limit events — separately from the flag database to protect the service.
Credentials are never exposed
Database credentials, connection strings, API keys and other secrets are used only on the server and are never sent to the browser or included in any response. Error messages never reveal internal system details.
Minimal data collection
The website does not require accounts and does not collect personal information beyond what is strictly necessary for security logging and abuse prevention.