SaaS Ranking

Taiga

taiga.io · Project management · checked 2026-09-05

26/100EBand E

Rank 22 of 26 in Project management, where the median is 41.5.

We measured 12 of 12 criteria for Taiga 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

Taiga

taiga.io · Project management

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

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 Taiga 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://taiga.io/legal/dpa – reached, no match (HTTP 404)
  2. https://taiga.io/dpa – reached, no match (HTTP 404)
  3. https://taiga.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://taiga.io/data-processing-agreement – reached, no match (HTTP 404)
  5. https://taiga.io/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://taiga.io/legal/gdpr – reached, no match (HTTP 404)
  7. https://taiga.io/trust/dpa – reached, no match (HTTP 404)
  8. https://taiga.io/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://taiga.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://taiga.io/subprocessors – reached, no match (HTTP 404)
  3. https://taiga.io/sub-processors – reached, no match (HTTP 404)
  4. https://taiga.io/legal/sub-processors – reached, no match (HTTP 404)
  5. https://taiga.io/trust/subprocessors – reached, no match (HTTP 404)
  6. https://taiga.io/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://taiga.io/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-05.

Show the 7 addresses we checked
  1. https://taiga.io/security – reached, no match (HTTP 200)
  2. https://taiga.io/trust – reached, no match (HTTP 404)
  3. https://taiga.io/legal/privacy – reached, no match (HTTP 404)
  4. https://taiga.io/privacy – reached, no match (HTTP 404)
  5. https://taiga.io/privacy-policy – reached, no match (HTTP 200)
  6. https://taiga.io/compliance – reached, no match (HTTP 404)
  7. https://taiga.io/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.taiga.io/ – The name "status.taiga.io" could not be resolved.
  2. https://taiga.io/status – reached, no match (HTTP 404)
  3. https://taiga.io.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-05.

Show the 5 addresses we checked
  1. https://taiga.io/pricing – reached, no match (HTTP 404)
  2. https://taiga.io/pricing/ – reached, no match (HTTP 404)
  3. https://taiga.io/plans – reached, no match (HTTP 404)
  4. https://taiga.io/en/pricing – reached, no match (HTTP 404)
  5. https://taiga.io/pricing-plans – reached, no match (HTTP 404)

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://taiga.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://taiga.io/subprocessors – reached, no match (HTTP 404)
  3. https://taiga.io/sub-processors – reached, no match (HTTP 404)
  4. https://taiga.io/legal/dpa – reached, no match (HTTP 404)
  5. https://taiga.io/dpa – reached, no match (HTTP 404)
  6. https://taiga.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://taiga.io/trust/subprocessors – reached, no match (HTTP 404)
  8. https://taiga.io/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://taiga.io/legal/sla – reached, no match (HTTP 404)
  2. https://taiga.io/sla – reached, no match (HTTP 404)
  3. https://taiga.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://taiga.io/trust/sla – reached, no match (HTTP 404)
  5. https://taiga.io/uptime – reached, no match (HTTP 404)
  6. https://taiga.io/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-05.

Show the 1 address we checked
  1. https://taiga.io/.well-known/security.txt – 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

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 63072000 seconds (730 days).
    Show the exact wording

    max-age=63072000

    Read at https://taiga.io/

Source: https://taiga.io/ · checked 2026-09-05

No third-party tracking before consent

weight 2 of 3

No third-party requests before any interaction.

Source: https://taiga.io/ · 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 9001 (their data centres or infrastructure), ISO 22301 (their data centres or infrastructure), ISO/IEC 27001 (their data centres or infrastructure), PCI DSS (their data centres or infrastructure), SOC 2 (named without a certification claim).
    Show the 5 exact wordings

    INTERXION MAD3 datacenter has certification for compliance with: PCI-DSS ISO 9001 ISO 14001 ISO 20001 ISO 22301 ISO 27001 ISO 50001 ENS SOC1 SOC2 INTERXION MAD3 also counts with sec

    Read at https://taiga.io/security/

    TERXION MAD3 datacenter has certification for compliance with: PCI-DSS ISO 9001 ISO 14001 ISO 20001 ISO 22301 ISO 27001 ISO 50001 ENS SOC1 SOC2 INTERXION MAD3 also counts with security measures such a...

    Read at https://taiga.io/security/

    AITIRE CLOUD has certification for compliance with: ISO/IEC 27001:2013 - Information security management systems — Requirements.

    Read at https://taiga.io/security/

    INTERXION MAD3 datacenter has certification for compliance with: PCI-DSS ISO 9001 ISO 14001 ISO 20001 ISO 22301 ISO 27001 ISO 50001 ENS SOC1 SOC2 INTERXION MAD3 also counts

    Read at https://taiga.io/security/

    on for compliance with: PCI-DSS ISO 9001 ISO 14001 ISO 20001 ISO 22301 ISO 27001 ISO 50001 ENS SOC1 SOC2 INTERXION MAD3 also counts with security measures such as 24×7 on-site security personnel, CCTV...

    Read at https://taiga.io/security/

Source: https://taiga.io/security/ · checked 2026-09-05

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://taiga.io/privacy-policy/ · 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.