SaaS Ranking

Teampass

teampass.net · Password management · checked 2026-09-05

26/100EBand E

Rank 7 of 20 in Password management, where the median is 19.5.

We measured 12 of 12 criteria for Teampass on 2026-09-05. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 26 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Teampass

teampass.net · Password management

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 26of 100 Rank 7 of 20

Published commitments2 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-05. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Teampass has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-05.

Show the 8 addresses we checked
  1. https://teampass.net/legal/dpa – reached, no match (HTTP 404)
  2. https://teampass.net/dpa – reached, no match (HTTP 404)
  3. https://teampass.net/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://teampass.net/data-processing-agreement – reached, no match (HTTP 404)
  5. https://teampass.net/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://teampass.net/legal/gdpr – reached, no match (HTTP 404)
  7. https://teampass.net/trust/dpa – reached, no match (HTTP 404)
  8. https://teampass.net/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-05.

Show the 7 addresses we checked
  1. https://teampass.net/legal/subprocessors – reached, no match (HTTP 404)
  2. https://teampass.net/subprocessors – reached, no match (HTTP 404)
  3. https://teampass.net/sub-processors – reached, no match (HTTP 404)
  4. https://teampass.net/legal/sub-processors – reached, no match (HTTP 404)
  5. https://teampass.net/trust/subprocessors – reached, no match (HTTP 404)
  6. https://teampass.net/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://teampass.net/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Data location stated

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://teampass.net/privacy · checked 2026-09-05

Show the 7 addresses we checked
  1. https://teampass.net/security – reached, no match (HTTP 200)
  2. https://teampass.net/trust – reached, no match (HTTP 404)
  3. https://teampass.net/legal/privacy – reached, no match (HTTP 404)
  4. https://teampass.net/privacy – found, but behind a sign-in
  5. https://teampass.net/privacy-policy – reached, no match (HTTP 404)
  6. https://teampass.net/compliance – reached, no match (HTTP 200)
  7. https://teampass.net/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-05.

Show the 3 addresses we checked
  1. https://status.teampass.net/ – The name "status.teampass.net" could not be resolved.
  2. https://teampass.net/status – reached, no match (HTTP 404)
  3. https://teampass.net.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-05.

Show the 2 addresses we checked
  1. http://teampass.net/ – redirects to https://teampass.net/
  2. https://teampass.net/ – no HSTS header

Is this wrong? Send us the URL

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-05.

Show the 8 addresses we checked
  1. https://teampass.net/legal/subprocessors – reached, no match (HTTP 404)
  2. https://teampass.net/subprocessors – reached, no match (HTTP 404)
  3. https://teampass.net/sub-processors – reached, no match (HTTP 404)
  4. https://teampass.net/legal/dpa – reached, no match (HTTP 404)
  5. https://teampass.net/dpa – reached, no match (HTTP 404)
  6. https://teampass.net/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://teampass.net/trust/subprocessors – reached, no match (HTTP 404)
  8. https://teampass.net/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-05.

Show the 6 addresses we checked
  1. https://teampass.net/legal/sla – reached, no match (HTTP 404)
  2. https://teampass.net/sla – reached, no match (HTTP 404)
  3. https://teampass.net/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://teampass.net/trust/sla – reached, no match (HTTP 404)
  5. https://teampass.net/uptime – reached, no match (HTTP 404)
  6. https://teampass.net/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Named privacy contact

weight 1 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://teampass.net/privacy · checked 2026-09-05

Show the 7 addresses we checked
  1. https://teampass.net/legal/privacy – reached, no match (HTTP 404)
  2. https://teampass.net/privacy – found, but behind a sign-in
  3. https://teampass.net/privacy-policy – reached, no match (HTTP 404)
  4. https://teampass.net/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://teampass.net/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://teampass.net/trust/privacy – reached, no match (HTTP 404)
  7. https://teampass.net/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 4

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://teampass.net/pricing · checked 2026-09-05

No third-party tracking before consent

weight 2 of 3

No third-party requests before any interaction.

Source: https://teampass.net/ · checked 2026-09-05

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001 (unclear from the sentence), SOC 2 (unclear from the sentence).
    Show the 2 exact wordings

    No tool makes an organisation compliant with ISO 27001, NIS2, GDPR or SOC 2 — those apply to how you operate, and are assessed by an auditor, not by a ven

    Read at https://teampass.net/compliance

    No tool makes an organisation compliant with ISO 27001, NIS2, GDPR or SOC 2 — those apply to how you operate, and are assessed by an auditor, not by a vendor.

    Read at https://teampass.net/compliance

Source: https://teampass.net/compliance · checked 2026-09-05

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://teampass.net/.well-known/security.txt · checked 2026-09-05

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.