Muahproxy private edition Privacy Policy
Updated: 2026-10-29
Publisher and service operator: Harvard Han Privacy contact: sportscar@gmail.com
Scope and the shared proxy service
This policy covers the full-feature private Android application com.muahproxy.app. Its cellular proxy, relay, usage history, IP/provider lookup, optional airplane-mode rotation and server-side OpenVPN features use the same operator and data practices described at https://taxreliefnews.com/proxy/privacy. That policy's registration, traffic, credential, live-store, backup and external-service descriptions also apply here. This page additionally describes the private edition's optional SMS/MMS features; they are absent from the separate Play package com.muahproxy.play.
Local SMS/MMS is optional
You may choose Muahproxy as Android's default SMS app and grant the necessary messaging/phone permissions to use its local inbox and composer. This changes the device's default SMS application. A system role or permission is not agreement to upload messages. The app cannot provide RCS service or capture cellular call audio through this messaging feature.
Ordinary SMS/MMS received by the default handler is maintained in Android's native message provider. Existing inbox history is not automatically copied to the remote service. Local user-selected sends, native inbox access and late carrier completion callbacks can continue independently of cloud consent, subject to Android role/permissions and carrier availability. Selected MMS files are read only for the requested message; this is not broad storage access.
Separate remote messaging consent
Remote SMS/MMS API access starts only after its separate, explicit on-device opt-in bound to the selected enrollment. While enabled, authorized API clients and the operator's authorized administration tools can request sends through an active SIM and retrieve newly captured incoming messages. The service processes message text, sender/recipient numbers, timestamps, SIM/subscription metadata, supported attachments, command state and delivery results. SIM phone-number information may be absent, unverified or stale; the UI reports those limits.
Messages received while remote capture is off are not retrospectively imported when it is enabled. Disabling remote access stops new remote sends/capture and deletes pending local API copies. Already uploaded live copies follow retention or a deletion request. Messages already submitted to the carrier cannot be recalled, and an ambiguous carrier result is not automatically resent with a new identity. Carrier charges, limits and delivery behavior still apply.
The remote API uses scoped credentials; a proxy password is not a messaging API token. Do not give a phone API token to anyone you do not authorize to send/read messages. Proxy/VPN clients alone do not receive messaging access.
Security and recipients
Phone-to-relay control/message transfer uses HTTPS/TLS. Message/attachment copies in the app's private store and live server messaging store are encrypted at rest. The operator has the service keys and can access authorized service data: this is not end-to-end encryption against the operator. Carrier SMS/MMS security is controlled by the carrier and protocol; this policy does not claim carrier messaging is end-to-end encrypted.
If you configure the portable PBX adapter, message text can be forwarded to your chosen Asterisk/SIP endpoint. You control that recipient and its configuration, logging, retention and any AMI transport protection. The app alone does not bridge SIM voice audio; a separate nearby hardware/Linux gateway is needed for that use.
Other network services and logging are described by the shared proxy policy. 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. It does not request an advertising ID or use SMS/MMS content for behavioral advertising targeting.
Retention and deletion
The server's messaging default is seven days and its configurable maximum is 30 days. This operator's verified configured period is 7 days for normal remote message/attachment/command records, subject to earlier capacity limits and deletion. Outstanding request/idempotency records can have a different lifecycle needed to prevent duplicate sends. Local unfinished carrier operations retain minimal callback bookkeeping until the operation finishes or is safely reconciled; already submitted carrier work is not silently replayed.
Managed backups become eligible for removal 30 days after creation, with daily cleanup and the incident/unfinished-restore limits described in the public proxy policy. External or host request/security logs and provider snapshots do not acquire that schedule. Deletion records must be honored on restore. Minimum registration/claim/device security hashes can remain indefinitely against resurrection/replay; completed deletion receipt hashes remain for seven days, and unresolved requests remain pending until resolved. Hashes are pseudonymous, not guaranteed anonymous.
Settings, then Privacy and data, offers Pause cloud access and Delete this registration. Confirm deletion and keep the saved request while pending. Completed deletion removes live registration, proxy/messaging credentials, remote messages/attachments, traffic/IP/history and the phone's VPN keys/profile metadata. Local captured API copies and unsent remote jobs are cleared. Already submitted jobs keep only necessary carrier callback bookkeeping. Android's ordinary SMS/MMS provider and files you separately saved/exported are not erased by cloud registration deletion; delete those through their normal local controls if desired.
Deletion does not undo carrier delivery, remove copies held by recipients/PBX systems, change your Android roles, or cancel required airplane-OFF recovery. Uninstalling or clearing app data does not itself delete server copies. Use https://taxreliefnews.com/proxy/delete-data for an external request if the app is unavailable. Contact sportscar@gmail.com for privacy/deletion assistance, and never email message bodies, bearer credentials, enrollment files or VPN private keys merely to identify a request.
Your operator
A custom relay or separately configured PBX can be operated by someone else. Review that operator's policy before granting access. Contact this publisher at sportscar@gmail.com about the service described here. The private app's successful operation or Android role eligibility does not represent Google Play approval for its optional messaging features.
Contact the publisher