Connection architecture

Security

A transparent overview of the controls LinkVpn uses to establish, route and verify an Android VPN connection.

Current architecture
Updated July 22, 2026

Android VpnService
Xray-based proxy core

1. Overview

LinkVpn uses Android's system VPN interface to capture traffic covered by the VPN and forward it to an Xray-based proxy core. The core then establishes the configured connection to the selected server.

Android shows a system permission dialog before the app can create a VPN interface. While connected, LinkVpn runs a foreground service and displays a persistent notification so the connection remains visible and can be stopped.

2. Connection path

  1. You select a location and connection option in LinkVpn.
  2. Android creates the VPN interface after system approval.
  3. Covered app traffic enters the local tunnel and is forwarded to the local proxy core.
  4. The proxy core connects to the selected LinkVpn server using the active route configuration.
  5. Server responses return through the same path to the requesting application.

Core sockets are protected from being routed back into the VPN interface. This prevents the connection to the VPN entry server from recursively entering its own tunnel.

3. Connection methods

The current LinkVpn configuration supports Xray VLESS routes using transport security appropriate to the selected server configuration, including:

  • VLESS over WebSocket with TLS;
  • VLESS Reality routes; and
  • VLESS over gRPC with TLS for configured infrastructure routes.

Availability depends on the server list and configuration delivered to the app. LinkVpn does not claim to use OpenVPN or WireGuard in the current Android architecture.

Encrypted transport protects the segment between your device and the configured VPN infrastructure. Traffic to websites should still use HTTPS for end-to-end protection beyond the VPN server.

4. Connection verification

Starting the local VPN components does not by itself prove Internet access. LinkVpn performs a connectivity check through the local proxy after the Xray core starts. A connection is reported as successful only after the proxy path returns the expected response from a known connectivity endpoint.

The app also measures server latency and monitors session traffic and transfer rates for the connected screen and foreground notification. These indicators are operational information, not a guarantee of future speed.

5. User controls

App exclusion

LinkVpn can display installed non-system applications so you can exclude selected apps from the VPN. Excluded apps use their normal network path and do not receive VPN protection from LinkVpn.

Disconnect control

You can disconnect from the app or foreground notification. Android system settings can also stop or replace the active VPN.

Connection status

The connected screen displays session duration, transferred data and current rates based on statistics reported by the proxy core.

6. Security limits

No VPN can make a device completely anonymous or eliminate every security risk.

  • Malware, unsafe downloads, phishing and compromised accounts remain dangerous.
  • Apps excluded from the VPN and traffic sent before connection use the normal network.
  • Websites and apps may identify you through logins, cookies, device signals or other techniques.
  • Network speed and availability vary by device, provider, region, server load and blocking conditions.
  • LinkVpn includes third-party advertising, analytics and attribution SDKs as described in the Privacy Policy.

7. Reporting a security issue

Send suspected security vulnerabilities to [email protected]. Include the affected app version, Android version, reproduction steps and expected impact.

Do not send live server credentials, access tokens, private user data or exploit other users while investigating. We do not currently operate a paid bug-bounty program.

Found a security issue?

Report it privately with enough detail for the LinkVpn team to reproduce and assess it.

Report privately