Briefly

I built Briefly because group conversations are often shaped by the quickest or most confident voice before everyone else has decided what they really think.

That is not always a problem. But it becomes one when hierarchy, embarrassment, social pressure, or the fear of being the awkward person in the room changes what people are willing to say.

Briefly is my attempt at a deliberately small alternative. A creator writes one question, optionally adds context, chooses when the discussion should disappear, and receives two links: one to share with participants and one to keep for managing the discussion.

Nobody creates a Briefly account or supplies an email address. Participants reply under randomly generated pseudonyms that remain stable within that discussion on the same browser. Replies can be threaded, agreed with, and sorted by Popular or Latest. The creator can close or reopen replies, remove a reply, change the retention period, or delete the discussion.

The topic, context, and replies are encrypted in the browser with AES-256-GCM before they reach Briefly. The content key stays after the # in the link, which browsers do not send in an ordinary HTTP request. Active discussion data is automatically deleted after the creator's chosen period, with a maximum of 30 days. Private discussion pages contain no analytics or third-party JavaScript.

I want to be equally clear about what Briefly is not. It is not a public forum, permanent community, survey dashboard, messenger, workplace suite, or a promise of perfect anonymity. Anyone who has a participant link can enter the discussion, and someone can still identify themselves through what they write. The separate management link is a capability and needs to be kept private.

I began it as a self-funded side project because I wanted a simple tool for the moments when a group needs candour without turning the conversation into an identity contest. The product is free and browser-first.

I would particularly value honest feedback on three questions:

1. Is the participant-link and management-link handoff immediately understandable?

2. Does the security explanation feel clear without overstating what the product can protect?

3. In what real situation would you use this, and when would you deliberately avoid it?

Briefly is live at https://brieflymade.com/?ref=indie-hackers-post

I am James Downing, the solo founder, and I will answer questions candidly, including the limitations.