Welcome. These Terms of Service govern the use of the Blossom Addon verification system (the "Service"). By using the Service you agree to these terms. If you do not agree, do not proceed with verification.
1. Purpose
The Service verifies Discord accounts, checks for VPN/proxy usage, and assigns a verification role within the configured Discord server. It exists to protect the community and reduce abuse.
2. What information we collect
- Discord account data (via OAuth2): username, discriminator, user ID, avatar URL, and a temporary access token used only to fetch user information.
- IP address: collected from the request headers for security checks (see the Privacy Policy).
- VPN/proxy detection result: a yes/no determination from a third-party IP intelligence provider.
- Timeout/block status: a temporary entry that prevents repeated verification attempts after VPN/proxy detection or abuse.
3. How we use collected information
- Confirm your identity and complete verification.
- Assign the configured verification role in the Discord server.
- Detect and block VPN/proxy usage to prevent abuse.
- Log verification events for moderation and security purposes (via an internal webhook to server administration).
4. Role assignment and verification outcomes
Successful verification assigns the configured role to your Discord account. If VPN/proxy usage is detected, verification is blocked, a temporary timeout is stored, and an alert is logged.
5. Restrictions
You must not attempt to bypass the verification process, use fraudulent accounts, or interfere with the Service. Violations may result in permanent denial of access and server sanctions.
6. Liability
The Service is provided as-is. The owner/operator is not responsible for indirect damages arising from the use or inability to use the Service.
7. Changes
These Terms may be updated. Continued use of the Service after changes constitutes acceptance of the revised Terms.
8. Contact
For questions, disputes, or data requests, contact the Blossom Addon administration team or the system owner.
Read the Privacy Policy for full details about what is collected and how it is handled.
