» Policy Issues and Abuse Reporting

This page explains AO3's core processes for policy enforcement and abuse reporting for all client users. We are committed to maintaining a positive environment for creation and communication, and all reports must follow the principles described on this page.

1. Report Scope

client that involves content identification errors, harassment, or violations of site usage habits can be submitted through the "Abuse Report" channel. Please note that the report does not involve content review, only actions that significantly deviate from community guidelines. If you encounter abnormal display or link jump problems when using AO3 reader function, you can also note relevant logs in the report for the technical team to locate.

2. Submission method

Please submit the report through the client built-in form published on the official website of AO3, and do not use unofficial channels. The report needs to include a specific entry number (e. g. work ID or comment timestamp) and a concise reason. If you encounter continuous errors after jumping from the AO3 official website to the client, for example, the prompt "AO3.CUBEART.CLUB HOST ERROR" is displayed, please submit the complete screenshot together with the time point, which helps to distinguish network faults from potential abuse.

3. Handling principles

Reports will be reviewed in the order of submission, and the normal use of the client will not be affected during the review. We will not make subjective value judgments on the content, only check whether it deviates from the published operating specifications. Exceptions involving HOME I ARCHIVE OF OUR OWN home page configuration or ARCHIVE OF OUR OWN overall function calls will be preferentially investigated by the infrastructure team and will not be included in the abuse disposal process.

4. User cooperation obligation

Submit a report, please make sure that you have logged in through the client and confirm that the current network environment is stable. If you encounter repeated redirects after jumping through the AO3 link entry, you can clear the client cache before committing the line. Users are encouraged to consult the FAQ categories in the ARCHIVEOFOUROWN Help documentation before reporting to reduce duplicate submissions.

The content of this page is only applicable to the operation within the client and does not cover third-party tools or external chain behavior. All report processing results will be fed back through the client message center, and other inquiries will not be accepted. Thank you for your understanding and cooperation.