COMMUNITY GUIDELINES
Privacy and submissions
What is stored
Accounts store an email address, display name, password hash, and creation date. Passwords are never stored in plain text. Posts and comments store their content, creation and modification times, and an IP address when provided by the trusted reverse proxy. Email addresses and IP addresses are visible only to administrators.
Submissions and moderation
New contributions and comments are reviewed before publication. Registered authors can edit or hide their own contributions. Editing sends a contribution back to review. Anonymous submissions cannot be edited or hidden by their author later. Create an account before submitting if you want these controls.
Hiding does not erase a post
Hiding removes a contribution from public pages, direct links, and public image access. The database retains its content and attachments, timestamps, author information, who hid it, and a record of the action. Administrators can consult this private archive. Previous versions may be retained in the moderation audit log.
Images and technical data
Uploaded images are converted to WebP, resized when necessary, and stripped of image metadata. Do not upload private information. A necessary, HTTP-only session cookie keeps you signed in. No advertising or analytics cookies are used. Raw submission IP addresses are cleared after the configured retention period (90 days by default) when the operator runs maintenance; moderation records remain.
Site operation
This is an early development portal. Email verification and password recovery by email are not connected yet. For account or privacy requests, contact the site operator through the channel where you found this project.
Likes and poll votes
Likes and general poll votes are linked to your signed-in account. Feature questions also accept guest responses. A necessary HTTP-only cookie remembers a guest browser for up to one year; the database stores a hash of its identifier. When a trusted proxy supplies an IP address, a keyed hash also limits guests to one response per question per IP. A shared network therefore permits only one guest response; sign in to respond individually. Clearing cookies or changing networks can weaken duplicate protection. Signing in uses a separate account identity. Counts and percentages may be public, but written alternative ideas and Other answers remain private to administrators. Hiding a question keeps its responses and audit history in the database.
Private contact messages
The Contact form stores your topic, email address, description, creation time, and source IP when supplied by the trusted proxy. A signed-in sender is also linked to their account. Only site administrators can read messages, sender emails, read status, and private technical details. No email is sent automatically and there is no built-in reply system. The supplied contact email is not verified. Archiving retains the message and its audit history. Raw IP addresses follow the same configured retention period as other submissions.