EasyPass is designed to be offline-first.
Your password vault is stored encrypted on your device and is not uploaded to EasyPass servers by default.
This policy describes how EasyPass handles data for:
(1) the EasyPass desktop app, (2) the EasyPass browser extension (“EasyPass Connector”), and (3) the EasyPass website.
- We do not collect browsing history for analytics.
- We do not sell personal data.
- The browser connector communicates locally with the EasyPass desktop app (
127.0.0.1).
1) What we collect
A. EasyPass Desktop App (local)
- Encrypted vault data stored locally on your device (e.g.,
vault.enc).
- Site metadata you save (domain, display name, username), stored in the encrypted vault.
- Credentials (passwords) you save, stored encrypted in your vault.
The desktop app is built so that the vault key stays on your device, protected by Windows security features where available.
B. EasyPass Connector Extension (local)
- Authentication information (credentials) may be accessed temporarily to autofill/save logins when you use the feature.
- Local pairing/auth values stored by the extension to securely connect to the EasyPass desktop app on your computer.
- Active tab URL/domain used to ensure autofill occurs only on the correct site.
The extension communicates with the EasyPass desktop app over a local connection (e.g., 127.0.0.1).
It is not designed to send credentials to remote servers.
C. EasyPass Website & Licensing (online)
If you use the EasyPass website or licensing/activation services, we may collect:
- Contact email (e.g., for receipts, support, activation, or optional OTP emails).
- Device identifier used for licensing/activation (a device fingerprint provided by the app).
- License identifiers and subscription status (e.g., trial/paid/expiry) needed to operate licensing.
- Basic server logs (IP address, timestamps, request path) for security and troubleshooting.
Payment processing (if you purchase) is handled by third-party payment processors. We do not store full payment card numbers on our servers.
2) What we do NOT do
- We do not sell your personal data.
- We do not use your data for advertising profiles.
- We do not collect your browsing history for analytics.
- We do not upload your encrypted vault contents to our servers by default.
3) How we use data
- To provide core functionality: saving logins, one-click login/autofill, and vault management.
- To keep the product secure: detecting abuse, preventing unauthorized pairing, and debugging failures.
- To provide licensing and account services (trial/paid verification) when you choose to use those services.
- To provide support when you contact us.
4) Sharing & third parties
We may share limited information with service providers only as necessary:
- Email delivery providers (only if you request email-based codes/receipts/support emails).
- Payment processors for purchases/subscriptions.
- Infrastructure providers for hosting the website/licensing endpoints.
We do not share your vault contents or plaintext passwords with third parties.
5) Data retention
- Vault data: stored on your device until you delete it.
- Extension pairing values: stored locally in your browser until you remove the extension or clear extension storage.
- Licensing records: retained as needed to provide licensing and comply with legal/accounting requirements.
- Optional OTP codes: intended to be short-lived and single-use.
6) Security
- Encrypted vault on disk (offline-first design).
- Local-only connector communication for autofill/save features.
- Authentication/authorization between the extension and desktop app (pairing + token-based access).
No system is perfectly secure. You are responsible for securing your device account and keeping your OS up to date.
7) Your choices
- You can delete vault entries within the app.
- You can remove the extension at any time (which deletes its local stored values).
- You can request support regarding licensing/account issues via the contact email below.
8) Children’s privacy
EasyPass is not directed to children and is intended for general audiences.
9) Changes to this policy
We may update this policy from time to time. We will update the “Last updated” date above.
10) Contact
