Fuerza de Voluntad is a support community where people share things they don't share anywhere else. That context changes everything: you're not optimizing conversion, you're caring for people. This post is about the technical and product decisions a space like this demands.
Privacy as a requirement, not a legal page
Here anonymity is a feature: nicknames with no real data, profiles with configurable visibility, and zero third-party trackers in sensitive areas. GDPR wasn't a final checklist. It shaped the architecture from day one: what gets stored, for how long, and who can see it.
Why Invision Community and not a custom forum
For a sensitive community, reinventing the forum is an irresponsible risk: moderation, reporting, granular permissions and privacy have decades of refinement behind them in mature platforms. We chose Invision Community and spent the budget on what actually makes the difference: customization, performance and support.
- A reporting system with response times agreed on with the moderators
- Private clubs for small groups with specific topics
- Integrated donations: the community sustains itself
- A warm visual theme: no dark patterns, no artificial urgency
QA for a community isn't QA for a store
My usual checklist measures flows and performance. Here we added tests I'd never run before: what exactly does an anonymous user see? can a search engine index a private thread? what happens with email notifications if someone shares a device? Every wrong answer here isn't a bug: it's real harm to a real person.
In sensitive communities, the edge case IS the main case. Design for the most vulnerable user and the rest is covered on its own.
Our community deals with very sensitive topics and we needed a solid, well-cared-for home. They gave us exactly that.
Rubén C., Administrator of Fuerza de Voluntad
