Your data never leaves your computer.

What we collect

Nothing. Digital Memory has no server, no account system, no analytics, no telemetry and no crash reporting. The developer receives no information about you, about your browsing, or about your use of the extension. There is no mechanism by which we could — not one that is switched off, but one that does not exist in the code.

What the extension stores

To let you search your own past browsing, the extension keeps a record of it on your device. Depending on which capture options you leave enabled, that record can include:

• the addresses, titles, descriptions and visible text of pages you visit, together with when you visited and roughly how long you stayed;
• your bookmarks, and the folders they sit in;
• your download history — filename, source address, file type, size and date;
• text you copy, along with the page you copied it from;
• notes you write, and the page each note is attached to;
• the text of PDFs you open, if you switch PDF indexing on — it is off by default;
• your own settings, and a search index built from all of the above so that searching is fast.

This is a record of things you have already seen in your own browser. The extension observes; it does not go looking for anything you did not open yourself.

Where your data lives

In IndexedDB, inside your own Chrome profile, on your own disk. It is never uploaded, synchronised, mirrored, backed up or transmitted. It is exactly as private as any other file on your computer, and it is subject to the same realities: anyone who can use your computer account, or read your disk, can read it.

The extension does not use Chrome's cloud-synced storage for your records, so your memory is not copied to other machines by your Google account.

Network activity

The extension makes no network requests. Its built-in Privacy panel shows the live count, and that claim is enforced rather than asserted: the build process scans the service worker and the page content script for network APIs — fetch, XMLHttpRequest, WebSocket, EventSource, sendBeacon — and the build fails if any of them appears where it should not.

No web fonts are loaded, no icons are fetched from a content-delivery network, and the PDF reader is bundled inside the extension rather than downloaded at run time. The content security policy permits scripts only from the extension's own package, so a remote script could not execute even if one were somehow injected.

The one exception, disclosed

One optional feature reads data, and it is off until you turn it on. Making a PDF searchable means reading the PDF. If you enable PDF indexing, the extension reads PDF files that you have already opened in a tab yourself, in order to extract their text locally.

Nothing is uploaded as part of this. The bytes go straight from the file into the local text extractor and the extracted text into your local database.

Why each permission is needed

Chrome shows a list of permissions when you install. Each one exists for a named feature, and the extension requests nothing it does not use:

• Bookmarks — read your bookmarks so they become searchable. They are never modified.
• Downloads — read download details so they become searchable, and save your export file when you ask for one.
• Tabs and web navigation — know which page you are actually looking at, and for how long, which is what the timeline is built from.
• Website content — read the text of pages you visit so you can search by what a page said, not only by its address. The reading happens inside the page and the result is stored locally.
• Storage — hold your settings and your records. Unlimited storage is requested because your searchable memory is the product, and Chrome's default quota would silently start discarding it.
• Side panel, context menus, alarms — the interface itself, right-click actions on your own selection, and periodic local housekeeping.
• Clipboard write — put a saved snippet back on your clipboard when you click it.
• Favicons — show each site's icon in lists, read from Chrome's local store rather than the network.

What is never recorded

• Passwords, one-time codes, and card details. Clipboard capture refuses password, OTP, CVV and card-number fields outright — text copied from them is never stored.
• Incognito windows, unless you explicitly allow the extension to run in them, which Chrome requires you to do yourself.
• Anything on pages Chrome protects, such as chrome:// pages and the Chrome Web Store, where extensions cannot read content at all.
• Whatever you switch off. Every category of capture can be disabled individually, or all at once.

Third parties

There are none. The extension contacts no third-party service, embeds no third-party script or tracking pixel, and uses no advertising, hosting, artificial-intelligence or analytics provider. Your data is not sold, transferred, shared or disclosed to anyone — not because we promise to refrain, but because it never leaves your machine in the first place.

This website holds itself to the same standard: it sets no cookies, loads no third-party scripts, embeds no fonts from a remote host and runs no analytics.

Your control over your data

• Export everything as JSON, CSV or Markdown, at any time, from Settings. There is no lock-in, because there is nowhere to be locked into.
• Import it back, on this machine or any other.
• Delete any single record, or reset the entire database, from Settings.
• Pause or disable capture entirely, or per category, whenever you like.
• Set a retention period and have older records removed automatically.

Retention and deletion

Records are kept until you delete them, or until the retention period you have set expires. Nothing is retained on your behalf anywhere else, so there is no copy for you to request and none for us to delete.

Uninstalling the extension removes its database with it. That deletion is permanent and cannot be undone — if you want to keep your memory, export it before you uninstall.

Children

The extension is not directed at children, and collects no data from anyone, of any age.

Changes to this policy

If this policy changes, the updated version will be published at this address with a new date at the top. Because the extension collects nothing, no future change can retroactively expose data that was never gathered in the first place.

Contact

There is no e-mail address on this page, and that is deliberate: an extension that publishes nothing about you should not require you to hand over an address of your own in order to ask a question about it.

Questions about this policy, or about how the extension handles your data, go through Digital Memory's listing on the Chrome Web Store — the same page you installed it from. Use the Support tab, which is the channel Google provides for contacting a developer directly. Bug reports and feature requests belong there too.

The listing is also reachable at any time from chrome://extensions — find Digital Memory, then follow the link to its Chrome Web Store page.