Rights-first handling, without pretending the inbox already exists

1. Rights-first publishing expectation

Creators are responsible for ensuring they own the work they upload or have explicit permission to distribute it. Uploading leaked, stolen, or unauthorized content is prohibited and may result in removal, creator rejection, suspension, or account closure.

• Rights-to-publish confirmation is already part of the creator post flow.
• HomieHoppers may request additional proof of rights or authorship during review.
• Repeat or deliberate infringement can lead to permanent removal from the platform.

2. How to report suspected infringement right now

The currently live path is the in-app report flow for creators and posts. Use it to identify the account or post involved, describe the issue clearly, and provide enough context for a reviewer to find the material quickly.

• Include the username and, when possible, the exact post URL or post identifier.
• Explain whether the issue is stolen work, unauthorized resale, impersonation, or a related rights problem.
• Add supporting detail so moderation does not have to perform interpretive dance to understand the complaint.

3. What a proper takedown notice should contain before launch

Before public launch, HomieHoppers should expose a dedicated copyright contact or form. A complete notice should include the claimant’s contact information, identification of the copyrighted work, identification of the allegedly infringing material, a good-faith statement, an accuracy / authority statement, and a signature or equivalent affirmation.

• Contact details for the claimant or authorized representative.
• A sufficiently specific description of the original work and the allegedly infringing material.
• A statement made in good faith that the disputed use is unauthorized.
• A statement that the notice is accurate and submitted by someone authorized to act on behalf of the rights holder.

4. Counter-notices and repeat infringement

Counter-notice handling is not yet automated in the current build, but the policy direction is clear: disputed rights claims should be reviewed carefully, documented, and escalated through a production-grade legal process before launch. Repeat infringement may justify creator rejection, content takedown, or broader suspension even while the final workflow is still being formalized.

5. Remaining launch gap

This page is intentionally candid: a dedicated copyright / DMCA inbox or webform still needs to exist before public launch. The in-app report flow is useful and already live, but it is not the full operational answer for outside claimants or formal legal handling.

If HomieHoppers launches publicly, copyright handling should be reviewed together with hosting, storage, CDN, and email provider policies to avoid the usual expensive surprises.