Muahproxy Play edition Privacy Policy
Updated: 2026-10-29
Publisher and service operator: Harvard Han Privacy contact: sportscar@gmail.com
What this edition does
This policy covers the proxy/VPN-only Android application com.muahproxy.play and its operator-provided relay. Muahproxy lets authorized clients use an Android phone's cellular connection through authenticated SOCKS5/HTTP proxy access or a server-created OpenVPN profile. The Android proxy app does not itself use Android VpnService to capture the phone's other apps.
The separate private application com.muahproxy.app has additional optional messaging features and a separate policy at https://taxreliefnews.com/proxy/privacy-private. Those messaging features are not part of this Play edition.
Registration and permission choices
Before cloud connection, the app asks you to review the selected operator's disclosure and agree. Android permission or assistant selection alone is not that agreement. Automatic enrollment creates an installation claim, a device identity, authentication credentials and proxy access. A device alias can be based on the phone model or text you choose. These identifiers are not your IMEI, IMSI, SIM serial number or advertising ID.
You can decline cloud access or pause it later. Local direct proxy access is separate. Phone-state permission is optional and supports carrier/call-status checks; known active calls can defer airplane-mode rotation. Rotation eligibility and its explanation can be sent with operator status, including an explanation that a call is in progress. This does not send call numbers, call contents or call history. Choosing Muahproxy as the Android assistant replaces your current assistant and authorizes its manual/authenticated remote airplane-mode requests. Automatic rotation schedules are a separate choice. This edition does not request SMS/MMS, Call Log, contacts, microphone or GPS permissions.
Data the service processes
- Installation/account identifiers, credentials, user-selected device alias, application/device version and connection capabilities needed to authenticate and administer the gateway.
- Cellular exit IP, observation times, carrier/network labels, provider/ASN information, connection state and operational events used to show current status and troubleshoot the requested service.
- Relay upload/download byte totals, time buckets, access-point attribution and session start/end/protocol records. Direct LAN transfers and unrelated phone-app traffic are not included in the relay ledger.
- Destination host/IP/port and the traffic necessary to establish and carry the proxy connections you authorize. Destination metadata is processed to route connections and enforce destination restrictions. The application traffic/session ledger does not store destination names, full URLs or packet/message payloads.
- OpenVPN profile names, certificate identity/status and cryptographic material used to create and revoke profiles. A profile contains private access credentials: protect exported copies and give them only to authorized users.
- Privacy consent and deletion state, including minimum security records needed to prevent a deleted registration or uncertain send/request from being recreated or replayed.
The operator can administer enrollments, proxy credentials, access points, reconnect requests, rotation policies and VPN profiles. Anyone you authorize with proxy/VPN credentials can consume this phone's mobile data. Service use may incur carrier charges and battery consumption.
Transmission, encryption and access
Enrollment, management and the phone-to-relay connection use authenticated HTTPS/TLS. Destination HTTPS remains encrypted between the client and destination website. This does not mean that all traffic is end-to-end encrypted or hidden from the relay operator.
Ordinary SOCKS5, HTTP proxy and direct LAN connections may carry unencrypted data, depending on the client and destination protocol. The operator processes the relayed traffic and can see plaintext carried by those protocols. An OpenVPN client encrypts its tunnel to the server gateway; the gateway still processes the resulting proxy traffic. Authentication does not itself encrypt a plain proxy connection.
Credentials are protected in the app's private storage. Access is limited through authentication and service controls. These controls are not a promise that a server operator cannot access data or keys available to that operator.
Other services and your chosen recipients
The app/relay uses ipify to observe public egress and RIPEstat to identify the network prefix/ASN/provider associated with an exit IP. These requests disclose network addresses and routine request metadata to those services. The ipify check runs periodically whenever the proxy service is active, including direct-only operation with the remote relay disabled; it has no separate opt-out while that service runs. Stopping the proxy stops its checks. The Pause cloud access action also stops the active proxy service. Cloudflare can process request/response content and network/request metadata for HTTPS connections passing through its front door, including initial enrollment when it uses that path. This does not mean those contents are routinely stored in logs. A later direct relay connection does not undo that earlier processing. The hosting provider supplies the relay infrastructure. A carrier and your selected destinations also process the traffic needed to deliver the requested connection.
You may choose to export a VPN profile, copy credentials or share a file with another app/device. The recipient then controls that exported copy. Do not share credentials with anyone you do not authorize.
External service processing and retention limits: Cloudflare handles parts of the public website and HTTPS front door, including an initial automatic-enrollment request when it uses that front door. Cloudflare can process request and response content passing through it, together with network/request metadata such as IP addresses, request paths and user agents; this does not mean those contents are routinely stored in logs. A later direct phone-to-relay connection does not undo that initial processing. The web server can also record request/security metadata under its host logging configuration. Hosting and edge providers may keep operational, security and diagnostic records under their applicable services and policies. We have not verified all provider account logging settings or provider-level retention periods. We therefore do not claim these records are absent or deleted within the application live-data or backup periods. Registration deletion removes the operator-controlled application data described in this policy; it does not itself verify deletion of independent provider records. Cloudflare privacy information is available at https://www.cloudflare.com/privacypolicy/.
The app displays the static label Sponsored by TaxReliefNews.com. The publisher identifies this footer as publisher attribution rather than paid advertising. This release does not request an advertising ID or use behavioral advertising targeting. The sponsor classification does not change the data flows described above.
Live-store retention
- Active registration and credentials: until you remove the registration or the operator retires it; unfinished deletion work stays pending until removal is confirmed.
- Traffic rollups: minute detail for up to 48 hours, hourly totals for up to 30 days, and daily totals for up to 365 days. Per-session records are kept for up to seven days with a bounded global capacity. Data can be removed earlier by capacity limits or deletion.
- Operational history: up to 30 days and 2,000 retained events, subject to bounds and expiry processing.
- Remembered cellular IPs: up to 30 days and 200 entries per phone, subject to deletion/capacity bounds.
- VPN client certificates: normally valid for up to 365 days; expiry/revocation stops new use. Full registration deletion purges that phone's live gateway configuration, profile keys/certificates and associated personal metadata rather than treating certificate expiry as erasure.
- Completed deletion receipts: seven days. Pending work is retained until its outcome is resolved. Minimal one-way registration/claim/device security hashes may be retained indefinitely to prevent resurrection or replay. These hashes are pseudonymous security data, not guaranteed anonymous data.
Managed application and VPN-manager backups, including the known legacy backup folders and root-private failed-deployment snapshots, become eligible for removal 30 days after creation. Scheduled daily cleanup normally removes eligible copies within the next day; outages or an unsafe/inconsistent backup can delay cleanup until the operator resolves the incident. Unfinished restore staging copies are retained for operator repair and are excluded from that normal schedule. These limits do not set the retention of hosting-provider snapshots, Cloudflare, host request/security logs or other external records; the known scope and limits are described above. Every restore must apply the current deletion records before serving registrations again. The operator does not treat a backup restore as permission to recreate deleted accounts.
Pause, deletion and your choices
Open Settings, then Privacy and data, to review the operator, pause cloud access or choose Delete this registration. Confirm the request. The app retains the original deletion receipt while the outcome is pending and offers Retry saved deletion request. Wait for confirmation rather than clearing app storage to guess whether the server finished.
A completed request revokes the live registration and removes associated live proxy/API credentials, traffic/IP/operational records and VPN profiles. Backup copies follow the bounded expiry above; minimal security hashes and temporary receipt/reconciliation records have the stated exceptions. Deleting the app or clearing its storage alone does not delete the server registration. Another person's copies of shared credentials/files and independent carrier/destination records are outside this app's deletion operation.
You can request deletion without the app using https://taxreliefnews.com/proxy/delete-data or contact sportscar@gmail.com. We may request proportionate proof that you control the registration. Never email proxy passwords, bearer tokens, enrollment files or VPN private keys. This app does not prevent you from changing Android roles/permissions or uninstalling it. Airplane-OFF cleanup remains available if a rotation was interrupted.
Contact and changes
Send privacy questions to sportscar@gmail.com. This policy describes this operator's configured service. A custom relay can have a different operator; review that operator's terms before connecting. Material data-practice changes require an updated policy and, where applicable, another disclosure/consent decision.
Contact the publisher