YIPEE Labs
Loading identity permissions and production state.
COPYRIGHT & REPORTING
Use YIPEE’s private in-product report when you can. This page explains what to include for a rights concern and what is—and is not—operational before formal launch.
REPORTING ROUTE
START HERE
Sign in and use the private Discovery Center report for a profile, invite, known creator, or block-related concern. Include the exact YIPEE link or handle whenever possible.
Report it privately with the affected person, production or output link, what you believe happened, and any immediate safety risk. Do not upload another person’s government ID or private media to make a report.
Gather the original work, the exact YIPEE material or link at issue, your contact details, your authority to act, and a concise explanation of the claimed infringement.
COPYRIGHT NOTICE INFORMATION
A complete notice should identify the copyrighted work, identify the material claimed to infringe (with enough information for us to locate it), provide your contact information, state that you have a good-faith belief the use is not authorized, state that the information is accurate under penalty of perjury and that you are authorized to act, and include a physical or electronic signature.
Do not send passwords, government-ID images, private Vault files, or unrelated sensitive material in a report. If the reported material is in a private production that you cannot access, describe how you know it exists and include any lawful reference you have. Knowingly false claims may have legal consequences.
CURRENT INTAKE STATUS
YIPEE Labs AI has not yet registered and published a designated copyright agent or activated a formal notice-and-counter-notice intake system. Until that happens, do not treat a message to a general YIPEE address or this page as a statutory takedown notice, and do not rely on a particular statutory timetable.
Before YIPEE accepts formal copyright notices for the live service, we will publish the designated-agent details, the submission route, a counter-notice path, an authorized-review workflow, and the handling timeline. That process will replace this pre-launch status notice. The current private reporting route may still be used to flag a safety or account concern, but it is not a substitute for a formal copyright notice.
For questions about this pre-launch policy, contact legal@yipee.ai. For terms that apply to use of the service, read the Terms & Conditions.
PROTECT THE PEOPLE IN THE WORK
YIPEE’s reporting path is designed to surface concerns without turning private identity material into another public asset.