Overview
This Privacy Policy explains what data PPC Tools Extension stores, how that data is used, and what third-party resources may be requested as part of user-facing extension features. The extension is designed to run locally in the browser and does not operate a developer-controlled backend for collecting extension data.
Data Stored in the Browser
PPC Tools Extension stores data only to provide and remember its extension features. Depending on which modules are enabled and configured, this may include:
- enabled or disabled module states;
- extension and module settings;
- panel position, size, and collapsed state;
- user-entered search query cleanup words and negative keyword lists;
- placement cleanup filters, excluded items, and panel state;
- ad highlighting domain lists;
- favicon cache entries used to display domain icons in ad highlighting tools;
- Google Tag Manager configurations, including client domain, GTM container ID, active or paused state, and timestamps.
This data is stored with Chrome extension storage in the user’s browser. Some settings may sync through Chrome Sync if the user has enabled browser synchronization.
How Data Is Used
Stored data is used only for the extension’s visible PPC workflow features: cleaning search query workflows, cleaning placement workflows, highlighting search ads, customizing supported advertising platform interfaces, blocking disruptive Yandex popups, and managing user-configured GTM injection workflows.
PPC Tools Extension does not use stored data for personalized advertising, user profiling, creditworthiness, lending decisions, or any unrelated purpose.
Supported Websites and Page Content
The extension runs static content scripts only on websites declared in its extension manifest, including Google Ads, Yandex Direct, Google Tag Manager, selected Yandex pages, Google Search result pages, and Yandex Search result pages. GTM Injector has no static content script on client domains: after a direct user action, it requests access only to the selected domain and registers a fixed packaged bootstrap through the Chrome User Scripts API.
Some modules read page content locally in the user’s browser to provide their visible functionality. For example, modules may read search query rows, placement rows, ad result domains, billing summary values, or Google Tag Manager page structure. This processing happens locally in the browser and is not sent to the developer.
Clipboard
The extension may write text to the clipboard only after a direct user action, such as clicking a copy control in a module UI. The extension does not read clipboard contents.
Google Tag Manager Injector
The GTM Injector manager UI is enabled by default for new installations, but it does not run anything automatically. Registration requires a valid GTM container ID, a domain explicitly selected by the user, user confirmation, and Chrome access to that exact domain.
The extension does not accept or store arbitrary JavaScript. Through the Chrome User Scripts API it registers a fixed bootstrap packaged with the extension, which loads gtm.js from www.googletagmanager.com for the user-selected container. The module does not add the <noscript> variant or request ns.html. This feature is not used to update, replace, or control the extension’s own packaged logic.
Favicons
Ad highlighting modules may request favicon files from domains shown in supported search result pages. These requests are used only to display recognizable domain icons in the extension UI. Favicon results may be cached locally in Chrome storage.
Data Sharing and Third Parties
PPC Tools Extension does not sell user data. PPC Tools Extension does not transfer saved extension data to the developer or to third-party data brokers.
Data may be handled by the browser’s own Chrome storage or Chrome Sync features if browser synchronization is enabled. When GTM Injector is used, Google Tag Manager resources are loaded by the page for the user-configured GTM container. Favicon requests may be sent to the corresponding website domains for icon loading. Normal visits to Google Ads, Yandex Direct, Google Tag Manager, Google Search, or Yandex pages are also subject to those services’ own terms and privacy practices.
Website Analytics
The public PPC Tools Extension website may store local website usage statistics in the visitor’s browser using localStorage and sessionStorage. This may include section views, interface preview interactions, UTM parameters, click IDs, referrer host, landing path, and timestamps.
This website analytics data is stored locally in the visitor’s browser by the static website and is not sent to a developer-operated analytics server by this site.
Data Retention and Deletion
Stored extension data remains in the user’s browser until the user changes settings, clears module data, clears browser extension data, disables browser sync storage, or uninstalls the extension.
Users can delete extension data by removing the extension from the browser. Depending on the browser, users may also clear extension storage from browser settings. Website analytics data can be removed by clearing site data for this website.
Security and Limited Use
The extension uses Chrome extension APIs and browser storage for its functionality. It does not require account registration and does not include a developer-operated backend for collecting extension data.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Changes to This Policy
This policy may be updated when the extension’s functionality, permissions, storage behavior, or data practices change. The «Last updated» date will be changed when the policy is updated.
Contact
For privacy questions, contact the developer through the developer email listed for PPC Tools Extension in the Chrome Web Store listing.
