SaaS Ranking
Menu

GitGuardian

gitguardian.com · Privileged access management · checked 2026-09-03

65/100CBand C

Rank 3 of 21 in Privileged access management, where the median is 22.

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

Overview

Transparency labelsaas-ranking.com

GitGuardian

gitguardian.com · Privileged access management

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

Published commitments5 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-03. 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 GitGuardian has no such document.

Gaps, heaviest first

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-03.

Show the 3 addresses we checked
  1. https://status.gitguardian.com/ – reached, no match (HTTP 200)
  2. https://gitguardian.com/status – reached, no match (HTTP 404)
  3. https://gitguardian.com.statuspage.io/ – Could not be fetched: fetch failed.

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

Show the 1 address we checked
  1. https://gitguardian.com/ – third-party requests before any interaction: ad.doubleclick.net, ajax.googleapis.com, api.hubapi.com, api.hubspot.com, assets.customer.io, bat.bing.com, bat.bing.net, bzr.openai.com, bzrcdn.openai.com, cdn.iubenda.com, cdn.prod.website-files.com, cs.iubenda.com, customerioforms.com, d3e54v103j8qbb.cloudfront.net, fonts.googleapis.com, fonts.gstatic.com, forms.hscollectedforms.net, forms.hsforms.com, gitguardian.containers.piwik.pro, gitguardian.piwik.pro, googleads.g.doubleclick.net, hubspotonwebflow.com, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, js.usemessages.com, px.ads.linkedin.com, region1.analytics.google.com, snap.licdn.com, stats.g.doubleclick.net, track.customer.io, track.hubspot.com, www.clickcease.com, www.google.com, www.google.de, www.googletagmanager.com

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

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

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

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://gitguardian.com/legal/privacy – reached, no match (HTTP 404)
  2. https://gitguardian.com/privacy – reached, no match (HTTP 404)
  3. https://gitguardian.com/privacy-policy – reached, no match (HTTP 404)
  4. https://gitguardian.com/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://gitguardian.com/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://gitguardian.com/trust/privacy – reached, no match (HTTP 404)
  7. https://gitguardian.com/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 7
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.gitguardian.com/legal/data-processing-addendum · checked 2026-09-03

✓

Subprocessor list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://www.gitguardian.com/legal/subprocessors · checked 2026-09-03

✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.gitguardian.com/legal/privacy-policy · checked 2026-09-03

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.gitguardian.com/pricing · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://gitguardian.com/ · checked 2026-09-03

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://www.gitguardian.com/ · checked 2026-09-03

✓

security.txt (RFC 9116)

weight 1 of 3

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

Source: https://gitguardian.com/.well-known/security.txt · checked 2026-09-03

History

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

Compare