Where to report
Email abuse@gologin.com. One email per case helps us act faster.
What to include
- What happened: a short description of the activity and which rule of the Acceptable Use Policy or which law you believe it breaks.
- When it happened: dates and times, with the time zone.
- Evidence: links, screenshots, server or firewall logs, email headers, transaction IDs. For traffic from our proxies, the IP addresses with exact timestamps and time zone.
- Who is involved, if you know it: the Gologin account email, workspace or profile name.
- How to reach you: your name, company and the email address we should reply to.
Please don’t send passwords or more personal data than the report needs.
What happens next
- We confirm that we received your report within 2 business days.
- We investigate and act under our Acceptable Use Policy: from a warning to closing the account and disabling proxies and cloud resources.
- We may ask you for more details. To protect our users’ privacy, we may not be able to tell you exactly what action we took.
An example
In October 2026 a proxy partner told us that one of our customers was sending abusive traffic to a financial service’s website through Gologin proxies. Within ten minutes our support team found the account behind the traffic and blocked it, then checked the customer’s other accounts and connection addresses for related activity.
Law enforcement and legal requests
Requests from police, courts and other public authorities, and other legal notices, go to legal@gologin.com. Please include:
- the name of the authority and the official contact of the person making the request;
- the legal basis for the request and the case or reference number;
- the accounts, data and period the request covers.
We review each request and respond to valid legal process in line with applicable law.
Security vulnerabilities in Gologin
If you have found a security issue in Gologin itself, write to support@gologin.com with the subject “Security” and the steps to reproduce it. Please give us reasonable time to fix it before you publish anything.