Privacy
Reviewed October 16, 2026
MiProxy handles account and order information to operate the workspace. A real proxy connection goes directly to the supplier gateway. This page describes those boundaries and the information currently documented for the workspace; a complete production privacy notice is still being finalized.
Information handled by the workspace
| Category | Examples | Operational purpose |
|---|---|---|
| Account and session information | Email, name, sign-in identity and session records | Account access and authorization |
| Orders and payment references | Selected packages, order state and payment-event references | Tracking checkout and allocation setup |
| Connection details | Gateway settings and encrypted credentials | Providing the authorized allocation's connection information |
| Usage snapshots | Aggregate supplier usage and sync times | Showing the latest available usage view |
| Support requests | Information participants submit about an issue or request | Administrator review and follow-up |
This table summarizes the known workspace model; it is not a completed inventory of every deployment log, cookie, vendor or data transfer.
Payments and sign-in
Stripe handles card details in the checkout flow; the MiProxy application does not store card numbers. Checkout currently uses test payments; public paid signup is not yet available. Sign-in uses the deployment's identity system and application sessions to identify the account and apply access controls.
The production notice needs a verified list of the identity, hosting, payment, communications and supplier services involved, including their roles and applicable retention practices.
Proxy connections and credentials
Stored gateway credentials are encrypted and revealed through an authenticated ownership check. Encryption is a protection for stored connection details; it is not a claim that no data exists or that every connected service has the same practices.
MiProxy's application does not relay proxy browsing payloads. A real connection uses the supplier gateway, and the supplier has separate data-handling practices. Those practices must be reviewed and disclosed for the selected service before production launch. The lack of an application traffic relay is not a network-wide “no logs” claim.
What to keep out of support requests
Do not send proxy passwords, session cookies, authorization headers or private destination URLs. A useful report normally needs the order reference, time, action and sanitized error. Remove credentials from screenshots and connection strings before sharing them.
Retention and deletion requests
Account deletion and other retention requests currently require manual review through workspace support. The production retention schedule and legal bases have not been finalized, so this draft does not promise a universal deletion deadline.
The documented 24-hour cleanup rule applies to local development email messages. It does not describe the retention of all account data, backups, production logs or supplier records.
Contact about your information
Existing customers can submit a privacy or deletion request through workspace support. If account access is unavailable, contact the administrator who arranged workspace access. A verified public privacy contact and named responsible entity remain required for the production notice.