1. What the site may collect
- Account data: username, display name, email, password hash, and basic profile fields you fill in yourself.
- Session data: login state, remember-me state, and security tokens required to keep the account signed in safely.
- User content: forum topics, replies, game descriptions, uploaded files, and attachments.
- Technical data: IP address and basic security logs used to defend against brute force, spam, abuse, and server errors.
Under the current project logic, a session may last up to 4 days if the user enabled remembered login.
2. Why this data is used
- To create and maintain the account, let users sign in, preserve sessions, and protect against unauthorized access.
- To show profiles, posts, avatars, and other public content inside the site interface.
- To moderate content, fight spam, detect malicious uploads, and enforce the rules.
- To support the project technically, investigate errors, protect the database, and improve the pages.
The site must not use email, profile data, or logs to sell data to advertisers or secretly pass information sideways. Under this policy, that is explicitly prohibited.
3. What is public
If you publish something on the forum or inside a public profile, other users and site guests may be able to see it.
- Public information may include username, display name, avatar, bio, profile links, topics, replies, descriptions, and uploaded public materials.
- Email, password, internal tokens, and technical service data should not be displayed publicly.
- Do not publish in your profile or posts anything you would not want visible from the outside. The internet likes pretending it never forgets.
4. Storage, deletion, and security
- Data is stored for as long as it is needed to operate the account, forum, security systems, and reasonable technical requirements.
- When content or an account is deleted, some information may temporarily remain in logs, backups, and system archives until the next cleanup cycle.
- The administration must take reasonable protective measures: store passwords as hashes, limit brute-force attempts, and avoid exposing internal service data publicly without need.
- No one can honestly promise absolute security, so users should also use a decent password and avoid exposing unnecessary personal data.
The current build may not yet include automatic tools for exporting, correcting, or fully deleting data. But this policy allows the administrator to handle such requests manually if you decide to add that flow later.