SaaS Ranking
Menu

XTM

xtm.cloud · Translation and localization · checked 2026-09-05

22/100FBand F

Rank 19 of 27 in Translation and localization, where the median is 30.

We measured 12 of 12 criteria for XTM on 2026-09-05. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 22 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

XTM

xtm.cloud · Translation and localization

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

Published commitments2 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 XTM 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://xtm.cloud/legal/dpa – reached, no match (HTTP 200)
  2. https://xtm.cloud/dpa – reached, no match (HTTP 200)
  3. https://xtm.cloud/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://xtm.cloud/data-processing-agreement – reached, no match (HTTP 200)
  5. https://xtm.cloud/legal/data-processing-addendum – reached, no match (HTTP 200)
  6. https://xtm.cloud/legal/gdpr – reached, no match (HTTP 200)
  7. https://xtm.cloud/trust/dpa – reached, no match (HTTP 200)
  8. https://xtm.cloud/privacy/dpa – reached, no match (HTTP 200)

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://xtm.cloud/legal/subprocessors – reached, no match (HTTP 200)
  2. https://xtm.cloud/subprocessors – reached, no match (HTTP 200)
  3. https://xtm.cloud/sub-processors – reached, no match (HTTP 200)
  4. https://xtm.cloud/legal/sub-processors – reached, no match (HTTP 200)
  5. https://xtm.cloud/trust/subprocessors – reached, no match (HTTP 200)
  6. https://xtm.cloud/privacy/subprocessors – reached, no match (HTTP 200)
  7. https://xtm.cloud/legal/subprocessor-list – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-05.

Show the 7 addresses we checked
  1. https://xtm.cloud/security – blocked or unavailable (HTTP 403)
  2. https://xtm.cloud/trust – reached, no match (HTTP 200)
  3. https://xtm.cloud/legal/privacy – reached, no match (HTTP 200)
  4. https://xtm.cloud/privacy – reached, no match (HTTP 200)
  5. https://xtm.cloud/privacy-policy – reached, no match (HTTP 200)
  6. https://xtm.cloud/compliance – reached, no match (HTTP 200)
  7. https://xtm.cloud/legal/privacy-policy – reached, no match (HTTP 200)

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.xtm.cloud/ – reached, no match (HTTP 200)
  2. https://xtm.cloud/status – reached, no match (HTTP 200)
  3. https://xtm.cloud.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-05.

Show the 1 address we checked
  1. https://xtm.cloud/ – third-party requests before any interaction: 14487846.fs1.hubspotusercontent-na1.net, 7052064.fs1.hubspotusercontent-na1.net, api.hubapi.com, app.hubspot.com, cdn.feedbucket.app, cdn.transifex.com, connect.facebook.net, consent.cookiebot.com, consentcdn.cookiebot.com, cta-service-cms2.hubspot.com, fonts.googleapis.com, fonts.gstatic.com, forms-na1.hsforms.com, forms.hscollectedforms.net, forms.hsforms.com, js.hs-analytics.net, js.hs-banner.com, js.hsadspixel.net, js.hscollectedforms.net, js.hsforms.net, js.hubspot.com, live-detector.svc.transifex.net, pagead2.googlesyndication.com, perf-na1.hsforms.com, px.ads.linkedin.com, region1.google-analytics.com, snap.licdn.com, static.hsappstatic.net, static.hubspot.com, telemetry.svc.transifex.net, track.hubspot.com, www.googletagmanager.com, xtm-14487846.hs-sites.com, xtm.ai

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://xtm.cloud/legal/subprocessors – reached, no match (HTTP 200)
  2. https://xtm.cloud/subprocessors – reached, no match (HTTP 200)
  3. https://xtm.cloud/sub-processors – reached, no match (HTTP 200)
  4. https://xtm.cloud/legal/dpa – reached, no match (HTTP 200)
  5. https://xtm.cloud/dpa – reached, no match (HTTP 200)
  6. https://xtm.cloud/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://xtm.cloud/trust/subprocessors – reached, no match (HTTP 200)
  8. https://xtm.cloud/legal/sub-processors – reached, no match (HTTP 200)

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

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://xtm.cloud/.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://xtm.cloud/legal/privacy – reached, no match (HTTP 200)
  2. https://xtm.cloud/privacy – reached, no match (HTTP 200)
  3. https://xtm.cloud/privacy-policy – reached, no match (HTTP 200)
  4. https://xtm.cloud/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://xtm.cloud/legal/privacy-notice – reached, no match (HTTP 200)
  6. https://xtm.cloud/trust/privacy – reached, no match (HTTP 200)
  7. https://xtm.cloud/datenschutz – reached, no match (HTTP 200)

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 3
✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://xtm.ai/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 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000

    Read at https://xtm.cloud/

Source: https://xtm.cloud/ · 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, ISO/IEC 27001, SOC 2 (unclear from the sentence), SOC 2 Type II.
    Show the 4 exact wordings

    or life sciences and regulated content, XTM is purpose-built for compliance, with ISO 27001, SOC 2, HIPAA, and GDPR certifications, full audit trails, and configurable AI controls per content risk lev...

    Read at https://xtm.ai/

    Learn More Security you can trust XTM meets global compliance standards, including SOC 2 Type II, ISO 27001, and GDPR, ensuring every project is delivered with full data privacy and protection.

    Read at https://xtm.ai/

    ity scoring (Intelligent Score), and brand-safety controls (Language Guard) within an ISO 27001 and SOC 2 certified environment.

    Read at https://xtm.ai/

    Learn More Security you can trust XTM meets global compliance standards, including SOC 2 Type II, ISO 27001, and GDPR, ensuring every project is delivered with full data privacy and protec

    Read at https://xtm.ai/

Source: https://xtm.ai/ · 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.