History Signals

Privacy Policy

Last updated: August 2, 2026

History Signals stores and analyzes a private browsing archive on the user's device. It has no developer-operated server, analytics, advertising, or tracking.

Data used

History Signals may process page URLs, titles, visit times, transitions, referring visit IDs, derived domains, local browsing paths, settings, and optional WebDAV credentials.

This information is used only to provide the extension's user-facing archive, search, Recall, trend, export, retention, and insight features.

Local archive and trends

Visit records are stored in IndexedDB on the user's device. They are kept forever by default unless the user chooses a retention limit or clears the archive.

Search, visits-over-time charts, frequently revisited sites, active hours, period comparisons, and other trend statistics are calculated locally from those records. Clearing History Signals does not change Chrome's native history.

Local insights

Every device can create a limited deterministic local interpretation. On compatible Chrome devices, the user may explicitly enable analysis through Chrome's built-in Prompt API and browser-managed Gemini Nano model.

Only bounded aggregate statistics, representative page titles, domains, timestamps, and local source IDs are supplied to the browser-provided model. Page content is not supplied.

Some languages may be translated locally before and after model analysis. Model prompts, translations, and results remain on the device.

History Signals does not use browsing records to infer emotions, identity, politics, personality, health, intent, productivity, or reliable time spent.

Export

Users may export their archive as JSON or CSV. Export is initiated by the user and creates a downloaded file on the device. The developer does not receive exported data.

Optional WebDAV copy

WebDAV is disabled until configured by the user. Records are encrypted locally with AES-GCM and a PBKDF2-SHA256-derived key before upload. The extension developer does not receive the encrypted copy or control its destination.

Current limitation: History Signals does not yet provide in-app restore or restore-integrity verification. The feature is an experimental encrypted copy rather than complete disaster recovery.

Sensitive WebDAV credentials and the encryption key are stored in chrome.storage.local. Browsing records are not stored in chrome.storage.sync.

Data sharing and sale

History Signals does not sell browsing history, use it for advertising, transfer it for unrelated purposes, or allow the developer or other humans to read it.

The only optional transfer is an encrypted copy to a WebDAV destination selected and configured by the user.

User controls

Users can search and inspect the archive, view local trends, generate or disable local insights, export data, choose retention, clear local data, configure or remove WebDAV, cancel an active copy, and remove the extension.

Chrome Web Store Limited Use

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.