Information We Access
The extension only accesses information necessary to operate its debugging features on the active browser tab. This includes page elements related to ad units, banner wrappers, ad request timing available from the browser Performance API, and the `uadrefresh_debug` cookie used for testing UAF behavior.
How This Information Is Used
- To detect supported ad units and banner wrappers on the current page.
- To show whether ad units appear to be duplicated, refreshed, or requested more than once.
- To scan the active page for banners at the user-configured interval when Realtime check is enabled.
- To let the user enable or disable the `uadrefresh_debug` cookie for debugging purposes.
- To copy ad unit IDs, banner IDs, or the displayed public IP address to the clipboard when the user clicks a copy button.
- To scroll to and visually highlight selected banner elements when the user clicks the Goto button in the extension popup.
- To display the expiration time of the debug cookie in the extension interface.
Chrome Permissions
- storage: Saves extension preferences, such as Realtime check status and scan interval, inside Chrome storage.
- cookies: Creates, reads, and removes the `uadrefresh_debug` cookie for the current site when requested by the user.
- activeTab and scripting: Injects the content script into the active tab so the extension can inspect supported ad units and banner wrappers.
- alarms: Schedules optional realtime banner checks at the interval configured by the user. This permission does not collect, transmit, or store personal data.
- host permissions for HTTPS pages: Allows the extension to operate on supported HTTPS pages where the user opens the popup.
Data Sharing
UAF Debugger Pro does not transmit ad unit data, banner data, cookie data, or browsing data to the developer's servers. No analytics, remote tracking scripts, or third-party data brokers are used by this extension. The public IP feature calls `https://api.ipify.org?format=json` only to display the current public IP address in the popup; ad data and cookie data are not sent with that request.
Storage and Security
Any small amount of state used by the extension, such as cookie expiration metadata, stays inside the browser through Chrome extension storage. Realtime scan settings and the latest banner scan result for a tab may also be stored locally in Chrome storage. The tool is intended to support internal debugging workflows and does not maintain a remote database of user activity.
Policy Updates
If the extension behavior changes in a way that affects privacy, this page should be updated to reflect the new functionality before release. Users should review this policy periodically for the latest version.