Latixo

Privacy and test data

What the current test processes.

This page describes the behavior of Latixo V1.10. It focuses on the public speed test and avoids promising retention periods for infrastructure logs that have not been independently verified.

Owner: Latixo TeamEffective: August 30, 2026Last reviewed: September 6, 2026

Data you submit

When you run a test, Latixo receives the public URL entered into the form and a Cloudflare Turnstile token. Do not submit URLs that contain secrets, personal data, private session links or information you are not authorized to test.

The application rejects URL credentials, private or reserved network destinations and non-standard ports. These controls reduce risk but do not turn a public URL into private data.

Network and security data

Your IP address is used to enforce rate limits, prevent more than one simultaneous job from the same IP and bind queue polling to the client that created the job. The Browser Node uses a keyed representation rather than exposing the raw IP in the public queue identifier.

Latixo is delivered through Cloudflare. Cloudflare may process connection data and the Turnstile verification under its own service terms and privacy practices. The origin web server and Cloudflare may also keep ordinary security and access logs according to their configured policies.

Test artifacts

A test can create a final screenshot, loading replay, network-derived measurements and the tested URL. In the current Browser Node design these results are held in memory for short-term delivery, normally up to five minutes before retrieval and approximately 60 seconds after delivery. Temporary replay files are removed when the job finishes.

The current application does not provide user accounts or a permanent public test-history database. Operational logs may still include error and request information needed to secure and troubleshoot the service.

The website being tested

Running a test causes Chromium in the location you select to request the submitted webpage and its resources. The tested site and its third parties will see traffic from that Browser Node and may process the request under their own policies. Latixo does not control content, cookies or third-party requests initiated by the tested page.

Your choices

  • Do not run a test if you do not want the public URL requested from the selected Browser Node location.
  • Remove secrets and private tokens from a URL before submission.
  • Use the service only for public pages you are authorized to test.
  • Do not rely on Latixo as a private browsing or anonymization service.

Changes to this notice

This notice should be reviewed whenever Latixo adds accounts, persistent result storage, analytics, additional processors or materially different infrastructure. The effective and reviewed dates above indicate the version currently published.