Safety transparency report
Each quarter, how often DeepShrink’s safety checks noticed that someone may be at risk, what happened then, and how the safety tests did. Totals only, never anything about one person.
The first report will appear here after DeepShrink has been open for a full calendar quarter. Each report covers one quarter and is published after it ends.
How the numbers are made
How they are counted
The numbers come from DeepShrink’s own records and are counted after the quarter ends, by calendar quarter in UTC. A safety record says that something happened: the level, which check noticed it, where in the app and whether the support shown was opened. It holds none of anyone’s words.
Records of accounts deleted before the count are gone and are not included, and safety records are kept for 365 days.
How no one can be singled out
Any number under 10 is shown as “fewer than 10”, and every larger number is rounded to the nearest 10. The report holds no words, no account ids and nothing about one person, and the exact numbers are not kept.
What is not counted
The report counts only the numbers above. Among what it leaves out:
- Messages the checks found nothing in. Every message is checked, but only a flag is recorded, so the report counts flags, not checks.
- What anyone wrote, or anything that could point to them.
- Whether someone was in fact at risk, or what they did after seeing support: DeepShrink cannot know.
- Calls to support lines and visits to services outside DeepShrink.
Corrections
A published report does not change. If we find a mistake, a dated correction appears under that report.
How DeepShrink responds when someone may be at riskUrgent help