ConsentFox observes website activity inside the browser to explain requests, associated companies, cookies, browser storage, and consent choices. The extension processes this information locally on the user’s device.
Data processed
ConsentFox may process the current page URL and hostname; network-request destinations and metadata; cookie names, values, and attributes; consent-interface text used for local detection; readable IAB Transparency and Consent Framework declarations; local and session storage key names and size indicators; IndexedDB, Cache Storage, and Storage Bucket names; service-worker registration URLs; top-level origin-private file names and kinds; and browser-provided persistence, usage, and quota estimates.
Cookie values are fetched for the cookie manager and can include session or authentication information. Values remain in memory while the popup is open, are hidden until the user explicitly reveals them, and are excluded from observation history and standard exports.
ConsentFox does not collect typed form content. It does not read localStorage or sessionStorage values, IndexedDB records, cached response bodies, or origin-private file contents. Browser security boundaries may prevent inspection of embedded or cross-origin storage; the interface reports unavailable coverage rather than presenting missing evidence as zero.
How data is used
The data is used only to provide before-and-after consent comparisons, request and company summaries, cookie and storage inventories, user-requested deletion, local history, watch preferences, and user-requested reports.
Local storage and retention
Short-lived tab observations are stored in Chrome session storage. Settings, watched-site preferences, user corrections, and bounded previous-visit summaries are stored in Chrome local extension storage. Users can select a retention period, reset a current comparison, and delete ConsentFox data from Settings.
Network transmission and sharing
ConsentFox 0.1.1 does not transmit browsing activity, cookies, storage inventories, reports, or usage analytics to the developer or another service. It has no user account, advertising integration, cloud synchronization, or remote analytics service. Data is not sold or shared with third parties by the extension.
User actions
ConsentFox can delete cookies selected by the user and clear selected browser-storage types for the current origin. These actions affect data stored in the browser. They do not delete information already received or retained by a website or third party.
JSON and readable exports are created only when the user requests them. Standard exports exclude cookie values.
Permissions
- Site access: detects consent interfaces and associates locally observed requests, cookies, declarations, and browser storage with websites the user visits.
- Cookies: displays cookie fields and values, observes cookie changes, and deletes cookies chosen by the user.
- Web request: observes request metadata without blocking or changing traffic.
- Browsing data: clears selected non-cookie site data only after an explicit user action.
- Tabs: identifies the active site, scopes observations to a tab, and preserves comparisons across same-site refreshes.
- Storage: keeps local settings, short-lived observations, corrections, watch preferences, and bounded history.
Security, remote code, and Limited Use
All executable code and classification data are packaged with the extension. ConsentFox does not download or execute remote code.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Changes
Material changes to data handling require an updated privacy policy and updated user disclosures before release.
Contact
ConsentFox is developed by Irfan Azam at ApusTek, LLC. For privacy questions, email mazam76@gmail.com.