What we store
The service stores a report identifier, submitted and normalised URL, domain, scan time, rule findings, risk score and limited policy-approved evidence. The full submitted address supports exact duplicate detection while the report is public, but public pages receive only a sanitised website origin. URL Radar does not retain credentials, cookies, authentication tokens, browser credentials, executed commands or downloaded payloads.
Payments and order information
Payments are processed through Stripe-hosted checkout. URL Radar does not receive or store your card number or CVC. Card and billing details are entered directly on Stripe.
URL Radar stores the checkout email supplied by Stripe, order and report references, Stripe checkout/payment references, amount, currency, payment and package status, and related timestamps. These records support report delivery, payment reconciliation, support and refunds. This is separate from the expiry of your private download link; link expiry does not mean that payment records have been deleted.
Public free scans and private archive
Free scans create a public report. For 24 hours, the dashboard links to it using a sanitised website address with paths, query values, fragments, embedded credentials and submitter information removed. The public report expires after 30 days and remains excluded from search indexing. The underlying report and policy-approved evidence are then kept in an owner-only private archive for defensive research, detector regression testing and future training material. They are not available through the expired public link.
External intelligence
Public RDAP and DNS lookups receive only the destination hostname or resolved public IP address. Enabled URL-reputation providers receive the final scheme, hostname, port and path for a list lookup; credentials, query values and fragments are removed first. Do not submit secret path values.
Service analytics
Aggregate product-journey events record only the page category (home, pricing or report), offer visibility and purchase-button actions, plus flags for recognised automation and allowlisted operator traffic. They use no visitor identifiers, cookies, local storage, target URLs or order tokens. Client events respect Do Not Track and Global Privacy Control. They are counts of events, not identified people or linked conversion sessions.
Restricted operational logs retain the submitted URL, report identifier, result summary, user agent and request network chain for up to 30 days. These records support abuse investigation and service monitoring and are not published.
For indexable public pages, a separate acquisition event records only the canonical route, the referring website hostname and bounded campaign labels when present. It does not retain the referrer path, an advertising identifier or a submitted scan URL.
Expiry and deletion
Public access and customer download grants expire on their stated schedules. Expiry removes public or customer access; it does not delete the owner-only defensive archive. Operational audit records keep their separate 30-day workspace retention. Contact URL Radar with a privacy or removal request.