Deja Vu

Last updated: June 2026

Deja Vu collects nothing, sends nothing, and stores nothing outside your own browser. Full stop.

What data is accessed

Deja Vu reads your Chrome browsing history from the last 90 days using the browser's built-in chrome.history API. This includes page URLs, titles, visit counts, and visit timestamps. When you open the popup, it may also read the URL of your currently active tab to show how many times you've visited that page.

What happens to that data

All processing happens entirely on your device, inside the extension. The history data is:

Matched locally against static URL pattern tables (shopping sites, search engines, news sites, and so on)
Used to generate observations about your own browsing patterns
Stored temporarily in chrome.storage.local (your browser's local storage) as a cached result
Discarded and regenerated each time you click Refresh or after the cache expires

What data leaves your device

None. Deja Vu makes zero network requests. There is no backend, no server, no analytics, no telemetry, and no remote API of any kind. Your browsing history never leaves your browser.

Permissions used

history - to read your last 90 days of visited URLs and generate observations about your own patterns
storage - to cache the generated observations locally so the popup loads instantly on reopen
activeTab - to read the URL of the tab you're on when you open the popup, so it can tell you how many times you've been there

No host permissions (<all_urls>) are requested. The extension never injects scripts into web pages.

Data retention

The cached result stored in chrome.storage.local contains only the computed output (observation text and aggregate counts), not your raw history. It is overwritten on every refresh and can be cleared at any time by removing the extension.

Third parties

There are no third-party SDKs, trackers, or services included in this extension.

Contact

Questions or concerns? Reach out at george.tsertsvadze97@gmail.com