SaaS Ranking
Menu

Permit.io: what they publish

permit.io · Password and identity · checked 2026-10-28

35/100EBand E

Rank 18 of 35 in Password and identity, where the median is 35.

Public transparency score, not a product or security rating. Latest check: 2026-10-28. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

2 days since the newest dated result, 2 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Permit.io

permit.io · Password and identity

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

Published commitments3 of 9 found

Measured behaviour1 of 3 found

Checked 2026-10-28. 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.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

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 Permit.io has no such document.

Where Permit.io sits in Password and identity

  1. A1 3%
  2. B1 3%
  3. C3 9%
  4. D9 26%
  5. E7 20%
  6. F14 40%
35 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Permit.io is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Permit.io states

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

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-28.

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

Is this wrong? Send us the URL

Across the market: Subprocessor list in Password and identity: 4 of 36 companies

✗

Data location: where they say data is hosted

weight 3 of 3

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

Seen at https://www.permit.io/trust · checked 2026-10-28

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

Is this wrong? Send us the URL

Across the market: Data location stated in Password and identity: 13 of 37 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-28.

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

Is this wrong? Send us the URL

Across the market: Status page with history in Password and identity: 11 of 37 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-10-28.

Show the 1 address we checked
  1. https://permit.io/ – third-party requests before any interaction: analytics-ipv6.tiktokw.us, analytics.tiktok.com, api.claydar.com, api.github.com, cdn-cookieyes.com, cdn.claydar.com, connect.facebook.net, directory.cookieyes.com, log.cookieyes.com, px.ads.linkedin.com, region1.google-analytics.com, snap.licdn.com, static.claydar.com, www.googletagmanager.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Password and identity: 2 of 36 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-28.

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

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Password and identity: 6 of 35 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-28.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Password and identity: 3 of 35 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-28.

Show the 1 address we checked
  1. https://permit.io/.well-known/security.txt – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Password and identity: 17 of 36 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-10-28.

Show the 7 addresses we checked
  1. https://permit.io/legal/privacy – reached, no match (HTTP 200)
  2. https://permit.io/privacy – reached, no match (HTTP 200)
  3. https://permit.io/privacy-policy – reached, no match (HTTP 200)
  4. https://permit.io/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://permit.io/legal/privacy-notice – reached, no match (HTTP 200)
  6. https://permit.io/trust/privacy – reached, no match (HTTP 200)
  7. https://permit.io/datenschutz – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Across the market: Named privacy contact in Password and identity: 15 of 36 companies

Evidence

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

Published, with a source 4
✓

Data processing agreement (DPA)

weight 3 of 3

Published and readable without a login.

Source: https://www.permit.io/legal/data-processing-addendum · checked 2026-10-28

Across the market: Data processing agreement in Password and identity: 8 of 36 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://www.permit.io/pricing · checked 2026-10-28

Across the market: Public pricing in Password and identity: 26 of 37 companies

✓

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

    Read at https://permit.io/

Source: https://permit.io/ · checked 2026-10-28

Across the market: HTTPS enforced with HSTS in Password and identity: 30 of 37 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page HIPAA, SOC 2 Type II.
    Show the 2 exact wordings

    Center Contact sales Community Slack Email Privacy Policy Terms & Conditions SOC 2 Type II attested HIPAA BAA available GDPR CCPA CNCF Silver Member © 2026 Permit Inc.

    Read at https://www.permit.io/security

    ;s Company About Trust Center Contact sales Community Slack Email Privacy Policy Terms & Conditions SOC 2 Type II attested HIPAA BAA available GDPR CCPA CNCF Silver Member © 2026 Permit Inc.

    Read at https://www.permit.io/security

Source: https://www.permit.io/security · checked 2026-10-28

Across the market: Certifications named in Password and identity: 20 of 36 companies

History

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

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Permit.io

4 found · 8 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-28.

Investigate 8 open evidence questions
  1. Subprocessor list

    Which subprocessors apply to our product, what does each process, and in which countries? Please share the current list.

    Inspect this check
  2. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  3. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  4. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  5. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  6. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  7. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check
  8. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    Inspect this check

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.