The Zero-Telemetry Privacy Policy

Stashfill does not maintain a backend, database, authentication server, or remote sync service. When you save a profile, snippet, or encrypted vault entry, it is stored strictly inside your browser's local sandbox via chrome.storage.local.

An automated CI check (scripts/check-code-safety.mjs) verifies that no outbound networking primitives exist in the production bundle:

Sensitive payment card credentials and private custom fields are encrypted using standard W3C Web Cryptography (crypto.subtle):

• Key Derivation: PBKDF2-SHA256 with 600,000 iterations and a 16-byte cryptographically secure random salt.
• Authenticated Encryption: AES-GCM 256-bit with unique 12-byte initialization vectors (IV) for every write.
• Auto-Locking Memory: Vault keys are wiped from in-memory runtime whenever the extension popup closes or after a period of idle inactivity.
• Clipboard Scrubbing: Whenever card details are copied to the clipboard, a 15-second timer automatically scrubs the system clipboard.

Stashfill requests only the minimal permissions required by Manifest V3 to fulfill its user-commanded autofill duty:

• storage: Persists your saved profiles locally on your computer.
• activeTab: Grants temporary access to the active webpage strictly when you click the popup or hit Alt+Shift+F.
• scripting: Executes the autofill script on demand.
• contextMenus: Offers right-click shortcuts in input context menus.

★ Note: Broad host permissions (<all_urls>) are NEVER requested at installation time.

Stashfill is distributed under the open-source MIT license. You can clone the repository, inspect every line of code, run the automated test suite with over 80% coverage, and compile the extension locally without relying on prebuilt binary assets.