Transparency Report

Reporting period: Q2 2026 (1 April – 30 June 2026)

Last updated: 13 April 2026

We publish this report quarterly to provide visibility into government and law enforcement interactions with Latens. Transparency is a core commitment, not a marketing exercise. If we say "no logs," we prove it here.

Lifetime statistics

Since Latens launched in April 2026.

0

Law enforcement requests received

0

National security requests received

0

Court orders received

0

User data disclosed

Q2 2026 (current quarter)

Law enforcement requests

0

Requests from police, AFP, state law enforcement, or other agencies for customer data.

National security requests

0

Requests under national security legislation, including ASIO warrants.

TOLA Act notices

0

Technical Assistance Requests (TAR), Technical Assistance Notices (TAN), or Technical Capability Notices (TCN) under the Telecommunications and Other Legislation Amendment (Assistance and Access) Act 2018.

Court orders

0

Court-ordered disclosure of customer data or infrastructure access.

DMCA / copyright takedown requests

0

Requests to identify customers or block content based on copyright claims.

User data disclosed to any third party

0

Instances where we disclosed any customer data to law enforcement, government agencies, or any third party.

Accounts terminated for abuse

0

Accounts terminated for violations of our acceptable use policy (Section 2 of our Terms of Service).

Warrant canary

Canary is alive

As of 13 April 2026, Latens has not received any secret court orders, national security letters, TOLA Act notices, or any other legal instrument that would prevent us from updating this transparency report or our warrant canary.

For the full warrant canary statement including TOLA Act declarations, visit latens.net/canary.

What we could provide if compelled

Even with a valid warrant, our ability to provide information is limited by our architecture:

We could provide:

  • Email address associated with an account
  • Subscription status and plan type
  • Device names (user-chosen labels like "Dad's phone")
  • Account creation date

We cannot provide (the data does not exist):

  • Browsing history, URLs visited, or DNS queries
  • IP addresses used to connect to the service
  • Connection timestamps or session durations
  • Traffic content, packet metadata, or destination servers
  • WireGuard private keys (deleted after first config download)

Update schedule

This report is updated quarterly on or around the 1st of January, April, July, and October. If this report has not been updated within 120 days of its stated date, you should consider whether it is still reliable.

Questions about this report can be directed to privacy@latens.net.