Privacy Policy β SERP Checker
Privacy Policy
This policy explains what data SERP Checker processes while operating SEO checks, analytics, client workspaces, and public client reports.
1. What data we process
- Account data: name, email, user role, profile settings.
- Client data: domains, URLs, keywords, competitors, languages, regions, and check configuration.
- Check results: rankings, answer-engine visibility, citations, technical and content metrics.
- Report data: public tokens, link expiry, block visibility settings, and view counts.
- Technical data: IP address, user agent, view timestamps, referrer, errors, and security events.
2. How we use the data
Data is used to run checks, build reports, render analytics, manage access, protect public links, diagnose errors, prevent abuse, and improve service quality.
3. Public client reports
When a public client report is opened, the system may record the view and detectable rule violations: attempts to print, copy, save the page, open the context menu, or use Print Screen. These signals exist to protect confidential reports and investigate abuse.
4. Third-party processors
To operate the service we may use external providers for search, answer-engine visibility, analytics, email delivery, and infrastructure. We share only the data required for each provider's function.
Google API Services Data
When a user connects Google Search Console, Google Analytics 4, or Google Play Console through OAuth, SERP Checker accesses only the scopes needed for the selected feature: Search Console performance data, Google Analytics reporting data, and Google Play app or review data. This data is used only to display analytics, generate client reports, sync metrics, and operate the connected account features requested by the user.
SERP Checker does not sell Google user data, does not use it for advertising, and does not transfer it to third parties except as necessary to provide or secure the service, comply with law, or with the user's explicit direction. Use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. Users can disconnect Google integrations in the application or revoke access from their Google Account permissions page.
5. Storage and security
The service uses access controls, session management, public-link tokens, password-protected reports, and audit logs. Retention depends on system configuration, data-owner requirements, and the technical need to keep reports available.
6. Rights and requests
Users and client subjects can contact the service administrator to request access, correction, restriction of processing, or deletion, where applicable to their role and the contract with the service owner.
7. Policy updates
This policy may be updated. The current version is always published on this page.