Overview
The passwd-sso browser extension ("the Extension") and the passwd-sso iOS app ("the App") are companions to the passwd-sso password manager. This policy explains what data they access, how it is used, and your rights. Unless a section is marked as Extension-specific or iOS-specific, it applies to both.
Data Collection
The Extension and the App do NOT collect, transmit, or sell any personal data to third parties. There is no analytics, advertising, or third-party SDK. All vault data is end-to-end encrypted and only decrypted locally on your device.
Data Accessed Locally (Extension)
The Extension accesses the following data solely on your device:
- storage — Extension settings and encrypted session state (via chrome.storage)
- activeTab — The URL of the current tab to match saved credentials for autofill
- clipboard — Temporarily writes passwords or usernames to the clipboard when you explicitly request it
- forms — Login form fields on web pages to provide autofill functionality
Server Communication
The Extension and the App communicate exclusively with the self-hosted passwd-sso server instance that you configure. No data is sent to any other server, and there is no passwd-sso-operated cloud backend. All communication uses HTTPS and encrypted payloads.
Browser Permissions (Extension)
The Extension requests the following permissions:
- storage — Save extension settings and encrypted session state
- alarms — Auto-lock the vault after a configurable timeout period
- activeTab — Detect the current page URL for credential matching and autofill
- scripting — Inject autofill scripts into web page forms
- contextMenus — Provide right-click menu options for quick copy and autofill
- clipboardWrite — Copy passwords and usernames to the clipboard on demand
- offscreen — Perform clipboard operations in the background
- hostPermissions — Access web pages for form detection and autofill (granted on demand)
passwd-sso for iOS (App)
The iOS app provides the same vault access natively on iPhone, using iOS system frameworks. It accesses the following solely on your device:
- Keychain & App Group — Stores encrypted session state and the vault bridge key, shared securely between the app and its AutoFill extension. Never transmitted.
- Face ID / Touch ID — Used only to confirm it's you before unlocking the vault or revealing a credential. Biometric data is processed by iOS and never seen by, or sent to, the app.
- AutoFill Credential Provider — When you enable passwd-sso under Settings → AutoFill & Passwords, iOS lets the app fill passwords, one-time codes (TOTP), and passkeys into apps and websites at your request.
- Passkeys (WebAuthn) — Passkey credentials are stored end-to-end encrypted in your vault and used to sign in; their private keys never leave your device unencrypted.
- Local cache — Encrypted vault entries are cached on device for AutoFill and offline list display, protected by the same end-to-end encryption.
The App contains no analytics or tracking SDKs and does not use the iOS advertising identifier.
Security
All password data is encrypted client-side using AES-256-GCM before transmission. The master passphrase never leaves your device. Key derivation uses PBKDF2 with 600,000 iterations.
Changes to This Policy
We may update this policy from time to time. Changes will be reflected on this page with an updated date.
Contact
If you have questions about this privacy policy, please open an issue on the project repository.