Protected account actions
Passwords are salted and strengthened with PBKDF2. Sessions use secure, HTTP-only cookies, expiration, same-origin checks, and per-session request tokens.
Fast in public.
Careful behind the scenes.
A redirect service is a trust service. ScanSteer separates the public scan path from protected account tools and collects only the analytics needed to make the product useful.
Tenant-separated records
Every dashboard operation verifies organization membership on the server. Database queries never rely on a hidden button as access control.
No raw scan IP storage
Daily visitor estimates use a one-way keyed hash. Raw IP addresses are discarded rather than saved in analytics records.
Billing stays with Stripe
ScanSteer uses Stripe-hosted Checkout and the Customer Portal. Card details never pass through or live in the ScanSteer database.
OPERATIONAL CONTROLS
Designed to fail quietly and safely.
- Signed billing events. Stripe webhook signatures are verified before any subscription record changes.
- Idempotent processing. A Stripe event can be delivered repeatedly without repeatedly changing access.
- Rate limits. Signup, login, reset, and contact endpoints limit automated abuse.
- Safe redirects. Destinations must use complete HTTP or HTTPS addresses; credentials embedded in URLs are rejected.
- Graceful suspension. Billing trouble pauses access according to plan rules without deleting a customer’s work.
- Security headers. Browser protections restrict framing, content sources, referrers, and unnecessary device permissions.
Found a security issue?
Please report it privately to security@scansteer.com. Include enough detail for us to reproduce it, and do not access data that is not yours.