KeyDock Privacy

Last updated: June 23, 2026

What KeyDock collects

The KeyDock Discovery Companion locally detects password login forms. When a login is submitted, it may collect site name, domain, launch URL, username or email when visible in a login form, page title, and detection time. KeyDock uses this information to show discoveries in the user's Discovery Inbox for review.

What KeyDock does not collect

KeyDock does not collect password values, passkeys, one-time codes, recovery codes, session cookies, payment data, health data, or browser password-manager vault contents.

How discoveries are handled

Captured discoveries stay in the browser extension's local storage until they are accepted by KeyDock, sent manually from the extension popup, or cleared by the user. If KeyDock is locked, captures remain queued instead of being discarded.

Chrome Web Store Limited Use

KeyDock's use of information received from Chrome extension APIs and browser pages complies with the Chrome Web Store User Data Policy, including Limited Use requirements. KeyDock uses collected metadata only to provide and improve account discovery and the Discovery Inbox workflow. KeyDock does not sell account metadata, does not use it for advertising, and does not transfer it except as necessary to provide KeyDock, comply with law, protect security, or with the user's consent.

Local vault

KeyDock stores non-secret account metadata in browser storage. When encrypted local-vault mode is enabled, account metadata is saved as Web Crypto ciphertext at rest in that browser.

Sharing

Solstera Labs does not sell KeyDock account metadata. During beta, KeyDock should be used with fake or low-risk accounts while the hosted sync and production security model continue to mature.

Contact

For KeyDock privacy questions, use the KeyDock support page.