SaaS Ranking
Menu

Handoff

handoff.ai · Construction estimating · checked 2026-09-03

17/100FBand F

Rank 9 of 18 in Construction estimating, where the median is 13.

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

Overview

Transparency labelsaas-ranking.com

Handoff

handoff.ai · Construction estimating

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

Published commitments1 of 9 found

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

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

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

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

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

Seen at https://handoff.ai/privacy-policy · checked 2026-09-03

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

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

No consent-free first load found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://handoff.ai/ – third-party requests before any interaction: ad.doubleclick.net, alb.reddit.com, api.hubapi.com, bat.bing.com, bat.bing.net, cdn.amplitude.com, cdn.sanity.io, cdn.trackdesk.com, connect.facebook.net, fonts.googleapis.com, fonts.gstatic.com, forms.hscollectedforms.net, forms.hsforms.com, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, onelinksmartscript.appsflyer.com, pixel-config.reddit.com, s3.us-west-2.amazonaws.com, track.hubspot.com, widget.intercom.io, www.google.com, www.googletagmanager.com, www.redditstatic.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://handoff.ai/legal/subprocessors – reached, no match (HTTP 404)
  2. https://handoff.ai/subprocessors – reached, no match (HTTP 404)
  3. https://handoff.ai/sub-processors – reached, no match (HTTP 404)
  4. https://handoff.ai/legal/dpa – reached, no match (HTTP 404)
  5. https://handoff.ai/dpa – reached, no match (HTTP 404)
  6. https://handoff.ai/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://handoff.ai/trust/subprocessors – reached, no match (HTTP 404)
  8. https://handoff.ai/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-03.

Show the 6 addresses we checked
  1. https://handoff.ai/security – reached, no match (HTTP 404)
  2. https://handoff.ai/trust – reached, no match (HTTP 404)
  3. https://handoff.ai/trust-center – reached, no match (HTTP 404)
  4. https://handoff.ai/compliance – reached, no match (HTTP 404)
  5. https://handoff.ai/legal/security – reached, no match (HTTP 404)
  6. https://trust.handoff.ai/ – The name "trust.handoff.ai" 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://handoff.ai/legal/sla – reached, no match (HTTP 404)
  2. https://handoff.ai/sla – reached, no match (HTTP 404)
  3. https://handoff.ai/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://handoff.ai/trust/sla – reached, no match (HTTP 404)
  5. https://handoff.ai/uptime – reached, no match (HTTP 404)
  6. https://handoff.ai/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-03.

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

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

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

Seen at https://handoff.ai/privacy-policy · checked 2026-09-03

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

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://handoff.ai/pricing · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://handoff.ai/ · checked 2026-09-03

History

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

Compare