This policy covers two things: the getsiteradar.com website and the SiteRadar WordPress plugin.
1. This website
getsiteradar.com sets no cookies and runs no analytics or advertising scripts. If you email us, we use your address only to reply.
Waitlist: if you join the launch waitlist, we store your email address on our own server (no third-party mailing service) and use it for one purpose: telling you when SiteRadar becomes available. We don’t share it, sell it, or send anything else. To be removed before or after launch, email [email protected] from that address.
2. The SiteRadar plugin — where your data lives
SiteRadar is self-hosted software. Everything it collects — visitor counts, affiliate click events, search-performance data, content audit results — is stored in your own WordPress database on your own server. Nothing is transmitted to us. We operate no servers that receive, store, or process your site data, and we have no access to it.
- Visitor analytics are aggregate and anonymous: no personal identifiers, no IP addresses stored, no cross-site tracking cookies.
- If you run several sites with the network dashboard, data moves only between your own WordPress installations, authenticated with a secret key you control.
3. Google user data (Search Console connection)
If you connect a Google account, SiteRadar requests the read-only scope webmasters.readonly to fetch your own Search Console data (impressions, clicks, positions, index coverage) for the sites you verify.
- This data is fetched directly from Google to your WordPress server and stored only there. It is never sent to us or to any third party.
- SiteRadar’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the plugin’s user-facing features — never for advertising, never sold, never used to train AI models.
- You can disconnect at any time from the plugin’s settings page, or revoke access at myaccount.google.com/permissions. Disconnecting deletes the stored token from your server.
4. Bing Webmaster and other APIs
The same principle applies to the optional Bing Webmaster connection and any AI provider you configure: your keys, entered by you, stored on your server, used only to fetch or process your own data. We never see them.
5. Purchases
When paid licences launch, checkout and billing will be handled by a payment processor acting as merchant of record; their privacy policy will apply to payment data and will be linked here. We will receive only what is needed to issue and validate your licence (name, email, licence key).
6. Contact
Privacy questions: [email protected]