SaaS Ranking
Menu

Postman

postman.com · API management · checked 2026-09-04

57/100CBand C

Rank 2 of 27 in API management, where the median is 26.

We measured 12 of 12 criteria for Postman on 2026-09-04. We found 7 with a source and did not find 5 at the addresses we checked. That is a transparency score of 57 out of 100, band C.

Overview

Transparency labelsaas-ranking.com

Postman

postman.com · API management

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
C 57of 100 Rank 2 of 27

Published commitments5 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-04. 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.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

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 Postman 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-04.

Show the 8 addresses we checked
  1. https://postman.com/legal/dpa – reached, no match (HTTP 404)
  2. https://postman.com/dpa – reached, no match (HTTP 200)
  3. https://postman.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://postman.com/data-processing-agreement – reached, no match (HTTP 200)
  5. https://postman.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://postman.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://postman.com/trust/dpa – reached, no match (HTTP 404)
  8. https://postman.com/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-04.

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

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-04.

Show the 1 address we checked
  1. https://postman.com/ – third-party requests before any interaction: accounts.google.com, munchkin.marketo.net, o1224273.ingest.us.sentry.io, static.cloudflareinsights.com, transcend-cdn.com

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-04.

Show the 6 addresses we checked
  1. https://postman.com/legal/sla – reached, no match (HTTP 404)
  2. https://postman.com/sla – reached, no match (HTTP 200)
  3. https://postman.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://postman.com/trust/sla – reached, no match (HTTP 404)
  5. https://postman.com/uptime – reached, no match (HTTP 200)
  6. https://postman.com/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://www.postman.com/security/ · checked 2026-09-04

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

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 7
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording European Union.
    Show the exact wording

    Postman has no in-house data centers and uses AWS to manage its data centers' physical and environmental security. Our company's product data and backups are hosted on AWS servers in the EU and the U....

    Read at https://www.postman.com/security/

Source: https://www.postman.com/security/ · checked 2026-09-04

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.postman.com/ · checked 2026-09-04

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.postman.com/pricing/ · checked 2026-09-04

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://postman.com/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://postman.com/

    max-age=31536000; includeSubDomains; preload

    Read at https://postman.com/

Source: https://postman.com/ · checked 2026-09-04

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://www.postman.com/legal/sub-processors/ · checked 2026-09-04

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page CSA STAR, HIPAA, ISO/IEC 27001, PCI DSS, SOC 2, SOC 2 Type II.
    Show the 6 exact wordings

    SOC 2 Type II PCI DSS HIPAA GDPR CCPA / CPRA CSA STAR TX-RAMP ISO 27001 ISO 42001 SOC 2 Type II reports, penetration test summaries, security questionnai

    Read at https://www.postman.com/security/

    SOC 2 Type II PCI DSS HIPAA GDPR CCPA / CPRA CSA STAR TX-RAMP ISO 27001 ISO 42001 SOC 2 Type II reports, penetration test summa

    Read at https://www.postman.com/security/

    SOC 2 Type II PCI DSS HIPAA GDPR CCPA / CPRA CSA STAR TX-RAMP ISO 27001 ISO 42001 SOC 2 Type II reports, penetration test summaries, security questionnaire responses, arch

    Read at https://www.postman.com/security/

    SOC 2 Type II PCI DSS HIPAA GDPR CCPA / CPRA CSA STAR TX-RAMP ISO 27001 ISO 42001 SOC 2 Type II reports, penetration test

    Read at https://www.postman.com/security/

    cident response policies and processes are audited as part of our System and Organization Controls (SOC 2) and other security assessments.

    Read at https://www.postman.com/security/

    All compliance documents SOC 2 Type II reports, penetration test summaries, audit reports, and security questionnaire responses ar

    Read at https://www.postman.com/security/

Source: https://www.postman.com/security/ · checked 2026-09-04

✓

security.txt (RFC 9116)

weight 1 of 3

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

Source: https://www.postman.com/.well-known/security.txt · checked 2026-09-04

History

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

Compare