SaaS Ranking

Termly

termly.io · Privacy compliance · checked 2026-09-05

52/100DBand D

Rank 6 of 35 in Privacy compliance, where the median is 26.

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

Overview

Transparency labelsaas-ranking.com

Termly

termly.io · Privacy compliance

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

Published commitments6 of 9 found

Measured behaviour0 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 Termly 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-05.

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

Show the 3 addresses we checked
  1. https://status.termly.io/ – reached, no match (HTTP 200)
  2. https://termly.io/status – reached, no match (HTTP 404)
  3. https://termly.io.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-05.

Show the 2 addresses we checked
  1. http://termly.io/ – redirects to https://termly.io/
  2. https://termly.io/ – no HSTS header

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://termly.io/ – third-party requests before any interaction: bat.bing.com, bat.bing.net, dev.visualwebsiteoptimizer.com, pagead2.googlesyndication.com, region1.google-analytics.com, static.cloudflareinsights.com, www.googletagmanager.com

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

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

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://termly.io/resources/articles/data-processing-agreement/ · checked 2026-09-05

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, European Union.
    Show the 2 exact wordings

    EU Data Storage Termly stores European users’ data securely in the EU/EEA, supporting businesses’ efforts to meet essential data protection requirements.

    Read at https://termly.io/

    EU Data Storage Termly stores European users’ data securely in the EU/EEA, supporting businesses’ efforts to meet essential data protection requirements.

    Read at https://termly.io/

Source: https://termly.io/ · checked 2026-09-05

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://termly.io/pricing/ · checked 2026-09-05

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://termly.io/resources/articles/data-processing-agreement/ · checked 2026-09-05

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page SOC 2.
    Show the exact wording

    Termly’s commitment to meeting the rigorous industry standards, we are currently preparing for the SOC2 audit process.

    Read at https://termly.io/security-faq/

Source: https://termly.io/security-faq/ · checked 2026-09-05

Named privacy contact

weight 1 of 3

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

Source: https://termly.io/legal-dictionary/privacy-policy/ · 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.