# Browserpass vs Pass: privacy compared

| Criterion | Browserpass | Pass |
| --- | --- | --- |
| Grade | B (88/100) | C (69/100) |
| Jurisdiction | Unknown | Unknown |
| Open source | Yes | Yes |
| No trackers or telemetry | Yes | No |
| No ads or data sales | Yes | Yes |
| Independent audit | No | No |
| Transparency report | Not applicable | Not applicable |
| Tells users about requests | Not applicable | Not applicable |
| TLS configuration | Not applicable | Not applicable |
| Security headers | Not applicable | Not applicable |
| Modern web standards | Not applicable | Not applicable |
| End-to-end encrypted vault | Yes | Yes |
| Local or self-hosted option | Yes | Yes |
| Full export | Yes | Yes |

**Browserpass.** Browserpass scores 88 out of 100 (grade B) on the password managers criteria. It meets 6 of 7 criteria: open source, no trackers or telemetry, no ads or data sales, end-to-end encrypted vault, local or self-hosted option and full export. It does not meet independent audit.

**Pass.** Pass scores 69 out of 100 (grade C) on the password managers criteria. It meets 5 of 7 criteria: open source, no ads or data sales, end-to-end encrypted vault, local or self-hosted option and full export. It does not meet no trackers or telemetry and independent audit. Automated tests: Mozilla HTTP Observatory grade B.

Source: https://privacyratings.com/compare/password-managers/browserpass-vs-pass/