Not full anonymity
Accounts and browsers can still identify you.
How it works · Early access
What happens when you press Connect
SecShield is designed so the connection state is obvious. This page explains the intended path in plain language, without overclaiming anonymity.
SecShield
Quick Connect
Connected
—:—:—
Protected connection
Protected
SecShield Protected
SecShield
Connected
—:—:—
Session timer placeholder
Protected
Path
Device to VPN server
When connected, traffic between your device and the VPN path is intended to travel inside an encrypted tunnel. Confirmed encryption and protocol details will be published when the production build is ready.
-
App establishes a protected session
You confirm connect in SecShield once apps are available.
-
Device traffic enters the tunnel
Local network observers should see encrypted VPN traffic, not clear destination contents where the tunnel applies.
-
Traffic reaches the VPN exit
From there it continues to the open internet.
Internet
VPN server to internet
Destination websites and services receive traffic from the VPN exit IP. They can still identify you through accounts, cookies, and app logins.
Visibility
What your ISP or local network sees
While connected, the local network or ISP typically sees that you are using a VPN path and can observe connection volume and timing. Destination contents inside the tunnel are not meant to be readable.
Exact visibility still depends on network setup, DNS behavior, and whether leak protections are active. DNS leak protection is currently Planned .
Destinations
What destination websites see
Sites see the VPN exit IP and whatever you send them after you visit or sign in. A VPN does not hide your identity from a service you log into.
IP address
IP address explanation
Your apparent public IP can change to the selected VPN exit while connected. If your IP appears unchanged, the app may not be connected, a split path may exist, or a page may be using cached information. See troubleshooting for safe checks.
Encryption
Encryption explanation
Confirmed encryption and protocol details will be published when the production build is ready.
DNS
DNS explanation
DNS translates site names into addresses. Leak protection aims to keep DNS lookups aligned with the VPN path. Confirmed DNS behavior will publish with production builds.
DNS leak protection Coming soon
Locations
Location selection
Recommended or manual location choice determines which exit your traffic uses when that control is available.
Location selection Coming soon
Public Wi-Fi
What changes on public Wi-Fi
On shared networks, a connected VPN reduces casual observation of traffic between your device and the VPN path. It does not replace caution about phishing, malicious portals, or device security.
Limits
Limitations
Not antivirus
Malware protection is a separate category.
Not phishing protection by itself
You still need to evaluate messages and websites carefully.
No streaming guarantee
Service availability depends on each provider.
Compare categories
VPN vs other tools
| Tool | Primary job |
|---|---|
| VPN (SecShield) | Protect connection path and reduce network exposure while connected |
| Antivirus | Detect and block malware on a device |
| Password manager | Store and fill strong unique passwords |
| Data removal | Request removal of personal data from brokers where available |
FAQ
How it works questions
Does connecting hide my identity from websites?
No. Sites still see the VPN exit IP and anything you send after signing in.
Is encryption confirmed yet?
Confirmed encryption and protocol details will be published when the production build is ready.
Where do I read more about privacy?
See the privacy summary.
Ready to follow early access?
Explore pricing preview or return to the product overview.