Approved hosts.
Your proxy can only reach the hosts you approve. You list the exact host names your app calls. Today that means HTTPS on port 443. Requests to any other host, to an IP address, to private or internal networks, or to mail ports are refused.
The allowlist is always on. There is no setting that opens the proxy to every destination, so a leaked proxy URL can’t be used to reach hosts you didn’t approve.
TLS to the proxy.
Your app connects to the proxy over TLS on port 3129 and sends your username and password inside that connection. HTTPS to the destination then goes through as CONNECT.
Dedicated IPs.
Two dedicated static IPs on separate servers in separate AWS availability zones. They carry only your traffic, never another customer’s.
What we log.
Connection metadata only (destination host, bytes, timing), never contents.
For each connection the proxy logs the time, the method, the destination host and port, the server IP address it resolved to, the status, bytes in and out, and how long it lasted. Query strings are stripped, and no URL paths, headers or bodies are logged. The Privacy Policy lists every record we keep and for how long.
Health data.
HIPAA-ready on every plan. BAA available on request. We never store request or response contents.
Your credentials.
Keep your proxy URL secret and out of the browser. If it may have leaked, tell us at support@staticpair.com.