Is History & Cache Cleaner for Google Chrome™ safe?
We analyzed History & Cache Cleaner for Google Chrome™ version 3.0.0's actual code and gave it a 82/100 trust score. This appears to be a purpose-aligned…
Bottom line
This appears to be a purpose-aligned cleaner with meaningful deletion access but no established misuse.
What it can access
It requests browser-data, cookie, storage, and active-page access for a cleaning tool, which fits its purpose but can affect sensitive data.[Q1][Q4][Q2]
Security weaknesses
No meaningful security weakness was established; clearing occurs through visible user actions and ordinary websites lack a privileged command channel.[Q8][Q16][Q21]
Signs of misuse
No evidence shows tracking, outside data sharing, remote code, or hidden actions beyond user-requested cleaning.[Q6][Q7][Q8][Q12]
Code findings
What access does this extension ask for, and does that access make sense for what it claims to do?
It has browsing-data and cookie deletion access plus storage, active-tab, and scripting permissions.
Declares storage, browsingData, cookies, activeTab, and scripting permissions. — manifest.json:29-35
Which websites can it run on, and can it read or change what appears on those pages?
It can inject a packaged floating cleaner button into the active page, but does not read page content.
Injects packaged content CSS and JavaScript into the active tab when the popup opens. — js/popup.js:25-71
Creates only a fixed image button and appends it to the page when enabled. — js/content.js:14-25
Can it see sensitive information you type, such as passwords, payment details, messages, or form entries?
No evidence of this behavior was found in the reviewed package.
Only manages the optional floating clear button and sends a fixed clear action. — js/content.js:1-65
Can it access private browser data such as cookies, signed-in sessions, browsing history, bookmarks, or downloads?
It can delete broad browser-stored data, including history, cache, cookies, form data, saved passwords, databases, and local storage.
Lists every selectable browser-data category. — options.html:31-143
Passes the saved selections and time range to chrome.browsingData.remove. — js/background.js:104-120
Can it access anything else on your device, such as files, location, camera, microphone, clipboard, or installed applications?
No evidence of this behavior was found in the reviewed package.
Requests no clipboard, downloads, capture, camera, microphone, or device permissions. — manifest.json:29-35
Does it send information outside your browser? If so, what information is sent, where does it go, and why?
No evidence of this behavior was found in the reviewed package.
Contains no fetch, XMLHttpRequest, beacon, or remote endpoint. — js/background.js:1-133
Only opens fixed vendor welcome and uninstall pages without attaching user data. — js/welcome.js:10-20
Does it download or run code, settings, or instructions supplied by a remote server?
No evidence of this behavior was found in the reviewed package.
All clearing rules come from packaged defaults and local user settings. — js/background.js:1-133
Can it take actions without a clear user request, such as opening pages, redirecting searches, downloading files, or sending requests?
No evidence of this behavior was found in the reviewed package.
Sends the clear action from the popup Clear button. — js/popup.js:1-20
The optional floating button sends clearBtn only when clicked. — js/content.js:14-34
Invokes clearing only for the two fixed runtime actions. — js/background.js:20-31
Can it change important browser settings, including your proxy, search engine, homepage, privacy settings, or other extensions?
No evidence of this behavior was found in the reviewed package.
Exposes selectable destructive browser-data operations. — options.html:31-143
Executes the selected browsingData removal. — js/background.js:104-120
Is any important behavior difficult to inspect because the code is hidden, heavily obfuscated, dynamically generated, or supplied by third parties?
No evidence of this behavior was found in the reviewed package.
Uses clear function names, fixed settings keys, and direct Chrome API calls. — js/background.js:1-133
Clearly implements the visible options page. — js/options.js:1-196
Does it use eval(), new Function(), or string-based timers to turn text into executable code?
No evidence of this behavior was found in the reviewed package.
Uses direct functions and Chrome APIs. — js/background.js:1-133
Injects only as a packaged file through chrome.scripting. — js/content.js:1-65
Does it track the websites, pages, searches, or links you visit?
No evidence of this behavior was found in the reviewed package.
Offers download-history, browsing-history, and time-range selections. — options.html:72-103,147-170
Converts the time range and data types into a browsingData removal request. — js/background.js:46-65,104-120
Does it create a persistent ID or browser fingerprint to recognize you?
No evidence of this behavior was found in the reviewed package.
Contains no tracking or telemetry request. — js/background.js:1-133
Uses only fixed welcome and uninstall URLs with no appended identifier. — js/welcome.js:1-21
Does it send cookies, session details, authentication data, or page contents elsewhere?
It can enumerate and delete cookies across the browser, but uses only cookie metadata for deletion and does not transmit cookie values.
Calls chrome.cookies.getAll and removes selected cookies using secure, domain, and name fields. — js/background.js:67-101
Provides explicit cookie deletion and include-or-preserve domain filters. — options.html:50-70
Does it record typing, form entries, clipboard contents, or screenshots?
It can delete saved form data and passwords when the user selects those categories, but does not read their contents.
Offers Form Data and Passwords as explicit deletion choices. — options.html:88-95,128-134
Deletes selected categories through browsingData.remove without reading entries. — js/background.js:104-120
Can a website or remote server send commands that make the extension take actions?
No evidence of this behavior was found in the reviewed package.
Declares no externally_connectable interface. — manifest.json:1-47
Handles only fixed internal clear and clearBtn messages. — js/background.js:20-31
Does it alter links, referral codes, advertisements, shopping carts, or search results?
No evidence of this behavior was found in the reviewed package.
Reads the floatbtn setting and creates or removes the packaged image button. — js/content.js:4-25,46-65
Labels the floating-button option. — options.html:20-27
Does it redirect or modify web traffic, request headers, downloads, or proxy settings?
No evidence of this behavior was found in the reviewed package.
Uses only local Chrome storage, cookie, browsing-data, tab, and messaging APIs. — js/background.js:1-133
Can it communicate with software on the computer or services running on localhost?
No evidence of this behavior was found in the reviewed package.
Requests no nativeMessaging permission. — manifest.json:29-35
Does it decode, decrypt, or unpack hidden data and then execute or inject it?
No evidence of this behavior was found in the reviewed package.
All clearing behavior and defaults are packaged locally. — js/background.js:1-133
Can ordinary websites access privileged extension features through messaging or exposed files?
No evidence of this behavior was found in the reviewed package.
Only the packaged button's own click listener sends the fixed clearBtn runtime message. — js/content.js:14-34
Declares no externally connectable messaging interface. — manifest.json:1-47
Does suspicious behavior activate only for certain users, websites, dates, or remote settings?
No evidence of this behavior was found in the reviewed package.
Presents the deletion scope, time range, cookie filters, and optional behaviors. — options.html:20-170
Provides the visible Clear button. — popup.html:34-37
Immediately executes the saved deletion choices after the clear message. — js/background.js:104-120
Does it perform hidden resource-intensive work, such as cryptocurrency mining?
No evidence of this behavior was found in the reviewed package.
Work is limited to user-requested browser-data deletion and optional tab reload. — js/background.js:1-133
Does it change form fields or where a form sends its information?
No evidence of this behavior was found in the reviewed package.
Form Data is a labeled browser-data deletion choice. — options.html:88-95
The page helper only adds a floating clear button. — js/content.js:1-65