- How long does the $9.95/mo price last?
- For good. It is not an introductory discount that expires after a few months: your team keeps its launch seat, and if you cancel and later subscribe to Pro again from the dashboard, you get $9.95/mo again.
- What happens if I change plans?
- Switching plans in the billing portal moves your subscription to that plan's regular price, and switching back there to Pro is billed at the regular $19.90/mo. To keep the launch price, stay on Pro, or cancel and subscribe to Pro again from the dashboard.
- Do I need a coupon code?
- No. While launch seats are open, upgrading to Pro from the dashboard checks out at $9.95/mo automatically.
- Is it a different product from regular Pro?
- No. Same 50,000 checks a month, same 30 requests per minute, same detection engine, production license, allow lists, and verdict-change webhook. Only the price differs.
- Can I try it before paying?
- Yes. The free sandbox plan gives you 1,000 checks a month with the same engine and no card, so you can wire up the integration first and upgrade when you ship.
- Do you log the URLs we send?
- No. Our request logs record your account, the verdict, reason codes and timings, never the URL, its query string or its hostname. Request logs are kept for 7 days.
- What do you store, and for how long?
- A one-way hash of each URL with its verdict: 6 hours for safe URLs, 24 hours for malicious or suspicious ones, 5 minutes for partial results. Hourly usage counts with no URLs, for 25 months, for your usage page and billing. Records of rate-limited requests with no URLs, for 90 days. For URLs we judge malicious or suspicious, the hostname only (never the path or query) and the IP addresses it resolved to, for 30 days after we last see it.
- What about short links?
- We follow up to three redirects to find the real destination, and never load the page itself. The shortening service receives that request, as it would from any browser. The destination URL is cached with the verdict for up to 24 hours so repeat checks are fast, then deleted.
- Does anyone else see our URLs?
- When a URL partly matches a known-bad list, we send a 4-byte hash prefix to our threat-intelligence provider, never the URL. If our local copy of those lists is more than 2 hours old, we fall back to sending that provider the normalized URL. All traffic is encrypted in transit, and we drop fragments and known tracking parameters before checking. Even so, don't put secrets in URLs you submit.