SaaS Ranking
Menu

Leapfin

leapfin.com · Financial planning and close · checked 2026-09-04

61/100CBand C

Rank 1 of 27 in Financial planning and close, where the median is 22.

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

Overview

Transparency labelsaas-ranking.com

Leapfin

leapfin.com · Financial planning and close

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

Published commitments6 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 Leapfin 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

✗

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://leapfin.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://leapfin.com/subprocessors – reached, no match (HTTP 404)
  3. https://leapfin.com/sub-processors – reached, no match (HTTP 404)
  4. https://leapfin.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://leapfin.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://leapfin.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://leapfin.com/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.leapfin.com/ – The name "status.leapfin.com" could not be resolved.
  2. https://leapfin.com/status – reached, no match (HTTP 404)
  3. https://leapfin.com.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-04.

Show the 1 address we checked
  1. https://leapfin.com/ – third-party requests before any interaction: 7052064.fs1.hubspotusercontent-na1.net, 8117914.fs1.hubspotusercontent-na1.net, api.hubapi.com, api.unifyintent.com, app.hubspot.com, cta-service-cms2.hubspot.com, fonts.googleapis.com, fonts.gstatic.com, js.hs-analytics.net, js.hs-banner.com, js.hsadspixel.net, js.hubspot.com, js.storylane.io, leapfin-8117914.hs-sites.com, perf-na1.hsforms.com, px.ads.linkedin.com, script.crazyegg.com, snap.licdn.com, static.hsappstatic.net, tag.unifyintent.com, tribl.io, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://leapfin.com/security – reached, no match (HTTP 404)
  2. https://leapfin.com/trust – reached, no match (HTTP 404)
  3. https://leapfin.com/trust-center – reached, no match (HTTP 404)
  4. https://leapfin.com/compliance – reached, no match (HTTP 404)
  5. https://leapfin.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.leapfin.com/ – The name "trust.leapfin.com" could not be resolved.

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://leapfin.com/.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 7
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.leapfin.com/dpa · checked 2026-09-04

✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording United States.
    Show the exact wording

    Transfers of Your Personal Information Personal information we collect may be stored and processed in your region, in the United States or in any other country where we or our affiliates, subsidiaries...

    Read at https://www.leapfin.com/privacy

Source: https://www.leapfin.com/privacy · checked 2026-09-04

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.leapfin.com/pricing · 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://leapfin.com/

Source: https://leapfin.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.leapfin.com/dpa · checked 2026-09-04

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

  • Highest uptime figure on that page 99.5 %.
    Show the exact wording

    During the Term, the Service will be operational and available to Customer at least 99.5% of the time in any calendar month (“ Service Level Warranty ”).

    Read at https://www.leapfin.com/sla

Source: https://www.leapfin.com/sla · 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.leapfin.com/privacy · checked 2026-09-04

History

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

Compare