Contact IPIDEA

Before you write

Include the account email, the plan involved and — for payment questions — the transaction hash. Payments are matched by hash and account, so that single line usually resolves the ticket immediately.

What support can do

• Set up targeting, sessions and endpoints for a specific workload
• Match a crypto payment that under- or over-shot the invoice
• Replace addresses that stopped behaving
• Explain which product line fits a job before you buy

Response times

Live chat is typically answered within minutes during active hours. Written requests are handled in order, and payment issues are prioritised because they block access.

Common questions support resolves fastest

• An endpoint returns the wrong country. Nine times out of ten this is DNS resolving locally — switch to socks5h:// and retest before reporting it.
• A payment confirmed but access did not open. Send the transaction hash; reconciliation is by hash and account, so that one line usually closes the ticket.
• An address stopped working. Report it rather than reassigning it. Replacements are issued after review, and moving a suspect IP to a fresh profile spreads the problem instead of solving it.
• Which product fits a workload. Describe the job before buying — the wrong product line is the most expensive mistake available here, and it is free to avoid.

What we cannot help with

Support does not write scraping logic, debug third-party antidetect software, or advise on how to approach a platform's terms of service. Anything inside the network — targeting, sessions, endpoints, billing, replacements — is ours to fix and we will.

Requests that fall outside the acceptable-use policy are declined rather than negotiated. It saves everyone the round trip.