How to remove yourself from dehashed.com
What they publish
A searchable index of leaked/breached credentials and PII (emails, usernames, passwords, IPs) aggregated from an estimated 13+ billion records across ~70 data sources, plus WHOIS/domain intelligence; this is stolen/leaked data being resold as a lookup service, not a self-generated consumer profile
Removing yourself, step by step
0 of 4 done- Submit a request via https://dehashed.com/support describing the exact data to be suppressed/removed and why.
- Or email support@dehashed.com directly, citing the "request that we delete your information" right described in the privacy policy at https://www.dehashed.com/legal.
- Be prepared to verify ownership of the email/account in question.
- Expect this to only cover DeHashed's index, not the underlying breach itself (which is out of anyone's control once leaked).
Tap a step to tick it off. Progress is saved in this browser only.
How they confirm it
unspecified — likely requires proof of identity/ownership of the affected email or account given the sensitivity of breach data
If they ignore you
Limited — DeHashed markets itself as a security-research tool operating on already-public leaked data, so legal leverage is weaker than with a traditional data broker; GDPR/CCPA deletion rights can still be asserted if the requester is a covered resident.
Re-listing risk for this site: High — DeHashed indexes already-public leaked breach dumps; even if one record is suppressed, new breaches containing the same person's data are continuously ingested and cannot be preemptively blocked
Common questions
How do I remove myself from dehashed.com?
Email their privacy address, support@dehashed.com. The guide above lists 4 steps, and this page writes the removal request for you to send from your own email.
Do I have to solve a CAPTCHA to opt out of dehashed.com?
Their opt-out form has a CAPTCHA, so you complete it yourself.
Will my information come back on dehashed.com?
High — DeHashed indexes already-public leaked breach dumps; even if one record is suppressed, new breaches containing the same person's data are continuously ingested and cannot be preemptively blocked. Check again in about 60 days.