1. Data we collect
Language Filter only needs data connected to running the bot, dashboard and moderation features. Depending on the features used, this can include:
- Discord account and server data: user IDs, usernames, display names, user tags, avatar references, guild IDs, guild names, channel IDs, thread IDs and role IDs.
- Configuration data: enabled features, dashboard settings, selected channels, custom dictionary words, anti-link rules, allowed/blocked links, category toggles, whitelist users, notice text and log channels.
- Moderation evidence: warning logs, deleted-message logs, reasons, action types, original or filtered message content, channel references, message IDs, active punishments and expiry times.
- AI moderation data: matched patterns, labels, confidence values, AI reasons, moderator advice, review decisions, attachment URLs or fingerprints, allowed/blocked AI learning rules, image fingerprints and appeal details.
- Dashboard activity: panel poll votes, changelog replies, support ticket category, title, details, replies and unread counts.
- Billing and usage data: subscription tier/status, Stripe identifiers, current period information, AI usage periods and credit balances.
- Technical data: server logs, errors, analytics needed to keep the service working and protect it from abuse.
We do not sell personal data. We also do not intentionally collect sensitive personal details beyond the content your server chooses to moderate or submit through support features.
Data we do not collect or store
Language Filter does not collect or store private message content for general tracking,
advertising, profiling or resale.
We do not collect or store:
- Passwords or Discord login credentials
- Discord OAuth access tokens for long-term use
- Payment card details, as billing is handled by Stripe
- Private messages sent outside of servers where the bot is installed
- Voice chat audio or call recordings
-
Sensitive personal information such as home addresses, government ID numbers,
banking details, health information or biometric data
- Data from guilds/servers where Language Filter is not installed
- Cross-server user profiles or shared reputation records
Any data stored by Language Filter is used only to provide the service, manage
guild-specific settings, display moderation logs, show dashboard statistics,
process optional AI moderation checks, handle billing status, provide support,
investigate issues, fix bugs, maintain security and prevent abuse.
Guild data is stored separately per guild/server. Data from one guild is not made
available to another guild.
2. How we use data
Data is used to provide the bot and dashboard features you enable, including filtering messages, applying warnings or punishments, showing logs, saving configuration, authenticating dashboard users through Discord OAuth, handling support tickets, displaying changelog/poll features, measuring feature usage, preventing abuse and enabling paid features.
Most server data is stored per guild/server. A guild's dashboard data is intended to be visible only to authorised admins or moderators for that same guild after they log in and are verified through Discord OAuth. Data from one guild is not shared with or shown to other guilds.
For example, identifiers such as user IDs, usernames, display names, user tags, avatar references, guild IDs, guild names, channel IDs, thread IDs and role IDs are used to show logs, moderation history, dashboard settings and stats inside the relevant guild dashboard.
3. AI and moderation processing
If AI moderation is enabled, relevant message content, context, attachment information or moderation metadata may be processed through OpenAI to classify, review or explain moderation events. AI features can include free screening, GPT review, safety monitoring, image analysis, repeat-violation monitoring and appeals.
AI features should be configured by server staff. Staff should review important decisions and handle appeals, because AI can make mistakes.
5. Sharing and processors
Data may be processed by trusted services required to operate Language Filter,
including Discord, payment providers for billing, AI providers for optional AI
moderation features, and hosting or infrastructure providers.
Language Filter is hosted on dedicated server infrastructure managed by Dane.
The server, application and database are controlled through server-level access,
permissions and security configuration.
Data may be accessed or disclosed only where necessary to operate the service,
provide support, investigate issues, fix bugs, prevent abuse, maintain security,
comply with legal requirements, or protect the service and its users.
4. Payments and subscriptions
Payments are handled by Stripe. Language Filter may store Stripe customer IDs, subscription IDs, price IDs, checkout session IDs, subscription status, billing event types and webhook receipt IDs so the dashboard can activate the correct plan. Full card details are handled by Stripe and are not stored by the Language Filter panel.
6. Retention and deletion
Server settings are kept until removed or the service no longer needs them. Moderation logs, deleted-message logs, AI logs, warning logs, active punishments, support tickets, poll votes, changelog replies and billing records may be kept for operational, security, audit and billing purposes. Some logs can be cleared from the dashboard where the feature provides a clear/reset option.
AI and moderation cleanup jobs may remove older logs depending on the configured retention window and backend maintenance settings. Backups, billing records or abuse-prevention logs may remain for a reasonable period where needed.
7. Your choices
Server owners and authorised staff can change or disable many features in the dashboard, including watched channels, dictionary entries, anti-link rules, AI tools, whitelist users and log settings. Users should contact their server staff first for server-specific moderation records because guild data is controlled and viewed within that guild's own dashboard.
Dane may access stored data where needed for maintenance, issue investigation, bug fixing, security checks or support, but this access is for operating and repairing the service when needed. For service-level privacy requests, contact Official GamersHub through the website or support channels.