1. Imminent danger and emergencies
If someone faces immediate physical danger, contact local emergency services first. Email is not an emergency-response channel.
For an immediate threat to life or safety, contact the appropriate emergency service or law-enforcement agency. Then send us the information below so we can identify any relevant HYPERHOSTGATE resource. Do not delay emergency assistance while waiting for our response.
2. How to submit an abuse report
Send enough detail to locate and assess the issue, but do not expose secrets or unnecessary personal data.
Email hello@hyperhostgate.com with “Abuse report” and the category in the subject. Include:
- your name, organization if applicable, and reliable contact information;
- the exact domain, IP address, URL, message header, or other resource involved;
- the date and time of the activity, including time zone;
- a concise description of what happened and why it violates law or our policies;
- relevant logs, screenshots, or original headers, with unrelated personal data redacted; and
- whether you are the affected person, an authorized representative, or a third-party reporter.
Do not send passwords, authentication tokens, private keys, full card numbers, or malware as an executable attachment. Large or sensitive evidence should first be described so we can arrange a safer transfer method if needed.
3. Details for common report types
Different incidents need different evidence. These details reduce delays and mistaken action.
Phishing or credential theft
Include the full URL, brand or person impersonated, how the link was delivered, and a screenshot. If safe, include the page source or redirect chain without entering credentials.
Malware, botnets, scanning, or network attacks
Include source and destination IP addresses, ports, protocol, timestamps with time zone, log excerpts, traffic pattern, and steps already taken. Explain how you attributed the traffic to a HYPERHOSTGATE resource.
Spam or abusive email
Include the complete original message headers and body, the date received, the recipient domain, and whether an unsubscribe request was ignored. Forwarding only a screenshot usually removes routing evidence.
Privacy, harassment, or intimate imagery
Identify the exact location, the affected person, your authority to act, and the specific privacy or safety concern. Minimize copies of sensitive imagery and use an official trusted-flagger or law-enforcement channel where available.
4. Copyright infringement notices
A copyright notice is a legal claim. Be accurate and identify each work and location clearly.
A copyright owner or authorized agent may send a notice containing:
- a physical or electronic signature;
- identification of the copyrighted work, or a representative list where one notice covers multiple works;
- identification and precise location of the material claimed to infringe;
- contact information reasonably sufficient for us to reach the complaining party;
- a statement of good-faith belief that the use is not authorized by the owner, agent, or law; and
- a statement, under penalty of perjury, that the notice is accurate and the sender is authorized to act.
Send the notice to hello@hyperhostgate.com and the mailing address below. We may forward it to the affected customer. Misrepresentations can create liability.
This reporting channel does not by itself represent that HYPERHOSTGATE has completed a U.S. Copyright Office designated-agent registration. Where such a designation applies, the current public Copyright Office directory entry controls.
5. Copyright counter-notices
If material was removed by mistake or misidentification, the affected customer may respond using the process required by law.
A counter-notice should include:
- the customer’s physical or electronic signature;
- identification and former location of the removed or disabled material;
- a statement under penalty of perjury that removal resulted from mistake or misidentification;
- the customer’s name, address, and telephone number; and
- consent to the jurisdiction and service-of-process terms required by applicable copyright law.
We may share a valid counter-notice with the original complainant and restore material when applicable law permits, unless the complainant timely confirms a court action. We may maintain and enforce a repeat-infringer policy where required.
6. Notices of illegal content
For a legal-removal request, identify the law, the exact content, and why it is illegal—not merely objectionable.
A notice concerning allegedly illegal content should provide a reasoned explanation of the legal basis, the precise electronic location, supporting evidence, the reporter’s contact details unless law permits anonymity, and a good-faith statement that the submission is accurate and complete.
For recipients covered by the EU Digital Services Act or a similar regime, this channel is intended to support electronic notices. We will assess applicable jurisdiction and role, communicate a decision where required, and provide a statement of reasons and available redress route when the law requires one.
7. How we handle a report
We triage severity, verify that the resource is ours, preserve relevant evidence, and choose proportionate action.
We may acknowledge receipt, request missing information, investigate technical records, notify the customer, restrict a resource, or preserve records. Action depends on credibility, severity, urgency, our role, applicable law, and the Acceptable Use Policy.
We may act without advance customer notice to address imminent harm, comply with a binding order, protect an investigation, or prevent evidence destruction. Otherwise, we generally provide the affected customer a fair opportunity to respond. We do not promise a specific outcome or disclose confidential customer information to a reporter.
8. Responses, corrections, and appeals
Affected customers can explain mistakes and provide context. Reporters can correct or withdraw inaccurate submissions.
If you receive an enforcement notice, reply through the identified channel with the reference number, the action challenged, supporting facts, and requested resolution. We will provide an internal review route where appropriate or legally required.
A reporter should promptly correct or withdraw a report that is no longer accurate. Knowingly false, abusive, or impersonated reports may be rejected and may violate law or our policies.
9. Security vulnerabilities
A vulnerability report needs a safer workflow than a general abuse complaint.
For a suspected vulnerability in a HYPERHOSTGATE-controlled system, follow the responsible-disclosure guidance in Trust & Security. Do not access customer data, disrupt service, extort payment, or publish an unremediated issue.
10. Abuse contact
Use email for electronic reports and the mailing address for formal notices.