Privacy Policy

This Privacy Policy (the "Policy") describes how Worldwide Asset and Server Protection ("WASP," "we," "us," or "our") handles information in connection with the WASP Service. The Service may include public websites, staff and partner dashboards, Discord bots, REST APIs, OAuth-based authentication, ban lookup tools, case and evidence management, appeals, audit logs, and network-wide security enforcement features.

Important privacy principle. WASP is designed for security, moderation, case review, and network protection. WASP does not sell personal information and does not use case data for targeted advertising.

1. Scope of this Policy

This Policy applies to personal information and other user-related information processed through WASP-operated services, including information handled through the WASP website, dashboards, bots, APIs, case systems, appeal systems, authentication flows, audit systems, and participating-server integrations.

This Policy does not replace the privacy policies or terms of Roblox, Discord, hosting providers, identity providers, or other third-party platforms. Participating communities may also maintain their own privacy and moderation policies.

2. Information We May Collect

Account and identity information: platform account identifiers (Discord or Roblox user IDs); usernames, display names, avatars; authentication or OAuth metadata; email address where a connected identity provider makes it available under an approved scope; roles, permissions, staff status, and access-control information.

Server, community, and integration information: server, guild, group, game, universe, community, or organization identifiers; names and basic metadata; configuration settings, integration status, bot permissions, API identifiers, and webhook configuration metadata.

Reports, cases, evidence, and appeals: reports submitted to WASP including reporter identity; case subjects, identifiers, linked accounts; screenshots, message records, moderation and audit logs, files, links, timestamps, staff notes; blacklist/network-action records, decision notes, appeal submissions and outcomes.

Technical and security information: IP address, device/browser information, user-agent data, request timestamps, session information; API request records, authentication attempts, rate-limit events, error and access logs; audit records of administrative actions.

We do not need everything. WASP aims to collect and retain information that is reasonably relevant to operating the Service, securing the Network, reviewing cases, and enforcing published rules.

3. Where Information Comes From

• You, when you sign in, configure an integration, submit a report, file an appeal, or contact support.
• Participating server owners, administrators, moderators, developers, or authorized representatives.
• Connected platforms and identity providers (Discord, Roblox) within an approved scope.
• WASP systems themselves, such as audit logs, API logs, authentication logs, and case records.
• Publicly available information where relevant to a case, appeal, or security investigation.
• Other reporters or witnesses who provide information to WASP.

4. How We Use Information

• Authenticate users and manage account, staff, partner, and administrative access.
• Connect and operate participating servers, bots, APIs, dashboards, and other integrations.
• Receive, investigate, document, and review reports and evidence.
• Issue, maintain, synchronize, or remove network enforcement actions in accordance with WASP rules.
• Process appeals, corrections, sanctions, and case reopenings.
• Provide ban lookups, case-status functions, audit functions, and other security features.
• Detect fraud, evasion, malicious automation, credential misuse, cyberattacks, and unauthorized access.
• Enforce the WASP Terms of Service, Blacklist Rules, staff procedures, and other applicable policies.
• Comply with lawful requests, protect rights and safety, and establish or defend legal claims.

5. Case, Evidence, and Blacklist Data

WASP case systems may contain information about alleged misconduct, evidence, staff findings, appeal history, and enforcement status. Because these records can materially affect access to participating communities, WASP treats case integrity as a core privacy and security concern.

Blacklist status is not a criminal record. A WASP blacklist or network restriction is a private moderation and access-control action. It is not a criminal conviction, civil judgment, or governmental determination.

6. Authentication and Connected Platforms

Some WASP features may use Discord, Roblox-linked information, OAuth, or another identity provider. WASP receives only information made available within the authorization and technical scope of that integration. You may be able to revoke an authorization through the applicable third-party platform; revocation may disable dependent features but does not necessarily delete information already lawfully retained.

7. How Information May Be Shared

Within WASP, information may be accessed by staff, reviewers, administrators, or authorized personnel who need it to perform their responsibilities, restricted by role. WASP may provide participating communities with information reasonably necessary to use network security features (user identifier, active network-action status, rule/category information, action dates). Detailed evidence or internal staff information is not disclosed to participating communities unless there is an operational need and disclosure is authorized.

No sale of personal information. WASP does not sell personal information for money and does not disclose case information to third parties for targeted advertising.

8. Public and Network-Facing Information

Network-facing information may include a platform user identifier, username or display name, current blacklist or enforcement status, applicable rule or category, action date, and expiration or appeal status. WASP avoids publishing private evidence, residential addresses, authentication credentials, or other sensitive data as part of an ordinary blacklist lookup.

9. Sensitive Information and Evidence Handling

Users must not submit passwords, session cookies, authentication tokens, full payment-card data, government identification numbers, medical information, private addresses, or other highly sensitive information unless it is genuinely necessary for an authorized security or case purpose. Where evidence contains irrelevant sensitive information, reporters should redact it before submission where practical.

10. Data Retention

WASP retains information for as long as reasonably necessary for the purpose for which it was collected, the integrity and security of the Network, enforcement and appeal history, dispute resolution, fraud prevention, legal obligations, or other legitimate operational needs. When information is no longer reasonably needed, WASP may delete, anonymize, aggregate, archive, or otherwise restrict it.

11. Security

WASP uses administrative, technical, and organizational measures intended to protect information, which may include role-based access, authentication controls, access logging, credential management, and review of privileged actions. No online service can guarantee absolute security; users are responsible for protecting their own accounts, passwords, tokens, and devices.

12. Your Choices and Privacy Requests

Depending on your location, you may have rights or choices concerning personal information. WASP may provide reasonable methods to request access, correction, deletion, restriction, or review, subject to applicable law and necessary limitations (identity verification, preservation of evidence, protection of others' privacy, and prevention of fraud or evasion). A request to correct or delete information is not automatically an appeal of a WASP enforcement action.

13. Children and Minors

WASP does not intentionally design case or support systems to solicit unnecessary sensitive personal information from children. Users must satisfy the minimum age and account requirements of the platforms through which they access WASP.

14. International Processing

Information may be processed or stored in jurisdictions other than where a user resides. Where applicable law requires safeguards for international transfers, WASP will use measures appropriate to the relevant service and legal requirements.

15. Third-Party Services

WASP may interact with Roblox, Discord, OAuth providers, hosting providers, content-delivery networks, logging or security providers, and other third-party services, which may independently collect or process information under their own policies.

16. Changes to this Policy

WASP may update this Policy to reflect changes in the Service, technology, integrations, legal requirements, security practices, or internal procedures. Material changes may be announced through an official WASP channel where practical.

17. Contact and Privacy Requests

Questions, privacy requests, concerns about evidence handling, or reports of suspected unauthorized disclosure should be submitted through the official WASP support or administrative channels published by WASP.