Not from us. Posting needs an account, but we store nothing that links a story to it, and we don’t store your name or IP address. A story shows only its month; our backup copies keep finer timing for 7 days, then drop it. So there’s no author to hand over, even to a court. Your story can still give you away through a name, a date or a very small team, and the check before posting flags those. Your employer’s network can also see that a work laptop or work Wi-Fi visited this site, so post from your own phone on mobile data.

The company, the city if you gave one, your role, the main reason, your story, the month you posted, the year you left if you gave it, and how many people said “Same here”. You need an account to post, but nothing we store names it next to the story. The only thing kept for you is a hash of your claim code. If you sign in, we also keep a keyed hash of your email, never the address. The address goes to an email-checking service each time a new address asks for a code, and to our mail provider each time we send you a code. More in the privacy policy.

You can’t edit it, so check the preview before posting. After you post, we show you a claim code once. It is the only way to delete the story or appeal if it is taken down, and we can’t recover it. Use Manage a story. Nothing else ties a story to you, so nobody can prove a story is theirs without that code. If a story names someone or puts someone at risk, tap Report on it.

The breakdown appears once 10 people have shared about a company. With only two or three stories, percentages could point to the people who wrote them.

On anonymous sites, comments turn into guessing who wrote what. If you worked there too, add your own story. It gets the same identifying-details check and counts toward the company’s breakdown.