Your information
Privacy Policy
What the Happy VPN Android client processes, and where third-party services are involved.
1. Scope and contact
This policy covers Happy VPN’s Android client and this support website. Contact testbatumyalcinn@gmail.com for privacy questions. Separate websites, Google services and VPN infrastructure operators also process information under their own practices.
This static website uses Firebase Hosting. Google can process IP addresses and HTTP request metadata to deliver and secure these pages. The website itself loads no analytics scripts, advertising tools or contact forms. If you email support, your email address and message are handled to respond to your request, including through the email provider.
2. VPN connections and server operators
With Android VPN permission, the client routes traffic through the selected VLESS or WireGuard gateway. A VPN gateway necessarily handles connection IP addresses, destination information and relayed traffic. A VPN tunnel protects the device-to-gateway connection; traffic without separate application-layer encryption may be visible at the gateway.
Server metadata is bundled in the app. WireGuard configuration requests send an installation-generated UUID, a backend-issued user token and the selected server address to the configuration backend. That backend supplies tunnel settings and keys. Its infrastructure may be operated by third parties. We have not verified server-side logging, deletion or retention practices and do not promise that no connection or traffic logs exist.
3. Firebase and Google services
- Analytics: Firebase Analytics is enabled in the current client, not gated by an in-app opt-in. App-defined events cover app opens, screen views and fixed actions such as connection requests or server selection. Those events do not include VPN profiles, destination lists, purchase tokens or custom user identities. The SDK may separately process app/device identifiers and technical metadata. Advertising ID collection is disabled and advertising-storage, user-data and personalization consent signals are denied.
- Crash reporting: Firebase Crashlytics collection is enabled for release builds and disabled for debug builds. Crash reports can include stack traces, app/device details and diagnostic information.
- Notifications and configuration: Firebase Cloud Messaging can process registration tokens and delivery metadata. Remote Config retrieves application settings and may process SDK identifiers and request metadata.
- Payment verification: Firebase anonymous authentication is used only in payment-verification flows, not to load the server list. Where subscriptions are offered, verification can send a Firebase identity token, Google Play purchase token, product identifier and package name to the verification service.
See Google’s Privacy Policy and Firebase privacy information for provider processing. Denying advertising consent does not mean all analytics or technical processing stops.
4. Optional diagnostics and web pages
If you start a speed test, the client contacts Cloudflare services for latency, download and upload measurements. These requests expose ordinary network metadata, including the connecting IP address; test traffic is generated for measurement. See Cloudflare’s Privacy Policy.
Premium web pages, when opened, can use JavaScript, first-party cookies and local web storage. Android WebView is configured to reject third-party cookies. The page host can receive network/browser metadata; review its privacy information before submitting personal or payment details.
5. Local storage, retention and security
The client stores preferences, installation identifiers, backend tokens and cached entitlement information in Android app storage. We do not represent all preferences as encrypted. Network services receive information needed for their functions and may process it in other countries.
Provider and server retention periods have not been verified. No specific deletion period or absolute security guarantee is promised. Removing local app data does not necessarily remove records held by Google, a backend or a server operator.
6. Your choices and requests
You can disconnect the VPN, avoid optional diagnostics or web pages, and manage Android notification permissions. For access, correction, deletion or retention questions, use privacy support. Requests are handled manually; deletion is not automatic or guaranteed for records outside our control. Do not send passwords, private keys, access tokens or full VPN configurations.
Privacy rights and applicable requirements depend on your location and the responsible operator. Material changes will be reflected in an updated document date; unresolved operator and retention details remain expressly unconfirmed.