Trust Center

Privacy, platform scope, and billing transparency in one place

This page documents what LionVPN currently claims, what depends on platform or account state, and which stronger trust signals require future third-party review.

View pricing terms Read privacy policy

No unsupported audit claims

We do not describe LionVPN as independently audited unless a third-party report is available to users.

Clear product scope

The current public product is VPN-first. SOCKS5 is supported where enabled, H2 is still progressive, and the Linux client is in development.

Channel-based billing

Refunds and cancellations follow the purchase channel: website, App Store, or Google Play.

Privacy and logs

What the no-logs message means on the public site

LionVPN positions privacy as a core product value. The public site should distinguish browsing activity from the account, payment, support, and operational data needed to run the service.

Do not claim anonymity or a verified no-logs audit without evidence.
Explain which account, payment, support, and operational records may exist.
Keep privacy policy, pricing, and support copy aligned.

Security program

What can be published before third-party review

A Trust Center can start with self-published transparency. Third-party participation is only required for claims such as independent audit, verified no-logs, penetration test, or audited infrastructure.

Publish a security contact and responsible disclosure route.
Document dependency updates and security fixes in product updates.
List planned external review separately from completed review.

Legal and platform handling

Requests, purchases, and activation should point to a single source of truth

Trust also depends on operational clarity. Users should know where to request refunds, how activation works, and how to resolve a paid-but-not-activated case.

Website purchases follow website checkout and current website terms.
App Store purchases follow Apple purchase, trial, subscription, and refund flows.
Google Play purchases follow Google Play purchase, trial, subscription, and refund flows.

If a payment is confirmed but access is not active, send the account email, purchase channel, and order details to support.

Contact support

Protocol and platform matrix

Current support, account-enabled features, and roadmap items

This matrix separates what is generally available today from features that depend on client version, account enablement, or active development.

Feature	Windows	macOS	Linux	iOS	Android
Encrypted VPN access Primary LionVPN access path for supported apps.	Current	Current	In development	Current	Current
AI smart routing Automatic route selection where the current client exposes it.	Current	Current	In development	Current	Current
Regional location selection Country and city choices shown by the current app and account.	Current	Current	In development	Current	Current
DNS handling DNS behavior managed as part of the encrypted access path.	Current	Current	In development	Current	Current
Kill switch controls Connection safety controls depend on platform and app release.	Version dependent	Version dependent	In development	Version dependent	Version dependent
Split tunneling Per-app or per-route controls depend on supported client builds.	Version dependent	Version dependent	In development	Version dependent	Version dependent
HTTP/2 transport H2 support is being added progressively.	In development	In development	In development	In development	In development
SOCKS5 access SOCKS5 is supported where enabled by client version and account configuration.	Supported where enabled	Supported where enabled	In development	Supported where enabled	Supported where enabled

How to read this matrix

Current means the capability is part of the public product scope for supported builds.
Version dependent means availability can change by platform release, operating system policy, and account state.
Linux is in development and has not been released as a public client yet.
SOCKS5 is supported where the current client and account configuration expose it.

What the no-logs message means on the public site

LionVPN positions privacy as a core product value. The public site should distinguish browsing activity from the account, payment, support, and operational data needed to run the service.

Do not claim anonymity or a verified no-logs audit without evidence.

Explain which account, payment, support, and operational records may exist.

Keep privacy policy, pricing, and support copy aligned.

What can be published before third-party review

Publish a security contact and responsible disclosure route.

Document dependency updates and security fixes in product updates.

List planned external review separately from completed review.

Requests, purchases, and activation should point to a single source of truth

Trust also depends on operational clarity. Users should know where to request refunds, how activation works, and how to resolve a paid-but-not-activated case.

Website purchases follow website checkout and current website terms.

App Store purchases follow Apple purchase, trial, subscription, and refund flows.

Google Play purchases follow Google Play purchase, trial, subscription, and refund flows.

Feature

Windows

macOS

Linux

iOS

Android

Encrypted VPN access

Primary LionVPN access path for supported apps.

Current

In development

Current

AI smart routing

Automatic route selection where the current client exposes it.

Current

In development

Current

Regional location selection

Country and city choices shown by the current app and account.

Current

In development

Current

DNS handling

DNS behavior managed as part of the encrypted access path.

Current

In development

Current

Kill switch controls

Connection safety controls depend on platform and app release.

Version dependent

In development

Version dependent

Split tunneling

Per-app or per-route controls depend on supported client builds.

Version dependent

In development

Version dependent

HTTP/2 transport

H2 support is being added progressively.

In development

SOCKS5 access

SOCKS5 is supported where enabled by client version and account configuration.

Supported where enabled

In development

Supported where enabled