Privacy

Effective November 11, 2026

Your projects stay in your browser

The redirect maps you paste or load, project names, file names, check results and the history of earlier checks are stored only in this browser (IndexedDB), together with the purchase record of an unlocked project. They are not uploaded to RedirectProof. CSV files and printable reports are created in your browser.

We cannot restore projects you remove from this browser or lose by clearing site data. Keep your CSV and, for unlocked projects, download the purchase record.

URLs sent to check redirects

To trace a redirect, the server has to request the URL. While a check runs, your browser sends the server the source URLs being checked (with their row position) and the project’s random ID, plus its purchase record when the project is unlocked. The server requests each URL and the redirect targets it returns, and sends the hop chain back to your browser. Expected URLs are never sent.

• Source URLs and redirect targets are held in memory only for the duration of the request. They are not written to a database or log.
• The requests are plain GET requests from our server with a fixed RedirectProof user agent, no cookies, no login and no body. The page content is not downloaded or kept; only the status code and Location header of each hop are read.
• The sites you check see our server’s IP address, not yours.
• To prevent abuse, the server keeps short-lived in-memory counters per IP address and per project ID (how many URLs were checked recently). They are not stored on disk.

Payments and orders

• Checkout: the payment method you chose, the project’s random ID (a UUID that says nothing about your site) and a random checkout attempt ID. The server creates the checkout with Square or PayPal and returns a signed ticket that your browser keeps.
• Payment verification: the server keeps the provider order identifier, the project ID, a random per-attempt value and the payment status in a private order ledger (the item is “RedirectProof Full Migration Check”, $49.00 USD). It checks with Square or PayPal until the provider confirms the payment or the order closes. After a confirmed payment, the return link can restore the unlock in another browser; the server stores only a keyed hash of that return code.
• Unlock check: when you open an unlocked project, its ID and purchase record are sent so the server can confirm them.

Payments are handled on Square’s or PayPal’s own pages under their privacy policies. RedirectProof does not see or store card numbers or PayPal credentials.

Campaign counters

The server counts free results CSV downloads, hosted-checkout starts and provider-confirmed live sales, with a coarse campaign label from a fixed list (for example redirectproof_guide, redirectproof_launch or redirectproof_agency), the language “en”, payment provider, mode and the integer price paid. No IP addresses, cookies, URLs, project names or results are stored with these counts. Order numbers are stored only as a keyed hash to avoid double-counting. Sandbox payments and the demo are never counted.

Local storage

Besides IndexedDB, the app uses local storage for the last project you opened and a campaign label from the link you arrived by (kept 30 days). No advertising or third-party tracking scripts are used.

Contact

Questions: contact support.