Aunt Cass Checks Your Browser History Full

What Aunt Cass Actually Does

Aunt Cass Checks Your Browser History Full is a browser extension that monitors every tab, page load, and URL you visit across your browsing sessions. The name comes from the Disney character, but the tool itself isn't particularly warm and fuzzy when it flags problematic history. It runs quietly in the background, logs data, and alerts you when something crosses your configured thresholds. That's basically it. The most common use case is parental monitoring. Parents install it on their kids' devices to track what sites are being visited. But I've also seen it used by therapists doing exposure tracking, by people managing their own ADHD with accountability tools, and even by businesses for compliance logging on shared workstations. The extension handles all of those scenarios with the same feature set, which is both a strength and a weakness. Download it from the Chrome Web Store or Firefox Add-ons page depending on your browser. Install the extension, open the options panel, and set your monitoring scope. By default it tracks all tabs across all windows. You can narrow that down to specific domains, time windows, or keyword triggers. The settings menu is straightforward but not intuitive — I had to dig around for about ten minutes before I found the custom exclusion rules.

Here's the part most guides skip: you need to grant the extension full browsing data permissions. It won't work otherwise. The permission request will look aggressive because it is — full access to every URL and page title you visit. If you're uncomfortable with that level of access, no amount of feature explanation will fix it.

How the Logging Actually Works

The extension captures a timestamp, URL, page title, and referrer for each page load. It stores everything locally on your machine by default. The data persists even if you clear your regular browser cookies and history, which is why it exists in the first place. Some versions support cloud sync for remote viewing, but I wouldn't recommend enabling that unless you trust the vendor's infrastructure. Local storage means less surface area for leaks. The logging frequency is roughly one entry per navigation event. If someone clicks a link that opens in the same tab, that's one entry. If they open a new tab and navigate away, that's two. Session boundaries are tracked separately. You can export the logs as CSV or JSON for analysis elsewhere. I've used the export to feed data into a simple Python script that generates weekly summary reports — takes about five minutes to set up once and then runs on autopilot.

A Real Problem I Hit

I ran into a specific issue where the extension would miss page loads that happened via JavaScript navigation — things like single-page applications where the URL changes without a full reload. Gmail, for example, would show up as a single long session instead of individual mailbox views. The workaround is to enable the SPA tracking mode in the extension settings, which hooks into the history API instead of relying on page load events. Once that's on, you'll see proper granular entries for route changes. It does add a small amount of overhead, so if you're tracking a site with extremely heavy JavaScript activity, expect slightly higher memory usage. Most people assume that installing the extension and leaving it at default settings gives them complete visibility. It doesn't. Here's what actually breaks tracking: incognito mode, extensions that override the navigation stack (some ad blockers do this), and apps that open links in custom protocol handlers instead of the browser. I spent an afternoon troubleshooting why my logs showed gaps, only to realize that a site-specific extension was intercepting link clicks and routing them through a wrapper that bypassed the browser's history entirely. No amount of Aunt Cass configuration would fix that. Another thing: the extension doesn't capture form submissions, search queries typed into address bars, or content within pages. It only sees what the URL bar shows. If someone searches "cheap flights to Lisbon" on Google, you'll see them visit google.com and then a results URL — but the actual query string is often stripped or truncated depending on how the site encodes it. For sensitive use cases, this creates blind spots that matter.

Limitations and When to Look Elsewhere

The biggest limitation is that it's entirely user-mode. It can't see anything outside the browser. App activity, mobile usage, encrypted messaging — none of that is captured. If you need cross-device or cross-application monitoring, this tool won't help you. There are dedicated parental control suites that cover those areas, though they tend to be more expensive and require more invasive system-level permissions. The extension also struggles with multiple user profiles in the same browser. If two people share a Chrome profile and both log into their own accounts, Aunt Cass sees one continuous stream of history without separation. You need separate browser profiles for each person, or you're just tracking overlapping noise. For most households and individuals, the free tier covers the basics adequately. The paid upgrade adds features like remote dashboard access and longer retention windows, but those features introduce their own complications around data security. Decide whether you actually need those before paying.

Getting the Extension

You can find the full version through the Chrome Web Store or Firefox Add-ons marketplace. Search for "Aunt Cass Checks Your Browser History Full" directly. Make sure you're downloading from the official listing — there are knockoffs that mimic the name but don't function the same way. The real extension has been around since 2019 and has consistent update cadence. Check the last update date on the listing before installing.