Skip to content

Data Plane Privacy

MyOwnProxy separates customer proxy traffic from control-plane administration. This boundary applies to both supported connection paths:

Application -> Gateway -> Pool-selected Node -> Internet
Application -> Gateway -> specific Node -> Internet

The Gateway and Node are Customer-controlled infrastructure. Normal application proxy traffic does not pass through the MyOwnProxy control plane.

What the control plane receives

The control plane receives and retains information needed to configure and operate MyOwnProxy, including:

  • Customer users, roles, and resource configuration.
  • Gateway and Node assignments, Proxy configuration, and Pool membership.
  • Gateway and Node public IP information.
  • Lifecycle state, heartbeat timing, health results, errors, host-resource observations, network-quality observations, and reported software versions.
  • Persistent Proxy Credential records and the material required to verify them. A temporary Proxy Credential is held by its issuing Gateway for verification until it expires. Credential passwords are shown to the customer only at issuance, creation, or rotation and cannot be retrieved later through the customer interface.
  • Customer-scoped administrative audit activity, including the actor, action, affected resource, timestamp, and applicable change information.

For a normal customer proxy connection, the control plane does not receive or retain:

  • Request or response content.
  • The source application address.
  • The destination hostname, destination IP address, or destination port.
  • A per-connection proxy record.
  • Per-connection bytes sent or received.

An ADMIN-requested Proxy live test returns operational results such as the observed exit IP and latency when available. That test is a control-plane diagnostic, not the application's proxy traffic path.

Gateway-local connection information

The Gateway must process the SOCKS5 source and destination information required to establish a connection. Current Gateway-local connection logging records:

  • A connection identifier and the source network address seen by the Gateway.
  • The requested destination hostname or IP address and destination port.
  • Whether the connection was allowed or failed.
  • Per-connection bytes sent and received.

These diagnostic entries remain on the Customer-controlled Gateway. MyOwnProxy does not have access to these local logs unless the Customer chooses to share them with MyOwnProxy Support. Their retention is controlled by the Customer through the Gateway host's logging configuration and operating-system maintenance. Review logs for sensitive connection metadata before choosing to share them with MyOwnProxy Support or another party; see Contacting Support.

The connection diagnostics do not record proxied request or response bodies or full application URLs. SOCKS5 connection setup identifies a destination host or IP and port; it does not provide the full URL requested inside an established connection.

External visibility

The selected Node makes the outbound Internet connection, so external destinations normally see the Node's public IP. MyOwnProxy does not make an anonymity claim about the application, Customer network, destination service, or other systems involved in the connection. Those systems can have their own logging and identification behavior.