SaaS Ranking
Menu

Brizy Cloud

brizy.io · Website builders · checked 2026-09-14

35/100EBand E

Rank 11 of 38 in Website builders, where the median is 24.5.

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

Overview

1 day since the newest finding, 1 since the oldest. 12 of 12 criteria measured in the last 30 days.

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

Brizy Cloud

brizy.io · Website builders

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

Published commitments3 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-14. 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 Brizy Cloud has no such document.

Where Brizy Cloud sits in Website builders

  1. A0 0%
  2. B2 5%
  3. C3 8%
  4. D4 11%
  5. E10 26%
  6. F19 50%
38 vendors with a score; 1 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Brizy Cloud 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 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-14.

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

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

Show the 3 addresses we checked
  1. https://status.brizy.io/ – reached, no match (HTTP 200)
  2. https://brizy.io/status – reached, no match (HTTP 404)
  3. https://brizy.io.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

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

Checked 1 address on 2026-09-14.

Show the 1 address we checked
  1. https://brizy.io/ – third-party requests before any interaction: alb.reddit.com, api-eu1.hubapi.com, app.convertbox.com, b-cloud.becdn.net, brizy-analytics-data-collector-dot-brizy-analytics.ew.r.appspot.com, brizy.containers.piwik.pro, cdn-cookieyes.com, cdn.convertbox.com, cdp-eu.customer.io, cloud-1de12d.becdn.net, d1hsde1uwi6p0a.cloudfront.net, d2zinxbvgvxnpa.cloudfront.net, fonts.bunny.net, js-eu1.hs-analytics.net, js-eu1.hs-banner.com, js-eu1.hs-scripts.com, js-eu1.hsadspixel.net, log.cookieyes.com, pagead2.googlesyndication.com, pixel-config.reddit.com, polyfill-fastly.io, px.ads.linkedin.com, region1.google-analytics.com, snap.licdn.com, static.cloudflareinsights.com, www.googletagmanager.com, www.redditstatic.com, www.youtube.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-14.

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

Show the 6 addresses we checked
  1. https://brizy.io/security – reached, no match (HTTP 404)
  2. https://brizy.io/trust – reached, no match (HTTP 404)
  3. https://brizy.io/trust-center – reached, no match (HTTP 404)
  4. https://brizy.io/compliance – reached, no match (HTTP 404)
  5. https://brizy.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.brizy.io/ – The name "trust.brizy.io" 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-14.

Show the 6 addresses we checked
  1. https://brizy.io/legal/sla – reached, no match (HTTP 404)
  2. https://brizy.io/sla – reached, no match (HTTP 404)
  3. https://brizy.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://brizy.io/trust/sla – reached, no match (HTTP 404)
  5. https://brizy.io/uptime – reached, no match (HTTP 404)
  6. https://brizy.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-14.

Show the 1 address we checked
  1. https://brizy.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
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording Australia, Canada, European Union, France, Germany, India, Netherlands, Singapore, United Kingdom, United States.
    Show the 10 exact wordings

    ext Expense management and receipt processing United Kingdom DigitalOcean Cloud hosting and virtual servers USA, Netherlands, Germany, Singapore, India, Australia, Canada Discord Internal communicatio...

    Read at https://www.brizy.io/privacy-policy

    List of third-parties Third-party Purpose Entity Location 1Password Password management and secure storage United States, Canada, & the EU aMember Membership and subscription management platform USA (...

    Read at https://www.brizy.io/privacy-policy

    List of third-parties Third-party Purpose Entity Location 1Password Password management and secure storage United States, Canada, & the EU aMember Membership and subscription management platform USA (...

    Read at https://www.brizy.io/privacy-policy

    U aMember Membership and subscription management platform USA (assumed) AWS Cloud infrastructure and hosting services Global (notably USA, Europe, Asia-Pacific) Brevo Email marketing and CRM France (h...

    Read at https://www.brizy.io/privacy-policy

    ext Expense management and receipt processing United Kingdom DigitalOcean Cloud hosting and virtual servers USA, Netherlands, Germany, Singapore, India, Australia, Canada Discord Internal communicatio...

    Read at https://www.brizy.io/privacy-policy

    Dext Expense management and receipt processing United Kingdom DigitalOcean Cloud hosting and virtual servers USA, Netherlands, Germany, Singapore, India, Australia, Canada Discord Internal communicati...

    Read at https://www.brizy.io/privacy-policy

    ext Expense management and receipt processing United Kingdom DigitalOcean Cloud hosting and virtual servers USA, Netherlands, Germany, Singapore, India, Australia, Canada Discord Internal communicatio...

    Read at https://www.brizy.io/privacy-policy

    ext Expense management and receipt processing United Kingdom DigitalOcean Cloud hosting and virtual servers USA, Netherlands, Germany, Singapore, India, Australia, Canada Discord Internal communicatio...

    Read at https://www.brizy.io/privacy-policy

    mer engagement and marketing automation platform USA Dext Expense management and receipt processing United Kingdom DigitalOcean Cloud hosting and virtual servers USA, Netherlands, Germany, Singapore,....

    Read at https://www.brizy.io/privacy-policy

    : List of third-parties Third-party Purpose Entity Location 1Password Password management and secure storage United States, Canada, & the EU aMember Membership and subscription management platform USA...

    Read at https://www.brizy.io/privacy-policy

Source: https://www.brizy.io/privacy-policy · checked 2026-09-14

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.brizy.io/pricing-cloud · checked 2026-09-14

✓

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; includeSubdomains; preload

    Read at https://brizy.io/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubdomains; preload

    Read at https://brizy.io/

    max-age=31536000; includeSubdomains; preload

    Read at https://brizy.io/

Source: https://brizy.io/ · checked 2026-09-14

✓

Named privacy contact

weight 1 of 3

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

Source: https://www.brizy.io/privacy-policy · checked 2026-09-14

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.