SaaS Ranking
Menu

Hyperscience

hyperscience.com · Robotic process automation · checked 2026-09-04

48/100DBand D

Rank 2 of 19 in Robotic process automation, where the median is 13.

We measured 12 of 12 criteria for Hyperscience on 2026-09-04. We found 5 with a source and did not find 7 at the addresses we checked. That is a transparency score of 48 out of 100, band D.

Overview

Transparency labelsaas-ranking.com

Hyperscience

hyperscience.com · Robotic process automation

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

Published commitments4 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-04. 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 Hyperscience has no such document.

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 location stated

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://www.hyperscience.ai/security/ · checked 2026-09-04

Show the 7 addresses we checked
  1. https://hyperscience.com/security – found, but behind a sign-in
  2. https://hyperscience.com/trust – reached, no match (HTTP 404)
  3. https://hyperscience.com/legal/privacy – reached, no match (HTTP 200)
  4. https://hyperscience.com/privacy – reached, no match (HTTP 200)
  5. https://hyperscience.com/privacy-policy – reached, no match (HTTP 200)
  6. https://hyperscience.com/compliance – reached, no match (HTTP 404)
  7. https://hyperscience.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-04.

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

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

Show the 1 address we checked
  1. https://hyperscience.com/ – third-party requests before any interaction: cdn-ilenoib.nitrocdn.com, cdn.cookielaw.org, fonts.gstatic.com, forms-na1.hsforms.com, forms.hsforms.com, geolocation.onetrust.com, to.getnitropack.com, www.googletagmanager.com, www.hyperscience.ai

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

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

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

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

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

Published, with a source 5
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.hyperscience.ai/legal-documents/dpa/ · checked 2026-09-04

✓

Subprocessor list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://www.hyperscience.ai/subprocessors/ · checked 2026-09-04

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://hyperscience.com/ · checked 2026-09-04

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://www.hyperscience.ai/legal-documents/dpa/ · checked 2026-09-04

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page Cyber Essentials, FedRAMP, HIPAA, ISO/IEC 27001, SOC 2, SOC 2 Type II.
    Show the 6 exact wordings

    Cyber Essentials Plus We maintain Cyber Essentials Plus certification, which is verified through an independent tech

    Read at https://www.hyperscience.ai/security/

    Current certifications and attestations include: FedRAMP High Authorization Our SaaS solution, delivered in partnership with Palantir FedSTART, is authorize

    Read at https://www.hyperscience.ai/security/

    Alignment with HIPAA, GDPR, and CCPA Our security and privacy practices are designed to support compliance with key priv

    Read at https://www.hyperscience.ai/security/

    Security Data centers in AWS, GCP, and AWS GovCloud via FedSTART are secured and certified against ISO 27001, SOC 2, and FedRAMP standards.

    Read at https://www.hyperscience.ai/security/

    ata centers in AWS, GCP, and AWS GovCloud via FedSTART are secured and certified against ISO 27001, SOC 2, and FedRAMP standards.

    Read at https://www.hyperscience.ai/security/

    SOC 2 Type II We undergo an annual independent SOC 2 Type II audit that evaluates the design and operatin

    Read at https://www.hyperscience.ai/security/

Source: https://www.hyperscience.ai/security/ · checked 2026-09-04

History

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

Compare