Network Control & Transparency
Transparency Report
This page is the framework and commitment for TuxlerVPN Mobile’s transparency reporting. It is not yet a populated report.
Status: pre-launch. As of the date below, the TuxlerVPN Mobile Android app has not yet launched publicly. There is therefore no reporting period to count, and no formal data requests, government demands, or abuse-related disclosures to disclose. When the first report is published, this page will be replaced with the populated report and a link back to this framework.
This page should be read alongside our Law-Enforcement Request Policy, which describes how we evaluate and respond to legal process.
What this page commits to
We commit to publishing a Transparency Report on a quarterly cadence once the app has launched. Each report will document the formal data requests, government demands, and abuse-related disclosures we received and acted on during the period it covers, using the categories and methodology described below.
Reporting period
The first Transparency Report will cover the period from the public launch of the TuxlerVPN Mobile Android app through the end of the next calendar quarter to close after launch, and will be published within sixty days after that period ends. Subsequent reports will cover three-month calendar quarters and will be published within sixty days of the quarter’s close.
Once launch occurs, this page will be updated with the exact launch date, the specific period covered by the first report, and the planned publication date.
Categories we will track
Each future report will use the following category structure, with both received and complied-with columns:
| Category | Received | Complied with | Data produced |
|---|---|---|---|
| Court orders (Panama) | n/a | n/a | n/a |
| MLAT / letter-rogatory requests (foreign) | n/a | n/a | n/a |
| Subpoenas / civil process | n/a | n/a | n/a |
| National security demands | n/a | n/a | n/a |
| Emergency disclosure requests | n/a | n/a | n/a |
| DMCA-related disclosures resulting in user-data release | n/a | n/a | n/a |
| Abuse-related disclosures resulting in user-data release | n/a | n/a | n/a |
The “n/a” placeholders will be replaced with counts when the first report period closes.
What we count
The categories above are defined as follows:
- Court orders (Panama). Formal orders issued by competent Panamanian courts and served on Tuxler Digital Services Corp.
- MLAT / letter-rogatory requests. Foreign legal-assistance requests properly transmitted via Panama’s central authority or through letters rogatory.
- Subpoenas / civil process. Civil subpoenas served in accordance with Panamanian civil procedure.
- National security demands. Any request invoking national-security powers under applicable law.
- Emergency disclosure requests. Requests for voluntary disclosure where the requester asserts an imminent risk of death or serious physical harm.
- DMCA-related disclosures. Counterparty disclosures arising from a complaint handled under the DMCA Policy, where user data was actually produced to a third party.
- Abuse-related disclosures. Disclosures arising from a credible abuse report under our Acceptable Use Policy or Supported & Prohibited Use Cases, where user data was actually produced to a third party.
Counts will reflect requests served on Tuxler Digital Services Corp. directly. Requests served on Google (the app’s distribution platform) for billing or Google-account information are reported by Google in its own transparency reports.
Methodology
- Legal-process intake is logged at the point of receipt. Our intake email for legal process is
[email protected]. See the Law-Enforcement Request Policy for what we accept and how to format a request. - Each request is evaluated by counsel for legal validity before any response. Where a request is invalid (wrong jurisdiction, scope overreach, missing legal basis, etc.), it is rejected with a written response.
- We commit to notifying the affected user before disclosure where legally permitted, except where a non-disclosure order is in force or where notification would create an imminent risk of harm. See the Law-Enforcement Request Policy.
- Where a request is pending evaluation at the close of a reporting period, it is carried into the next report.
This framework is in force as of the date below. The first set of counts will be published with the first report.
Scope notes
Future reports will cover requests served on Tuxler Digital Services Corp. directly. We will not have insight into:
- Requests served on Google relating to Google Play billing identities. Those are within Google’s reporting scope.
- Requests served on our processors (Sentry, our customer-support provider, our web hosting provider, our cloud infrastructure providers) where TuxlerVPN Mobile was not also served. Those processors operate under their own legal processes and publish their own reports where applicable.
- Requests served on individual VPN gateway server providers. TuxlerVPN Mobile gateways are designed not to retain content or per-session metadata after disconnect (Privacy Policy §2.6), so even where a request reaches a gateway, the data available to be produced is limited.
Data we will be able to produce
Because TuxlerVPN Mobile is designed to discard VPN-session data on disconnect, the data we will be able to produce in response to a valid request is limited by what we retain. The current retention list is in Logging & Retention Data and in our Law-Enforcement Request Policy.
Historical reports
There are no prior reports. The first report will be published after the period described under “Reporting period” above closes.
Updates
Last reviewed: 3 May 2026. This page will be updated when the app launches, when the first report is published, and on each subsequent quarterly cadence.