SaaS Ranking
Menu

Ibexa

ibexa.co · Content management systems · checked 2026-09-03

30/100EBand E

Rank 6 of 17 in Content management systems, where the median is 26.

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

Overview

Transparency labelsaas-ranking.com

Ibexa

ibexa.co · Content management systems

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

Published commitments2 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 Ibexa has no such document.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-03.

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

Show the 7 addresses we checked
  1. https://ibexa.co/legal/subprocessors – reached, no match (HTTP 404)
  2. https://ibexa.co/subprocessors – reached, no match (HTTP 404)
  3. https://ibexa.co/sub-processors – reached, no match (HTTP 404)
  4. https://ibexa.co/legal/sub-processors – reached, no match (HTTP 404)
  5. https://ibexa.co/trust/subprocessors – reached, no match (HTTP 404)
  6. https://ibexa.co/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://ibexa.co/legal/subprocessor-list – 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-03.

Show the 3 addresses we checked
  1. https://status.ibexa.co/ – The name "status.ibexa.co" could not be resolved.
  2. https://ibexa.co/status – reached, no match (HTTP 404)
  3. https://ibexa.co.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-03.

Show the 5 addresses we checked
  1. https://ibexa.co/pricing – reached, no match (HTTP 404)
  2. https://ibexa.co/pricing/ – reached, no match (HTTP 404)
  3. https://ibexa.co/plans – reached, no match (HTTP 404)
  4. https://ibexa.co/en/pricing – reached, no match (HTTP 404)
  5. https://ibexa.co/pricing-plans – 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-03.

Show the 1 address we checked
  1. https://ibexa.co/ – third-party requests before any interaction: ad.doubleclick.net, cdn.matomo.cloud, consent.cookiebot.com, consentcdn.cookiebot.com, deliver.raptorstatic.com, fonts.googleapis.com, forms-eu1.hsforms.com, ibexa.matomo.cloud, js-eu1.hs-scripts.com, js-eu1.hsforms.net, snap.licdn.com, static.hsappstatic.net, tracking.g2crowd.com, unpkg.com, www.google.com, 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://ibexa.co/legal/subprocessors – reached, no match (HTTP 404)
  2. https://ibexa.co/subprocessors – reached, no match (HTTP 404)
  3. https://ibexa.co/sub-processors – reached, no match (HTTP 404)
  4. https://ibexa.co/legal/dpa – reached, no match (HTTP 404)
  5. https://ibexa.co/dpa – reached, no match (HTTP 404)
  6. https://ibexa.co/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://ibexa.co/trust/subprocessors – reached, no match (HTTP 404)
  8. https://ibexa.co/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://ibexa.co/security – reached, no match (HTTP 404)
  2. https://ibexa.co/trust – reached, no match (HTTP 404)
  3. https://ibexa.co/trust-center – reached, no match (HTTP 404)
  4. https://ibexa.co/compliance – reached, no match (HTTP 404)
  5. https://ibexa.co/legal/security – reached, no match (HTTP 404)
  6. https://trust.ibexa.co/ – The name "trust.ibexa.co" could not be resolved.

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://ibexa.co/legal/sla – reached, no match (HTTP 404)
  2. https://ibexa.co/sla – reached, no match (HTTP 200)
  3. https://ibexa.co/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://ibexa.co/trust/sla – reached, no match (HTTP 404)
  5. https://ibexa.co/uptime – reached, no match (HTTP 404)
  6. https://ibexa.co/legal/uptime-sla – 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
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.ibexa.co/about-ibexa/privacy-policy · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://ibexa.co/ · checked 2026-09-03

✓

security.txt (RFC 9116)

weight 1 of 3

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

Source: https://ibexa.co/.well-known/security.txt · checked 2026-09-03

✓

Named privacy contact

weight 1 of 3

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

Source: https://www.ibexa.co/about-ibexa/privacy-policy · checked 2026-09-03

History

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

Compare