Privacy Policy — Never Lose Text

Last updated: 2026-10-08 (applies to version 3.0.0)

Never Lose Text is a Chrome extension that saves text you type into web pages so you can restore it if it is lost. This policy explains exactly what the extension does with that text.

Summary

Never Lose Text stores the text you type only on your own device. It sends nothing anywhere. There are no servers, no accounts, no analytics, and no third parties.

What the extension stores

To do its job, the extension saves the following locally, using Chrome's chrome.storage.local API on your computer:

• Text you type into text boxes on web pages (the drafts it can restore for you).
• Where that text came from: the page URL, page title, and site hostname, so history can be grouped by site and you can jump back to the page.
• A technical identifier for the text box the text came from, so the right draft is offered in the right place.
• Your settings: theme, how long to keep text, how many versions to keep per text box, which sites are blocked, and which sites have restore hints disabled.
• Local diagnostic counters: counts of successful and failed saves, plus a short list of recent error codes and the hostname they occurred on. These never contain your typed text or full URLs, and are only shown to you inside the extension.

What the extension never does

• It never transmits your text, browsing data, or any other information off your device. The extension makes no network requests of any kind.
• It has no analytics, telemetry, tracking, or advertising.
• It does not sell or share data with anyone, because it never receives any.
• It does not use your data for any purpose other than restoring your own text to you.

The popup contains a link to a donation page. It opens in a new browser tab only when you click it, and the extension sends no data to that site.

Text the extension deliberately ignores

The extension excludes text boxes that appear to hold sensitive information, including:

• Password fields, one-time codes, and two-factor codes.
• Credit card numbers, security codes (CVC/CVV), and payment inputs.
• Fields labelled with things like PIN, token, secret, IBAN, or social security number.

Sites can also be blocked entirely in the extension's settings, and the extension can be told to ignore any individual site.

Where your data lives and how to delete it

All data stays in your browser profile on your device. You are in full control:

• Delete individual drafts, a site's history, or everything from the extension's popup.
• Auto-delete older versions after 7, 30, or 90 days in Settings. The latest version per text box and favorites are kept regardless of age. The default is no age-based deletion.
• Delete all history also removes the legacy backup retained when upgrading from 2.x.
• Export and import a backup in Settings. An export is a JSON file containing your saved text, favorites, and settings. It is created only when you click Export and is saved where you choose; the extension never uploads it. Keep backup files as carefully as the text they contain.
• Uninstalling the extension removes all of its stored data from your browser.

If you use Chrome with sync enabled, note that the extension stores data with chrome.storage.local, which is not synced between devices.

Permissions and why they are needed

• storage / unlimitedStorage — to save your drafts and settings on your device.
• tabs — to know which site the current tab is on, so the popup and badge can show that site's history and respect your blocked-site list.
• contextMenus — to offer your saved versions in the right-click menu.
• scripting — to load the capture script into a page when it is not already running, for example on a page that was open before the extension was installed.
• alarms — to schedule periodic local cleanup of expired text according to your retention settings.
• Host access (<all_urls>) — text boxes exist on any website, so the extension must be able to run on the sites where you type. It only ever reads text from editable fields and only stores that text locally.

Children's privacy

The extension is not directed at children and collects no information about anyone.

Changes to this policy

If the way the extension handles data ever changes, this policy will be updated and the change will be described in the extension's changelog, which is visible in the popup.

Contact

Questions about this policy: d.artoumian@gmail.com