Reports & Complaints Policy

1. Purpose and Scope

This policy applies to complaints and reports involving content, impersonation, intellectual property, referral fraud, short-link abuse, API misuse, privacy rights, unauthorized access, and other policy breaches across covered domains and services.

Reports may be submitted by users, rights holders, partners, security researchers, or impacted third parties.

2. Required Report Content

To begin review, provide as much of the following as available:

• Reporter name and best reply email.
• Affected domain and full URL(s) or endpoint path(s).
• Date/time range in UTC if possible.
• Relevant IDs (referral ID, promo ID, slug, request ID, campaign ID, verification timestamp if applicable).
• Evidence attachments (screenshots, logs, messages, ownership proof).
• Requested remedy (remove content, disable link, review event, revoke key, etc.).

Intentionally false or materially misleading reports may be rejected and may result in reporting restrictions.

3. Domain and System Routing

Select the branch matching the impacted system. If a report affects multiple branches, include all relevant branches in one submission so investigation can be coordinated.

4. CSAM Zero-Tolerance and Emergency Protocol

Ronan Hayes Management maintains a zero-tolerance policy for child sexual abuse material (CSAM), child sexual exploitation content, or any conduct that facilitates exploitation of minors. This section is the controlling CSAM policy for all covered services.

4.1 Immediate Response

• Potentially impacted content, links, assets, and routes are disabled or quarantined without delay.
• Related accounts, credentials, and API access may be suspended pending investigation.
• Relevant logs and operational records may be preserved for lawful investigation and mandatory reporting.
• CSAM incidents are triaged as critical and escalated immediately.

4.2 Reporter Requirements for CSAM Incidents

• Provide exact URL(s), short link(s), endpoint path(s), and timestamps.
• Include screenshots or evidence needed to locate the incident quickly.
• Include urgent context where immediate harm risk exists.
• Use email subject: [CSAM] Urgent Report - [Domain/Path].

4.3 CSAM Branch Handling

4.4 Mandatory Escalation

The Company follows applicable legal obligations for reporting and cooperation with authorized child safety channels and law enforcement. If a child is in immediate danger, contact emergency services first. In the United States, online child sexual exploitation may also be reported to NCMEC CyberTipline.

5. Review Workflow and Response Targets

1. Intake and Acknowledgment: Initial acknowledgment is typically sent after basic report validation.
2. Triage: Severity, legal exposure, and security risk are evaluated; urgent threats are prioritized.
3. Evidence Review: Logs, records, and supporting documents are compared to policy requirements.
4. Action Decision: Content, links, keys, or access rights may be modified, restricted, or removed.
5. Closure Notice: Reporter receives outcome status when legally and operationally permissible.

Timelines vary by report complexity, legal process, and evidence quality. Emergency safety matters may be acted on immediately.

6. Possible Outcomes

• No action if report is unsupported, out of scope, or contradicted by verified evidence.
• Informal corrective notice with required remediation steps and monitoring window.
• Content, route, campaign, or integration restrictions pending additional investigation.
• Permanent removal, key revocation, account suspension, or legal escalation where warranted.
• Data-rights handling according to the Privacy Policy and applicable law.

7. Appeals and Reconsideration

If you believe an outcome was materially incorrect, you may submit a reconsideration request with new, specific evidence not included in the original report. Repetitive submissions without additional evidence may be closed without further review.

8. Abuse of Reporting Process

Abuse of this process, including knowingly false claims, harassment submissions, or attempts to disrupt operations through fabricated complaints, may lead to report rejection and access restrictions.

9. How to Submit

Send reports to contact@ronanhayes.net with a clear subject line: [Branch + Issue Type] - Short Description. For child-safety reports, use the CSAM subject format listed in Section 4.

Include the required evidence checklist from Section 2 to avoid intake delays.

10. Policy Updates

This policy may be updated to reflect legal developments, infrastructure changes, or improved safety controls. Continued use of covered services after updates indicates acceptance of the revised process.