Acceptable Use

1. Illegal and harmful content

Do not use the service to create, host, distribute, promote, or facilitate content or conduct that is illegal, exploitative, or materially harmful. This includes child sexual abuse material, credible threats, non-consensual intimate material, trafficking, targeted harassment, or instructions primarily intended to cause imminent physical harm.

2. Security abuse

Do not distribute malware, ransomware, credential stealers, botnets, phishing kits, or payloads intended for unauthorized access or disruption. Do not attack, scan, overload, evade controls on, or gain unauthorized access to ReImage or third-party systems.

Good-faith security research, defensive tooling, malware analysis, and dual-use code are permitted when presented and used lawfully, responsibly, and without targeting systems without authorization. Clearly document legitimate research context and handle dangerous samples safely.

3. Spam and deception

Do not send unsolicited bulk messages, create accounts or repositories at scale for promotion or manipulation, impersonate others, conduct phishing, publish knowingly fraudulent material, artificially inflate activity, or evade enforcement through alternate accounts.

4. Rights of others

Do not infringe copyright, trademark, privacy, publicity, confidentiality, or other rights. Do not publish personal data, credentials, secrets, or private communications without lawful authority. Rights holders may report specific material through the abuse process.

5. Infrastructure and Actions

Use shared resources reasonably. Unless ReImage expressly approves otherwise, you may not use ReImage Git or Actions for:

• cryptocurrency mining or proof-of-work computation;
• persistent servers, proxies, relays, tunnelling, or unrelated hosting;
• denial-of-service activity, credential testing, mass scanning, or exploitation;
• high-volume automated mirroring, scraping, package publication, or artifact storage that degrades service;
• circumventing runner isolation, quotas, rate limits, or technical safeguards; or
• workloads unrelated to building, testing, documenting, or maintaining hosted software.

Never place production credentials or sensitive secrets in public repositories, workflow definitions, logs, or artifacts.

6. Enforcement

We consider context, severity, intent, risk, history, and willingness to remediate. Responses may include a warning, content restriction, Actions disablement, rate limiting, temporary suspension, preservation of evidence, or account termination. Urgent threats may be addressed without prior notice.

If you believe enforcement was mistaken, reply to the notice or contact info@reimage.cc with the affected account, decision, and relevant context.

7. Reporting

Report suspected violations through the Report Abuse page. Do not misuse reporting tools to harass users, suppress lawful speech, or submit knowingly false claims.