Privacy policyContent and disclaimer

Posting a story needs an account, but nothing we store links a story to it. We keep as little as we can about the account.

What we store

The stories people publish: company, city if given, role, reason, the story, the month it was posted, the year the writer left if given, and the “Same here” count. All of it is public. None of it is linked to whoever wrote it: no account number, session or key is stored with a story.

If you put a name or other personal detail in your story, it becomes part of that public story. The check before posting points these out.

For each story we also keep a hash of its claim code (a random code shown to you once after you post), beside the story number and nothing else. With the code you can delete the story or appeal a takedown. We can’t recover a lost code. An appeal is stored with the story number and the month.

Because you sign in to post, we also store the following. We never store your email address, and nothing below says which stories you wrote.

• Your account: a number, and the day you signed up. Reports from accounts under 7 days old aren’t counted.
• Your login: a keyed hash of your email address or Google ID. We can’t turn it back into the address, and only our server’s secret key can recreate it.
• Your passkey, if you use one: the public key and credential ID. The private key stays on your device.
• Your session: a hash of the sign-in cookie, and its 30-day expiry.
• Whether posting is suspended for your account, if it has been.
• Your “Same here” taps and reports: a keyed hash of you and the story, with no account number beside it. The secret key is kept on the server, not in the database or its backups.

We keep, in memory only until the server restarts: sign-in codes (10 minutes, 5 tries) and the half-finished steps of passkey and Google sign-in.

Where your email goes

When you sign up with an email address, we send it to skink.dev each time a new address asks for a sign-in code, and skink.dev checks that it isn’t a throwaway address. Each time you ask for a sign-in code, we send the address to our email provider so it can deliver the code. We don’t keep it after that. Google sign-in uses the “openid” scope only: we don’t ask Google for your email or profile, and Google learns that you signed in to LoggedOut. Google Workspace (work) accounts are refused, because your employer’s admin can see that sign-in.

You can delete your account at any time. That removes the account, its sign-in methods, sessions and your “Same here” and report records. Story totals stay unchanged, and your stories stay up. Only a hash of your login is kept for 180 days, as the law requires, then erased.

What we don’t store

• IP addresses, request logs, exact posting times or browser details.
• Analytics, ads or third-party scripts. Even the fonts come from LoggedOut. The only cookies are the sign-in cookie, and a short-lived one during sign-in.
• Which stories you read, or which account wrote any story.

Spam protection

To stop one person flooding the site, the server makes a one-way code from your connection’s address and keeps it in memory. It limits sign-in emails (5 an hour) and new accounts (3 a day). Each account may post 5 stories a day, one every 30 seconds, counted in memory against the account and gone at restart. Signed-out reading is limited to the newest 10 stories plus up to 10 single-story views a day, counted in memory with the same one-way code and never written to disk. The code can’t be turned back into an address, is never written to disk, and is gone when the server restarts.

On your device

An unfinished story stays in this browser tab until you post it or close the tab. Your theme is saved in this browser and isn’t sent to us.

Work devices

If you use a work device or network, your employer can see that you visited, even though we can’t.

Removal

Tap Report on a story that breaks the content rules, could identify someone, or should come down for a legal reason. A report stores the story, the reason and the month. We review each one by hand. A story reported by 20 different people comes down at once and stays down until we’ve reviewed it. Stories don’t expire, because an expiry date would reveal when each one was posted.

The author can delete their own story at any time with its claim code; that is deleted for good. We can’t tell anyone who wrote a story, because nothing we store says.

Every story here is the personal opinion and experience of the anonymous person who wrote it. LoggedOut does not write, check, verify or endorse any story, and nothing here is a statement of fact by LoggedOut about any company or person.

Community rules

• Write about your own experience at a company you worked for.
• Describe people by role (“my manager”), never by name, photo, handle or contact details.
• No threats, harassment, hate, or encouragement of violence.
• No confidential information you are legally bound to keep secret, such as trade secrets or customer data.
• Don’t make up events or post about a company you never worked for.
• Don’t use the site to identify, pile on or contact a private person.

Removal

Tap Report on the story and pick a reason. We remove stories that break these rules, could identify a private person, or that we’re legally required to take down. A story reported by 20 different people comes down at once until we review it. We review every report by hand, but we can’t reply, and we can’t tell you who wrote a story. If your own story is taken down, you can appeal with its claim code on the Manage a story page.

No warranty

LoggedOut is provided as is. We aren’t responsible for decisions based on a story, so check important facts elsewhere. A company page counts what people posted. It isn’t a rating.

Stories aren’t legal, medical, financial or employment advice. If you’re in danger, contact emergency services.