how this site operates
this page exists so that those who care know what happens when they make an account, upload files, comment, or delete things
simple version
in short:
we try to be as exhaustively compliant with our idea of an ideal "totally anonymous" experience as possible by default; all database entries that we store have at least one obvious, user-facing indication of storage, all of your data (and we mean all of it) can be deleted at any time, for any reason, and any and all deletions are user-facing, and tested. once you delete something, we and you forever lose access to it (the entire footprint) once the cache window rolls over (currently 5 minutes), as if you yourself were never present on the site. any and all required user information in any and all contexts is anonymous, both in isolation and in context, and we never store plain text passwords; only hashes, meaning we don't know your (decrypted) password.
what is public
uploaded posts, visible files, titles, descriptions, artist names, profile pictures, custom username colors, public profile pages, post counts, comment counts, and comments are visible to other people on the site
(if you post with a publish date, you can still see that post before that date while other people should not see it until it publishes)
what is stored
account usernames, password hashes, account creation times, profile picture references, upload records, upload metadata, uploaded files, publish dates, expiration dates, comments, and whether or not an account has already seen certain first-time notices
(uploaded files and profile pictures are stored in object storage, site records, users, posts, file references, comments, and settings are stored in the site's database)
passwords and logins
passwords are stored as hashes, never as plain text. login sessions are designed to persist until the user explicitly signs out, unless the browser, server, or site configuration clears the session earlier
files and downloads
uploaded files may be streamed from object storage or served through temporary signed links depending on the storage setup; people who can view a public post may be able to open or download the files attached to it
(the site tries to support large and miscellaneous files, but upload reliability can still depend on the browser, network, hosting provider, object storage, and server limits outside the page itself)
comments and usernames
registered usernames link to their profile pages; names that do not belong to registered accounts are displayed as plain text so that they do not pretend to be real accounts, and claimable by anyone
comments are public where they appear, and may also be shown on the commenter's profile page
moderation and administration
site administrators may need to view, edit, remove, or repair site content, files, comments, and account records to keep the site working, fix abuse, recover from errors, or handle maintenance
because the site is independently run, there may be downtime, manual maintenance, or emergency changes when something breaks
deleting things
when an account, post, profile picture, or file is deleted through the site, the site attempts to remove the matching database records and stored objects it controls
copies that were already downloaded, cached, archived, indexed, backed up, or shared outside the site may not be possible for the site to remove
tracking and third parties
the app itself does not include ad tracking or analytics code in its templates. the site still depends on normal infrastructure such as hosting, object storage, server logs, and browser requests, which may process technical data needed to deliver pages and files
in short; have common sense
(even though it is allowed as long as it is legal) generally do not upload private information, secrets, credentials, unreleased work you are not ready to share, or anything you would not want viewers or administrators to access
more detail
accounts
an account mainly exists to connect a reliable (pseudo-)identity to uploads, comments, profile information, profile pictures, username color settings, and account-specific notices. account pages are public when someone visits them
the site does not store plain-text passwords, only hashes, and uses login sessions so that the browser can remain signed in
uploads
upload records can include the uploader's username, title, category, slug, description, publish date, expiration date, file metadata, and object-storage keys for the uploaded files
scheduled posts are hidden from other users until their publish date, but the uploader may still be able to view and manage them before they publish
files
files and profile pictures are kept outside the main database in object storage; the database stores references to those objects so that the site knows which files belong to which post(s) or account(s)
depending on the storage configuration, files may be streamed through the site or opened through temporary signed links; anyone who can access a public post may be able to access the files attached to it
comments
comments are stored with their post, name, body, creation time, and account link when the commenter is a registered user. comments are public on the post where they appear, and can also appear on the commenter's profile page
registered names link to profiles, unregistered names stay plain-text so that they do not impersonate real site accounts, and are claimable by anyone
deletion and limits
deleting something through the site removes what the site controls, that currently being matching database rows and stored objects. the site cannot reliably remove copies that were already downloaded, cached, archived, screenshotted, indexed, backed up, or shared somewhere else
operation
the site depends on hosting, object storage, server software, browser requests, and logs that may process technical information needed to deliver pages and files. administrators (currently "rshc" & "tee") may access or change content and records when needed for moderation, maintenance, abuse handling, bug fixes, or recovery
GDPR compliance
rshc; the site operator, operates out of Czechia, and must thus comply with the GDPR; they hereby declare their best effort to do so in good faith, and that they are the sole responsible party for the site's operation and compliance. Also hereby, and in good faith, they, in return, request that their identity be privatised to the greatest extent possible whenever legally permitted under European law during any possible future proceedings.