Our approach
The best way to protect data is to not have it. UserHint collects the minimum a feedback tool needs: cookieless page-view analytics that identify no one, no advertising scripts, no payment card data on our servers, and a widget that stores nothing in a visitor's browser until they open it. This page describes the measures behind that, honestly and without badges we have not earned.
Encryption in transit
All traffic to the Service, including every widget request from your visitors' browsers, is encrypted with TLS (HTTPS). The Service sits behind an edge network that provides DDoS protection and a web application firewall.
Application security
- Passwords are stored only as salted hashes (bcrypt); we never see or store them in plain text.
- Two-factor authentication (TOTP) is available on every account, with recovery codes.
- New accounts must verify their email address before using the product.
- Sessions use HTTP-only, same-site cookies, and forms are protected against cross-site request forgery.
- The widget API applies rate limits and abuse detection so it cannot be used to flood your inbox or our infrastructure.
- The application is built on a mature, security-maintained web framework, and dependencies are kept up to date.
Infrastructure and access
The Service is hosted with an established cloud provider. Production access is strictly limited and requires key-based authentication. The full list of infrastructure providers, with roles and locations, is in the subprocessor section of our Data Processing Agreement.
Data minimization
- The widget sets no cookies on your site and stores nothing in a visitor's browser until the visitor opens it.
- Submissions carry only what the inbox shows: the message, an optional rating, the page, and coarse device context.
- Visitor IP addresses are kept at most 30 days, for abuse prevention only.
- Deleting a submission, a widget, or an account removes the covered data immediately and permanently.
Reporting a vulnerability
If you believe you have found a security issue in UserHint, email [email protected] with enough detail to reproduce it. We will acknowledge your report quickly, keep you informed while we fix it, and credit you if you want. Please give us a reasonable time to fix an issue before disclosing it publicly, and do not access data that is not yours while testing.