Last updated: April 13, 2026 · Applies to the 4$0 Discord bot, related web panels, and API services operated by the project owner.
Verification & IP addresses.
Member verification uses Discord OAuth (sign in with Discord). By default we do not store or display visitor IP addresses in Discord logs. If a server administrator enables same-network alt detection, the service stores an opaque fingerprint of (server + IP) to detect multiple Discord accounts verifying from the same network. If they enable VPN / proxy blocking, the visitor’s public IP is sent to a third-party reputation API only for that check (not posted in Discord); that feature is optional and off by default. Logs may include account context from Discord’s OAuth response and basic browser metadata (such as User-Agent) where available.
1. Information We Collect
Depending on how you use the service, we may process:
Discord account data — user ids, usernames, avatars, roles, guild membership, and message content visible to the bot in channels where it has permission.
Bot configuration & usage data — settings your server administrators configure (channels, roles, toggles, ticket metadata, moderation logs, etc.).
Product / license data (4$0 Auth) — if enabled, keys, sessions, HWID bindings, and related auth records stored in the operator’s database.
Technical logs — standard server or application logs (errors, rate limits) on the host running the bot; content is minimized to operate the service.
2. How We Use Information
To operate Discord features you enable (tickets, suggestions, moderation, counters, verification, etc.).
To enforce server rules and administrator-configured protections (including anti-abuse systems).
To provide web dashboards and APIs tied to the same configuration database.
To communicate essential service information (for example, support links or system status).
3. Data Storage
Data is stored on infrastructure controlled by the person or organization running this bot (for example, SQLite files on a VPS). Retention follows operational needs and administrator actions (exports, backups, wipes). There is no guarantee of indefinite retention unless your operator configures backups.
4. Third-Party Services
The bot relies on Discord as the primary platform. Optional integrations (for example, AI providers, payment processors, or external APIs) may process data under their own policies when explicitly configured. Review each integration’s documentation before enabling it.
5. User Rights
Where applicable privacy laws grant rights (access, correction, deletion, objection, portability), contact the server operator / data controller listed below. Discord also provides tools to leave servers, manage apps, and control your account.
6. Children’s Privacy
The service is not directed at children under 13. Server operators are responsible for age-appropriate rules in their communities.
7. International Transfers
Discord and your operator’s hosting may process data in multiple countries. By using the bot in a server, you understand processing may occur outside your country of residence.
8. Changes to This Policy
We may update this page to reflect product or legal changes. The “Last updated” date will change when revisions are published.
9. Contact Information
For privacy questions about a specific community, contact that community’s server administrators. For questions about this codebase deployment, contact the operator of the public base URL shown in /dashboard or your hosting provider.