Clear boundaries, not absolute claims.

What the app offers

Proxy Conduit offers a managed WireGuard VPN subscription and a free Bring Your Own SOCKS5 route. The routes have separate credentials, lifecycle state and responsibilities. The app does not promise complete anonymity.

Managed identity and subscriptions

Managed functionality uses an anonymous Firebase Authentication user ID. A BYO-only startup does not create that identity. When you use managed functionality, the backend processes that user ID, Google Play product and purchase-history state, entitlement status, lifecycle timestamps and a generated device identifier. Google Play processes payment credentials; Proxy Conduit does not receive card or bank details.

Google Play purchase tokens are transmitted to the first-party backend for verification, encrypted at rest for bounded lifecycle reconciliation and never placed in app-defined logs or public deletion flows.

Managed VPN

The Android device generates the WireGuard private key locally. The backend receives the public key, node/location choice, assigned tunnel address and peer lifecycle data. VPN nodes necessarily process packet destination IPs while forwarding traffic. Selected DNS resolvers receive DNS queries, and destinations receive the traffic you send.

Bring Your Own SOCKS5

Proxy profiles, optional username/password and DNS settings are stored in the app sandbox. Credentials are encrypted at rest. The selected proxy receives the connection data and credentials required to operate it. Its availability, privacy and security are controlled by you and that provider, not by Proxy Conduit.

Public IP and approximate location

The app and first-party backend perform public/exit-IP verification. Public IP services including ipify, icanhazip, ifconfig.me and Cloudflare can observe the request IP. Geo-IP services including ipapi.co and ipwho.is receive the observed IP and can return approximate city, country and network-provider information. This is Approximate Location derived from IP, not Android precise location or GPS.

Firebase diagnostics

Firebase Crashlytics remains active to receive crash logs, diagnostics, installation/session identifiers and a strict set of app version, Android version, coarse screen, connection-type, state and fixed error-category fields. App-defined Crashlytics context excludes proxy credentials, purchase tokens, private keys, raw configurations, browsing history and raw endpoint values.

The replacement Android app does not include Firebase Analytics. Older distributed versions may have sent app-interaction events. Historical Analytics data follows the configured Google Analytics retention and deletion controls. Firebase currently documents Crashlytics retention for 90 days before removal begins and deletion of Firebase Authentication and Installation data from live and backup systems within up to 180 days after a deletion request.

Local storage and diagnostics

The app stores profiles, encrypted credentials and private keys, settings, managed recovery state and bounded diagnostics in its private sandbox. Persisted connection events use opaque identifiers, retain category/outcome fields for up to 24 hours and are capped. Aggregate traffic and local log records are retained for up to seven days. You can clear diagnostics in Settings. Files explicitly exported outside the sandbox remain under your control.

Deletion and recovery

Managed users can request deletion in the app or at proxyconduit.io/data-deletion. New managed users can create a high-entropy recovery credential. Proxy Conduit stores only a keyed hash of that credential and an encrypted identity reference. Short-lived web authorizations expire after ten minutes and are single-use. Public deletion rate limits use short-lived keyed network identifiers.

Deletion revokes managed peers and access, removes first-party entitlements and correlated lifecycle records, removes recovery credentials, requests Firebase identity deletion, and then lets the app clear its local sandbox. Provider cleanup and access-token drain can remain pending temporarily. A random status receipt remains for up to 30 days. A non-reversible keyed tombstone is retained for restore safety so an old backup cannot silently recreate deleted access.

Service providers and recipients

Processing can involve Google Play Billing, Firebase Authentication, Crashlytics, Firebase Installations/Sessions, Google Cloud hosting and database services, VPN hosting providers, public-IP/geo-IP services, DNS resolvers and a proxy provider selected by you. Data is shared only as required for the selected function, security, legal compliance or support. Provider retention and lawful disclosures can differ from first-party retention.

Support and legal retention

Support messages are used to answer the request and protect account ownership. Never send passwords, proxy credentials, Firebase tokens, raw purchase tokens, WireGuard private keys or Authorization headers. Proxy Conduit may retain narrowly required security, fraud, accounting or legal records where a documented obligation applies; technical tokens and route data are not retained indefinitely for speculative reasons.

Your choices

You decide whether to use managed service functionality, which route to select, when to connect, whether to export files, and when to clear diagnostics or request deletion. Deleting Proxy Conduit data does not cancel a Google Play subscription. Manage subscription billing separately in Google Play.