Dating app safety promises depend on people doing the work behind them. This reflection revisits my account from July 2023, with that date kept clear.
On 8 July 2023, I spoke about the people behind dua’s safety work: checking suspicious profiles and responding to reports, Monday to Sunday. A promise on a screen needs people doing the work behind it.
Those details belong to that recording. They are not a verification of today’s staffing, service hours or safety outcomes. The enduring founder question is what work sits behind the promise to take users seriously.
For a product team, start by tracing what happens after somebody asks for help. Where does the report arrive? Who reviews it? What information is needed to understand it, and what happens when the first person cannot resolve it?
These questions make responsibility visible. A button or a reassuring sentence is only one part of an experience that also depends on what happens afterwards.
Look at the explanation alongside the reporting process. Does it tell people how to raise a concern and what kind of response to expect? Does it make promises the team can actually support? Where circumstances vary, clarity is more useful than an absolute assurance.
The source post describes a team’s effort, not a guarantee that nothing can go wrong. I want the same distinction in the written version: take the work seriously, make responsibilities clear and keep the promise connected to what the team can deliver.