Encryption in transit
The Hitsteps website, dashboard and tracking endpoints accept only TLS 1.2 or newer. Plain HTTP is redirected to HTTPS, with managed certificates.
Everything your security review needs, on one page: the standard answers and a direct security contact.
The Hitsteps website, dashboard and tracking endpoints accept only TLS 1.2 or newer. Plain HTTP is redirected to HTTPS, with managed certificates.
The Hitsteps application and its databases run in Hetzner data centers in Germany and Finland. Servers are firewalled, patched and monitored, and production data access is limited to authorized staff. Databases are backed up regularly, and backups are encrypted (AES-256) before they leave our servers.
Without visitor consent, session recordings mask identifying details in the browser, before anything is sent. Passwords and payment card fields are always masked. IP anonymization is on by default, and each website's data stays in its own account. We do not sell your data, use it for advertising or use it to train AI models.
Dashboard access requires sign-in, and you can turn on two-factor authentication with an authenticator app, backup codes and trusted devices. Passwords are stored only as one-way hashes, never in plain text. Sign-in is rate-limited, repeated failed attempts trigger a CAPTCHA check, and sign-ins are recorded in a security audit log.
Email security@hitsteps.com about any security issue you find. Researchers can also report privately through our Open Bug Bounty program.
Privacy Policy Subprocessors security.txt security@hitsteps.com
Send your questionnaire or any open question to security@hitsteps.com.