Privacy, with clarity.

This describes the current implementation. A public operator must publish its identity, contact and jurisdiction before launch.

Your account and devices

We store your name, email, salted password hash, random device IDs, device labels, session-token hashes, sharing preferences and daily transfer totals. For SharpVPN-SDK peers we also store the partner name, SDK version, consent version and time, administrative access state, last observed public IP and approximate country. Browser sessions expire after seven days. Windows sessions remain active until sign-out or device revocation; the apps protect bearer tokens with Windows DPAPI and never save your password.

Your traffic

Dedicated-node traffic goes directly from the Windows client to an authenticated operator-managed exit. The control website selects nodes and receives cumulative usage reports; it does not relay that payload. Application HTTPS remains encrypted to its destination, while the exit and intervening network can see connection metadata. The HTTP CONNECT authentication hop itself is not TLS-wrapped.

Community traffic travels through the Sharp PHP relay to a consenting exit peer. Relay packets are temporarily queued until acknowledgement. Closed queues are removed after 60 seconds and connection metadata after 24 hours. Server and node access logs may retain source addresses according to operator configuration.

Your contribution

Desktop sharing is disabled by default. SharpVPN-SDK displays a separate consent screen before installing or enabling its automatic Windows service. When enabled, other users access destinations through your public IP and consume your internet allowance. You can disable sharing, change its daily cap, revoke a session, or stop the SDK from its notification-area icon. Administrators can block a peer and close its active routes. Peer totals measure bytes accepted by the relay. Dedicated-node totals are client-reported and enforce a 1 GiB per-account UTC allowance; they are not a billing ledger.

IP country information

The server compares a peer's public IP with a private local copy of the GeoLite2 Country database and caches the approximate country for seven days. Individual IP addresses are not sent to MaxMind, P3TERX or another geolocation API. The maintenance task periodically downloads a complete updated database from P3TERX over HTTPS. Country information is approximate and does not identify a home or street address. If the local database is unavailable, VPN and peer operation continues without a country label.

Community expectations

Do not use the service for abuse, unauthorized access, harassment or illegal activity. TCP destinations are supported. Plaintext application protocols remain plaintext at exits, so use HTTPS or other end-to-end encryption. Application DNS uses Cloudflare DNS-over-HTTPS through the selected exit. The outward-IP check contacts api.ipify.org, and the first connection downloads the tunnel runtime from GitHub.

Before public operation

The operator must provide abuse handling, account deletion and recovery, backup retention, email verification and account-farming controls. Capacity and networking code should be independently reviewed before a public launch.