Private Chrome history manager

BrowseTrail

Rebuild closed research sessions from Chrome history, search across visits, save important pages, add notes, and keep browsing metadata local to your own device.

extension Chrome Store Coming Soon shield_lock Privacy Policy support_agent Support

Local

IndexedDB

Sessions

rebuilt

No

analytics

BrowseTrail product card with private and searchable browsing history message
history

Rebuild closed sessions

BrowseTrail groups visits into sessions so users can find a piece of work later and reopen the useful pages together.

search

Search local history

Search by title, URL, domain, tag, note, collection, date, saved state, and archive state without sending queries anywhere.

inventory_2

Keep what matters

Pin pages, add notes, group visits into collections, export reports, and choose retention rules from the extension settings.

Why BrowseTrail exists

Chrome history is useful, but it is not built like a research notebook.

Browser history remembers individual visits. BrowseTrail turns those visits into a clearer trail: sessions, saved pages, notes, tags, collections, filters, and exports. It is designed for people who regularly research, compare, troubleshoot, learn, shop, write, or work across many tabs.

The goal is simple: help users answer "where was that page?" without sending their browsing life to another server.

Manage research sessions

Recover a previous work trail by seeing nearby visits grouped together, then reopen the pages that still matter.

Build a private reference layer

Save pages with notes, tags, and collections when a bookmark is too broad and a browser tab is too temporary.

Audit your own browsing patterns

Use activity maps, visit totals, domain breakdowns, and date filters to understand where time went.

Export when needed

Generate JSON, CSV, and HTML reports locally for backup, review, or documentation workflows.

How it works

Import, organize, search, save, export.

BrowseTrail keeps the workflow intentionally plain so users can use it every day without turning history management into another project.

1

Import

Bring Chrome history metadata into local IndexedDB.

2

Rebuild

Group nearby visits into useful session trails.

3

Search

Filter by text, domain, dates, saved state, tags, and notes.

4

Save

Keep important visits in collections with context.

5

Control

Export, archive, delete, or apply retention cleanup locally.

Store screenshots

Five screens for the Chrome Web Store listing.

These screenshots show the timeline, session reconstruction, search, insights, and privacy controls from the seeded store capture set.

BrowseTrail timeline screen with week activity map and browsing visits
Timeline and activity map
BrowseTrail sessions screen showing reconstructed browsing sessions
Session rebuild
BrowseTrail search screen with local history filter results
Search and filters
BrowseTrail insights screen with browsing totals and activity trends
Insights
BrowseTrail privacy settings screen with local-only controls
Privacy controls

Demo video

Watch BrowseTrail in motion.

The demo walks through local history import, timeline scanning, session rebuild, search, insights, saved pages, and privacy settings.

play_circle Open YouTube demo

Privacy by construction

No account, no server, no telemetry.

BrowseTrail stores Chrome history metadata in local IndexedDB only. It does not read page contents, inject content scripts, request host permissions, load remote code, or send history data to NHR Soft.

Local data only

Visits, sessions, tags, notes, collections, and settings stay on the user device.

Minimal permissions

The extension uses history, storage, and alarms for local history organization and retention cleanup.

User-controlled deletion

Users can delete visits, clear extension data, set retention periods, or uninstall the extension.

Local exports

JSON, CSV, and HTML exports are generated by the browser and saved wherever the user chooses.