Privacy Policy
This policy describes the data used to provide website health monitoring and account access.
Account and demo data
The demo page uses clearly labeled fictional data. Signed-in monitoring and scans process your account email, submitted domains, and saved scan results.
Production data practices
Google verifies your email for sign-in. We store your account email, monitored domains, group permissions, scan history and subscription identifiers to provide the service. Stripe processes payments; card details are not stored by this application. Operational email is sent through SMTP2GO when configured. Contact chris@deepsecurity.io for privacy questions or to request account data deletion. Some billing or abuse-prevention records may need to be retained; applicable requirements and the affected records will be reviewed with your request.
Public scan evidence and providers
Scans store public findings, static title and heading observations, visible-text fingerprints, third-party resource hostnames, and assessment timestamps. When configured, submitted and final homepage URLs are sent to Google Web Risk; homepage URLs are sent to Google PageSpeed Insights for lab testing. Observed package names and version declarations are sent to OSV for advisory lookup. Provider results may be cached, and recommendations use visible hosting-edge indicators. The scanner does not submit forms or sign in to monitored sites.
Website analytics
Vercel Analytics measures visits and selected interactions on public marketing pages, including demo clicks, plan selection, scan outcomes, scroll milestones, and Core Web Vitals (LCP, INP and CLS). Submitted domains, email addresses, scan evidence, account pages, and URL query parameters are excluded from our custom marketing events. Analytics honors supported Do Not Track and Global Privacy Control preferences. Server-side aggregate reporting separately counts verified sign-ins, first observed accounts and first paid subscriptions using hashed deduplication keys. It does not reconstruct historical signups or transmit account details in browser analytics. We do not use advertising trackers or session replay in this implementation.
Cookies and tracking
Sign-in uses an opaque HttpOnly, Secure, SameSite=Lax session cookie backed by a revocable server-side session, with an eight-hour absolute expiry and a 30-minute inactivity limit and short-lived OAuth cookies to verify the sign-in request. We use an essential signed device cookie (hf_scan_device) to help enforce two lifetime free scans and deter abuse. It is HttpOnly and Secure in production, with a maximum age of 400 days. Account, device, and platform-provided IP identifiers are stored as keyed hashes in the scan-usage ledger rather than raw values. Lifetime usage is retained to prevent quota resets. Shared networks may share the free allowance; paid plan access is checked separately. This cookie is used for service protection, not advertising.
