Skip to content
WrapOS

Legal · content safety

Reports and takedowns

What to include when reporting content, and the operational dependency that must be active before public user uploads launch.

Last updated 9 September 2026

Reporting inbox not configured

This early build has no active public takedown address. User publishing must remain disabled until `NEXT_PUBLIC_SUPPORT_EMAIL` points to a monitored inbox and the response process is owned.

What to report

  • Copyright or trademark infringement.
  • Use of a private image without consent.
  • Illegal, hateful, deceptive, or otherwise prohibited content.
  • A design that impersonates a creator or misstates its license.

What to include

  • The public WrapOS URL or design identifier.
  • What right or policy is affected.
  • Your relationship to the work or person involved.
  • Enough contact information to ask necessary follow-up questions.

How reports should be handled

Public access should be restricted quickly when a credible report indicates immediate harm. The operator should preserve an auditable record, review ownership and context, notify affected parties where appropriate, and record the final decision.