🔒 Privacy Policy

1. Information We Collect & Source

To provide moderation, server protection, and join-safety telemetry, we collect and process specific Discord platform-derived data:

Discord API Data

We only read and store data that is explicitly shared by the server or accessed through permissions granted by the guild administration:

• User Identifiers: Discord User IDs, usernames, display names, and global name snapshots.
• Guild Information: Discord Guild IDs, server names, and owner identifiers.
• Moderation logs: Punishments executed in servers (bans, kicks, timeouts, mutes) including incident timestamps and reasoning.
• Audit Logs: Events fetched via the Discord View Audit Log permission (moderator IDs, targets, action types).
• External Bot Logs: Messages scanned from moderator-designated log channels (Carl-bot, Dyno, MEE6, Wick, etc.).
• AutoMod Events: Alert logs generated by Discord's native AutoMod rules.

User/Admin Inputs

• Evidence Files: Text notes, links, or screenshot files uploaded manually by server staff to substantiate moderation requests.
• Appeals: Statement content, contact info, and appellant explanations submitted through the appeals portal.

2. Why We Collect Information & How It Is Used

We process data strictly for security, abuse prevention, and guild safety purposes:

• Heuristic Risk Indicators: To compile safety scorecards for incoming server members based on historical reports and server events.
• Staff Review Cases: To notify server moderators when a member matches a high-risk footprint, allowing manual verification.
• Audits & Appeal Tracking: To review false positive reports and restore account standings.

3. Data Retention & Minimization

We follow strict data minimization principles:

• Moderation Footprints: Stored footprint events, imported bot logs, and server-wide scan history are set to expire after 90 days. Once expired, they are permanently purged from our active databases.
• Verified Registry Records: Approved ban registry cases are retained indefinitely to maintain cross-server network protection, or until a successful appeal or deletion request is processed.

4. Data Sharing & Privacy Controls

• Guild Isolation (Local Footprints): All footprint data derived from server audit logs, AutoMod signals, external bot logs, and manual staff notes is strictly isolated to the server where it was collected. It is never shared across other servers or visible to unauthorized communities.
• Global Registry (Opt-In): Only verified Banstone cases, reports submitted via the registry system, and appeal histories are synchronized across the global Banstone network. Server admins can opt-out of global sharing in the dashboard settings.

5. Right to be Forgotten (Deletion & Correction)

Users have the right to request deletion or correction of their personal data:

• Correction: If your username or association snapshot is incorrect, or if a local footprint event was a false positive, server staff can mark the event as reversed, instantly recalculating your risk score.
• Deletion Requests: You can submit a request to permanently delete your stored data by contacting our support team:
  • Support Contact: support@banstone.dev or via our Discord Support Server.
  • Upon receipt, all identifying Discord IDs and username snapshots linked to your profile will be permanently purged or anonymized within 30 days.

6. Compliance with Discord Terms

Use of this application is governed by this policy, and all actions must also comply with:

• Discord Terms of Service
• Discord Developer Terms of Service
• Discord Developer Policy
• Discord Community Guidelines