Skip to main content

​
Signup and email verification

Create an account at eclipseproxy.com. We email a verification code: paste it back.

​
Code didn’t arrive

  1. Check spam and promotions folders
  2. Verify your email spelling is correct
  3. Contact support with the email you tried if the code still doesn’t arrive

​
”Invalid token”

Codes expire when you request a new one. Use the most recent code, or contact support if you need help.

​
Forgot which email I signed up with

We can usually find it from other info. Message support with:
  • Account username (e.g., eclipse_yourname)
  • A proxy credentials string you’ve used (mask the password: we identify the account from it)
  • Approximate signup date
  • General payment information (transaction ID, partial payment details)
  • Other email addresses you might have used to contact us
We verify ownership before revealing or changing anything.

​
Change account email

Account email can only be changed through support. Message us with your current email, the new email you want, and a reason. Existing proxy credentials don’t change: your scripts keep working.

​
Account password vs proxy password

These are different. To reset your proxy password (the one that goes into your scripts), see Authentication.

​
Suspected unauthorized use

If your dashboard shows unexpected usage:
  1. Reset proxy password immediately (in dashboard)
  2. Update your own integrations with the new password
  3. Remove unfamiliar IPs from the whitelist
  4. Optional: change account password via the forgot password link

​
Delete account

Contact support to delete your account. When an account is deleted, all remaining bandwidth is forfeited.

​
What gets deleted

  • Account login (email, password hash)
  • Dashboard data (settings, IP whitelist, plan history)
  • Communication history after a short retention window

​
What we keep

  • Financial records (required by tax law)
  • Aggregate anonymized usage statistics
We do not retain:
  • Browsing history or destinations
  • Per-request logs
  • Personal identifying information beyond what’s required for financial records

​
Privacy and logs

​
What we log

  • Aggregate bandwidth usage per account (for billing)
  • Account email, username, encrypted password hash
  • Account activity (logins, password resets for security)
  • Analytics data and referral information

​
What we don’t log

  • Destination URLs you connect to
  • Request bodies or response contents
  • Per-request IP correlation: we don’t store which accounts hit which sites or when
  • Per-request logs: we don’t generate per-request logs at all
We deliberately don’t store per-request logs for performance reasons.

​
Upstream visibility

  • Destination site sees the residential/mobile IP, not yours or ours
  • Residential users whose IP you’re using see nothing: proxy connections happen at a layer they’re not exposed to
  • Upstream providers see aggregate proxy traffic from our infrastructure, not your identity
Because we don’t log destination data, we can’t see which sites you visit or details about your connections. This is a fundamental design choice for your privacy and our operational simplicity.