Privacy & threat model
What this site keeps, what it publishes, and what it cannot protect you from.
Screenshots
Screenshots are read on your device. If your browser has built-in text detection (the Shape Detection API), that is used first; otherwise open-source text-recognition software (Tesseract) runs inside your browser. The review screen says which one read your screenshot. Either way, the image is not uploaded. Only the text you review is sent, and only when you ask for the review screen. The image is not kept in a draft, a thumbnail, or any error report. Files are limited to 8 MB and 16 megapixels.
Because the image is processed on your device, there is no photo metadata (such as location data) for us to receive or remove.
Scrubbing
Before you file, fixed rules remove the greeting name, the sender’s first name, phone numbers, every other number, emails, links, places and other capitalized words that may be names. Rules also drop phone screen labels, the contact name at the top of a conversation, your own replies, and other conversations visible in a screenshot. The rules are the same for every report. Nothing in the message can change them, including text written to look like instructions.
Rules make mistakes. That is why you review the scrubbed message and can remove more text before filing.
What is stored
| Field | Stored | Public |
|---|---|---|
| Screenshot | No (never uploaded) | No |
| Full sender number | No (used once, then discarded) | No |
| Sender area code | Yes | Yes, as a count |
| Sender prefix (next 3 digits) | Yes | No |
| Keyed hash of the number | Yes, expires after 30 days | No |
| Scrubbed message | Yes | No, only pattern counts |
| Category | Yes | Yes, as a count |
| City named in the message | Yes | No |
| Filing time | Yes | Day only |
| Your IP address | No. Held in memory only, as keyed codes: up to an hour for rate limits, and up to 7 days (reset when the server restarts) to spot the same report filed again from the same connection. The key for that check is created when the server starts and is never saved. | No |
| Deletion receipt | Only a scrambled version | No |
There are no accounts, cookies, analytics, tracking pixels, or third-party scripts.
The site’s service worker stores copies of the app’s own files (styles, scripts, icons, the report page and the on-device text-recognition files) on your device only, so repeat visits load faster. It stores no report data. You can remove it by clearing this site’s data in your browser settings.
This table describes what this app keeps. The hosting provider runs its own network and HTTP logging, separately from the app. The official instance is hosted on Railway, whose HTTP logs record the IP address each request came from (Railway’s log documentation). How long Railway keeps them is set by Railway, not by this site: see Railway’s privacy policy.
The keyed hash, honestly
The keyed hash is pseudonymous, not anonymous. Its protection is the secrecy of one key on this server. Anyone who obtained that key and the stored area code and prefix could recover a sender number by trying at most 10,000 candidates. The hash is used only inside this site, to spot the same sender sending the same text twice within 24 hours, and, in memory only, the same report filed again from the same connection within 7 days. It expires after 30 days and is never shown or exported. If the key is rotated, old hashes no longer match new ones.
Residual risks
- In a small dataset, a combination of prefix, city named in the message, category and time could point to one business. That is why those fields are never published together, or at all.
- Reports can be spoofed or fabricated. Three matching reports show repetition, not three independent witnesses.
- Your browser and phone keep their own history. This site cannot clear it.
- The hosting provider can see network traffic metadata such as IP addresses, and keeps its own logs (see above).
- Reports from different connections cannot be linked. Someone using several networks or a VPN can still file the same report more than once.
- People sharing a mobile carrier’s connection may occasionally have a genuine report not counted.
- When a report is not counted because the same connection filed it recently, that flag is stored with the report. It implies the two reports came from the same connection, though not which one.
Deletion
Your receipt code is the only way to delete a report. We store only a scrambled version of it, so we cannot recover it. Deleting removes the report at once from counts and patterns, and from every future data release. A pattern that falls below 3 reports disappears. Copies already downloaded cannot be recalled. Backups are kept for at most 7 days, and a restore re-applies the deletion list so a deleted report does not come back.
Contest or takedown
If something on this site harms you, for example a pattern that points at your business or number, tell us privately. Flagged patterns are removed from public views while they are reviewed. The maintainer aims to respond within 7 days; security and takedown requests come before other work. You can also email [email protected].
Contacts
Privacy: [email protected] · Security: [email protected] · Abuse and takedown: [email protected]