Frequently Asked Questions
Privacy, coverage & how it works
Straight answers on Sentinel's zero-plaintext cryptography, dark-web and stealer-log intelligence, attack-surface scanning, consent, compliance and how the plans work. 58 questions and counting.
Today: public code hosts (GitHub), paste sites, an internal breach and credential corpus, the HaveIBeenPwned Pwned Passwords range API, and Certificate Transparency logs (crt.sh) — plus first-party DNS, TLS and port checks on domains you have verified. Tor/.onion marketplace crawling, ransomware leak-site ingestion and our own stealer-market collection are on the roadmap, not live. We never claim to 'scan the whole dark web'; we validate exposure against breach and credential corpora and tell you exactly which sources we hold.
In four steps: normalised into a canonical form, shown only as a masked value such as u***r@example.com, hashed into a blind index for matching, and encrypted with AES-256-GCM under your tenant’s key. A stolen database or backup therefore yields meaningless ciphertext and one-way hashes, not your identifiers.
Still have a question we have not answered?
Open a free account and run a live scan in minutes, or explore the console with a seeded demo account.