SOCTitan

How we protect the data we handle

Our portal shows leaked passwords so that you can fix them. That makes it a target, so it is built to be harder to misuse than the systems it protects. This page is written for your IT lead and your data-protection officer.

Who can get in

  • No public registration. Accounts are created by us, or by a partner for their own clients, after we have checked who the customer is.
  • Device binding. An account opens on one device only. The first sign-in stores a random 256-bit device key in a secure, HTTP-only cookie; we keep only its SHA-256 hash. Any other device is refused until an administrator resets the binding.
  • Sign-in codes. Administrators and partners must use an authenticator app. It can be required for any other user too.
  • Expiring access. Each account has an end date set in hours. When it passes, open sessions end on the next click.
  • Lockout and throttling. Repeated wrong passwords lock the account for 15 minutes. Sign-in attempts are limited per network and per username.
  • Short sessions. Sessions end after 30 minutes without activity and after 8 hours in any case.

What each person can do

  • Each search type is a separate permission, set per user.
  • Seeing a leaked password in clear text is its own permission. Without it, passwords are masked before they leave our server.
  • Exporting is a separate permission, and exports keep passwords masked unless the user may see them.
  • Searches are limited per minute and per day for each account.

What is recorded

Every sign-in, failed sign-in, search, password reveal, export and administrator change is written to an audit log with time, account and network address. Customers can see their own activity in the portal. Partners see the activity of their own clients. Logs are kept for 3 months and then deleted automatically.

How the platform is built

  • All traffic is encrypted with TLS, with HSTS and a strict content security policy. The site loads no third-party scripts, fonts, trackers or analytics.
  • Your browser only ever talks to soctitan.com. Searches are run by our server; connection keys to our licensed data sources are stored outside the web server’s public folder and are never sent to the browser.
  • Full results are kept on our server for 20 minutes only, encrypted with a per-account key, so that you can reveal or export them. After that they are deleted.
  • Passwords for portal accounts are stored with Argon2id. Sign-in secrets are encrypted at rest.
  • Every form is protected against cross-site request forgery, and every page is protected against being framed by another site.

Data protection

SOCTitan is operated from Germany and follows the EU General Data Protection Regulation. We have documented a legitimate-interest assessment, a data-protection impact assessment and a record of processing activities, and we offer a data-processing agreement to every business customer.

The same documentation supports your own obligations under:

  • South Africa: Protection of Personal Information Act (POPIA)
  • Kenya: Data Protection Act, 2019
  • Uganda: Data Protection and Privacy Act, 2019
  • Rwanda: Law No. 058/2021 on the protection of personal data and privacy
  • Tanzania: Personal Data Protection Act, 2022

Customers may only search domains, addresses and accounts they own or are authorised to assess. Searches of third parties without authorisation are forbidden by our terms and end the account.

Request our data-processing agreement

Found a problem?

If you believe you have found a security weakness in SOCTitan, please tell us. See how to report a vulnerability.