Privacy Policy for VHP Bridge
Last updated: 30 August 2026
This policy explains what information the VHP Bridge app (com.ostechnologies.vhpbridge, the "App") handles, why, and the choices you have.
In short: VHP Bridge does not require an account and does not ask you for any personal information. It relays the local proxy traffic of the companion VPN Hotspot & Proxy app through your device's own active VPN; that traffic passes through your device only and is never logged, inspected, stored, or sent to us. The App uses Google Firebase to receive crash reports, understand aggregate usage, and deliver notifications. It shows no ads and does not sell your data.
1. Who we are
The App is published by OS Technologies ("we", "us"), the data controller for the limited information described below. Contact: ostechnologies.apps@gmail.com.
2. What the App does
VHP Bridge is a helper for the separate VPN Hotspot & Proxy app. When a full-device VPN is active, VHP Bridge runs a small on-device relay on the loopback address (127.0.0.1) so that the proxy server in VPN Hotspot & Proxy stays reachable over Wi-Fi while browsing traffic still travels inside the VPN tunnel. All relaying happens locally on your device.
3. Information the App handles
3.1 Information you provide
None. There is no sign-up, login, profile, or form. If you email us for support, we receive the address you write from and whatever you choose to include, and use it only to reply.
3.2 Traffic that passes through the relay
VHP Bridge forwards bytes between the companion app and your device's active VPN. It has no protocol awareness of that traffic: it does not read, modify, record, or transmit the contents, destinations, or metadata of what you browse. Nothing about that traffic reaches us or any third party through this App.
3.3 Network and VPN status (on-device)
The App checks whether a VPN is currently active on the device so it knows whether to relay. This check is performed locally and is not transmitted.
3.4 Device-integrity signals (on-device)
To resist tampering and repackaging, the App checks its own signing certificate and package name and whether it is running in a debuggable build or an emulator. These checks run on your device. If the App crashes, some of these values may appear in the crash diagnostics below.
3.5 Information collected automatically via Google Firebase
The App includes the following Google Firebase SDKs. Google processes this data as our service provider; see Google's Firebase Privacy and Security (https://firebase.google.com/support/privacy) and Google Privacy Policy (https://policies.google.com/privacy).
- Firebase Crashlytics - to diagnose and fix crashes and stability issues. Data: crash stack traces, exception type, the state of the App at the time of the crash, device model and manufacturer, OS version, App version and build, a random Crashlytics installation identifier, and timestamps. We also attach the App version as a custom key.
- Firebase Analytics (Google Analytics for Firebase) - to understand aggregate feature usage and stability trends. Data: App-open and in-App interaction events, session start/length, a pseudonymous App-instance identifier, coarse location (country/region) derived from IP address (the IP address itself is not retained by Google Analytics), device and OS attributes, and - where available and permitted - the Android Advertising ID.
- Firebase Cloud Messaging (FCM) - to deliver notifications such as important update or service notices. Data: an FCM registration token identifying this App install on this device. It changes if you reinstall or clear App data.
4. How we use this information
- Keep the App stable and fix crashes and bugs.
- Understand, in aggregate, which features are used and how the App performs across device and OS versions.
- Send you occasional operational notifications.
- Detect and prevent fraud, abuse, tampering, and security incidents.
- Comply with legal obligations.
Where the GDPR or similar laws apply, our legal basis is our legitimate interest in operating a secure, reliable App, and - where required for analytics or advertising-identifier processing - your consent, which you can withdraw as described in Section 8.
5. Sharing and disclosure
- Service providers. Google LLC processes the Firebase data above on our behalf under its data-processing terms.
- No sale; no advertising. We do not sell or rent your data, and the App contains no advertising SDKs.
- Legal. We may disclose information if required by law or valid legal process, or to protect the rights, safety, or property of users or the public.
- Business transfer. If the App or our business is acquired, data may transfer to the successor under this policy.
6. Data retention
- Crashlytics crash records: retained for up to 90 days by Google.
- Firebase Analytics event-level data: retained for the period configured in our Firebase project (up to 14 months), after which it is aggregated or deleted by Google.
- FCM tokens: valid until the token is refreshed, the App is uninstalled, or App data is cleared.
- Support emails: kept only as long as needed to resolve your request.
7. International transfers
Firebase data is processed on Google's servers, which may be located in the United States or other countries. Google applies Standard Contractual Clauses and other safeguards for such transfers.
8. Your choices and rights
- Notifications. Turn off notifications for the App at any time in Android Settings > Apps > VHP Bridge > Notifications.
- Advertising ID. Reset or delete it in Android Settings > Privacy > Ads. On Android 12 and later, deleting it causes apps to receive a string of zeros.
- Stop all analytics and crash collection. Uninstall the App. No further data is collected after uninstall.
- Access, correction, deletion, objection, portability. If you are in a region that grants these rights (e.g. the EEA, UK, or California), email ostechnologies.apps@gmail.com and we will respond within the time your law requires. Because the Firebase identifiers above are not linked to your name, please include your Crashlytics installation ID or App-instance ID if you want a specific record located; otherwise we can confirm deletion of the relevant project data.
9. Children
The App is a networking utility not directed to children. We do not knowingly collect data from children under 13 (or under 16 where applicable). If you believe a child has provided information, contact us and we will delete it.
10. Permissions the App requests
- INTERNET - relay traffic and communicate with Firebase.
- ACCESS_NETWORK_STATE - detect whether a VPN is active.
- FOREGROUND_SERVICE and FOREGROUND_SERVICE_SPECIAL_USE - keep the relay running while you tether, with a persistent notification.
- POST_NOTIFICATIONS - show the relay status and any operational notices (Android 13+).
- AD_ID (com.google.android.gms.permission.AD_ID) - declared because Firebase Analytics may read the Advertising ID. The App shows no ads.
11. Security
Data in transit to Firebase is encrypted with TLS. The relay operates only on the device's loopback interface. No system can be guaranteed perfectly secure, but we apply reasonable safeguards appropriate to the limited data involved.
12. Changes to this policy
We may update this policy as the App or applicable law changes. Material changes will be reflected by a new "Last updated" date on this page and, where appropriate, an in-App or notification notice.
13. Contact
OS Technologies
Email: ostechnologies.apps@gmail.com
Website: https://ostechnologies.web.app
This policy covers the VHP Bridge Android app only. The companion VPN Hotspot & Proxy app has its own privacy policy.