SaaS Ranking
Menu

HelioScope

helioscope.com · Solar design and proposal · checked 2026-09-03

9/100FBand F

Rank 8 of 11 in Solar design and proposal, where the median is 9.

We measured 12 of 12 criteria for HelioScope on 2026-09-03. We found 1 with a source and did not find 11 at the addresses we checked. That is a transparency score of 9 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

HelioScope

helioscope.com · Solar design and proposal

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

Published commitments1 of 9 found

Measured behaviour0 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.

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 HelioScope 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://helioscope.com/legal/dpa – reached, no match (HTTP 200)
  2. https://helioscope.com/dpa – reached, no match (HTTP 200)
  3. https://helioscope.com/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://helioscope.com/data-processing-agreement – reached, no match (HTTP 200)
  5. https://helioscope.com/legal/data-processing-addendum – reached, no match (HTTP 200)
  6. https://helioscope.com/legal/gdpr – reached, no match (HTTP 200)
  7. https://helioscope.com/trust/dpa – reached, no match (HTTP 200)
  8. https://helioscope.com/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-03.

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

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

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.helioscope.com/ – reached, no match (HTTP 200)
  2. https://helioscope.com/status – reached, no match (HTTP 200)
  3. https://helioscope.com.statuspage.io/ – Could not be fetched: fetch failed.

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

Show the 2 addresses we checked
  1. http://helioscope.com/ – redirects to https://www.helioscope.com/
  2. https://helioscope.com/ – 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-03.

Show the 1 address we checked
  1. https://helioscope.com/ – third-party requests before any interaction: ad.doubleclick.net, api.company-target.com, api.hubapi.com, api.hubspot.com, bat.bing.com, connect.facebook.net, consent.cookiebot.com, consentcdn.cookiebot.com, dsum-sec.casalemedia.com, forms.hscollectedforms.net, helioscope.aurorasolar.com, id.rlcdn.com, image2.pubmatic.com, js-na1.hs-scripts.com, js.driftt.com, js.hs-analytics.net, js.hs-banner.com, js.hsadspixel.net, js.hscollectedforms.net, js.hubspot.com, js.usemessages.com, load.sumo.com, partners.tremorhub.com, pixel.rubiconproject.com, px.ads.linkedin.com, region1.analytics.google.com, s.company-target.com, snap.licdn.com, stats.g.doubleclick.net, tag-logger.demandbase.com, tag.demandbase.com, 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-09-03.

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

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://helioscope.com/security – reached, no match (HTTP 200)
  2. https://helioscope.com/trust – reached, no match (HTTP 200)
  3. https://helioscope.com/trust-center – reached, no match (HTTP 200)
  4. https://helioscope.com/compliance – reached, no match (HTTP 200)
  5. https://helioscope.com/legal/security – reached, no match (HTTP 200)
  6. https://trust.helioscope.com/ – The name "trust.helioscope.com" 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://helioscope.com/legal/sla – reached, no match (HTTP 200)
  2. https://helioscope.com/sla – reached, no match (HTTP 200)
  3. https://helioscope.com/legal/service-level-agreement – reached, no match (HTTP 200)
  4. https://helioscope.com/trust/sla – reached, no match (HTTP 200)
  5. https://helioscope.com/uptime – reached, no match (HTTP 200)
  6. https://helioscope.com/legal/uptime-sla – reached, no match (HTTP 200)

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

Show the 1 address we checked
  1. https://helioscope.com/.well-known/security.txt – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://helioscope.com/legal/privacy – reached, no match (HTTP 200)
  2. https://helioscope.com/privacy – reached, no match (HTTP 200)
  3. https://helioscope.com/privacy-policy – reached, no match (HTTP 200)
  4. https://helioscope.com/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://helioscope.com/legal/privacy-notice – reached, no match (HTTP 200)
  6. https://helioscope.com/trust/privacy – reached, no match (HTTP 200)
  7. https://helioscope.com/datenschutz – reached, no match (HTTP 200)

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 1
✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://helioscope.aurorasolar.com/pricing/ · checked 2026-09-03

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.