SaaS Ranking

LXT

lxt.ai · Data labelling · checked 2026-09-04

26/100EBand E

Rank 11 of 31 in Data labelling, where the median is 22.

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

Overview

Transparency labelsaas-ranking.com

LXT

lxt.ai · Data labelling

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 26of 100 Rank 11 of 31

Published commitments2 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 LXT 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-04.

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

Show the 7 addresses we checked
  1. https://lxt.ai/legal/subprocessors – reached, no match (HTTP 404)
  2. https://lxt.ai/subprocessors – reached, no match (HTTP 404)
  3. https://lxt.ai/sub-processors – reached, no match (HTTP 404)
  4. https://lxt.ai/legal/sub-processors – reached, no match (HTTP 404)
  5. https://lxt.ai/trust/subprocessors – reached, no match (HTTP 404)
  6. https://lxt.ai/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://lxt.ai/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.lxt.ai/ – The name "status.lxt.ai" could not be resolved.
  2. https://lxt.ai/status – reached, no match (HTTP 404)
  3. https://lxt.ai.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-04.

Show the 5 addresses we checked
  1. https://lxt.ai/pricing – reached, no match (HTTP 404)
  2. https://lxt.ai/pricing/ – reached, no match (HTTP 404)
  3. https://lxt.ai/plans – reached, no match (HTTP 404)
  4. https://lxt.ai/en/pricing – reached, no match (HTTP 404)
  5. https://lxt.ai/pricing-plans – 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.

  • Third-party hosts we saw on the first load 1 pcdn.co.
    Show the exact wording

    s40145.pcdn.co

    Read at https://lxt.ai/

Checked 1 address on 2026-09-04.

Show the 1 address we checked
  1. https://lxt.ai/ – third-party requests before any interaction: s40145.pcdn.co

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-04.

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

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

Show the 1 address we checked
  1. https://lxt.ai/.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-04.

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

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

    Our data processors include: Information technology infrastructure and cloud storage service providers Google Cloud Platform and Amazon Web Services located in the United States; Transactional marketi...

    Read at https://www.lxt.ai/privacy-policy/

Source: https://www.lxt.ai/privacy-policy/ · 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; includeSubDomains; preload

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

    max-age=31536000; includeSubDomains; preload

    Read at https://lxt.ai/

    max-age=31536000; includeSubDomains; preload

    Read at https://lxt.ai/

Source: https://lxt.ai/ · checked 2026-09-04

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page HIPAA, ISO/IEC 27001.
    Show the 2 exact wordings

    eral Data Protection Regulation (GDPR) and Healthcare Insurance Portability and Accountability Act (HIPAA), among others - organizations deploying AI solutions need to ensure that the data they use to...

    Read at https://www.lxt.ai/services/secure-ai/

    n in technology Jobs Get Started Close Join our crowd Contact sales Secure data processing services ISO 27001 certified facilities ensure that your data remains secure Connect with our data experts Se...

    Read at https://www.lxt.ai/services/secure-ai/

Source: https://www.lxt.ai/services/secure-ai/ · checked 2026-09-04

History

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

Compare