SaaS Ranking
Menu

Inzwa Cloud: what they publish

inzwa.io · Environmental monitoring and data analysis · checked 2026-10-31

0/100FBand F

Rank 5 of 5 in Environmental monitoring and data analysis, where the median is 9.

Public transparency score, not a product or security rating. Latest check: 2026-10-31. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

3 days since the newest dated result, 3 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

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

Inzwa Cloud

inzwa.io · Environmental monitoring and data analysis

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

Published commitments0 of 9 found

Measured behaviour0 of 3 found

Checked 2026-10-31. 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.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

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 Inzwa Cloud has no such document.

Where Inzwa Cloud sits in Environmental monitoring and data analysis

  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D0 0%
  5. E0 0%
  6. F5 100%
5 vendors with a score. Bands have fixed thresholds, see how the score works.

The band of Inzwa 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 Inzwa Cloud states

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 (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-31.

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

Is this wrong? Send us the URL

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-31.

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

Is this wrong? Send us the URL

✗

Data location: where they say data is hosted

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-10-31.

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

Is this wrong? Send us the URL

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-31.

Show the 3 addresses we checked
  1. https://status.inzwa.io/ – The name "status.inzwa.io" could not be resolved.
  2. https://inzwa.io/status – reached, no match (HTTP 404)
  3. https://inzwa.io.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

Public pricing with figures

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-10-31.

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

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-10-31.

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

Is this wrong? Send us the URL

✗weight 2 of 3

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

Checked 1 address on 2026-10-31.

Show the 1 address we checked
  1. https://inzwa.io/ – third-party requests before any interaction: ad.doubleclick.net, api.hubapi.com, c.bing.com, c.clarity.ms, cta-service-cms2.hubspot.com, fonts.googleapis.com, fonts.gstatic.com, forms.hscollectedforms.net, i.clarity.ms, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, js.hubspot.com, perf-na1.hsforms.com, region1.analytics.google.com, scripts.clarity.ms, stats.g.doubleclick.net, track.hubspot.com, www.clarity.ms, 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-10-31.

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

Is this wrong? Send us the URL

✗

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-10-31.

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

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

Show the 1 address we checked
  1. https://inzwa.io/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-10-31.

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

Nothing to show here yet.

History

100 0 2026-10-24: 0 of 1002026-10-31: 0 of 100 2026-10-24 2026-10-31
Score over the last 2 runs we measured Inzwa Cloud in: 0 (2026-10-24), 0 (2026-10-31).

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Inzwa Cloud

0 found · 12 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-31.

Investigate 12 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Subprocessor list

    Which subprocessors apply to our product, what does each process, and in which countries? Please share the current list.

    Inspect this check
  3. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  4. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  5. Public pricing

    Please confirm the total cost for our seats and usage, including minimum commitments, add-ons, overages and renewal terms.

    Inspect this check
  6. Certifications named

    Please share the current certificate or audit report and its scope, covered legal entity, products and validity period.

    Inspect this check
  7. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  8. HTTPS enforced with HSTS

    How is HTTPS enforced on the product and sign-in domains we will use? Please distinguish those domains from the public website.

    Inspect this check
  9. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  10. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  11. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check
  12. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    Inspect this check

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.