SERP-Check Privacy Policy
Last updated: 2026-07-15
SERP-Check is a Chrome extension for manually opening localized Google Search result pages by country, language, optional city or coordinates, and device profile.
Summary
SERP-Check does not send user data to the developer and does not operate any developer-controlled servers.
The extension does not include analytics, tracking pixels, telemetry, advertising SDKs, remote logging, or advertising. It does not sell user data or share user data with data brokers, advertising platforms, or other unrelated third parties.
SERP-Check handles a limited set of user-provided values locally to provide its user-facing features. When the user explicitly opens a search, Google receives the search query and localization parameters as part of the Google Search URL.
Data Handled Locally
SERP-Check stores the following settings in `chrome.storage.local`:
- search query;
- selected country and search language;
- selected city or manually entered coordinates;
- selected device profile;
- selected session mode;
- selected popup interface language.
These settings are used only to restore the popup state and prepare a user-requested Google Search page. They remain on the user's device and are not synchronized or transmitted to the developer.
The user can remove the locally stored settings by clearing the extension's data, removing the extension, or using the relevant browser controls.
Chrome Web Store Data Categories
For Chrome Web Store disclosure purposes, SERP-Check handles the following categories:
- **Authentication information:** Google cookie records are processed transiently only when the user explicitly selects the optional search-cookie cleanup mode. Authentication cookies are not removed, and their values are not read by SERP-Check logic, stored, logged, analyzed, or transmitted.
- **Location data:** the user-selected target country, city, or manually entered coordinates. SERP-Check does not determine or track the user's actual physical location.
- **Web browsing activity:** the user-entered search query and the Google Search URL generated for the requested check. SERP-Check does not read the user's general Chrome browsing history or monitor unrelated websites.
SERP-Check does not collect personally identifiable information, health information, financial or payment information, personal communications, general user activity, or website content.
Google Search URLs
When the user starts a check, SERP-Check builds a Google Search URL from the selected query and localization parameters, including `gl`, `hl`, `uule`, and `pws=0`, and opens it in a Chrome tab or comparison windows.
Google receives the search query and URL parameters because the user explicitly requests navigation to Google Search. This transmission is necessary to provide the extension's stated functionality. SERP-Check does not send this information to any developer-controlled server.
Google processes information received through Google Search according to Google's own terms and privacy policy.
Google Cookies
Cookie access is optional. SERP-Check requests the `cookies` permission and access to `*://*.google.com/*` only when the user selects the search-cookie cleanup mode and starts a check.
In that mode, the extension obtains cookie records for `google.com` and its subdomains only to compare cookie names against a fixed allowlist of Google Search and consent-state cookies, such as `NID`, `AEC`, and `CONSENT`. Only matching cookies are removed before the search page opens. This reduces the influence of the previous Google Search session.
Authentication cookie families, including `SID`, `HSID`, and `APISID`, are not included in the removal allowlist and remain untouched, so the user's Google account sign-in is preserved. Cookie values are not read by SERP-Check logic, used for profiling, stored, logged, analyzed, or transmitted.
The regular mode without cookie cleanup does not access or change cookies.
The incognito mode does not remove cookies from the normal Chrome profile. To avoid reusing or disrupting another private session, SERP-Check requires existing incognito windows to be closed before it creates a new incognito session.
Device Emulation
For a user-selected mobile or tablet profile, SERP-Check uses the Chrome Debugger API only on tabs created for that check. It applies viewport, touch, User-Agent, platform, and supported Client Hint emulation before navigating to Google Search.
SERP-Check does not use the Debugger API to inspect, collect, modify, or transmit Google Search page content.
Data Sharing and Sale
SERP-Check does not sell user data.
SERP-Check does not transfer user data to the developer, advertising platforms, data brokers, analytics providers, or other unrelated third parties.
Google receives the query and localization parameters only when the user explicitly opens a Google Search page. This is required to provide the extension's single user-facing purpose.
Limited Use
SERP-Check's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
User data is used only to provide the extension's user-facing SERP localization features. It is not used or transferred for personalized advertising, profiling, unrelated purposes, creditworthiness decisions, or lending purposes.
Remote Code
SERP-Check does not load or execute remotely hosted code. All runtime JavaScript, device profiles, localization data, and location data are packaged with the extension.
Opening a user-requested Google Search page is navigation to a website and is not remote code execution by the extension.
Third-Party Location Data
The packaged city and location dataset is derived from GeoNames data under the Creative Commons Attribution 4.0 license. The dataset is processed locally and does not cause requests to GeoNames at runtime.
GeoNames: https://www.geonames.org/
Creative Commons Attribution 4.0: https://creativecommons.org/licenses/by/4.0/
Changes to This Policy
This Privacy Policy may be updated when SERP-Check functionality or data handling changes. The latest version will remain available at the same public URL.
Contact
For privacy questions, contact the developer at `yarikbes@gmail.com` or through the LinkedIn profile linked from the extension footer:
https://www.linkedin.com/in/yaroslav-rudyi/