SaaS Ranking
Menu

SignWell

signwell.com · E-signature · checked 2026-09-05

43/100DBand D

Rank 10 of 24 in E-signature, where the median is 39.

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

Overview

Transparency labelsaas-ranking.com

SignWell

signwell.com · E-signature

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
D 43of 100 Rank 10 of 24

Published commitments4 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-05. 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 SignWell 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-05.

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

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

Show the 1 address we checked
  1. https://signwell.com/ – third-party requests before any interaction: ad.doubleclick.net, alb.reddit.com, analytics.twitter.com, api.hubapi.com, api.hubspot.com, aplo-evnt.com, app.hubspot.com, assets.apollo.io, bat.bing.com, bat.bing.net, bzr.openai.com, bzrcdn.openai.com, cdn.usefathom.com, connect.facebook.net, ddwl4m2hdecbv.cloudfront.net, exceptions.hubspot.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, js.usemessages.com, n.clarity.ms, p.typekit.net, px.ads.linkedin.com, r.wdfl.co, region1.analytics.google.com, script.crazyegg.com, scripts.clarity.ms, snap.licdn.com, static.ads-twitter.com, static.cloudflareinsights.com, static.hotjar.com, static.hsappstatic.net, stats.g.doubleclick.net, t.co, track.hubspot.com, use.typekit.net, www.clarity.ms, www.facebook.com, www.google.com, www.google.de, 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-05.

Show the 8 addresses we checked
  1. https://signwell.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://signwell.com/subprocessors – reached, no match (HTTP 404)
  3. https://signwell.com/sub-processors – reached, no match (HTTP 404)
  4. https://signwell.com/legal/dpa – reached, no match (HTTP 404)
  5. https://signwell.com/dpa – reached, no match (HTTP 404)
  6. https://signwell.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://signwell.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://signwell.com/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-05.

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

Show the 1 address we checked
  1. https://signwell.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-05.

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

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording Canada, United States.
    Show the 2 exact wordings

    This includes cloud hosting environments, sub-processors, and specialized advertising networks located within Canada and the United States.

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

    This includes cloud hosting environments, sub-processors, and specialized advertising networks located within Canada and the United States.

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

Source: https://www.signwell.com/privacy/ · checked 2026-09-05

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.signwell.com/ · checked 2026-09-05

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.signwell.com/pricing/ · checked 2026-09-05

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 63072000 seconds (730 days).
    Show the exact wording

    max-age=63072000; includeSubDomains; preload

    Read at https://signwell.com/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=63072000; includeSubDomains; preload

    Read at https://signwell.com/

    max-age=63072000; includeSubDomains; preload

    Read at https://signwell.com/

Source: https://signwell.com/ · checked 2026-09-05

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page HIPAA (unclear from the sentence), ISO/IEC 27001 (a named provider of theirs), ISO/IEC 27017 (named without a certification claim), ISO/IEC 27018 (named without a certification claim), SOC 2 (unclear from the sentence), SOC 2 Type II (named without a certification claim).
    Show the 6 exact wordings

    Trusted by more than 65,000 businesses Jump to section eSignature Compliance SOC 2 Compliance HIPAA Compliance GDPR NOM-151 21 CFR Part 11 Financial Services Regulatory Alignment Network and System S

    Read at https://www.signwell.com/security/

    Both AWS data centers and services are certified by independent auditors according to ISO 27001 (information security management system), ISO 27017 (information security management systems in the

    Read at https://www.signwell.com/security/

    certified by independent auditors according to ISO 27001 (information security management system), ISO 27017 (information security management systems in the cloud), ISO 27018 (information privacy in t...

    Read at https://www.signwell.com/security/

    tion security management system), ISO 27017 (information security management systems in the cloud), ISO 27018 (information privacy in the cloud), SOC 2, and HIPAA requirements, meaning that systems op...

    Read at https://www.signwell.com/security/

    Trusted by more than 65,000 businesses Jump to section eSignature Compliance SOC 2 Compliance HIPAA Compliance GDPR NOM-151 21 CFR Part 11 Financial Services Regulatory Alignment Net

    Read at https://www.signwell.com/security/

    SOC 2 Type II SignWell is SOC 2, Type II (Security, Availability, and Confidentiality) compliant.

    Read at https://www.signwell.com/security/

Source: https://www.signwell.com/security/ · checked 2026-09-05

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.