SaaS Ranking

Sign.com

What Sign.com publishes, measured on their own site. Every result below links the page we found it on, or lists the addresses we checked.

Vendor site: sign.com · category: E-signature

Data processing agreement

Published and readable without a login.

Source: https://sign.com/legal/dpa · checked 2026-08-31

Subprocessor list

No subprocessor list found.

Checked 7 addresses on 2026-08-31.

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

Is this wrong? Send us the URL

Data location stated

The hosting location is stated on a public page.

Source: https://sign.com/legal/privacy · checked 2026-08-31

Status page with history

No public status page found.

Checked 3 addresses on 2026-08-31.

Show the 3 addresses we checked
  1. https://status.sign.com/ – The name "status.sign.com" could not be resolved.
  2. https://sign.com/status – reached, no match (HTTP 404)
  3. https://sign.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Public pricing

No public pricing with figures found.

Checked 5 addresses on 2026-08-31.

Show the 5 addresses we checked
  1. https://sign.com/pricing – reached and rendered, no match
  2. https://sign.com/pricing/ – reached, no match (HTTP 200)
  3. https://sign.com/plans – reached, no match (HTTP 404)
  4. https://sign.com/en/pricing – reached, no match (HTTP 404)
  5. https://sign.com/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Certifications named

No named certification found.

Checked 6 addresses on 2026-08-31.

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

Is this wrong? Send us the URL

Uptime SLA with a figure

No uptime figure found.

Checked 6 addresses on 2026-08-31.

Show the 6 addresses we checked
  1. https://sign.com/legal/sla – reached, no match (HTTP 404)
  2. https://sign.com/sla – reached, no match (HTTP 404)
  3. https://sign.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://sign.com/trust/sla – reached, no match (HTTP 404)
  5. https://sign.com/uptime – reached, no match (HTTP 404)
  6. https://sign.com/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

HTTPS enforced with HSTS

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://sign.com/ · checked 2026-08-31

No third-party tracking before consent

No consent-free first load found.

Checked 1 address on 2026-08-31.

Show the 1 address we checked
  1. https://sign.com/ – third-party requests before any interaction: alb.reddit.com, analytics-ipv6.tiktokw.us, analytics.tiktok.com, assets.calendly.com, bat.bing.com, bat.bing.net, connect.facebook.net, pagead2.googlesyndication.com, pixel-config.reddit.com, region1.google-analytics.com, tr.capterra.com, www.facebook.com, www.googletagmanager.com, www.redditstatic.com

Is this wrong? Send us the URL

security.txt (RFC 9116)

No security.txt found.

Checked 1 address on 2026-08-31.

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

Is this wrong? Send us the URL