Privacy
Privacy policy
Short version: we don't collect, store, or sell anything from your diagnostic runs.
TL;DR
- All probes run in your browser. Nothing is uploaded.
- We use Vercel Analytics for page views and Core Web Vitals only — no probe results, no IP, no fingerprint.
- The optional share link is a short opaque blob stored on a Cloudflare Worker, auto-deleted after 30 days.
- We don't use third-party trackers, ads, or social pixels.
What we collect
We do not collect any diagnostic data. The probe results stay in your browser and are rendered into the DOM only. If you click Share, the rendered summary is uploaded to a Cloudflare Worker as a JSON blob. The blob contains the per-service reachability, inferred routing regime, your public IP as seen by the cdn-cgi/trace endpoints, and a UTC timestamp. The Worker stores it for 30 days, then deletes it. The blob's URL is the only thing you can hand to other people — there is no PII inside.
Analytics
We use Vercel Analytics (page views, referrer, country) and Vercel Speed Insights (Core Web Vitals). Both are cookieless, server-aggregated, and never see probe results. You can opt out by enabling your browser's Do Not Track or by blocking the vercel-insights.com / vercel-analytics.com domains.
Cookies
We set a single cookie: ipcombo-locale, used to remember your language choice for one year. That's it. No advertising cookies, no third-party cookies, no cross-site tracking.
Third-party services we load
We embed the 45 service icons we test (from each service's own favicon endpoint or, for missing icons, Google's favicon service). We do not embed third-party JavaScript, advertising tags, or social widgets. Our only externally-loaded script is Vercel's analytics, loaded by the platform itself.
Your rights
You can request a copy of any share blob you created, or ask us to delete it, by emailing privacy@ipcombo.com. We respond within 30 days.
Changes to this policy
If we change anything material, we'll bump the Last-updated date at the top and add a short note in the changelog. Substantive changes (e.g. adding a backend log) will also be announced on the blog.