VPN encryption
Traffic between your device and the VPN server is encrypted using the WireGuard protocol.
This page describes how LogicGuard is designed to protect connections and credentials. We avoid unsupported claims like absolute “zero logs” unless a formal policy guarantees them.
Traffic between your device and the VPN server is encrypted using the WireGuard protocol.
A modern VPN protocol with a focused design, strong cryptography, and efficient performance characteristics.
Client private keys are generated and kept on the device. Server private keys stay on the VPS disk — not in MySQL.
API access uses Laravel Sanctum tokens. Extension sessions are short-lived and device-bound.
Rate limiting, validation, policies, and security headers reduce abuse and accidental exposure.
The Chrome extension talks to a local native host over Native Messaging with a strict method allowlist.
VPN nodes expose a private HMAC agent for peer operations — not a public management shell.
Passwords, tokens, and private keys must not appear in application logs. Agent tokens are encrypted at rest.
Prefer HTTPS in production, rotate admin credentials, keep MySQL and agent ports off the public internet.
Filament admin access is limited to users marked as administrators with an active status.