Abuse Reporting

Abuse reporting is a future hosted-content readiness area for Prox Cloud. It is not a backend implementation in the current phase.

Future Report Entry

Public or shared hosted surfaces should eventually expose a Report abuse entry that can capture:

• Reported URL or resource ID.
• Reporter contact path when appropriate.
• Abuse category.
• Short description.
• Supporting evidence or screenshots when safe.
• Severity and urgency hints.

Takedown Queue Concept

A takedown queue should let operators triage reports, preserve evidence, and record outcomes. It should not be a hidden ad hoc inbox once public UGC exists.

Possible queue states:

• new
• triaging
• needs-more-information
• actioned
• rejected
• appealed
• closed

Admin Actions Concept

Future admin actions may include:

• Suspend account or workspace.
• Disable public profile.
• Unpublish public Space.
• Disable public link.
• Remove search indexing.
• Lock a resource while review is pending.
• Trigger an emergency kill switch for a surface.

These are action concepts only. This document does not implement them.

Evidence And Audit Concepts

Prox Cloud should preserve enough evidence to explain operational decisions later:

• Original reported URL and timestamps.
• Actor and target identifiers.
• Submitted report category and text.
• Operator action and reason.
• Before/after visibility state.
• Related security or activity events.

Self-Hosted Versus Prox Cloud

Self-hosted operators control their own domains, deployments, databases, object storage, access model, users, and content operations. Prox Cloud hosted content uses Prox OS-operated infrastructure and requires Prox Cloud operational responsibility.