Abuse Reporting and Enforcement Policy

1. Purpose and Scope

This Abuse Reporting and Enforcement Policy explains how suspected misuse of the Spark Rack Network and Services should be reported, how Spark Rack evaluates reports, what information may be required, and what enforcement actions may be taken.

1. All Spark Rack Customers and prospective Customers;
2. All End Users, authorized users, administrators, and account contacts;
3. All Spark Rack websites, portals, control panels, networks, servers, storage systems, software, and Services;
4. All resellers and downstream customers where applicable;
5. All Customer Data and Customer Content processed through the Services; and
6. All third-party providers used to support an applicable Service.

This Policy supplements the Acceptable Use Policy and does not replace emergency services, law enforcement, court process, or specialized copyright procedures.

2. Reportable Matters

Reports may concern:

1. Phishing and credential theft;
2. Malware, ransomware, botnets, or malicious code;
3. Spam or unsolicited messaging;
4. Fraud, impersonation, or deceptive activity;
5. Denial-of-service attacks or unauthorized scanning;
6. Unauthorized access or attempted access;
7. Child sexual exploitation or abuse material;
8. Threats, stalking, harassment, or credible danger;
9. Copyright, trademark, or other intellectual-property concerns;
10. Privacy violations or unlawful disclosure;
11. Illegal goods, services, or content;
12. Network or resource abuse;
13. Sanctions, export, or legal restrictions;
14. Compromised Customer systems;
15. Violation of the Acceptable Use Policy; or
16. Another activity that creates material risk to people, property, data, or the Spark Rack Network.

3. Use the Correct Reporting Channel

A report should be submitted through the abuse, security, legal, copyright, or support channel appropriate to the issue.

Emergencies involving immediate danger of death or serious physical injury should first be reported to local emergency services or law enforcement.

A copyright claim should use the DMCA process. A vulnerability report should use the Vulnerability Disclosure Policy. A billing dispute should use the billing channel.

4. Information Required in a Report

A useful report should include:

1. The reporter’s name and reliable contact information;
2. The affected domain, URL, IP address, hostname, email address, message identifier, account, or Service;
3. A clear description of the activity;
4. The date, time, and time zone;
5. Complete email headers where relevant;
6. Relevant logs, screenshots, packet captures, or transaction records;
7. Steps used to verify the activity;
8. The requested action;
9. Any immediate safety or security concern;
10. Whether law enforcement or another provider has been contacted; and
11. A statement that the report is accurate to the reporter’s knowledge.

5. Technical Evidence

Technical evidence should be complete enough to identify the source, destination, time, protocol, and event.

A report based only on an IP address without timestamp and time zone may be impossible to investigate because addresses may be shared, reassigned, translated, or dynamically allocated.

Email reports should include full headers rather than a screenshot alone. Web reports should include exact URLs rather than only a homepage.

6. Incomplete and Misdirected Reports

Spark Rack may request clarification, return an incomplete report, refer the reporter to another provider, or close a report that does not identify a Spark Rack Service.

Spark Rack is not required to investigate generalized allegations, unsupported demands, automated notices lacking evidence, or reports outside Spark Rack’s control.

7. Anonymous Reports

Spark Rack may review an anonymous report, but inability to contact the reporter may prevent verification, follow-up, or enforcement.

A reporter concerned about retaliation should explain the concern. Spark Rack will limit disclosure where reasonably possible but cannot guarantee anonymity when disclosure is required by law, fairness, investigation, or legal process.

8. Good-Faith Review

Spark Rack evaluates reports in good faith using available evidence, technical records, applicable law, Customer explanations, provider information, and the nature of the risk.

Spark Rack may determine that no action, additional information, temporary restriction, Customer remediation, or immediate suspension is appropriate.

An abuse report is an allegation, not proof.

9. Customer Notification

When appropriate and legally permitted, Spark Rack may forward a report or relevant details to the affected Customer and request a response or remediation.

Spark Rack may withhold reporter contact information, security-sensitive details, legal restrictions, or information that could endanger a person or compromise an investigation.

Serious or urgent incidents may be acted upon before Customer notice.

10. Response and Remediation Deadlines

Spark Rack may establish a deadline based on severity, harm, scope, history, and technical risk.

Deadlines may require immediate action for phishing, malware, active attacks, child exploitation, imminent danger, or widespread abuse.

Customer must acknowledge the report, contain ongoing harm, preserve relevant evidence, explain corrective actions, and provide requested information.

11. Emergency and Immediate Action

Spark Rack may act immediately and without advance notice when reasonably necessary to:

1. Prevent death or serious physical injury;
2. Stop an active attack;
3. Contain malware or ransomware;
4. Disable phishing or credential theft;
5. Stop child exploitation;
6. Protect another Customer;
7. Protect network reputation;
8. Prevent significant data loss;
9. Comply with law or provider requirements;
10. Preserve evidence; or
11. Prevent material harm.

12. Enforcement Options

Depending on the circumstances, Spark Rack may:

1. Provide guidance or a warning;
2. Require removal or correction;
3. Require software updates or credential rotation;
4. Require malware cleanup or reinstallation;
5. Rate limit or filter traffic;
6. Block a port, protocol, address, domain, URL, message, or file;
7. Disable an account function;
8. Null route an IP address;
9. Quarantine a system;
10. Suspend a Service;
11. Suspend an Account;
12. Refuse new Orders;
13. Decline renewal;
14. Terminate a Service or Account;
15. Preserve records;
16. Notify an upstream provider, registrar, registry, payment processor, or authority;
17. Charge for remediation where permitted; or
18. Take another reasonable action.

13. Proportionality and Escalation

Spark Rack may consider severity, intent, knowledge, repetition, harm, Customer cooperation, technical feasibility, prior history, and risk to other users.

Spark Rack is not required to use the least restrictive action when immediate broader restriction is reasonably necessary or targeted restriction is not technically practical.

14. Compromised Systems

A Customer may violate policy even when malicious activity results from compromise rather than intent.

Customer remains responsible for securing, patching, monitoring, cleaning, reinstalling, and validating Customer-controlled systems.

Spark Rack may require complete reinstallation rather than attempting uncertain cleanup.

15. Spam and Messaging Abuse

Spark Rack may consider complaint rates, recipient consent, list source, headers, content, opt-out behavior, bounce handling, reputation, compromised accounts, and sending pattern.

Spark Rack may suspend sending before completing a full investigation when continued traffic threatens shared infrastructure or provider relationships.

16. Phishing, Malware, and Fraud

Apparent phishing, malware, ransomware, credential theft, or fraud may be disabled immediately.

Spark Rack may preserve content and logs, notify affected providers, rotate credentials, block access, require reinstallation, or refer the matter to authorities.

Customer must not restore known-malicious content without written authorization and remediation.

17. Child Safety

Apparent child sexual abuse material, grooming, enticement, sextortion, trafficking, or exploitation may result in immediate restriction, preservation, termination, and reporting to the National Center for Missing & Exploited Children or law enforcement as required or permitted by law.

Spark Rack will not return prohibited material to Customer and may limit details to protect victims and investigations.

18. Threats and Personal Safety

Reports of threats, stalking, harassment, self-harm, or danger are evaluated based on specificity, credibility, immediacy, available context, and legal authority.

Spark Rack is not an emergency dispatch service. Reporters should contact emergency services when immediate intervention is needed.

19. Intellectual Property Reports

Copyright reports must use the DMCA and Copyright Policy.

Trademark and other intellectual-property claims should identify the right, registration where applicable, exact material, legal basis, and requested action.

Spark Rack may require a court order for complex ownership, fair-use, nominative-use, resale, criticism, parody, or contractual disputes.

20. Content Disputes and Legal Process

Spark Rack does not ordinarily decide defamation, privacy, ownership, employment, contract, or commercial disputes based solely on conflicting allegations.

Spark Rack may require a court order, valid legal process, agreement of the parties, or clearer evidence before restricting content that is not obviously unlawful or dangerous.

21. Preservation of Records

Spark Rack may preserve available records when required by law or reasonably necessary for investigation, fraud prevention, safety, policy enforcement, dispute resolution, or anticipated legal process.

Preservation does not guarantee that every requested record exists, is complete, or can be produced in a particular format.

22. Information Disclosure

Spark Rack does not provide private Customer information merely because a person submits an abuse report.

Information may be disclosed with Customer consent, as necessary to provide or protect the Service, under valid legal process, in qualifying emergencies, or as otherwise permitted by law and the Privacy Policy.

23. False and Abusive Reports

A person must not submit a report known to be false, forged, misleading, impersonated, or intended to harass, censor, extort, disrupt competition, obtain private data, or interfere with lawful activity.

Spark Rack may restrict a reporter’s access to reporting channels, preserve evidence, notify affected parties, or refer serious misuse to authorities.

24. Customer Appeals

Customer may request review of an enforcement decision by providing complete facts, corrective actions, supporting evidence, and the requested outcome.

An appeal does not automatically stay enforcement. Spark Rack may maintain restrictions while risk remains.

Spark Rack’s good-faith determination is final unless a separate contract or applicable law provides another process.

25. No Guarantee of Enforcement Outcome

Spark Rack does not guarantee that every report will result in suspension, removal, disclosure, restoration, prosecution, or any particular result.

Spark Rack may be legally or technically unable to disclose the result of an investigation.

26. Reporter and Customer Conduct

Reporters and Customers must communicate professionally and must not threaten, harass, dox, impersonate, retaliate against, or unlawfully contact another party or Spark Rack personnel.

Disputes should be handled through lawful reporting, appeal, and court processes.

27. Reseller Responsibilities

A reseller must maintain an abuse-reporting process, identify downstream customers, forward notices, impose deadlines, take corrective action, and cooperate with Spark Rack.

The reseller remains responsible for all downstream activity and may not delay urgent action while attempting to contact an End User.

28. Costs of Abuse Response

Spark Rack may charge reasonable fees for extraordinary investigation, emergency intervention, cleanup, restoration, repeated review, legal compliance, or remediation caused by Customer activity when permitted by the Terms of Service.

Payment of fees does not require Spark Rack to restore a Service or permit continued risky activity.

29. Contact

Reports should be submitted through the appropriate abuse or security channel in the Customer Portal or published abuse reporting method.

Spark Rack
Attn: Abuse and Network Safety
PO Box 2215
Valdosta, GA 31604
United States

30. Acknowledgment

By using the Services, Customer acknowledges that:

1. Customer is responsible for all activity under the Account, including compromised systems and downstream users.
2. Spark Rack may act immediately when necessary to prevent harm.
3. An abuse report is an allegation and does not automatically prove wrongdoing.
4. Spark Rack may forward reports or relevant details to Customer.
5. Customer must respond within deadlines and complete required remediation.
6. Spark Rack may suspend or terminate Services for serious, repeated, or unresolved Abuse.
7. Private Customer information is not released merely because a report is submitted.
8. Spark Rack does not guarantee a particular enforcement or disclosure outcome.