SaaS Ranking

iMocha

imocha.io · Recruiting assessment · checked 2026-09-04

30/100EBand E

Rank 12 of 26 in Recruiting assessment, where the median is 26.

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

Overview

Transparency labelsaas-ranking.com

iMocha

imocha.io · Recruiting assessment

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

Published commitments3 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.

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 iMocha 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 processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-04.

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

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

Show the 3 addresses we checked
  1. https://status.imocha.io/ – The name "status.imocha.io" could not be resolved.
  2. https://imocha.io/status – reached, no match (HTTP 404)
  3. https://imocha.io.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://imocha.io/pricing – reached and rendered, no match
  2. https://imocha.io/pricing/ – reached, no match (HTTP 200)
  3. https://imocha.io/plans – reached, no match (HTTP 404)
  4. https://imocha.io/en/pricing – reached, no match (HTTP 404)
  5. https://imocha.io/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://imocha.io/ – third-party requests before any interaction: ajax.googleapis.com, cdn.prod.website-files.com, d3e54v103j8qbb.cloudfront.net, fonts.googleapis.com, fonts.gstatic.com, img.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-04.

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

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://imocha.io/legal/sla – reached, no match (HTTP 404)
  2. https://imocha.io/sla – reached, no match (HTTP 404)
  3. https://imocha.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://imocha.io/trust/sla – reached, no match (HTTP 404)
  5. https://imocha.io/uptime – reached, no match (HTTP 404)
  6. https://imocha.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-04.

Show the 1 address we checked
  1. https://imocha.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 European Economic Area, United States, Virginia.
    Show the 3 exact wordings

    The personal data that we collect from you may be transferred to, and stored at, a destination outside the European Economic Area("EEA") or the UK.

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

    Where We Store Your Personal Data iMocha is hosted on Microsoft Azure with our primary data center in Virginia, USA.

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

    Where We Store Your Personal Data iMocha is hosted on Microsoft Azure with our primary data center in Virginia, USA.

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

Source: https://www.imocha.io/privacy-policy · checked 2026-09-04

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

    Read at https://imocha.io/

Source: https://imocha.io/ · checked 2026-09-04

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001, SOC 2 Type II.
    Show the 2 exact wordings

    n Government & Public Sector Contact and Request Overview March 9, 2026 iMocha is SOC 2 Type II and ISO 27001:2022 certified, ensuring enterprise-grade data security and governance.

    Read at https://www.imocha.io/trust-center

    y & Data Protection Government & Public Sector Contact and Request Overview March 9, 2026 iMocha is SOC 2 Type II and ISO 27001:2022 certified, ensuring enterprise-grade data security and governance.

    Read at https://www.imocha.io/trust-center

Source: https://www.imocha.io/trust-center · checked 2026-09-04

Named privacy contact

weight 1 of 3

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

Source: https://www.imocha.io/privacy-policy · checked 2026-09-04

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.