VeiligWijdemeren
A free, anonymous community safety platform for residents of Wijdemeren — built without collecting personal data.
Type
Community platform
Our role
Strategy, design, app development
Status
In active testing
The problem
Residents in Wijdemeren had no independent, anonymous way to share safety concerns with their community. Existing channels required personal information, were not anonymous and often went unacknowledged.
The result was that many safety observations — things residents genuinely wanted their neighbours to know about — were never shared at all. Not because people did not care, but because the available options felt either too complicated, too official or too exposed.
Who it is for
Residents of the Wijdemeren municipality — a community of around 25,000 people. People who want to share something they noticed with their neighbours. People who want to stay informed about what is happening in their area.
The platform is deliberately not for official use. It is not connected to police systems or municipal databases. It is a community tool, built for and governed by the community.
Build the simplest thing that genuinely helps — without collecting anything you do not need.
The core insight was that anonymity and utility are not in conflict — they just require different technical choices. You do not need to know who is making a report to make the report useful to a community.
VeiligWijdemeren is built around that principle. No accounts, no personal data, no tracking. Reports go through a lightweight moderation process before being published, which keeps the content reliable without requiring identity verification.
The platform is free. It will stay free. It is maintained as a public resource for the Wijdemeren community.
The process.
Understanding what residents actually needed
We started by talking to residents, not building features. The core insight was simple: people wanted to share local safety observations with their community — anonymously, without an account, without their data being stored. Everything else followed from that.
Deciding not to collect data
Most platforms ask for more information than they need. We made an early decision that VeiligWijdemeren would work without personal data — no accounts, no tracking, no profiles. This shaped every technical decision that followed.
Designing for trust, not engagement
The interface was designed to make the platform feel safe and understandable. Clear language about what we collect (nothing personal) and what we do with reports (community moderation before publishing). No dark patterns, no notification tricks.
Building the moderation system
Without user accounts, preventing spam required a different approach. We built a lightweight moderation layer so that reports are reviewed before appearing publicly — keeping the platform useful without compromising on privacy.
Testing with real residents
The platform went into testing with actual Wijdemeren residents before any public launch. Their feedback shaped the final design — what information was useful, what felt confusing and what built confidence in the platform.
What we chose to do — and not do.
No user accounts
Accounts create friction and collect data. You can report a safety concern without one.
Community moderation instead of AI filtering
Algorithmic content moderation gets community context wrong. Human review gets it right.
Free — permanently
Community safety tools should not have a subscription model. This is a public resource.
Not connected to official systems
Independence matters. The platform is for the community, not for data collection by authorities.
What we took from this.
Starting from a privacy-first position does not make building harder — it makes it clearer. When you cannot collect data to solve a problem, you have to find a better approach to the underlying problem instead.
Community trust is earned through transparency, not through features. The clearest thing we could do to build confidence was to explain exactly what the platform does and does not collect, in plain language, on every relevant screen.
Testing with real users before launch is not optional. The residents who tested VeiligWijdemeren found things we had missed — not because they were technical, but because they were the actual people the platform was built for.
Next project
Leg 'm neer