SaaS Ranking

Content, media and collaboration / Content management systems

Builder.io

What Builder.io publishes on builder.io, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 23/100 FBand F

Rank 6 of 9 in Content management systemscategory median 26checked 2026-09-02

8 gaps found: 8 criteria not found at the addresses we checked. 3 found8 not found1 not measured

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Builder.io

builder.io · Content management systems

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

Published commitments3 of 9 found

Measured behaviour0 of 2 found, 1 not measured

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

Show the full transparency label

Transparency labelsaas-ranking.com

Builder.io

builder.io · Content management systems

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

Published commitments3 of 9 found

Measured behaviour0 of 2 found, 1 not measured

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

Not found, heaviest first

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-02.

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

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-02.

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

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

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

Is this wrong? Send us the URL

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-02.

Show the 2 addresses we checked
  1. http://builder.io/ – redirects to https://builder.io/
  2. https://builder.io/ – no HSTS header

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

Show the 1 address we checked
  1. https://builder.io/ – third-party requests before any interaction: api.amplitude.com, app.launchdarkly.com, cdn.cookielaw.org, cdn.jsdelivr.net, clientstream.launchdarkly.com, events.launchdarkly.com, fonts.googleapis.com, fonts.gstatic.com, geolocation.onetrust.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-02.

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

Show the 6 addresses we checked
  1. https://builder.io/security – reached, no match (HTTP 200)
  2. https://builder.io/trust – reached, no match (HTTP 200)
  3. https://builder.io/trust-center – reached, no match (HTTP 200)
  4. https://builder.io/compliance – reached, no match (HTTP 200)
  5. https://builder.io/legal/security – reached, no match (HTTP 200)
  6. https://trust.builder.io/ – reached, no match (HTTP 200)

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

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

Is this wrong? Send us the URL

Published evidence 3

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.builder.io/ · checked 2026-09-02

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.builder.io/m/pricing · checked 2026-09-02

Named privacy contact

weight 1 of 3

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

Source: https://www.builder.io/legal/privacy · checked 2026-09-02

Not measured by us 1

security.txt (RFC 9116)

weight 1 of 3

Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.

Show the 1 address we checked
  1. https://builder.io/.well-known/security.txt – blocked or unavailable (HTTP 403)

Is this wrong? Send us the URL

Keep going