Nice History Plugin
🔍 Security Report Available View on Chrome Web StoreChrome will indicate if you already have this installed.
Overview
Keep your history. Lose the noise.
Sometimes Chrome’s address bar starts remembering the wrong things — awkward suggestions, unwanted reminders, or a few sites you never meant to revisit. The usual “fix” is brutal: wipe your entire browsing history.
Nice History is the quieter solution.
It automatically removes history entries for a curated list of domains, so your history stays useful — without the few items that make you want to delete everything.
What it does:
- Automatically removes visits to selected domains from your browsing history
- Keeps your history intact, while quietly handling the sensitive (NSFW) bits
Shows simple, lightweight stats:
- Shh Moments (how many entries were removed)
- Database size (how many domains are covered)
- Last updated (when the list was refreshed)
Why install it
- You rely on your history — you just don’t want everything in it
- You want to stop embarrassing or unwanted autocomplete suggestions
- You want a solution that runs quietly in the background, without maintenance
Privacy-first by design
- No accounts. No tracking. No analytics.
- Runs locally on your device
- Stores only local settings and a simple counter
Install it — and forget it.
If something deserves silence, it doesn’t need a permanent place in your history.
Tags
Privacy Practices
Security Analysis — Nice History Plugin
Permissions
Code Patterns Detected
Package Contents 11 files · 3.8MB
What This Extension Does
Nice History Plugin is a privacy-focused browser extension designed to automatically filter out specific domains from your Chrome browsing history. It solves the problem of unwanted autocomplete suggestions or sensitive entries cluttering your history without requiring you to manually delete them. Ideal for users who want to maintain a useful history while keeping it clean of noise, this lightweight tool runs locally with minimal network activity.
Permissions Explained
- historyexpected: This permission allows the extension to read your browsing history so it can identify and delete entries for specific websites you select. It is essential for the core function of cleaning up your history automatically.
Technical: Accesses the chrome.history API to retrieve visit records (URL, timestamp, title) and execute deletion commands. If compromised, an attacker could theoretically read a user's full browsing trail or manipulate history entries to hide malicious activity. - storageexpected: This permission lets the extension save your settings (like which domains to filter) and statistics locally on your computer. It ensures your preferences persist between browser sessions.
Technical: Uses chrome.storage.local API to store JSON objects containing user-defined domain lists and counters. Data is encrypted at rest within Chrome's profile storage, isolated from other extensions and websites. - contextMenusexpected: This permission enables the extension to add custom options to your right-click menu, likely allowing you to quickly add domains to the filter list or manage settings directly from a page.
Technical: Registers event listeners on chrome.contextMenus API. While it can be used to inject code into pages if misconfigured, standard usage only modifies the UI layer. It does not inherently grant access to page content unless combined with other permissions like 'activeTab'.
Your Data
The extension does not send any data to external servers. All processing happens locally on your device, and no personal information is transmitted over the internet.
Technical Details
Code Findings
The extension uses a method to insert text into the browser interface that could theoretically be exploited if untrusted data were injected, though this is unlikely given its local-only nature.
Technical: Code analysis detected an 'innerHTML' assignment pattern. In a broader context, this can lead to Cross-Site Scripting (XSS) if user-controlled input is not sanitized before insertion. However, in this specific extension, the input source is strictly limited to user-defined domain names stored locally.
💡 Using innerHTML is common for rendering dynamic UI elements like lists or counters in content scripts or popup windows.
The extension has broad access to your entire browsing history to perform its filtering function. This is necessary but means it can see every site you visit.
Technical: Utilizes chrome.history.getAllVisits() and chrome.history.deleteURLs(). The API returns full URL strings and timestamps. No page content or form data is accessed, only the metadata of visited pages.
💡 History management extensions require this permission to function. Without it, they could not delete entries or provide statistics.
The extension operates entirely on your computer and does not connect to the developer's servers or any third-party analytics.
Technical: Network monitoring confirms no DNS lookups or HTTP requests. The 'Fetch API' usage is likely for internal logic (e.g., fetching a local JSON file if bundled) rather than external endpoints. No telemetry is sent.
💡 Privacy-focused extensions often omit network activity to prove their trustworthiness and reduce attack surface.
Nice History Plugin presents a low-risk profile suitable for privacy-conscious users. While it holds the 'history' permission which is sensitive, its usage is strictly aligned with its stated purpose of local data filtering, and it demonstrates excellent hygiene by avoiding external network calls. The only technical finding regarding 'innerHTML' is theoretical and practically neutralized because the extension does not process untrusted external inputs. Users can confidently install this tool to clean their history without fear of data leakage.
