Abuse, DMCA and takedown process.
Pre-launch disclosure draft: This page describes the intended process. A responsible operator must review, adopt and publish a final legally reviewed policy before public launch. Do not treat this draft as legal advice.
Operator contact
Designated contact for abuse and takedown notices: abuse@refs.sh. This address is a placeholder until a responsible operator is assigned. Notices sent here are reviewed by the operator or a designated reviewer.
Reporting abuse
Use the report form on a skill listing, which submits to /api/reports. A report includes a public skill ID, an issue category and explanatory text. Reports enter human review through /admin/reports. Reports do not automatically remove a listing, and the service does not require an account to report an issue.
DMCA notice requirements
A valid takedown notice should include: identification of the copyrighted work claimed to be infringed; identification and location (URL) of the allegedly infringing material; your contact information; a statement of good faith belief that the use is not authorized; a statement of accuracy and authority to act on behalf of the rights holder; and a signature (physical or electronic). Incomplete notices may be returned for clarification.
Appeal and reinstatement
A listing owner or affected party may submit a counter-notice to abuse@refs.sh. The operator reviews the counter-notice and may reinstate the listing after the applicable window unless the original complainant provides evidence of court action. Reinstatement decisions are documented in the review record.
Response windows
The operator aims to acknowledge a notice within 2 business days and to reach a decision or request further information within 7 business days. Complex or high-volume matters may take longer; the reporter will be kept informed of status.
Data handling
Issue reports store a public skill ID, issue category, explanatory text and review decisions. Abuse notices and counter-notices may include contact details and identifiers provided by the sender. Submission, report and editor login endpoints use keyed hashes derived from request IP addresses to enforce rate limits. Hosting systems may separately retain access logs. The system uses Supabase for operational database storage when configured.
Operator responsibilities
The operator is responsible for reviewing notices, making takedown and reinstatement decisions, retaining review records, protecting reporter and respondent information, and publishing final terms and a designated contact before launch. External source links and CLI installs follow their own third-party terms and practices.
See also Privacy & data handling and Terms & transparency.