Privacy, in plain English
This site is for confessions people would rather not attach their name to. So here is what actually happens to yours — what is stored, who can read it, and where the gaps still are.
Your account
Sign-in runs on the Base44 platform, which holds your email address and a password it stores hashed — we never see it in plain text — plus an anonymous handle we invent for you (Velvet Ostrich 42, or similar) and a session token your browser keeps so you stay signed in. Your email is never shown next to a story, comment or vote. There is no public profile and no page that lists what one handle has written.
What you post, and who can read it
A story, a comment, your handle, the product name, the tag, the symptoms, the severity and the rough timing are readable by anyone with an account — not by the open internet. Every story page is marked noindex, so it stays out of search results. Screenshots still travel: treat anything you publish as findable by the people who already know you, because we can take a post down but we cannot un-copy a screenshot.
What stays private
Your saves, reactions and reposts are yours alone — nobody else's page shows them. Moderators can see them where a report or a safety issue has to be investigated, and reports go only to moderators. There is no way for another reader to message you and no direct messages to leak.
Photos, in detail
Location data, camera model and capture time are stripped in your browser before the upload: the image is redrawn and re-saved, so only pixels leave your device. That file goes into private storage, not onto a public web address — the site asks for a link that expires within the hour each time it needs to show your photo, so a copied link stops working. The blur is still a display setting rather than a lock: while a link is live, anyone reading that story can peek, exactly as you can. Every photo is screened by an automated image check and reviewed by a moderator if it is flagged, and refused if it shows a face, nudity, a child or a sales pitch.
Who receives data
Base44 hosts the site, the database and the file storage, and sends the sign-in, verification and password-reset emails. When you attach a photo, that image is sent to an AI model provider so it can be screened before publication — nothing else you write is sent there. Visitor analytics are switched off in the code: no ad pixels, no session recording, no data brokers, no marketing tools. The hosting platform keeps ordinary technical logs, including IP addresses, for security and abuse, and moderators can read the database to enforce the ground rules.
Deleting things
Delete a story from My page and it goes immediately, taking its comments, reactions, saves and reposts with it. Delete everything wipes every story, comment, vote, save and repost you have made. Two honest exceptions: when a post was reported or removed by a moderator, the moderation log keeps the decision and a short excerpt so the record still means something, and an appeal stays open until it has been answered. Host backups and technical logs can outlive a deletion by a short period.
How long we keep it
Published posts stay until you delete them. Moderation decisions and the decision log are kept indefinitely, because they are how complaints get answered. Technical logs sit with the host on their own retention period. There is no written deletion schedule yet — it is on the review list below rather than dressed up as one.
Health data and UK GDPR
What people describe here is information about their bodies, which UK GDPR treats as special-category data. We ask for as little as possible, never a name, and never put an email beside content. Our position is that publishing a post yourself makes the experiences you describe manifestly made public by you to the site's members — the condition we rely on for showing it — and that the operator has a legitimate interest in keeping that record. You can ask for a copy of your data, correction, restriction, objection or erasure through My page, and you can complain to the Information Commissioner's Office at ico.org.uk.
Adults only
Side Effects is for over-18s. We ask you to tick a confirmation rather than hand over a date of birth or any ID, because the point of this place is that we collect almost nothing. If we find an account belongs to someone under 18, the content comes down.
Still to be reviewed — not yet claimed
These are open, in order of how much they matter. We are listing them rather than writing around them.
- •The operator's legal identity, registered address and a contact route for data requests — the policy cannot be signed off without them.
- •A lawyer's confirmation of the lawful basis and the Article 9 condition for health data, plus a data protection impact assessment.
- •A written retention schedule, including how long host backups keep a deleted post.
Two decisions were taken rather than left open: photos now sit in private storage behind short-lived links, and individual story pages are marked noindex — they stay out of search engines on purpose, because a distinctive detail is how a confession gets traced back to a person.
One honest caveat that no policy can fix: the internet is memory. A distinctive detail — a date, a town, a job, a very specific hospital corridor — can identify you to someone who already knows you. Leave the details only your friends would recognise out of it.
Last updated 13 November 2026. This page is checked whenever the code changes: if a statement here stops matching how the site works, the statement is the thing that gets fixed.