TypeVault Privacy Policy

Effective date: July 17, 2026

The short version

TypeVault collects nothing. The drafts and versions it saves live on your device, in your browser's local storage, and are never uploaded, shared, or sent to any server. Password fields are never captured.

What TypeVault stores, and where

• As you type into normal text fields, textareas and rich (contenteditable) editors, TypeVault saves debounced, versioned snapshots of that text to chrome.storage.local — your browser's on-device extension storage.
• It also stores your settings (how many versions to keep, which sites are paused). That's everything.
• None of this ever leaves your machine. TypeVault operates no servers and includes no analytics, telemetry, or tracking of any kind.

What TypeVault never captures

• Passwords. Fields of type password are always ignored.
• Very short text (a handful of characters) is skipped, so incidental keystrokes aren't stored.
• TypeVault does not read your browsing history, does not track which pages you visit, and does not scrape page content — it only snapshots the specific fields you actively type into.

Your control over your data

You can pause capturing on any individual site or everywhere, choose how many versions are retained, export your entire vault as JSON, or clear everything at any time from the TypeVault manager. Uninstalling the extension removes all stored drafts.

Payments (Pro upgrade)

The optional one-time Pro upgrade is processed by ExtensionPay and Stripe. ExtensionPay handles your email address and payment status; card details are handled by Stripe. TypeVault never sees or stores your payment information. See the ExtensionPay privacy policy and the Stripe privacy policy.

Remote code

TypeVault contains no remote code. All logic ships inside the extension package and runs locally.

Changes

If this policy changes, the new version will be posted at this address with an updated effective date.

Contact

Questions or issues: open an issue on GitHub.