Privacy
Your information deserves care.
A clear account of what this website is designed to process and what still needs owner review.
Information this website processes
Browsing the public pages does not require an account. When Discord sign-in is enabled, the website receives your Discord identifier, username, display name, and avatar reference. It stores those details with a hashed session identifier, expiration time, and verification state. It does not request your email address.
Why it is used
These details connect a website session to your Discord identity and support membership verification. One-time verification records are tied to a Discord identifier. The database stores a keyed hash of new verification codes and an unrelated placeholder in the legacy code field.
Cookies and tracking
Necessary cookies protect sign-in and hold an opaque session identifier. No optional analytics or marketing trackers are installed. Read the cookie policy for names and lifetimes.
Retention and security
Website sessions expire after 24 hours; sign-in state expires after ten minutes. Unused verification codes expire after ten minutes. Expired records need the operator’s scheduled cleanup. Used verification records are retained as membership proof until the owner approves a retention and revocation policy. Access is restricted to the backend; credentials and codes must not be placed in public logs.
Public announcement mirror
When configured, the existing Discord bot sends selected public channel announcements to the website. The website stores message IDs, sanitized text, source channel IDs, dates, pin state and sync times. Deleted posts become empty tombstones to prevent delayed updates from restoring removed content. Personal author profiles and attachment files are not copied. Retention and request handling need operator approval. Source links lead back to Discord.
External services and technical logs
Discord handles its own accounts and services under its own policies. Hosting and database providers may process technical access logs. The owner must identify actual providers, regions, access controls, and retention before this policy is approved. External social and store links lead to services with separate policies.
Support, purchases, and privacy requests
This website has no ticket, appeal, or payment form. Support happens through the official community route; purchases, when available, happen through the approved merchant. Use community support to request the current privacy contact while the dedicated contact and request process are being confirmed.
Participation and younger players
The operator must confirm its participation and age policies, including the rules of external services and applicable law. Do not submit private information about other players or children through public community channels.
Review and changes
The owner must review this text against the actual processing operations and relevant jurisdictions before adopting it. Approved changes should be dated and communicated through the official community channels.