Privacy and your data
No smoke. Here’s what’s stored.
A privacy product shouldn’t ask you to just trust it. Here’s every byte the software actually writes, plus the one thing it doesn’t do: end-to-end encryption. Yeah, really — read that part twice.
Uncensored Room does not ask for an email address, phone number, real name, contacts, or location. It stores a username, a hashed password, your messages and uploads in a server-side SQLite database, a seven-day session cookie, and short-lived IP-based rate-limit and audit records. The public pages also increment a first-party pageview counter that sets no cookie and writes no IP address to disk. Messages are readable in that database and by the server operator.
Never asked for — those fields don’t even exist
- Email address
- Phone number
- Real name or government ID
- Contacts, address book, or location
- Third-party analytics, advertising IDs, or cross-site cookies
- A tracking script, cookie, pixel, or cross-site identifier of any kind
No third-party trackers, analytics scripts, ad SDKs, or font CDNs. Fonts, icons, styles, and scripts all come from the same origin, so loading a page tells nobody else that you showed up.
The one thing that does get counted is the site’s own traffic: one line in a local SQLite table per public pageview, holding the page, the referrer, the search terms if the engine passes them, and a rough device type. No cookie, no JavaScript, no IP address written to disk — the IP is hashed with a secret that stays on the server. Do Not Track is honoured, and the counter never runs inside a room, the API, or an account page.
What actually hits the disk
- Username (2–20 characters) and a password stored as a hash via PHP password_hash()
- Messages, room names, and membership records in a server-side SQLite database
- Uploaded images, voice notes, and files in the server's upload directory
- A session cookie named WECHAT_SID, HTTP-only, SameSite=Lax, valid for 7 days
- IP addresses used for sign-in and sign-up rate limiting, and in the admin audit log for administrative actions
- Last-active timestamps, used to show who is online (inactive for 75 seconds counts as offline)
- Anonymous first-party page views on the five public pages: path, referrer, search terms when the engine passes them, and a coarse device / browser / OS / country bucket. Your IP and browser string are hashed with a local secret and never stored, and the counter sets no cookie
The part you shouldn’t skip
Messages are not end-to-end encrypted. They are readable in the site's database, and the admin console can view chat history and export or back up data. Only deploy on a server you trust.
Transport security (HTTPS) is provided by the host, not by the application itself. Use HTTPS in production so passwords, cookies, and messages are not sent in clear text.
Sign-in attempts are rate limited (12 failures per IP and 6 per username per 10 minutes) and sign-ups are limited to 5 per IP per hour. These counters are short-lived operational records.
There is no public profile, discovery feed, or search index of rooms inside the product. Search engines only see the public informational pages, never room contents.
This page describes the software itself. The operator of a specific deployment may add hosting-level logs or policies of their own.
Unfiltered means no automated content filtering; it does not mean anonymous or encrypted. Messages are stored in readable form, the operator can read them, and rate limits still apply.
The pageview counter is first-party and cookieless: no IP address, no cookie, no third-party request, no JavaScript. Do Not Track and Global Privacy Control visitors are skipped entirely, only the five public pages are counted, and raw rows are deleted after 400 days.
The short version
| Question | Answer |
|---|---|
| Email or phone | Not requested.Sign-up is a username and a password only. |
| End-to-end encryption | No.Messages are plain readable rows in the site's SQLite database; HTTPS protects the connection only. |
| Who can read messages | Room members and the server operator.The admin console can browse chat history and export or back up data. |
| Third-party requests | None.All assets are self-hosted on the same origin. The pageview counter is first-party too. |
| Traffic stats | First-party, cookieless.Page, referrer, search terms, device class. No cookie, no script, no IP stored, Do Not Track honoured, public pages only, deleted after 400 days. |
| Session lifetime | 7 days.One HTTP-only, SameSite=Lax cookie named WECHAT_SID. |
| Automatic message expiry | None.Messages remain until a room owner or administrator deletes them. |
Keep digging
Features and the hard numbers → · Privacy questions in the FAQ → · How to start a room →
Questions about a specific deployment go to whoever runs that server. Hosting providers may keep their own access logs, and those are outside the application.
Go on then
No filter on the conversation, and zero mystery about what’s stored.
Open Uncensored Room