How We Source, Protect, and Govern Proxy Access
Running a proxy network responsibly means being clear about where IPs come from, what data we keep, and what the service may be used for. This page summarises those practices. It is written in plain language; the binding terms are in our Privacy Policy, Terms of Service, and KYC Policy.
Residential IP sourcing
Residential capacity is provided through partner networks that recruit participants directly. Participants opt in, can see that their connection may be used for proxy traffic, and are compensated for participation. We do not knowingly include devices that were enrolled without consent, and we remove capacity when a partner cannot demonstrate how consent was obtained.
- Consent-based enrollment through partner applications and programs.
- Compensation for participants who share their connection.
- Ongoing review of partner sourcing documentation.
- Removal of capacity tied to credible abuse or consent complaints.
Data we handle
Account data
Name, email, billing details, and authentication records needed to operate your account and meet tax and accounting obligations.
Usage data
Bandwidth consumption, request counts, and error rates used for billing, capacity planning, and abuse detection.
Traffic content
We do not inspect or sell the content of your proxied requests. Operational metadata may be retained for a limited period for security and billing.
Support data
Messages and attachments you send to support, retained so we can resolve the issue and maintain a record of the request.
Privacy requests
Depending on where you live, you may have rights to access, correct, delete, or port your personal data, and to object to certain processing. Send requests to service@graviix.com from the email address on the account. We may need to verify your identity before acting. Details, including retention periods and legal bases, are set out in the Privacy Policy.
Acceptable use
Graviix is built for legitimate access to publicly available information, testing, monitoring, and research. The service may not be used to break the law, evade access controls, send spam, conduct fraud, distribute malware, or interfere with services in a way that causes harm. You are responsible for complying with the terms of the websites you access and with applicable data protection law.
- No credential stuffing, account takeover, or unauthorized access.
- No bulk collection of personal data where consent or a lawful basis is absent.
- No spam, phishing, malware distribution, or fraud.
- No attempts to disrupt or overload targets or the proxy network itself.
Security controls
Access is issued per proxy user so it can be rotated or revoked independently. Accounts can restrict access by IP allowlist, and abnormal usage patterns are reviewed. We recommend separate proxy users per application and rotating credentials when a team member leaves.
If you believe a Graviix IP address is being used for abuse, email service@graviix.com with the IP, timestamp, and a short description. We investigate reports and take action where warranted.
Verification and KYC
To reduce fraud and comply with payment-provider requirements, some accounts are asked to verify their identity or business details. The KYC Policy explains what may be requested and how it is stored. Verification requirements are applied consistently and are not based on nationality.
Compliance questions
Is using a proxy legal?
Proxies are lawful tools in most jurisdictions, but legality depends on what you do with them and where you operate. You are responsible for your use case and for following the target site’s terms.
Do you sell customer data?
No. We do not sell account or traffic data. Limited operational data is processed to run the service, as described in the privacy policy.
How do I report abuse from your network?
Email service@graviix.com with the IP address, time in UTC, and details of the request. We review reports and can disable the associated account.
Can I get a data processing agreement?
Business customers can request a DPA through support. Include your legal entity name and the data categories involved.