Privacy

What stays local

All measurement, generation and validation happens with JavaScript on the page you are looking at. That is a deliberate design choice, not just a privacy promise: it is why the tools work on localhost, on staging, and on pages you have not published yet. A favicon you upload to the simulator is read in the browser and never leaves it.

The one outbound request, and when it happens

There is a single exception, and it is your own asset. On the social preview tool, when you supply an image URL, your browser loads that image to render the card, exactly as it would on any web page. That request goes to the image's host, not to realserp, and only happens because you entered the URL. No other tool makes any outbound request with your data.

Analytics

If analytics are enabled, realserp uses privacy-conscious, pageview-level measurement through a first-party proxy, with autocapture and session recording turned off, so no keystrokes or tool input are ever collected. As shipped, the analytics key is unset, which means nothing analytics-related loads at all. If that changes, this page will describe exactly what is measured before it is turned on.

Cookies

The tools set no tracking cookies. The only thing stored on your device is a single local preference remembering whether you chose light or dark theme, which stays in your browser and is never sent anywhere.

Ads and affiliate links

realserp is funded by contextual tool recommendations and, in future, by display advertising. Affiliate links are disclosed inline wherever they appear, and are covered on the about page. If and when display ads are enabled, any ad provider's own data practices will apply to the ad slots, and this page will name the provider and link its policy.

Questions

If anything here is unclear, or you believe a tool sent data it should not have, tell us on the contact page. A privacy report is treated as a bug report.