Disqus
No tracked subprocessors.
Documents
| Document | Verified | Changed | Evidence |
|---|---|---|---|
| Trust center | snapshot | ||
| Data processing addendum | snapshot | ||
| Privacy policy | snapshot | ||
| Terms | snapshot | ||
| Security page | snapshot | ||
| Status page statuspage | snapshot |
Subprocessors
None extracted.
Listed as a subprocessor by (1)
Purposes as each company states them.
Pluralsight pluralsight.com Platform Communications Tool
Security record
What public security catalogs list for Disqus, in their words.
Data breaches
- Disqus 17,551,044 accounts Email addresses; Passwords; Usernames
In October 2017, the blog commenting service Disqus announced they'd suffered a data breach. The breach dated back to July 2012 but wasn't identified until years later when the data finally surfaced. The breach contained over 17.5 million unique email addresses and usernames. Users who created logins on Disqus had salted SHA1 hashes of passwords whilst users who logged in via social providers only had references to those accounts.
Have I Been Pwned
Breach data: Have I Been Pwned (CC BY 4.0), which calls every entry a breach, including data scraped from public pages (evidence)
Changes
None since tracking began.