Archive of Our Own

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with Whatsit, who volunteers as a Chair in training for the Policy & Abuse committee (PAC) and a tag wrangler.

How does what you do as a volunteer fit into what the OTW does?
As a tag wrangler, I make sure that the fandoms I wrangle have properly canonized tags, which helps users find works that have the characters, relationships, tropes, and themes they're looking for. I fully and completely believe that the tagging system on AO3 is practically one of the modern wonders of the world, and I'm really pleased to be able to do my small part in contributing to it.

My other role is working for the Policy & Abuse committee, where we respond to reports of Terms of Service violations. Anyone who's ever spent time on an unmoderated comments section somewhere knows the importance of moderation in keeping a site usable and enjoyable, and PAC works (mostly) behind the scenes to make sure that's the case for AO3.

What is a typical week like for you as a volunteer?
I try to spend at least an hour or so per day on PAC work, since some of it is time-sensitive and has deadlines attached. This often involves working with tickets that have been sent in about violations, but sometimes it means working on documentation updates or helping to train new volunteers on the committee.

I usually also do at least one big tag wrangling session per week, during which I get caught up with wrangling the tags in my fandoms. I really like putting music on and settling in for a few hours (or more) of wrangling, so this setup works really well for me.

What made you decide to volunteer?
I have a background in book indexing and a particular interest in categorization and taxonomy, so as soon as I found out that tag wranglers were a thing on AO3, I definitely wanted to be one! It sounded like the kind of thing that would be right up my alley (and it was). On a broader level, I think AO3 is one of the best things going on the Internet, in terms of creating a space where people can freely share their fanworks without fear of the content purges that have plagued many other sites. With censorship encroaching on so many other spaces, I think what AO3 stands for is more important than ever. I really believe in the philosophy of the site and I'm glad to be a part of it.

What has been your biggest challenge doing work for the OTW?
Time management! I'm on two separate committees and I also have a day job and a fairly active family life, which is a lot to juggle. But I've had success setting boundaries for myself that keep me from over-committing or burning out. I find that setting specific times during which I'll do specific tasks not only keeps that task from eating up my entire day (which either wrangling or PAC work could otherwise easily do) but also allows me to really focus on that task during the allotted time.

What fannish things do you like to do?
I'm an active fic writer and I participate in quite a few multi-fandom fic exchanges. I find that having an external deadline is great for motivating me to actually finish a fic, something I was historically not great at before doing exchanges. I also hang out on a couple of fandom discords and have been known to go to the occasional convention. And, of course, I spend entirely too much of my free time reading vast amounts of fic.

Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in the comments. Or if you'd like, you can check out previous Five Things posts.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.

Today is World Password Day, and we'd like to take this opportunity to remind everyone of some best practices to keep your accounts secure.

Last year, AO3 saw a rise in users who lost access to their AO3 accounts due to reused or insecure passwords that were found in data breaches from other sites. In response, our Policy & Abuse committee alongside our Accessibility, Design, & Technology, and Systems committees took steps to recover, secure, and notify the owners of over 10,000 at-risk accounts.

Over the past year, we released many new features to proactively make AO3 accounts more secure, including:

• Automatic confirmation emails notifying you when your username, password, or email has been changed
• Adding a verification step to the process for changing the email associated with your account
• Notifying you if your current or new password matches a password that was discovered in a data breach from another site
• Preventing users from choosing new passwords that are extremely short
• Increasing the maximum password length from 40 to 72 characters
• Requiring you to provide the email address associated with your account in order to reset your password
• Updating the layout and wording of how you change or reset your password

How To Protect Your AO3 Account

The best thing you can do to protect yourself on AO3 and other sites is ensure your passwords are strong, unique, and secure. In general, for both AO3 and elsewhere, we recommend that you:

• Regularly check haveibeenpwned.com to see if your emails, passwords, or other information has been exposed in data breaches or whether your passwords have appeared in known data breaches.
• Change your passwords for any breached websites and any accounts on other sites where you may have used the same password.
• Set a unique, secure password for each and every one of your accounts on all platforms.
• Use a password manager. This will help you to set unique, secure passwords for each of your accounts without worrying about forgetting them. Many browsers have a free, built-in password manager if you would prefer to avoid third-party software.
• Make sure to check your email regularly. Don't use a temporary, school, or work email for any personal accounts. (If you need to update the email associated with your AO3 account, go to your Preferences page and click on the "Change Email" button in the top right. Follow the instructions on that page to update your email address.)
• Keep your antivirus software and operating system up to date, and set them to scan for malware regularly.
• Log out when you've finished using devices that others have access to, and don't share your personal devices with other people.
• Never reuse passwords or share your passwords with anyone for any reason.

Future Changes

Keeping AO3 safe for all our users is one of our highest priorities. We continue to remain on the lookout for other ways we can help you protect your account.

We encourage you to follow us on our official platforms and sign up for OTW News by Email to keep track of important announcements and updates to AO3. If you're specifically interested in learning about new features, security updates, and bug fixes, we recommend that you pay attention to our release notes.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.

NOTE: This is a living document and will be updated in response to changes and new types of spam as observed by OTW volunteers.

LAST UPDATED: July 23, 2026

As AO3 continues to grow, there has been an increase in the amount and variety of spambots that attempt to harass or scam users. Spambots may try to imitate other users and even AO3/OTW volunteers to appear more realistic. This post shares a brief update on how we're working to combat this issue, what types of spam we've seen, and what you can do if you encounter spam comments on AO3.

What We're Doing

Protecting our users from scammers and bots targeting AO3 is important to us, and we are actively working to combat spam on the site in a variety of ways—both visible and not. We will not share a detailed list of every change we've made (so as to not provide spammers with information about how to circumvent these measures), but some examples include introducing comment rate limits for logged-in users, changing the default comment setting on new works to "Registered users only", spam checking comments and comment edits from new users, and making a variety of improvements to the admin tools used by our Policy & Abuse volunteers to handle reports and remove spam comments.

We continue to consider and undertake additional technical changes to help prevent and improve our response to spambots. However, it is important to us that any anti-spam measures we implement do not substantially harm users who are browsing or attempting to comment normally. Many more aggressive anti-spam measures would make AO3 less accessible, particularly for users using assistive devices such as screen readers.

In addition to taking technical steps to help address the issues, we continue to post updates about spambots and other important changes to AO3 on our Tumblr, Bluesky, and Twitter/X. We encourage you to follow us on these platforms to stay informed about what's going on.

Types of Spam Comments

Below is a list of different types of spam comments that have been posted on AO3 over the last year. We intend to maintain this list and add new types of spam to it as they are identified; however, this list may not include every type of spam comment that could possibly be received. We encourage you to remain vigilant and follow internet safety best practices.

If you're not sure if something is a spam comment, you're welcome to contact Policy & Abuse for assistance. Before doing so, we encourage you to click through the links below to learn more about each type of comment and use your best judgement to determine if a comment appears to be genuine or could be a scam.

• Art Commission Spam: These comments come from both guests and registered accounts who pretend to be artists who want to make comics or illustrations for your fanfic. They may ask questions or praise your work to try and get you to reply to them, before convincing you to contact them off AO3 (often via Discord). They will try to scam you into paying for their art, which is either AI-generated or does not exist at all. (First reported August 2024, news post published December 2024)
• Deprecated Fandoms Spam: These guest comments claim that AO3 will be "deleting works to conserve server space". There is no such thing as a deprecated fandom and there is no limit on the number of fanworks that can be posted to a specific tag. (First reported May 2025, Tumblr announcement May 2025)
• AI Use Accusation Spam: These guest comments will accuse you of using AI in your work. They may mention a particular AI generator or AI detection service, or claim that they "saw you remove the AI prompts from your work". (First reported April 2023, Tumblr announcement November 2025)
• Harassing Spam: These guest comments will accuse you or another user of promoting discriminatory beliefs, deceiving fans, or similar behaviors. They often suggest that you "consider adding more diverse characters" to "repair the trust you've lost with your audience". (First reported October 2025, Tumblr announcement November 2025)
• Praise and Unsolicited Suggestions Spam: These guest comments will compliment your writing but then offer ridiculous suggestions for how to make your work better. Similar to the harassing spam, they may ask you to add a minority character to your work or threaten to publicly expose you if you don't do what they want. (First reported October 2025)
• Special Character/Keysmash Spam: These comments are usually long and consist entirely of emojis or nonsense, keysmash-style sequences of characters from a variety of non-Latin scripts or languages (e.g., Chinese, Cyrillic, Thai, etc). (First reported November 2025)
• Reporting To Authorities Spam: These guest comments threaten to report you or your work to the authorities or your employers. They also may allege security concerns like your email being compromised or spyware on your computer. (First reported December 2025, Tumblr announcement December 2025)
• Disparaging Spam: These guest comments insult you or your writing, claiming that you "wasted your talents" or "have no life". They may also threaten suicide or tell you to delete your work. (First reported December 2025)
• PowerShell Spam: These comments present you with a piece of code to enter into your computer's terminal/command line. While they claim that the purpose of the code is for your protection or security, the code in these comments would actually delete all documents from your hard drive. (First reported January 2026)
• Doxxing Threat Spam: These guest comments claim that they know where you live, have seen you in person, and/or threaten to meet you face-to-face. They often say that they have or will post your personal information (name, address, etc.) online or that they are stalking you in real life (e.g. "left a gift in a briefcase near your house"). (First reported January 2026, Tumblr announcement January 2026)
• Spam Impersonating OTW Volunteers: These guest comments claim to be AO3/OTW volunteers and say that there has been a data breach or that AO3 and other sites (such as Reddit) have been sending out fraudulent password reset emails. (First reported January 2026, Tumblr announcement February 2026)
• Downtime Spam: These guest comments claim that the March 2026 AO3 downtime was caused by hackers and AO3 has a virus that will destroy your device, and encourage reformatting your device or deleting all your works. (First reported March 2026)
• Suicide Baiting Spam: These guest comments insult your work and say that you should kill yourself. They are often machine-translated into languages unrelated to the work, as well as Morse and binary. (First reported May 2026, Tumblr announcement June 2026)
• Hardcover Book Spam: These guest comments praise you and your work, then ask you to mail a "hardcover copy" to a specific address, usually in Canada, with a promise of payment. (First reported June 2026, Tumblr announcement June 2026)
• Trust & Safety Phishing Comments: These comments claim to be from AO3 Trust & Safety Team telling you that your account has been restricted and you need to click on a link and pay to have your account verified. (First reported July 2026, Tumblr announcement July 2026)

None of the accusations these spam comments make are true. The bots are merely spamming false accusations in order to alarm or harass AO3 users. It is generally safe to ignore these comments once you've removed and/or reported them as outlined below.

What You Can Do

Do not engage in conversation with spam commenters. Do not provide your email or social media contact information to a commenter who asks for it. Scammers try to get you to talk to them privately, because it is often easier to deceive or manipulate people in a one-on-one conversation.

Do not click on any links, run any code commands on your computer, or search out and harass any users named in these comments. Scammers often copy the username of a real AO3 user on their guest comments to make them look more real. Pay attention to the "(Guest)" indicator which will appear next to the name of anyone who comments while not logged in.

For spam comments on your own work, the best way to handle them depends on whether they are from registered accounts or guests. Refer to the instructions below on how to handle Spam from a Guest User or Spam from a Registered Account.

If you see a spambot comment on someone else's work, you can report the comment as spam to Policy & Abuse (even if it's a guest comment) as you would a comment on your own work. You can also let the creator know the comment is from a bot and that they should mark it as spam.

Please don't report comments that have already been deleted. As part of handling a report about spam comments (whether from guests or registered accounts), we will remove other comments made by the same bot. If the comments have been deleted, the bot has already been actioned and no further reports are needed.

Spam from a Guest User

If you receive a spambot comment on your work which is posted by a guest:

1. Go directly to the comment on your work, either by clicking on the link in your email or in your AO3 inbox.
   
   Note: The "Spam" button only appears when viewing a guest comment directly on your work. This is because the AO3 comment inbox is merely a copy of the work's comments—deleting a comment from your AO3 inbox does not delete the comment from the work itself.
2. Click on the "Spam" button to mark the guest comment as spam, remove it from your work, and help train our automated spam-checker to reject similar spam comments in the future.
   
   Note: Marking guest comments as spam does not submit a report to the Policy & Abuse committee, but unless you are receiving dozens of guest spam comments in a short time period, there is no need to submit a separate report.

To prevent future guest spam comments, you may also want to consider disabling anonymous commenting or restricting your work to registered users only.

If you are reporting multiple guest comments, please submit only one report and include all comment links in your report description. (You can get the direct link to a specific comment by selecting the "Thread" button on the comment and copying the URL of that page.)

If you are receiving dozens of guest spam comments in a short time period, we recommend turning on comment moderation and providing us with a link to the unreviewed comments section of the affected work(s) instead of reporting the comments individually.

Spam from a Registered Account

If the spam comment is posted by a registered AO3 account:

1. Select the "Thread" button on the spam comment. This will take you to the specific comment page.
2. Scroll to the bottom of the page and select Policy Questions & Abuse Reports.
3. In the "Brief summary of Terms of Service violation" field, enter "Spambot".
4. In the "Description of the content you are reporting" field, enter "This is a spambot, their username is USERNAME." (replace USERNAME with the account's actual username)
5. Optionally, you may also choose to block or mute the account.

Please don't report multiple spam accounts in one report. Each account is actioned separately and listing more than one account per report delays our response to you.

Closing

In general, please follow internet safety best practices and be cautious of unsolicited advertisements or harassing comments on your work. For some advice on other ways you can protect your AO3 account, take a look at this internet security guidance from our Policy & Abuse volunteers.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.

In the last year, AO3 has seen a rise in "art commission" spambot comments. The bots leaving these comments pretend to be artists who want to make comics or illustrations for a fan's fic. After convincing their targets to contact them off AO3, they scam their targets into paying for that art. Fans have reported that after sending payment, they either received AI-generated art or nothing at all.

AO3 has been working on various methods that we hope will reduce the spam. However, these scammers are persistent and creative about circumventing our protections.

To avoid falling victim to one of these scams, the Policy & Abuse committee recommends:

1. Do not commission art from someone who solicits you by commenting on your work on AO3. Commercial activity is prohibited on AO3. If someone is encouraging behavior that violates our Terms of Service, it’s a good idea to be cautious. They likely do not have your best interests in mind.
2. Do not provide your email or social media contact information to a commenter who asks for it, even if they say they'd just like to discuss your work further. Scammers try to get you to talk to them privately, because it is often easier to deceive or manipulate people in a one-on-one conversation.

Example of this type of scam

This is just one example of how a scammer tries to lure the work creator onto a different platform where they can pressure the creator into commissioning art. These scammers use AI to generate realistic-sounding comments. The comments often contain generic praise or statements that could apply to any work, but sometimes they are extremely lengthy and/or specific. If the creator is suspicious and asks why the scammer wants to move the conversation off-site, they will typically claim that they aren't a scammer and/or that they can explain things better in private.

However, unlike a regular user, a scammer will always do at least one of two things:

1. They will ask you to commission art from them, or
2. They will share their contact information and/or ask for your information (such as an email address or username on a site that supports private messaging, like Instagram or Discord)

If you suspect that you've received a spam comment on your work, don't reply and especially do not provide them with your contact information. Just report the comment to Policy & Abuse so that we can take care of it.

What to do if you encounter this scam

If you receive a scam comment from a guest, you can press the "Spam" button on the comment. This helps train our automated spam-checker to better detect this type of behavior.

If you encounter a scammer that has a registered account, or if you encounter a guest posting scam comments on someone else's work, please report them to the Policy & Abuse committee. To do so:

1. Select the "Thread" button on the scammer's comment. This will take you to the specific comment page.
2. Scroll to the bottom of the page and select Policy Questions & Abuse Reports.
3. In the "Brief summary of Terms of Service violation" field, enter "Spambot".
4. In the "Description of the content you are reporting" field, enter "This is a spambot, their username is USERNAME."

Reporting in this fashion helps us auto-sort your report so that it can be handled as soon as a Policy & Abuse volunteer is available. To help us address reports about these types of bots as fast as possible, please only submit one report per account, and don't include multiple accounts in the same report.

If you encounter a scam commenter on someone else's work, you can let the work creator know the commenter is likely a bot and link them to this news post.

We also encourage you to share this post on social media and help spread the word about how to protect yourself from scammers and reduce spam on AO3.

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we're posting a weekly spotlight series about the TOS and our policies. We'll also be reading comments and answering questions on this and our other spotlight posts.

For our last post in this series, we'll be talking about our non-commercialization policy. AO3 doesn't allow users to engage in commercial promotion of any type, which includes everything from paywalls to tip jars, and quite a lot in between. In this post, we'll discuss why AO3 doesn't allow commercialization, what kinds of activities are considered to be commercial promotion, and what to do if you see commercial promotion on AO3.

Don't go looking for things to report.

Please do not start searching for works to report after reading this post. We know that commercial promotion frequently appears on AO3. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

What is commercial promotion?

Commercial promotion covers all references or links to commercial sites, monetized features of non-commercial sites, and anything else that makes it clear someone is asking for or has received financial contributions.

On AO3, you can't encourage anyone to give other people money, or talk about anyone having given people money in the past. This applies whether you are promoting yourself or a friend, or even if you're collecting donations for other people or causes. If there is money changing hands, then it likely violates AO3's TOS.

AO3 is a non-commercial space.

AO3 was created and is managed by the Organization for Transformative Works (OTW), a nonprofit organization committed to the defense and protection of fanworks from commercial exploitation and legal challenges. The OTW is entirely staffed by unpaid volunteers, and AO3 is itself entirely non-commercial. No one involved in AO3's creation or management profits from it. The site is made available free of charge to all fans who wish to share their works with other fans and fan communities.

We understand that many people today choose to monetize their creative activities. However, in order to keep AO3 as the non-commercial space it was designed to be, users are not permitted to engage in any commercial activity on the site.

When you use AO3, you agree to follow our Terms of Service, which includes the non-commercialization policy. This applies to all parts of the site, whether you're posting a work based on an existing source or creating content entirely original to you.

AO3's non-commercialization policy applies to the entire site.

Real-world commercialization is banned everywhere on AO3. This includes:

• Profile pages
• Usernames, pseuds, and pseud descriptions
• Works (including all tags, beginning or end notes, chapter notes, summaries, and titles)
• Series (including titles, summaries, descriptions, and notes)
• Bookmarks (including tags and notes)
• Comments
• Prompt memes, gift exchanges, and other collections
• Any other part of AO3

It's okay for fictional characters in fanworks to talk about fictional monetization. For example, it's fine if a character has a fictional OnlyFans or Patreon within the story, as long as that commercial reference doesn't direct the reader to a real-world OnlyFans or Patreon account for the work creator or anyone else.

What are some examples of commercial activities?

There is a wide variety of things that are not allowed under AO3's non-commercialization rules.

Links or references to any commercial site or service. A "commercial site" is any site whose primary purpose is to facilitate the transfer of money. This includes, but is not limited to:

• Storefronts like Amazon or Etsy
• Crowd fundraisers like Kickstarter or GoFundMe​​
• Tip jars or membership subscriptions like Ko-Fi or Patreon
• ​​Payment platforms like PayPal or Venmo

Links or references to the monetized features of non-commercial sites. This covers any site that has features you can enable or opt-in to earn revenue, but the primary purpose of the site is social media, sharing artwork, or anything else that isn't inherently payment-focused. This includes, but is not limited to:

• Paywalls or early-access content like Wattpad Paid Stories or Webtoon Canvas
• Storefronts like DeviantArt Shop or Instagram Shop
• Tip jars or membership subscriptions like TikTok Donation Stickers or Twitch Prime

Previews and other promotions for paid content. This covers situations like excerpts or teasers shared in an attempt to entice people to purchase a book or become a paying subscriber. It also includes references to paywalled or early-access content (e.g. "Patreon subscribers get the new chapter one week early before I post it on AO3").

Advertising content or services involving an exchange of money, such as buying merchandise, collecting donations, offering paid commissions, or selling published works.

Any other language which one might interpret as requesting or having requested financial contributions, whether for yourself or others. This covers indirect references, euphemisms, or other language intended to get around the TOS. Some examples of this include:

• Thanks for the coffee!
• My ☕ username is the same as my username here
• This chapter is brought to you by my patrons
• You know where to find me if you want early or bonus chapters
• Check out my Twitter to learn how you can donate to me since I'm not allowed to discuss it here
• If you want to hear more about my ideas, talk about fandom, or find more of my stuff for a coin, visit my Tumblr

Solicitation is not allowed, whether it's for yourself or on behalf of someone else.

Commercial activity is not permitted on AO3. It doesn't matter if you're promoting yourself or a friend, or even if you're collecting donations for other people or causes.

This means that if you paid an artist to create artwork for your fanfic, you're not allowed to mention that they have a Patreon or use any other language that suggests people should also commission or donate to them. If you like a book by a particular author, you are certainly welcome to gush about what a great book it is, but you can't link to the Amazon page where it's for sale or encourage others to buy it.

What is the difference between a commercial site and a non-commercial site that has monetization features?

As mentioned above, a commercial site is a platform that is first and foremost intended to facilitate the exchange of money. For example, while you can use Ko-Fi as a blog, the site's primary purpose is to encourage people to give each other money. Ko-Fi's social features are secondary to its purpose as a donation and paid membership platform. This means you cannot link to or mention your or anyone else's actual Ko-Fi on AO3 whatsoever.

An example of a non-commercial site that has monetization features is DeviantArt, an art gallery that is mainly intended as a place to share artworks. DeviantArt also allows its users to opt-in to additional monetization features, such as the DeviantArt Shop. Because DeviantArt's paid features are both optional and not the primary reason people use the site, you can talk about or link to DeviantArt on AO3 – as long as you aren't directing anyone to a paywalled post or referencing DeviantArt's paid features in any way.

Can I link or mention a social media site where I talk about making money or collecting donations?

You're allowed to link or mention social media like Tumblr or personal websites like WordPress, even if you sometimes post about commercial activities on those sites. However, you cannot reference commercial promotion on AO3 itself, nor may you link, mention, or give instructions for finding an account, page, or post that is solely promoting paid content.

Statements such as "Follow me on social media" or "Check out my Linktree" are fine. Directing people to an Amazon author page or to the Ko-fi link in your Twitter bio would not be allowed. This includes things like "Check out my Linktree to learn how you can support me" in cases where you are clearly referring to monetary support.

Can I post a fanwork created for a charity drive or for-profit zine?

While you cannot promote, solicit, or otherwise ask for donations on AO3, you are allowed to add your work to a collection or otherwise briefly mention why you created a fanwork, as long as you do so in a non-commercial manner. This means you can say "This was created for [Event]" or "Originally Written for [Name of Person/Zine]" as long as you do not directly link to a donation page or ask others to donate to them.

Keep in mind we also do not permit mentions of monetary transactions, regardless of when they occurred. A note such as "This was a $100 bid for Fandom Trumps Hate" would still be considered commercialization.

I've seen authors say their works are commissions. Is this allowed?

You are allowed to gift your work to someone else or otherwise briefly mention why you created a fanwork, as long as you do so in a non-commercial manner. Because not all commissioned fanworks were created for pay, we do permit usage of the word "commission" as long as there is no indication that a monetary transaction was involved in the creation of the work or that you are available to create other paid commissions.

For example, phrasing like "This is a commission for X" is acceptable, but "Commission for my Gold Tier Patron, Julie" or "My client agreed to let me post the first chapter of their commission" isn't. The context makes it clear that both "patron" and "client" are references to a paying sponsor.

I've seen others ask for donations or advertise paid commissions. Why can't I?

As our TOS FAQ explains, we don't review content until it's reported to us. You may have seen somebody else mentioning their paywalled content or otherwise engaging in commercial activities on AO3, but that doesn't mean that it's allowed. All it means is that nobody has reported that content to us yet, or that we haven't finished processing the report.

What will happen if I get reported for commercial promotion?

First, we'll review the reported work to confirm that you violated our TOS by engaging in commercial activities on AO3. If we determine that you did, we'll send you an email telling you to remove the violating material.

If your work can be edited to fix the issue, you'll be asked to edit the work. Your work may be hidden from other users until you do. If you choose not to edit the work, or if your work cannot be edited into compliance with the TOS, it will be deleted.

PAC will only ever contact you by email, and only after we've determined that your work violates our Terms of Service. We will never comment on your work or contact you through social media. Please make sure to keep your account's email address up to date and check it regularly (including your spam folder), or else you may miss our warning email.

If you repeatedly post works that violate our commercial promotion policies, you may be temporarily suspended. Continuing to violate the TOS will result in your being permanently banned from AO3. You can learn more about warnings and suspensions in our TOS FAQ.

What should I do if I encounter commercial activity on AO3?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can report the work to us.

What about spam comments?

The best way to deal with spam comments, commercial or otherwise, depends on whether the comments are from registered accounts or guests.

How do I report commercial activity?

Although we ask that you do not deliberately seek out commercial promotion to report, if you come across commercial activity while browsing, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3.

Please don't report more than one user at a time or submit multiple reports about the same user. When reporting multiple works by the same user, please submit only one report with links to each work you're reporting, so that all information about that user is in the same place.

Please tell us exactly where in the work the commercialization is. The best way to do this is to give us a description or short quote that we can search for in order to immediately find the content. If you are reporting multiple works by the same creator, please group all the works into one report and provide this information for each work.

For example, a report of commercial promotion might look like this:

Link to the page you are reporting: https://ao3-rd-3.onrender.com/works/00000000

Brief summary of Terms of Service violation: Commercial promotion

Description of the content you are reporting:
This work by USERNAME advertises a ko-fi in the end notes of chapter 3.

If you are reporting additional works, please include all relevant links and other information in your report description:

Description of the content you are reporting:
This work by USERNAME advertises a ko-fi in the end notes of chapter 3.

Some of their other works also contain commercial promotion:

https://ao3-rd-3.onrender.com/works/23456789 encourages readers to purchase their book on Amazon: "If you're curious what else I've been working on or want to support me elsewhere, check out my new short story on Kindle Unlimited!"

https://ao3-rd-3.onrender.com/works/34567890 contains an embedded image with a Patreon watermark. Underneath, the sentence "If you want more like this, click here" takes you to their commissions price sheet.

You can add more details if you like, but this example provides the basic information we need:

• Who posted the commercial promotion: Tell us their username or if the work is anonymous or orphaned.
• Where we can find the work(s): Enter one URL in the "Link to the page you are reporting" field, and (if applicable) include links to any other violating works in the description of your report.
• What violates the TOS: Explain why you think commercial promotion has occurred, for example by including a quote and/or providing context for a comment exchange. A brief description of the situation is fine; you don't need to be very detailed or quote an entire TOS or FAQ section.

You'll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same work. While PAC investigates every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about commercial promotion?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you've found commercial promotion on AO3, or if you want to know whether a particular work contains commercial promotion, please report the work to us as described above. For more information, you can read our TOS FAQ on Commercial Promotion.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we're posting a weekly spotlight series about the TOS and our policies. We'll also be reading comments and answering questions on this and our other spotlight posts.

In today's post, we'll discuss two categories of TOS violations that have a lot of overlap: plagiarism and copyright infringement.

Don't go looking for things to report.

Please do not start searching for plagiarized or infringing works to report after reading this post. We know that plagiarism and copyright infringement can happen on AO3, as on any site. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

AO3 is for transformative fanworks

AO3 is an archive for fanfiction and other transformative fanworks. Transforming a work means that you are adding a new expression, different purpose, or alternate perspective to the source work. A transformative fanwork doesn't copy the original source; instead, it uses the characters, setting, or other inspiration from an existing work to make a new, distinct creative work.

Transformative fanworks can be posted without requiring permission from the creator of the original work. When considering whether a work is transformative, we apply the same standards to fanworks as to professional works. This means that a fanwork based on another fanwork is allowed, just as much as a fanwork of a professionally published novel is. You are allowed to write a story or create fanart about someone else's original character, or to use the same general ideas, tropes, or story structures as someone else. Two works can share the same premise, setting, and plot while still being transformative.

However, replacing names, swapping out words for their synonyms, or making other superficial changes to the source work is not considered transformative. A transformative work needs to have a large amount of creative expression that is original to you.

Plagiarism vs copyright infringement

Plagiarism occurs when a person reproduces large portions of someone else's work or very heavily bases their work on another without adequately transforming it, and doesn't credit the source. This lack of credit makes it appear as though the copied work is entirely their own original, unique idea and expression.

To avoid potential issues of plagiarism, you can cite your source by linking back to the original, for example by using AO3's Inspired By feature. However, just because you provided credit doesn't mean you're automatically okay: your work may still be in violation of our other policies, such as copyright infringement.

Copyright infringement occurs when a work reproduces large portions of a different work, whether verbatim or with very little alteration (i.e. not in a transformative manner), without the authorization of the copyright owner. Even if you credit the source, reproducing too much of someone else's content is still a violation of their copyright unless you have the copyright owner's explicit permission.

Permission is not required for short quotations. Use a limited amount that's reasonable for your purpose, such as:

• 2-3 lines of lyrics per song
• 2-3 lines of text per short chapter of a novel
• 10 minutes of screentime per TV episode or movie

If you want to include longer excerpts, you will need the copyright owner's permission. This applies regardless of whether the original work is a fanwork or published professionally.

Permission to reuse fanworks

Some fan creators will give other people permission to reproduce larger portions of their works than would ordinarily be permitted by copyright laws alone. They may do this by granting blanket permissions for particular uses (for example, "Anyone can translate or podfic my work, but I don't allow reposts or nameswaps") or by applying an official license (such as Creative Commons) to the work, which grants various permissions based on terms specific to the exact license.

If permission to reproduce the work is accompanied by specific terms, then you must follow those terms. For example, a creator may say, "You can translate my fic so long as you link back to the original." In that case, if you post your translation without providing a link, you’re violating our policies. In order for your translation to be allowed, you would need to include the link as requested.

Common types of infringement

Unauthorized reposts

If you want to upload someone else's work to AO3, you need to have their permission. It doesn't matter how difficult it might be to contact them: even if the original creator posted their work a decade ago and then vanished from the internet, they still have copyright over their own work.

If you can't get permission but you still want to save or share somebody else's fanwork from another site, you can create an external bookmark that links to the work on that site, and add tags and notes to your bookmark so that other AO3 users can also find and enjoy the work.

Minor edits and adaptations

Making minor changes to a work doesn't make the work original to you. If you've only changed the characters' names and/or pronouns, or corrected the original author's grammar or formatting, that isn't transformative. You'll need the creator's permission to adapt their work like this and post it to AO3.

Too many quotes: transcripts and "character reaction" works

Transcripts (whether of TV episodes, movies, plays, video games, etc.) are protected by copyright. You cannot repost canon material on AO3, as this is typically a violation of our copyright infringement and/or non-fanwork policies.

If you're creating a fanwork where the characters are reacting to another piece of media (such as by reading or watching the book, show, or movie that they were originally from), then that is allowed if and only if you don't include too many quotes from the original source. Even if the lines of the original book or script are broken up by the characters' reactions, you still can't reproduce more than a few lines of the original text. If you'd like to post a work in which characters read or watch another work, then we suggest heavily reducing the number and length of your quotes, and/or briefly summarizing the events they're reacting to instead of quoting directly from the original work.

Songfics with lyrics

Song lyrics are protected by copyright, which means you can't reproduce large portions of lyrics without permission. This includes both songfics where the lyrics are interspersed throughout the story text and fics with characters singing songs as part of their dialogue. If the part of the song you want to highlight is more than a few lines, we suggest instead linking to a licensed source, such as the artist's official YouTube channel.

Embedded artwork

Copyright doesn't just apply to written text, but to all types of creative work regardless of the medium. In order to embed or upload someone else's images, audio, or videos onto your AO3 account, you must have the original creator's permission and credit them appropriately.

If you don't have permission, or don't know how to credit the original creator, then we suggest instead using HTML or AO3's Inspired By feature to link directly to the creator's own original post.

Unauthorized podfics & translations

If you want to podfic or translate someone else's work, you need their permission to do so. According to United States law, audio recordings and translations are considered derivative, not transformative. AO3 welcomes fan-podficcers and fan-translators. However, your content must comply with U.S. law for us to be able to host it, which means that you must have the permission of the copyright owner in order to post your podfic or translation on AO3.

Infringing on orphaned works

Orphaning a work does not mean the original creator is giving up their copyright, even if their username is no longer displayed on the work. The only thing the original creator did when orphaning their work was agree to transfer that specific copy of their work to AO3's orphan_account.

Just like with any other work, if you wish to podfic or translate an orphaned work, you will need permission from the original creator. This can come in the form of an author's note on the work or an additional tag such as Podfic Welcome. If the work contains no such statement, and you don't know or can't find the original creator to ask for permission, then you may not podfic or translate the work.

If you plan on orphaning your works and you want to ensure that other users can continue to adapt or translate them, consider adding a permission statement to each of your works before orphaning them.

Posting public domain works

While public domain works are no longer protected by copyright, reposting someone else's work is not transformative. AO3 is an archive for fanworks and for original works created in a fannish context. Therefore, you cannot upload other people's public domain works to AO3.

However, as public domain works are not protected by copyright, some types of derivative works (such as your own translation) may be posted on AO3.

I've seen others post plagiarized or infringing works. Why can't I?

As our TOS FAQ explains, we don't review content until it's reported to us. You may have seen somebody else posting an unauthorized translation or public domain work on AO3, but that doesn't mean that it's allowed. All it means is that nobody has reported that work to us yet, or that we haven't finished processing the report.

What will happen if I get reported for plagiarism or copyright infringement?

First, we'll review the reported work and any provided sources to confirm whether or not your work contains plagiarized or infringing material. If we determine that your work is in violation, we'll send you an email telling you to remove the violating material.

If your work can be edited to fix the issue, you'll be asked to edit the work. Your work may be hidden from other users until you do. If you choose not to edit the work, or if your work cannot be edited into compliance with the TOS, it will be deleted.

PAC will only ever contact you by email, and only after we've determined that your work violates our Terms of Service. We will never comment on your work or contact you through social media. Please make sure to keep your account's email address up to date and check it regularly (including your spam folder), or else you may miss our warning email.

If you repeatedly post works that violate our copyright and/or plagiarism policies, you may be temporarily suspended. Continuing to violate the TOS will result in you being permanently banned from AO3. You can learn more about warnings and suspensions in our TOS FAQ.

What should I do if I encounter a work that contains plagiarized or infringing material?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can report the work to us.

How do I report a work for plagiarism or copyright infringement?

Although we ask that you do not deliberately seek out violating works to report, if you encounter one while browsing, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3. The copyright owner or their authorized legal representative can also file a DMCA claim, as explained on our DMCA Policy page.

In order for us to uphold a complaint, we need you to provide us with specific information about exactly what was copied and from where. Without these details, we may not be able to action your report.

If the work in question is no longer available online, but you have a copy of the work (such as a PDF), please say so. We may ask you to provide that copy to help us in our investigation.

Please be specific in your report. If you send us a link to an 80,000-word fic and say only "This work rips off mine!" without providing any details (such as a link to your own work), that's not enough information for us to act on. We will need to email you back asking for more information, and if you don't provide us with that information, we won't be able to investigate. If we can't verify the infringement for ourselves, then we won't take any action.

Please don't report more than one user at a time or submit multiple reports about the same user. When reporting multiple works by the same user, please submit only one report with links to each work you're reporting (correctly matched up with the original source), so that all information about that user is in the same place.

If you give us a link to one work and say "All of their other works look like plagiarism too!" without giving us details about those works or their sources, that isn't enough information for us to act on those other works. If you give us a jumbled or incomplete list of links, or if you report each work by the same user separately, this makes our volunteers' work much harder.

For example, a report might look like this:

Link to the page you are reporting: https://ao3-rd-3.onrender.com/works/00000000

Brief summary of Terms of Service violation: Plagiarism

Description of the content you are reporting:
This work by Ernie is plagiarized from Bert's work, "Fifty Shades of Oatmeal": https://ao3-rd-3.onrender.com/works/23456789

The entire thing is copied, Ernie just swapped out Elmo's name for the Count's and changed some of the colors.

If you are reporting additional works, please include all relevant links and other information in your report description:

Brief summary of Terms of Service violation: Plagiarism and Copyright Infringement

Description of the content you are reporting:
This work by Ernie is plagiarized from Bert's work, "Fifty Shades of Oatmeal": https://ao3-rd-3.onrender.com/works/23456789

The entire thing is copied, Ernie just swapped out Elmo's name for the Count's and changed some of the colors.

Another of Ernie's works plagiarizes from Big Bird's "If You Give a Monster a Cookie":

Ernie's work (plagiarism): https://ao3-rd-3.onrender.com/works/34567890
Big Bird took down their fic when they published it as an original story. Here's a link to the published version: https://www.monstercookiebooks.com/books/9876543210/if-you-give-a-monster-a-cookie

I also have a downloaded copy of the original fic I can give you if you need it.

The plagiarized section is in Ernie's chapter 2, where it starts at "Every time that Cookie Monster goes to the store, he can't resist going and picking up more chocolate chip cookies."

This is plagiarizing chapter 3 of Big Bird's work, which starts, "Whenever Cookie Monster went to the store, he couldn't resist buying more chocolate chip cookies."

The entire rest of the fic is like that, with only minor edits to each sentence. It's over ten thousand words long!

Finally, this other work contains the full lyrics of "I Love Trash" as sung by Oscar the Grouch: https://ao3-rd-3.onrender.com/works/45678901

Here's a link to the song on YouTube: https://www.youtube.com/watch?v=zJekxVILnhw

You can add more details if you like, but this example provides the basic information we need:

• Who posted the violating work(s): Tell us their username or if the work is anonymous or orphaned.
• Where we can find the violating work(s): Enter one URL in the "Link to the page you are reporting" field, and (if applicable) include links to any other violating works in the description of your report.
• Where we can find the original source material: Include a link to each original source and tell us what parts of the source were copied, for example by including chapter numbers or quotes from the relevant scenes.
• What violates the TOS: Explain why you think each work you're reporting is infringing and match each reported work to its original source. A set of links and a brief description of each work is fine; you don't need to be very detailed or quote an entire page.

You'll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same incident. While PAC investigates every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about plagiarism and copyright infringement?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you've found a plagiarized or infringing work, or if you want to know whether a particular work qualifies as plagiarism and/or copyright infringement, please report the work to us as described above. For more information, you can read our TOS FAQ on Copyright Infringement and Plagiarism.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

ETA: Edited to improve wording

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we're posting a weekly spotlight series about the TOS and our policies. We'll also be reading comments and answering questions on this and our other spotlight posts.

Today's post from the Policy & Abuse committee is about harassment. As stated in Section II.H of our Terms of Service, "Harassment is any behavior that produces a generally hostile environment for its target. Examples include bullying, threats, and personal attacks by or towards individuals or groups of people."

Harassment is not tolerated on AO3 in any form—regardless of whether it occurs in works, tags, comments, usernames, pseuds, profiles, icons, or any other type of content.

What qualifies as harassment?

Threats and insults

When directed towards other users, threats and insults constitute harassment, and we will act on them if reported to us. This includes when phrases such as "X/Y shippers are creeps" are present in work tags or summaries.

Severe harassment

Some harassment is severe enough that it creates a hostile environment not just for the target, but for anyone who witnesses it. Engaging in severe harassment will result in harsher penalties.

The following are all considered to be severe harassment when directed towards other AO3 users:

• Death threats/wishes
• Threats of violence/bodily harm
• Slurs directed at other users
• Self-harm/suicide baiting (suggesting that someone should hurt or kill themselves)
• Doxxing or threats of doxxing (connecting a user's non-public, personally identifying information to their online handle)

Anyone can report these, whether or not they're the primary victim. PAC will remove all instances of severe harassment that are reported to us.

Call-out posts

A call-out is when someone posts a work (or a chapter or author's note) that criticizes someone for their behavior in an attempt to draw public attention to that person.

We consider call-out posts to be harassment. If you see a call-out post, whether or not it is targeted at you, you can report it to us. Call-out posts are not allowed, regardless of what the target of the call-out has done.

If you encounter someone who has violated the AO3 Terms of Service, please don't post a call-out and violate the TOS yourself. Instead, we recommend that you submit an Abuse report and use AO3's blocking and muting features to avoid that person.

Interacting after being blocked

A blocked user is expected to cease all interaction with the person who blocked them. We consider attempting to "get around" a block to be harassment. If you've blocked someone and think they're evading your block, you can report them to us.

What does not qualify as harassment?

Offensive content

What's considered offensive and unacceptable varies from person to person. AO3 hosts a wide range of content that many users find to be offensive, and in our last post, we discussed some of the ways you can avoid such content.

You may not leave comments attacking the creator of a work you find offensive.

You can mute the user so you don't see any of their works, bookmarks, or comments. If you want to make sure they can't communicate with you, you should also block them.

Criticism

We don't consider criticism of a work, constructive or otherwise, to be harassment in and of itself. Offensive opinions and comments that aren't direct personal attacks are also not harassment (for example, expressing negative views about celebrities or the content of a work).

If somebody says your work is bad, that's an opinion about your work, not a personal attack against you. However, repeatedly leaving negative comments in a short period of time, pressuring you to delete your work, or encouraging others to engage in similar behavior could be considered harassment depending on the circumstances.

Arguments

People are allowed to argue or disagree with your opinions. Argument is not harassment, and PAC will not intervene simply because users are arguing with or being rude to each other. If someone in the argument is using personal attacks, you can report them to us, but in general, PAC does not mediate disputes between users. If you want to end an argument, you should tell that person you will not respond further; if necessary, you can also block them.

If you are a bystander witnessing an argument rather than one of the participants, then we are unlikely to uphold your complaint unless someone is engaging in severe harassment. When it comes to rude or moderately antagonistic comment exchanges, we rarely act on third-party reports.

Do Not Interact (DNI) requests

Requesting that someone does not interact with you is not harassment in itself, but it may be considered harassment if paired with an insult or threat (for example, "DNI you weirdos who ship this" or "no incest lovers allowed I will stomp you all to death with my hooves").

If you want someone to stop interacting with you, you should block them. If you never want to encounter them again, you can also mute them.

What should I do if I'm getting harassing comments on my works?

PAC tries to prioritize urgent reports such as harassment, but there will always be a delay while we investigate and take action. We recommend that you immediately block any registered user who harasses you. We also recommend that you enable one or more of the Privacy options on your work(s) while you wait for our response.

To edit the Privacy options on your work, select the "Edit" button, then navigate to the "Privacy" section. If you want to edit the Privacy options on multiple works at once, you can do so easily using our "Edit Multiple Works" tool.

Changing your Privacy options does not have to be permanent; you can update them at any time. If you're being harassed, we recommend changing your Privacy options at least for a short period of time.

The options available to you in the Privacy section are as follows:

Only show your work to registered users

You can use this feature to lock your work so only registered users can see it. If you are the victim of a mass-harassment campaign, this will prevent "drive-by" comments from guest users. Works that have been restricted to AO3 users will have a blue lock symbol displayed next to the title and are not accessible to guest users.

Enable comment moderation

Comment moderation prevents any new comments (from both registered users and guests) from being publicly displayed on your work until you approve them. If you don't approve a particular comment, then it will not be made public. PAC volunteers are able to see unreviewed/unapproved comments, so you can report a harassing comment without marking it as approved.

If you're being harassed by a guest user but don't want to disable anonymous comments entirely, you can use comment moderation to prevent harassing guest comments from appearing on your work.

If the harassment was posted by a registered user, comment moderation can help too. It not only prevents their comments from being shown to others, but also makes it easier for us to investigate, as long as you leave their comments unapproved and don't delete them yourself.

Who can comment on this work

There are three comment settings:

1. Registered users and guests can comment: Anyone can comment, including guests. (Note: If your work is restricted to registered users, guest users won't be able to access it and therefore cannot comment even if this option is enabled.)
2. Only registered users can comment: This is the default option. Only logged-in users can comment on your work, while guests and logged-out users cannot.
3. No one can comment: This will disable all new comments on your work, regardless of whether the user is logged in or a guest.

Changing these settings will not affect any existing comments.

Archive locking, comment moderation, and comment restriction can all be used in conjunction with each other. For example, you can enable comment moderation and set your work to only allow registered users to comment at the same time. This means you won't receive any guest comments at all, and comments from registered users will have to be manually approved.

What should I do if I encounter harassing content on AO3?

You can report harassment through the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3. If you wish to avoid future contact from a registered user, we recommend blocking and muting them.

If the harassing content has been deleted, we generally won't be able to investigate unless you're able to provide screenshots or other copies of the harassing content. While it's not possible to upload images to our reporting form, you can include links to images hosted on third-party sites in your report description. You can also specify in your report that you saved copies of the harassment, which we may ask you to provide in our initial response to your report.

How do I report harassing comments?

Comments can be reported through the Policy Questions & Abuse Reports form like all other content on AO3. You can get the direct link to a specific comment by selecting the "Thread" button on the comment and copying the URL of that page, or by clicking on the link in your email or AO3 inbox.

If you're reporting moderated comments, you don't have to approve the comments or link every single comment in your report—just give us the link to your work's unreviewed comments page, and specify which comment(s) you're reporting (if you have a lot of unapproved comments).

Please don't submit multiple reports about the same user. When reporting multiple works or comments by the same user, please submit only one report with links to everything you're reporting, so that all information about that user is in the same place. If the harassment is ongoing, you can turn on comment moderation—if you mention that you've done so and link your work's unreviewed comments page in your report, we'll check that page for any new harassing comments submitted, without you needing to file an additional report.

For example, a report of a harassing comment might look like this:

Link to the page you are reporting: https://ao3-rd-3.onrender.com/comments/000000000

Brief summary of Terms of Service violation: Harassment

Description of the content you are reporting:
USERNAME went on a slur-filled rant in this comment on my work.

If you are reporting additional comments, please include all relevant links and other information in your report description:

Brief summary of Terms of Service violation: Harassment (repeated nasty comments and block evasion)

Description of the content you are reporting:
USERNAME went on a slur-filled rant in this comment on my work.

After I froze the thread, they commented with more slurs and insults here: https://ao3-rd-3.onrender.com/works/1234/comments/123456789

I blocked them and turned on comment moderation but then they commented again as a guest: https://ao3-rd-3.onrender.com/ works/1234/comments/234567890

I have screenshots and copies of the email notifications if you need them.

A report of a harassing work might look like this:

Link to the page you are reporting: https://ao3-rd-3.onrender.com/works/00000000

Brief summary of Terms of Service violation: Harassment in tags and notes

Description of the content you are reporting:
USERNAME has a harassing tag: "go away x/y freaks or i'll call the cops"

And in the end notes they have more harassment: "incest lovers do not comment or I will slice your toes off"

If you are reporting additional works or comments that are part of the same incident, please include all relevant links and other information in your report description:

Description of the content you are reporting:
USERNAME has a harassing tag: "go away x/y freaks or i'll call the cops"

And in the end notes they have more harassment: "incest lovers do not comment or I will slice your toes off"

One of their other works (https://ao3-rd-3.onrender.com/works/23456789) also has harassment and I think is not a fanwork? It's a long rant about why x/y shippers are idiots.

The comments of this work are full of harassment, mostly by guests, but the creator calls a bunch of people pedophiles in these threads:
https://ao3-rd-3.onrender.com/comments/123456789
https://ao3-rd-3.onrender.com/comments/234567890

In the second thread linked above, there's also a "kys" (kill yourself) comment by USERNAME2, which the creator responds to with "u first".

You can add more details if you like, but these examples provide the basic information we need:

• Who posted the harassing content: Tell us their username(s) or if the comment(s) or work(s) are anonymous or orphaned.
• Where we can find the harassing content: Enter one URL in the "Link to the page you are reporting" field, and (if applicable) include links to any other violating works or comment threads in the description of your report.
• What violates the TOS: Explain why you think harassment has occurred, for example by including a quote and/or providing context for a comment exchange. A brief description of the situation is fine; you don't need to be very detailed or quote an entire TOS or FAQ section.

You'll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same incident. While PAC investigates every report we receive, it can take several months for us to process a report.

What if I have more questions about harassment?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you are being harassed, think you've found harassing content, or if you want to know whether a particular work or comment qualifies as harassment, please report the work(s) or comment(s) to us as described above. For more information, you can read our TOS FAQ on harassment.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we're posting a weekly spotlight series about the TOS and our policies. We'll also be reading comments and answering questions on this and our other spotlight posts.

Over 15% of all complaints that PAC receives each year are about content that users consider offensive but does not violate the AO3 Terms of Service. This includes, but is not limited to:

• Fictional depictions of societally taboo topics, immoral behaviors, or crimes (such as bestiality, child sexual abuse, incest, and rape)
• Fiction that contains or promotes offensive and/or oppressive viewpoints
• RPF (real person fiction) that contains explicit content or portrays people in a negative light
• Explicit fanworks for canons whose creators have said they dislike explicit content

Offensive fanworks are not against the AO3 Terms of Service, and PAC will not remove fanworks simply for being offensive.

AO3 is a home for all fanworks

AO3 operates under the principle of maximum inclusiveness of fanwork content. We will not make moral judgements about a work: if it's a legal fanwork that does not violate any of our policies, we will not remove it from AO3.

Don't report works for being objectionable or offensive. If you wish to avoid certain content when browsing AO3, you can use the tools discussed below.

Why does AO3 allow fanworks about content that is illegal where I live?

There is a difference between fictional content about acts that would be illegal if performed in real life, and content that is itself illegal to post or access in a particular jurisdiction.

AO3's Terms of Service are designed to comply with United States law (specifically, the laws of Manhattan, New York). It is legal in the U.S. to create and share fictional content about murder, theft, assault, or other such crimes. It is also generally legal in the U.S. to create and share fictional content about topics such as bestiality, child sexual abuse, incest, and rape. AO3 allows users to post and access fiction about all of these topics.

In accordance with U.S. law, AO3 prohibits sexually explicit photographs, videos, and other photorealistic images of children (also known as Child Sexual Abuse Material, or CSAM). This includes embedded images, links, and any attempts to solicit, distribute, or otherwise obtain or provide access to such material – whether in a work, comment, or anywhere else on AO3.

However, stories and non-photorealistic artwork (such as drawings or cartoons) that depict sexual activity involving characters under the age of eighteen are allowed, provided that the works are properly rated and warned. Even if the work features real people, fiction about real people is still fiction, and therefore it is allowed on AO3.

Depending on where you live, the laws that apply to you may be more restrictive than the ones described above. All users are responsible for following the laws that apply to them. If certain content that is allowed on AO3 is illegal for you to access, then you should ensure you carefully observe all relevant ratings and warnings, and use the tools discussed below to avoid accessing any work that indicates it may contain such content.

What about other explicit or suggestive photorealistic images?

Photographic or photorealistic images of humans may not be used to illustrate works featuring underage sexual content (regardless of whether the images themselves are explicit in nature). This includes (but is not limited to) photographs of children, porn gifs, photo manipulations, computer-generated or "AI" images, and other linked or embedded images that could potentially be mistaken for photographs of real humans.

If the work appears to feature underage sexual content (as indicated by the "Underage Sex" Archive warning or other contextual markers present in the work's tags, notes, or text), then PAC may require all photographic or photorealistic images of humans, regardless of their perceived age, to be removed from the work.

If your work does not feature underage sexual content, or if the images are not photorealistic, then please read our Terms of Service FAQ: Can I embed explicit images in my fanworks?

Real Person Fiction (RPF)

RPF is fiction based on real people. AO3 does not consider RPF works (in and of themselves) to be harassment of the individuals represented in the works. RPF works are allowed on AO3, even if they contain explicit content, negatively portray their subjects, or are about individuals who are minors and/or not well-known.

However, harassment and doxxing are both prohibited under our Terms of Service. This means that we do not allow works that advocate for actual harm to be done to a real person, nor do we allow works that disclose non-public information about a real person.

Fiction is generally permitted to include public information such as age, profession, city of residence, media or "stage" names, and publicly known legal names. However, if someone uses a pseudonym that they have not linked to their legal name, you're not allowed to post content that links the two.

What if the creator of a canon states that they dislike explicit fanworks or don't want people to create fanworks based on them or their work?

Creators are free to dislike fanworks, explicit or otherwise. However, AO3 holds the position that transformative fanworks are legal under United States law, and do not require the original creator's permission to be posted. If a fanwork does not otherwise violate our Terms of Service, then that fanwork is allowed on AO3.

I don't want to see certain kinds of works. How can I avoid them?

We want all our users to enjoy using AO3, but each user is responsible for their own browsing experience. If you encounter a work that upsets you, please leave the work, and use the following tools to manage your browsing experience and avoid seeing it again.

Tag exclusion filters

AO3 has an extensive tagging system. Tags can be used to filter out works when you are browsing a tag or using the work search function.

As discussed in our post about ratings and warnings, all works containing adult content must be rated "Mature", "Explicit", or "Not Rated". If you don't want to encounter adult content, you can use filters to exclude all works with these ratings. If you encounter a work rated "General" or "Teen" that has explicit content, you can report it to PAC.

In addition, all fanworks that contain underage sexual activity, rape/non-consensual sex, graphic violence, or major character death must be labeled with the respective Archive warning or the "Creator Chose Not To Use Archive Warnings" label. Much like ratings, you can use filters to exclude any or all Archive warnings (including "Creator Chose Not To Use Archive Warnings"). If you encounter a work that is missing an Archive warning, you can report it to PAC.

Creators frequently apply relationship and additional tags to indicate other kinds of warnings or content. All of these tags can also be used to exclude works. When a tag is excluded, any tags that are linked to it as synonyms or subtags will also be excluded. For example, if you exclude the "Child Abuse" tag, works that are tagged with "Canonical Child Abuse", "Abused Children", etc., will also be excluded, even though they don't use the exact tag "child abuse".

How to use tag exclusion filters

To exclude a tag using the filters sidebar:

1. You can get to any canonical tag's works page by clicking on a tag, either directly on a work or by using Tag Search.
2. Open the filters sidebar. On a large screen, it'll automatically be visible on the right-hand side of the screen. On a small screen, select the "Filters" button to make it appear.
3. Navigate to the "Exclude" section.
4. You can expand each tag type to see the most common tags used on works in your search results. If the tag you want to exclude is listed, select the X next to it.
5. If you're trying to exclude a Fandom, Character, Relationship, or Additional tag that is not one of the most common tags, type the tag into the "Other tags to exclude" box.
6. Select the "Sort and Filter" button at the bottom of the sidebar. This will apply the chosen search filters to the list of works you can see, removing any works with the tags you've excluded.

Exclude by keyword search

In addition to using tags to exclude content, you can exclude a keyword or phrase by inserting a minus sign in front of it in the "Search within results" box. Doing so will mean that any works which contain your keyword or phrase in their metadata will not show up in your results. Metadata includes the title, creator, tags, summary, and beginning and end notes, but it does not include content in the body of the work or individual chapter notes.

In addition to excluding specific keywords, you can also use this method to avoid works created by a particular user: just type -creators:USERNAME into the search box. You can filter out multiple creators at a time by typing this same command multiple times, separated by commas or spaces (for example, -creators:USERNAME1,-creators:USERNAME2).

If you're browsing a work tag, then you can exclude keywords using the filters bar. Type your keyword exclusion into the "Search within results" box, then select "Sort and Filter".

If you're using Work Search, use the "Author/Artist" field to filter out works by a particular user. You can also filter them out from "Any Field": if you do that, you'll catch not just any works they've created, but also any works created by someone else where their username is mentioned in the tags, summary, notes, or other metadata.

Permanently avoid seeing specific users or works

If there is a user that you never want to see again, you can mute them. Muting a user means that you will no longer see works or bookmarks they've created, other users' bookmarks of their works, or comments they've left on AO3. To mute a user, simply select the Mute button on their profile page.

Muting a user will result in a banner at the top of every work search results page. If you want to hide this banner, you can add a site skin that includes p.muted.notice {display: none;}. Site skins customize the way AO3 looks to you while you're logged in.

You can also use site skins to hide specific works that you don't want to see. Once set up, your site skin will be active whenever you're logged into your account on any device.

To use a site skin to hide a particular work:

1. Find the work ID. The work ID is the number in the URL immediately after /works/
2. While logged into your account, go to archiveofourown.org/skins
3. Select "Create Site Skin" (or edit your skin if you're already using one)
4. In the CSS box, type .work-000 {display: none !important;}, replacing "000" with the ID of the work you want to mute
5. To mute multiple works, use a comma-separated list: .work-000, .work-111, .work-222 {display: none !important;}
6. Save or update your skin. If it's new (or if you weren't already using it), you'll also need to select the button labelled "Use"

If you need help creating or using skins, filters, work searches, or any other AO3 feature, please contact Support.

Can I permanently block a tag or have a persistent filter?

Unfortunately, it's not currently possible to save a set of tags or search exclusions directly on AO3, although you may be able to find third-party tools or site skin instructions to help you do this. AO3 doesn't have those kinds of built-in persistent filters: every time you open a new search page or works list, the filters will be reset. However, if you run a search using filters, you can bookmark the results page in your browser. The bookmarked page will keep the same search and filter settings when you return to it later.

What if I have more questions about offensive content?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

For more information, you can read our TOS FAQ on offensive content vs illegal content.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we're posting a weekly spotlight series about the TOS and our policies. We'll also be reading comments and answering questions on this and our other spotlight posts.

Last week’s post was on ratings and Archive warnings. This week, we'll discuss the other kinds of tags that we enforce, as well as the ones that we don't. At the end of this post, we'll provide details on the info that we need included in an incorrect tag report in order to be able to handle it as quickly and efficiently as possible. Although these are minor policy infractions, investigating them can take us a very long time to investigate if the report doesn't contain enough information.

Don't go looking for things to report.

Please do not start searching for incorrectly tagged works to report after reading this post. We know that incorrectly tagged works are a problem on AO3. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

Not all tags are required

Every work on AO3 must have at least one rating, Archive warning, fandom, and language tag. If these tags are used incorrectly, then PAC (or, as we'll discuss below, the Support committee) may intervene. We discussed ratings and warnings in our last post, and we'll explain what we mean by "incorrect" fandom and language tags below.

All other types of tags, such as category, character, relationship, and additional tags, are optional. Our rules for those kinds of tags are much looser. You're not required to use them if you don't want to, and PAC does not enforce the accuracy of these tags.

Fandom tags

Every work must have at least one fandom tag, and some may even have more than one. You are not required to tag every fandom that appears in your work. However, you should not use fandom tags for fandom content that does not appear in your work.

For example, if you're planning a one-shot anthology for multiple fandoms, you should only add a particular fandom tag after the relevant chapter for that fandom has been posted. Please don't include a fandom tag if you haven't yet added any content from that fandom to your work.

We take a pretty broad view of what counts as "fandom content", and we generally defer to the creator's judgement. We don't intervene in cases where franchise or sub-franchise tags have been used. For example, if Darth Vader shows up in your work, you're allowed to tag it with Rogue One: A Star Wars Story (2016), even if your work is primarily about the Star Wars Original Trilogy. Similarly, if Cloud Strife appears in your work, you could tag your work with Compilation of Final Fantasy VII and/or Kingdom Hearts (Video Games) as fandom tags because Cloud is a character in both fandoms. If a fandom has both a movie and a comics version, we will defer to creators on whether to use the fandom tags for one or the other (or even both). It's up to the work's creator to use their best judgement about which fandom tags are most suitable.

However, we do have a few minimum standards. Generally, we don't consider the following scenarios sufficient to mean a fandom is represented in a work:

• A minor or off-hand reference to a well-known/pop-culture element from fandom A, such as an item, location, or the name of a character
• The characters of fandom B are consuming the canon of fandom A, such as by playing a game or watching a movie
• The characters of fandom B are roleplaying as the characters from fandom A

If a fandom doesn't feature in your work beyond minor references such as these, you should not tag that fandom on your work. Instead, you can use an additional tag such as References to The Nightmare Before Christmas (1993) or Inspired by The Great Gatsby.

RPF vs FPF

On AO3, we generally differentiate between RPF (Real-Person Fiction) and FPF (Fictional-Person Fiction). When you're writing about a canon's real-life actors (such as Chris Hemsworth or Mark Ruffalo), you should indicate that by using the "RPF" version of a tag (such as Marvel Cinematic Universe RPF). If you're writing about the fictional characters (such as Thor or Bruce Banner), and not their actors, then you should use the tag for that fictional universe (such as Marvel Cinematic Universe). Even if you're writing about a real-life actor on set, filming a movie, you should still only use the RPF fandom tag and not the tag for the fictional universe: the fictional character isn't actually present in the work, it's simply the actor doing their job.

Sometimes, fandoms have only RPF components, typically when the fandom is for a reality show or other non-fictional canon. For example, fandoms like Boys Planet (Korea TV) and My Favorite Murder (Podcast) do not involve any fictional characters, so the RPF-FPF divide does not apply to them.

A fandom tag that is an actor's name, such as Pedro Pascal - Fandom, is automatically considered RPF. These fandom tags should not be applied to works that are only about the characters an actor portrays. Instead, you can use an additional tag such as Joel (The Last of Us) Played by Pedro Pascal. If you’re a fan of a specific actor or pairing and enjoy seeing them in the different roles they've played, you may also be interested in the Actor X/Actor Y Character Combinations additional tag format.

Generic fandom tags

Because we take a very broad view of how relevant a fandom tag is, it's always OK to use a generic fandom tag such as Unspecified Fandom, No Fandom, or even Original Work. Just as you can always opt out of applying a specific rating (by instead using "Not Rated") or a specific warning (by instead using "Creator Chose Not To Use Archive Warnings"), you may opt out of using a specific fandom tag by instead using a generic or non-specific fandom tag.

You're never required to use any particular fandom tag. If you want to tag all your fanworks with Unspecified Fandom instead of specific fandom tags, you're free to do so. We may require a creator to remove an inaccurate fandom tag, but we will never require a specific fandom tag to be added.

Synonymous tags

AO3's tag system relies on Tag Wrangling volunteers, who link synonymous tags to a canonical tag if both tags are the same type and have the same meaning. This is why you can click on Buffy the Vampire Slayer or BtVS - Fandom and the same set of results will pop up; these two fandom tags have both been made synonyms of the canonical fandom tag Buffy the Vampire Slayer (TV). The Buffy the Vampire Slayer (TV) works page will show works tagged with exactly "Buffy the Vampire Slayer (TV)" and works tagged with any synonymous fandom tags. If you want to learn more about how tag wrangling works, refer to the Tag Wrangling Work Description.

PAC does not handle issues relating to what tags are canonical, how tags are formatted, or which tags have been made synonymous with which other tags. We only look at the exact tag on a given work, not where it's linked to. If you have concerns about a Tag Wrangling decision, please contact Support instead.

Language tags

Every work must be tagged with a language reflecting the language the work is presented in. If the work has multiple primary languages, or no language at all (e.g. artwork), we'll defer to the creator's judgement about which language to tag their work with.

In 2021, Support took over responsibility for handling language tags. If you find a fanwork that's labeled with an incorrect language, please report it to Support, not to PAC. Support will contact the creator and ensure their work is labeled with a language that's represented in the work.

Non-mandatory (optional) tags

Creators can use the category, relationship, character, and additional tag fields to provide more information about their work, but they're not required to. Neither PAC nor Support will judge the accuracy or relevance of these kinds of tags.

However, all tags (regardless of type) are still subject to our general content policies. Tags can't be used to engage in commercial activity or harass other users, because these are both not allowed on AO3. (Later posts in this series will discuss these kinds of violations and how we handle them.)

Harassment generally includes tags which insult or threaten other AO3 users. As mentioned above, inaccurate tagging is not considered harassment. Tags which express negative views of characters or relationships are also not considered harassment. AO3 is open to all kinds of fanworks, including ones that are critical, mocking, or parodies.

If you dislike the way a particular user tags their works, the TOS FAQ has some tips on how to avoid content you don't want to encounter.

What happens if I'm reported for tagging an incorrect fandom?

First, we'll review the reported work to confirm whether your fandom tags are actually incorrect. If you need to update them, we'll send you an email telling you to fix the issue.

If you don't fix it, we'll remove any inaccurate fandom tags. If doing this means we end up removing all of the fandom tags on your work, we'll add the "Unspecified Fandom" tag instead.

We don't ever delete works for having incorrect tags. While we do require inaccurate fandom tags to be fixed, it is very rare for us to apply any penalties to a user's account for incorrectly tagging a fandom. We usually only penalize a user if they revert the changes we made or required them to make, or if they are frequently mistagging their works despite repeated attempts from us to contact them.

However, tags are still subject to our Content Policy. If you violate our commercial promotion or harassment policies with your tags, penalties will be applied accordingly. We'll discuss those policies in later posts.

What should I do if I encounter a work that has an incorrect tag?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can:

• Report the work to PAC, if the incorrect tag is a fandom tag.
• Report the work to Support, if the language is incorrect.
• Mute the work or its creator, if the incorrect tag is a category, character, relationship, or additional tag; or if the issue is with the work's completion status, updated date, kudos count, or other metadata.

How do I report a work with the wrong fandom tags?

Although we ask that you do not deliberately seek out incorrectly tagged works to report, if you come across a work tagged with one or more incorrect fandoms, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3. If a work is tagged with multiple incorrect fandoms, please give us a list of all of the fandom tags you think are incorrect and should be removed.

Regardless of what type of incorrect tag you're reporting, please don't report more than one user at a time or submit multiple reports about the same user for the same reason. When reporting multiple works by the same user, please submit only one report with links to each work you're reporting, so that all information about that user is in the same place.

For example, a report of a work with an incorrect fandom might look like this:

Link to the page you are reporting: https://ao3-rd-3.onrender.com/works/00000000

Brief summary of Terms of Service violation: Incorrect fandom tag

Description of the content you are reporting:
This work by USERNAME is tagged with "Star Wars" but it's actually only about the Avengers, and the characters just watched Star Wars for movie night.

If you are reporting additional works, please include all relevant links and other information in your report description:

Description of the content you are reporting:
This work by USERNAME is tagged with "Star Wars" but it's actually only about the Avengers, and the characters just watched Star Wars for movie night.

Some of their other works also have the wrong fandom:

https://ao3-rd-3.onrender.com/works/23456789 is tagged "The Avengers (Marvel Movies)" but it's about Chris Evans and Robert Downey Jr. which means it's RPF and should be tagged with the RPF fandom tag. Steve Rogers and Tony Stark don't appear anywhere in the work.

https://ao3-rd-3.onrender.com/works/34567890 This work tags "The Legend of Zelda: The Ocarina of Time" when the character's sword only shapeshifts into the Master Sword for two sentences before turning into another sword.

You can add more details if you like, but this example provides the basic information we need:

• Who posted the incorrectly tagged work(s): Tell us their username or if the work is anonymous or orphaned.
• Where we can find the work(s): Enter one URL in the "Link to the page you are reporting" field, and (if applicable) include links to any other violating works in the description of your report.
• What violates the TOS: Explain which fandom tag(s) on each work you're reporting are incorrect. A brief list or description is fine; you don't need to be very detailed or quote an entire TOS or FAQ section.

You'll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same work. While PAC and Support investigate every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about tags?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you've found a work that is tagged with a fandom that doesn't appear in the work, please report the work to us as described above. If you think you've found a work that is tagged with an incorrect language, please report it to Support instead. For more information, you can read our TOS FAQ on other tags.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we're posting a weekly spotlight series about the TOS and our policies. We'll also be reading comments and answering questions on this and our other spotlight posts.

AO3 is a home for all fanworks and operates under the principle of maximum inclusiveness of fanwork content. We allow content of any rating, and all kinds of fictional topics, as long as the creator provides basic information about the intensity and type of content that may be present in a work.

PAC handles many different types of TOS violations, including incorrect ratings and Archive warnings. In this post, we'll discuss the requirements for ratings and warnings as well as provide information on how to report works with incorrect ratings or warnings. We do our best to investigate every report, but incorrect ratings and warnings can take us a very long time to investigate if the report doesn't contain enough information.

Don't go looking for things to report.

Please do not start searching for works with incorrect ratings or warnings to report after reading this post. We know that these kinds of TOS violations are a problem on AO3. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

Ratings

All works on AO3 must have a rating. Creators can either select a specific rating ("General Audiences", "Teen and Up", "Mature", or "Explicit") or opt out of providing a specific rating by applying the non-specific rating "Not Rated".

Our TOS divides ratings into two tiers: ratings that will trigger the Adult Content notification ("Mature", "Explicit", or "Not Rated"), and ratings that won't ("General" or "Teen"). When you click on a work rated "Mature", "Explicit", or "Not Rated", a banner will warn you that you're about to access a work that may contain adult content. By selecting the "Yes, Continue" button on the banner, you are agreeing to access a work which may contain adult content. Registered users can disable this notification, which is enabled by default on new accounts.

Works rated "General" or "Teen" are not subject to this notification system. If a work rated "General" or "Teen" contains explicit content that you believe should trigger the Adult Content notification, you can report that work to PAC, and we will investigate whether that work needs to use one of the three higher ratings.

However, PAC doesn't make any distinctions within these two tiers. This means that we won't require a work rated "General Audiences" to be changed to "Teen and Up", and we won't require a work rated "Mature" or "Not Rated" to be changed to "Explicit", or vice versa. We defer to the work's creator(s) for those decisions: the only part we enforce is whether or not the work needs a rating that triggers the Adult Content notification.

Archive warnings

There are four specific Archive warnings: "Underage Sex", "Rape/Non-Con", "Graphic Depictions of Violence", and "Major Character Death". Any work on AO3 that contains content relating to one of the four specific Archive warnings must be tagged with either that warning or the non-specific "Creator Chose Not To Use Archive Warnings" label.

Creators can always Choose Not To Warn.

The "Creator Chose Not To Use Archive Warnings" (CNTW) label is a blanket warning. It means "Read at your own risk!" or "This work may contain any of the four specific Archive warnings." If you don't want to encounter content depicting underage sexual activity, rape/non-consensual sex, graphic violence, or major character death, then you should not click on works tagged with "Creator Chose Not To Use Archive Warnings".

When you post a work, you can use the CNTW label if you don't want to apply a specific Archive warning. For example, if you don't want to spoil a plot twist by adding a "Major Character Death" warning, you can instead apply "Creator Chose Not To Use Archive Warnings" to your work. You can also apply a combination of CNTW and other Archive warnings. If your work contains rape and a major character death, and you want to warn for the former without spoiling the latter, you can label the work with both "Rape/Non-Con" and "Creator Chose Not To Use Archive Warnings".

If you don't Choose Not To Warn, then you may need to add a specific warning.

As mentioned above, you can always opt out of applying Archive warnings by instead selecting "Creator Chose Not To Use Archive Warnings". If you do not select this label, then in the following circumstances, you must use one or more of the four specific Archive warnings:

The "Underage Sex" warning is required on works that depict or describe sexual activity involving characters under the age of eighteen (18). We don't consider dating activities, like kissing, to be sexual content. Offscreen sexual content also doesn't need a warning.

For characters that are underage in canon, we do not automatically assume (without evidence) that they are also underage in the fanwork. If there are no indications that a particular character is under 18, we will assume they are 18 or older. When evaluating works, we consider explicit statements of a character's age as well as contextual clues (such as the work being clearly set in a time period where the character is underage). If you're worried that a character in your fanwork may be misinterpreted as being younger than 18, you can always specify the character's age in the tags, notes, or body of your work.

The "Rape/Non-Con" warning is required on works that depict onscreen rape or non-consensual sex. If the work only contains a reference to non-consensual sex, then we don't require this warning to be applied. Additionally, there are circumstances that are not considered consensual in real life, but don't necessarily require the "Rape/Non-Con" warning on AO3. For example, we don't inherently require a "Rape/Non-Con" warning for adult/minor relationships (though we might require "Underage Sex" or CNTW). We also do not require a "Rape/Non-Con" warning for situations that are dubiously consensual, such as the Sex Pollen or Fuck or Die tropes. When in doubt, we defer to the creator's judgement.

Similarly, the "Graphic Depictions of Violence" warning is only required if the work contains graphic violence that is explicitly shown "onscreen" in the work.

We require "Major Character Death" when the character is both a major presence in the fanwork and they're dead by the end of the fanwork. We don't take canon into consideration here – what we're interested in is whether the character is a major presence in your fanwork. If you create a fanwork centered on a character that dies and stays dead in your work, that work should be warned for "Major Character Death" even if they only appear for one line in canon. If that same character dies before the start of your work, and dealing with the grief of their loss is a major part of the fanwork, "Major Character Death" is also required in this situation.

If your work features a character death and that character returns in a later chapter that is currently posted, then this warning is not required. However, if the character does not return to life until a sequel fanwork, the warning is still needed on the work in which they died. Archive Warnings apply to individual fanworks, not to series of works.

"No Archive Warnings Apply" may coexist with other warnings.

There is also a sixth label in this category: "No Archive Warnings Apply". The best way to think of this Archive warning is as a placeholder. If "No Archive Warnings Apply" is the only Archive warning on a work, then it means that the work should not feature underage sex, rape/non-consensual sex, graphic violence, or major character death – or if it does contain such content, it is only a brief reference.

However, the "No Archive Warnings Apply" label can be present on a work that is also labeled with any or all of the other five Archive warnings. In that case, the other warning label always takes precedence. PAC never removes any Archive warnings already on a work. We only add the "Creator Chose Not To Use Archive Warnings" label to the work if it's missing a required warning.

For example, some users may apply a "Major Character Death" warning and a "No Archive Warnings Apply" warning in order to emphasize that while the work may contain Major Character Death, it doesn't contain any of the other warnings. The presence of "No Archive Warnings Apply" does not negate the "Major Character Death" label on the work – a major character death may still occur in this work.

If both "No Archive Warnings Apply" and "Creator Chose Not To Use Archive Warnings (CNTW)" are applied to the same work, then the CNTW warning is what takes precedence, and the work may contain content relating to any of the four specific Archive warnings. Some users may apply both the CNTW label and the "No Archive Warnings Apply" label for ambiguous situations, or to emphasize that while they don't think the work contains something that needs a warning, it is open to interpretation. However, you should not assume anything about a creator's intentions or the severity of content in the work – consider works warned with both CNTW and "No Archive Warnings Apply" the same way you'd consider works tagged with only CNTW or any/all of the specific Archive warnings.

We generally defer to the creator's judgement.

For borderline cases, PAC will defer to the creator's judgement. However, if we feel that a work depicts content clearly requiring one of the four specific Archive warnings, we'll require the creator to either add the warning or opt out by applying the "Creator Chose Not To Use Archive Warnings" label.

Can I use Additional tags instead of Archive warnings?

Sometimes users include warnings in the Additional tags of their work. If the content is merely a reference or offscreen, this is fine. However, for any content requiring an Archive warning, the label must also be added in the Archive warnings category. For example, while you are welcome to include an additional tag of "rape" on your work featuring a rape scene, you still need to apply the "Rape/Non-Con" Archive warning (or CNTW).

Why does AO3 have only four required Archive warnings?

AO3's warning system is deliberately minimal. When AO3 was created, these four warnings were chosen as a balance between the most common types of content that users wanted a warning for, and what would be feasible for PAC (a small team comprised entirely of volunteers) to enforce in a consistent and fair manner. We know that there are many other kinds of content that you might not want to see, so we encourage you to check out the additional tags, summary, notes, and bookmarks of a work before opening it. However, PAC will not enforce the use of tags or warnings beyond what is required by the TOS.

It's what's in the work that counts.

When it comes to ratings and warnings, we evaluate what is in the body of the work. If an author says in their notes that they plan to include explicit sex eventually, but the only chapter posted is a fluffy introduction with no explicit content, then we will not require that the work be given one of the higher ratings. Similarly, if a work carries an additional tag of "X dies at the end" but nobody actually dies in the work, then we will not require a "Major Character Death" warning.

Because of this, please do not report works based on what is in their additional tags or summary. Many creators may have begun works and added additional tags or notes based on their plans for future updates, but plans change, and not all works in progress are completed. Please only report works to us when there is actual content in the work itself that necessitates a rating or warning change.

Ratings and warnings are not promises.

AO3's warnings and ratings both mean "may contain", not "must contain". If you want to rate your fluffy, non-sexy slice-of-life as "Explicit", you're allowed to do that. A higher rating means that a work may contain explicit content, not that it must contain such content. Similarly, if you want to warn for "Major Character Death" even though nobody has died, you're allowed; we don't ever make someone remove a warning.

What will happen if I get reported for having an incorrect rating or missing warning on my work?

First, we'll review your work to confirm whether or not your work's rating and/or warnings are insufficient. If we determine that the rating or warnings need to be changed, we'll send you an email notifying you to update your tags.

We'll only ever contact you by email, and only after we've already reviewed your work and confirmed that the current rating and/or warnings are insufficient. We will never comment directly on your work or contact you through social media. Please make sure to keep your account's email address up to date and check it regularly (including your spam folder), or else you may miss our email.

If you don't update your tags, we'll change them. For an incorrect rating, we'll set the work to "Not Rated". For a missing warning, we'll add the "Creator Chose Not To Use Archive Warnings" label to the work. We won't remove any of the warnings that are already on the work.

We don't ever delete works for having insufficient warnings or ratings. While we do require all works to have appropriate ratings and warnings (as specified in the TOS), it is very rare for us to apply any penalties to a user's account for insufficient ratings or warnings. We would usually only penalize a user if they undo changes we made or required them to make. A user may also receive a penalty if they repeatedly mislabel their works even after being contacted about similar violations, or for the purposes of harassment.

What should I do if I encounter a work that has the wrong rating or a missing warning?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can report the work to us.

How do I report a work with the wrong rating or missing warnings?

Although we ask that you do not deliberately seek out incorrectly tagged works to report, if you come across a work with the wrong rating or missing warnings while browsing, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3.

Please don't report more than one user at a time or submit multiple reports about the same user. When reporting multiple works by the same user, please submit only one report with links to each work you're reporting, so that all information about that user is in the same place.

Please tell us exactly where in the work the content requiring the higher rating or warning is. The best way to do this is to give us a short quote from the relevant scene that we can search for in order to immediately find the content. If you are reporting multiple works by the same creator, please group all the works into one report and provide this information for each work.

If the rating or warning issue pertains to a specific character, please tell us the name of that character as used in the work. If it's Bert who died, please tell us it's Bert, so that we don't spend time trying to figure out if it was Ernie (who was only badly wounded). If you are reporting a missing "Underage Sex" warning, please tell us exactly where the underage sexual content occurs and where the indication of the character's age is. As a reminder, if there are no indications that a particular character is under 18, we will assume they are 18 or older.

Rating and warning issues can take a lot of time for us to investigate if we're not given clear information about where the violation has happened. PAC will not act unless we've confirmed a policy violation ourselves. If we're sent a report about a work that is 80,000 words long and the report only says "contains rape", we have to confirm that there is a rape scene somewhere in those 80,000 words before requiring a "Rape/Non-Con" (or CNTW) warning. If we can't find it easily, the most likely result is that we'll reply to you asking you to give us more info – and if you don't, we'll close your report with no further action. So please make sure to include as much information as possible when submitting a report.

For example, a report of a work with an incorrect rating might look like this:

Link to the page you are reporting: https://ao3-rd-3.onrender.com/works/00000000

Brief summary of Terms of Service violation: Incorrect rating

Description of the content you are reporting:
This work by USERNAME is rated G but it's entirely smut from the very first sentence.

If you are reporting additional works, please include all relevant links and other information in your report description:

Brief summary of Terms of Service violation: Incorrect ratings and warnings

Description of the content you are reporting:
This work by USERNAME is rated G but it's entirely smut from the very first sentence.

Some of their other works also have the wrong rating or warning:

https://ao3-rd-3.onrender.com/works/23456789 is rated T with No Archive Warnings Apply, but it has underage sex onscreen. CHARACTERNAME is 17 (in chapter 2 it says "after his seventeenth birthday party three weeks ago") and has sex in chapter 4 (starting at "He stepped closer, leaning in...")

https://ao3-rd-3.onrender.com/works/34567890 has the main character CHARACTERNAME die at the end (search for "She gasped in horror"), but the work isn't tagged with Major Character Death or Creator Chose Not To Warn.

You can add more details if you like, but this example provides the basic information we need:

• Who posted the incorrectly tagged work(s): Tell us their username or if the work is anonymous or orphaned.
• Where we can find the work(s): Enter one URL in the "Link to the page you are reporting" field, and (if applicable) include links to any other violating works in the description of your report.
• What violates the TOS: Explain why you think the rating and/or warning(s) on each work you're reporting are incorrect, for example by including a quote from the relevant scene(s). A brief description of the work is fine; you don't need to be very detailed or quote an entire TOS or FAQ section.

You'll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same work. While PAC investigates every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about ratings and warnings?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you've found a work that's incorrectly rated or missing a warning, or if you want to know whether a particular scene requires a specific rating or Archive warning, please report the work to us as described above. For more information, you can read our TOS FAQ on ratings and Archive warnings.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we're posting a weekly spotlight series about the TOS and our policies. We'll also be reading comments and answering questions on this and our other spotlight posts.

PAC handles both major and minor policy infractions. We get tens of thousands of reports each year about a lot of different types of TOS violations, but approximately half of all reports are about one specific thing: the violations we call "non-fanworks". In this post, you'll learn about some of the most common types of non-fanworks, why we don't allow them, where to put this type of content instead, and what you can do if you see a non-fanwork on AO3.

Don't go looking for things to report.

Please do not start searching for non-fanworks to report after reading this post. We know that non-fanworks are a problem on AO3. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

AO3 is an archive for fanworks, not other kinds of content.

AO3 has a very specific purpose: to host fanworks, and only fanworks. Our definition of "fanwork" is broad: fanworks can take many shapes and forms, including fanfiction, fanart, podfics, fanvids, fancrafts, fannish non-fiction, original works, and more.

What are some examples of non-fanworks?

Works that are not fanworks should not be posted to AO3. These include (but are not limited to):

• Fic searches or requests for recommendations
• Advertisements for roleplay partners or servers
• Personal messages to other users
• Updates, polls, or announcements
• Reaction, blog, or vent posts
• Spam, shitposts, or memes
• Reposted novels or other published works
• Placeholders and other empty works
• Links to or lists of works you've read or created
• Ideas or prompts for fanworks
• Requests for other users to provide you with ideas or prompts for fanworks

AO3 has many features that you can use instead of posting a non-fanwork.

There are many AO3 tools and features that are designed to assist you with finding, recommending, and creating fanworks. Please use these features instead of posting a non-fanwork.

• Tags and Search: AO3 has an extensive tagging and searching system, which you can use to browse for works you might be interested in or find a specific work.

• Bookmarks: You can use bookmarks to save or share fanworks hosted on AO3 or other sites. AO3 bookmarks can be organized using tags, notes, and collections.

• Series and Collections: You can make a series to organize your fanworks so that other users know what order to read them in, or a collection to group similar kinds of fanworks together. Fanworks can be placed in multiple series or collections at the same time.

• Prompt Memes: Prompts or ideas for fanworks that you would like to see (or requests for others to give you ideas for fanworks to create) are not themselves fanworks. Instead, you can request or post prompts using a prompt meme, which is a specialized type of collection that lets multiple users share and fulfill each other's ideas.

• Drafts: All works on AO3 must be fanworks; empty placeholder works aren't fanworks. You shouldn't post a placeholder work that has no content, nor should you remove all the content from your work while you're editing it. If you have a work in progress that you aren't ready to post yet, please save your work as an unpublished draft instead.

• Profile and Notes: You can share links to your accounts on other sites or provide updates on your writing progress by editing your profile or adding notes to your fanworks.

If you need help using any of AO3's features, please contact Support.

I've seen others post these "non-fanworks". Why can't I?

As our TOS FAQ explains, we don't review content until it's reported to us. You may have seen somebody else post a fic search or a prompt as a work on AO3, but that doesn't mean it's allowed. All it means is that nobody has reported that non-fanwork to us yet, or that we haven't finished processing the report.

What if I plan to delete it as soon as possible?

Works on AO3 must be fanworks. By posting a non-fanwork, you're violating our TOS. If someone reports your work to us, we may still take action even if you've already deleted the work.

What will happen if I get reported for posting a non-fanwork?

First, we'll review the reported work to confirm that you violated our TOS by posting a non-fanwork. If we determine that your work is a non-fanwork, we'll hide the work and send you an email telling you to delete the non-fanwork. In some cases, we may offer you the chance to edit your work instead.

We'll only ever contact you by email, and only after we've determined that your work is a non-fanwork. We will never comment on your work or contact you through social media. Please make sure to keep your account's email address up to date and check it regularly (including your spam folder), or else you may miss our warning email.

If you repeatedly post non-fanworks, you may be temporarily suspended. Continuing to violate the TOS will result in you being permanently banned from AO3. You can learn more about warnings and suspensions in our TOS FAQ.

What should I do if I encounter a non-fanwork?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can report the work to us.

How do I report a non-fanwork?

Although we ask that you do not deliberately seek out non-fanworks to report, if you come across a non-fanwork while browsing, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3.

Please don't report more than one user at a time or submit multiple reports about the same user. When reporting multiple works by the same user, please submit only one report with links to each work you're reporting, so that all information about that user is in the same place.

For example, a non-fanwork report might look like this:

Link to the page you are reporting: https://ao3-rd-3.onrender.com/works/00000000

Brief summary of Terms of Service violation: Non-fanwork

Description of the content you are reporting:
This work by USERNAME is a search for a fanfic.

If you are reporting additional works, please include all relevant links and other information in your report description:

Description of the content you are reporting:
This work by USERNAME is a search for a fanfic.

Some of their other works are also not fanworks:

https://ao3-rd-3.onrender.com/works/23456789 is a request for roleplaying partners.

https://ao3-rd-3.onrender.com/works/34567890 is a list of prompts.

You can add more details if you like, but this example provides the basic information we need:

• Who posted the non-fanwork(s): Tell us their username or if the work is anonymous or orphaned.
• Where we can find the work(s): Enter one URL in the "Link to the page you are reporting" field, and (if applicable) include links to any other violating works in the description of your report.
• What violates the TOS: Explain why you think each work you're reporting is not a fanwork. A brief description of the work is fine; you don't need to be very detailed or quote an entire TOS or FAQ section.

You'll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same work. While PAC investigates every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about non-fanworks?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you've found a non-fanwork on AO3, or if you want to know whether a particular work is a fanwork, please report the work to us as described above. For more information, you can read our TOS FAQ for examples of fanworks and non-fanworks.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

ETA: As mentioned earlier in the post, original works are a type of fanwork allowed on AO3. For more information, please refer to our TOS FAQ: Can I post original fiction?.

This year, in recognition of World Password Day, we’re asking all fans to spend a few minutes ensuring that their passwords – and their AO3 accounts – are secure.

Recently, the Policy & Abuse committee (PAC) has seen an increasing number of users who have lost access to their AO3 accounts because they used an insecure password. We'd like to reassure our users that there is no indication that AO3 has experienced a data breach. PAC has been able to determine that all of the affected users' login information had been compromised in other ways, such as by accidentally downloading malware to their devices and/or by re-using the same password on AO3 that they had also used on a compromised website.

In early 2025, several large datasets were posted online, containing hundreds of millions of email/password pairs obtained from malware and compromised websites. It's common practice for scammers to test these compromised email/password pairs on other websites, in case the affected passwords were reused elsewhere. This allows the scammer to access accounts on websites that have never experienced a data breach, such as AO3. After gaining access to an account, the scammer may then change the account's email, password, and/or username, or sell the account information to other people.

AO3 is always free to use, but some people might not understand how to create their own AO3 account. There are many reasons for this, such as language barriers and unfamiliarity with our site. These people may purchase AO3 account information in the mistaken belief that AO3 accounts can be sold legitimately. They only discover they have been scammed once PAC re-acquires the account to give it back to the original owner.

PAC has been working diligently to identify compromised accounts and restore them to their original owners. We have also been working with the victims of the account-selling scam to help them create their own free AO3 accounts. Unfortunately, sometimes these victims, thinking the account they purchased legitimately belongs to them, may delete works or other content posted by the original account owner. While PAC can restore ownership of an account, we are unable to restore deleted content.

Ensure Your Password is Secure

You can reduce your vulnerability to this kind of incident by following internet security best practices:

• Set a unique, secure password for each and every one of your accounts on all platforms.
• Don't ever reuse passwords or share your passwords with anyone else for any reason.
• Use a password manager. This will help you to set unique, secure passwords for each of your accounts without worrying about forgetting them. Many browsers have a free, built-in password manager if you would prefer not to download third-party software.
• Keep your antivirus software and operating system up to date, and set them to scan for malware regularly.
• Check the website haveibeenpwned.com to see if your emails, passwords, and other information may have been exposed in data breaches. Change your passwords for any breached websites and any accounts on other sites where you may have used the same password.

If you are ever worried that your AO3 account is at risk of being compromised, you should do the following:

• Change your password immediately. This will automatically log you – and anyone else accessing your account – out of all sessions on all devices.
  • If you’ve forgotten your password, but you have access to the email address currently associated with your AO3 account, you can log out and reset your password instead.
  • If you’ve forgotten your password, and you no longer have access to the email address you used for your account, please contact Support.
• Make sure the email address associated with your AO3 account is one that you check regularly, as this is where all notifications about your account will be sent. If you need to update your email address, please refer to our FAQ about changing your email.

If you've received an email from @archiveofourown.org saying that the email associated with your account has been changed to one you don’t recognize, and you can't log in to your account, please contact Policy & Abuse. PAC treats compromised accounts as a matter of high priority, and will work with you via email to restore your account. If it's been over a week and you have not heard back from a PAC volunteer about the status of your account, check your email (including any spam, social, or other folders) before replying to our email or submitting a new Abuse report.

Again, we emphasize that there has not been any breach of AO3's servers. We are also developing and implementing additional measures to help prevent unauthorized access to AO3 accounts. However, your account is only as secure as your password and email. We encourage all users to take a few minutes today to ensure that your AO3 password is unique and your email address is up to date.

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with GenreCat, who volunteers as part of the Policy & Abuse Committee.

How does what you do as a volunteer fit into what the OTW does?

The Policy & Abuse committee is responsible for interpreting and enforcing the Terms of Service on AO3. When users report content that they believe isn't allowed on AO3, that report comes to us. We then investigate independently and determine if the report is about something that is actually against AO3's Terms of Service. If it is, then we'll contact the person who posted it and tell them what they need to remove and why. If it's not a violation, we'll let the reporter know, and provide information about how they can avoid seeing similar content in future. We also answer questions about what is or isn't allowed on AO3.

Because we're an all-volunteer team, and not a very large one, the wait-times on tickets can be lengthy. Here's some advice if you want your ticket to be processed more quickly:

1. Provide us a direct link to the thing you want to report. If that's a work, provide us a link to the work. If you want to report multiple works, provide links to each work in your report description. If it's a comment, select the 'Thread' button on the comment to get the direct link to that comment. If you only report the user's profile instead of the thing they posted, we have to go track it down, which immediately makes a case take longer.
2. Don't report more than one user at a time (unless they're co-creators on the same violating work). Having multiple unrelated users on one report complicates the paperwork for us.
3. Don't encourage other people to also report it. We investigate every report we receive, and we don't make rulings based on how many people reported it. All mass-reporting does is give us more admin work that has to be handled before we can actually address the problem.
4. If you're reporting plagiarism or copyright infringement, give us a link to the source material. Please don't make us guess!
5. Be succinct. We only need a short description of what and where the problem is -- a single sentence is usually sufficient.

What is a typical week like for you as a volunteer?

I usually do PAC work every day, sometimes in long chunks and sometimes just quick check-ins. If I only have a short period of time, I'll catch up on messages from other volunteers and check new tickets that have come in. If there's tickets that haven't been categorized, I'll categorize them—categories help PAC volunteers decide what tickets to work on next. If there's higher-priority tickets, I'll quickly glance at them to attach evidence and see if there's something that we can resolve quickly.

When I have more time to work in a stretch, I'll review cases that other volunteers are handling and sign off on their plans of action, or I may pick up new tickets of my own to handle. I also spend quite a lot of my time working on documentation. PAC is constantly reviewing portions of our internal policies, training, and guidance material, which I like being involved in; it helps us determine better methods of doing things and ensures that we stay consistent in our rulings.

What made you decide to volunteer?

I'd been on AO3 for about a decade, and I'd always wanted to volunteer, because I feel like AO3 is a really important thing for fandom to have. I've been in fandom long enough to remember how slash fiction was banned or highly censored on a lot of older sites explicitly because of homophobia, and compared to that AO3 was a much-needed breath of fresh air. However, the stars had never quite aligned for me to apply—until the middle of 2020, when like many people, I suddenly had a lot more time where I was supposed to be at home. So when the next round of applications opened, I sent mine in.

What has been your biggest challenge doing work for the OTW?

The OTW is a very big organization, and it has a lot of inertia. At times, trying to push for necessary change—procedural or cultural—has been very frustrating. However, since I've joined the OTW I've seen this improve a lot, both within PAC and within the OTW overall. I'm very hopeful that we've got a brighter future ahead of us.

On a much less serious note: in terms of tickets that are challenging, personally it is the ones that are labelled only 'spam'. This is because many, many things get called 'spam', so I never know what the ticket is about until I go and investigate the link. A small sample of things I have seen called 'spam' includes: donation requests, duplicate postings of works, fanworks that have deliberately terrible grammar and spelling, fanworks that have the wrong pairing tag, comments consisting entirely of emojis, works that are just "WIP coming soon", works that are solely requests for prompts, copyright infringement, plagiarism, works with dozens of extra fandom tags, death threats, and comments from actual spambots. Some of these are violations, some of them aren't. It's nice to have a better idea of what I'm getting into before I open a report. So a request for anyone reading this—if you're reporting actual spambot spam, please say 'spambot' somewhere in your report instead of just 'spam'! And if it's not an actual spambot, please include an extra 2-3 words of description. Your ticket-handler will appreciate it!

What fannish things do you like to do?

I spend a lot of time reading and writing fic! Fellow PAC volunteers introduced me to several new fandoms in the last couple of years, the biggest of which are MXTX's novels. One of the things I love about big fandoms is that there's so much fic, it would be really difficult for me to work through it all—there's always something new to read.

Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in the comments. Or if you'd like, you can check out earlier Five Things posts.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan-run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

As we continue to work on better balancing the responsibilities of our Support and Policy & Abuse committees, we are shifting two further types of issues from Policy & Abuse to Support's mandate:

Fannish Next-of-Kin

This is an option we offer that allows a designated person to manage your account if you die or become incapacitated. To learn more about the Fannish Next-of-Kin program, you can read our TOS FAQ on the subject. Please note that if you have a currently-in-process Fannish Next-of-Kin request, our Policy & Abuse team will complete the ones that they have already received.

Going forward, if you wish to set up a Fannish Next-of-Kin, or need to change or activate one currently in place, please contact Support.

Duplicate works

Sometimes, due to a glitch or error, a work may be posted multiple times. This can be reported to our Support team, who will investigate and take down exact duplicates. Please note that works that contain different content (such as a work that is an edited or rewritten version of another work) will not be considered exact duplicates.

If you wish to report works that are exact duplicates of one another, please include links to both or all of the works in question in your report to our Support team. We hope these changes will be helpful by allowing our Policy and Abuse team members to devote more of their time and energy to other issues!

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with DZ, who volunteers as a Policy & Abuse staffer.

How does what you do as a volunteer fit into what the OTW does?

Archive of Our Own is the fanwork hosting subset of the OTW. From original works to microbial art, all kinds of fanworks are welcome on the Archive as long as they comply with the ToS. Every committee in the OTW is fully run by volunteers and I signed over my time to the Archive's Tag Wrangling and Policy & Abuse committees.

As a wrangler, I sort and connect the tags people put on their works. If you ever wonder why a fic tagged "Not your grandma's abo" appears under Non-Traditional Alpha/Beta/Omega Dynamics" when you filter, I am one of the people making sure that happens. Every tag is seen and sorted by a real person eventually. One of my favorite things to do as a wrangler is to create fandom-specific tags.

As a part of the Policy & Abuse committee (PAC), I investigate reports for content believed to break the Terms of Service. While that tends to be the bulk of my PAC duties, I also answer questions and help clear up any confusion about policy. If someone is uncertain if something is allowed on the Archive; confused why their work seems to be missing or deleted; or wondered why their account is suspended, they can submit a question using the "Policy Questions & Abuse Reports" link found on the bottom of every page.

What is a typical week like for you as a volunteer?

For wrangling, I tend to do that whenever I have free time and extra spoons. So my schedule varies a bit, I often sneak in a bit of wrangling before I leave for work in the morning once or twice a week. If I'm busy, I try to scan the fandoms I've assigned myself to and see which ones need more attention.

As for my PAC duties, I have what I call a "PAC week" which spans four days of the week. I do a different mix of tasks each of those days such as investigating reports, drafting letters, or following up on any of the cases I'm handling during this time. I regularly beta-read drafts for other team members. Every case is reviewed by at least two staff members. There's always a lot to do. Outside of this time, I avoid any time-intensive or spoons-heavy task -- often any PAC task in general.

I find that having a schedule is useful for PAC since I find it harder to pause in the middle of doing a task and pick it back up again -- sometimes this is because the task can't be broken up and sometimes this is just because of how my brain works. Different volunteers have different preferences. I know some do a little each day or pick one day out of their week to do everything so I guess I am in the middle.

What made you decide to volunteer?

I have always been the kind of fan who was terrible at not getting more involved once I really got into something. When I was into K-Pop, I moderated forums. When I was really into D&D, I was very involved in helping others create Homebrew and edit their homebrew.

I actually tried to join Tag Wrangling 3 years in a row but the app always closed before I had time to fill it out. Then, one day in 2020 I checked again on a whim and saw that the position was open. I later decided to join PAC because my involvement bug bit again.

What has been your biggest challenge doing work for the OTW?

What do you call work-life balance but for volunteering?

The Archive grew a lot in the past year and continues to grow. More users means more tags, more people who report violations, and more questions about what's allowed on the Archive. Neither committee requires that I make it my part-time job, but with so much to do I can feel a bit overwhelmed, and like I'm falling behind even though I decide how much I do.

It didn't help that I joined during the pandemic. So I had a lot more free time to spend on wrangling, and by the time I joined PAC, doing OTW stuff daily was just my normal. I enjoy wrangling and doing PAC work but I'm trying to remember to leave more time to do other stuff I enjoy.

What fannish things do you like to do?

Beyond squeeing and finding things to become a fan of? I write fic. Well, I plan fic -- writing tends to go much, much slower. I also dabble in meta and gif making occasionally. I even tried to learn how to create podfic a while back. I like to think of myself as a fannish jack of all trades, master of none. I have a lot of enthusiasm but I may not be the most skilled in any of it. I'm having fun.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

In order to better balance the workloads of our Support and Policy & Abuse committees, we are making some changes to who is responsible for which kinds of requests.

Policy & Abuse will continue to address Terms of Service violations, and Support will continue to answer questions on how to use the site and address bug reports, as always. But there are some cases which Policy & Abuse have previously been handling, and which will now be handled by Support. These are:

• Loss of access to an account (for example, if you no longer remember or have access to the email address you used to set up your account in order to receive a password reset)
• Questions and problems concerning orphaned works
• Works labeled with an incorrect language

If you need to report one of these issues, please contact Support. If you direct a report of any kind to the wrong department, it's okay! We'll either transfer the report directly, or ask you to resubmit it to the correct team.

We hope these changes will be helpful by allowing our Policy & Abuse team members to devote more of their time and energy to other issues!

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with Lydia, who volunteers as a Policy & Abuse staffer.

How does what you do as a volunteer fit into what the OTW does?

The Archive of Our Own was created to protect and preserve transformative fanworks of all kinds. As a fanwork archive, we believe in maximum inclusiveness of content: if you’ve created a fanwork—whether fiction or meta; derivative or original work; fanfic, fanart, fanmix, podfic, or fanvid—then regardless of the subject matter, your fanwork is welcome on AO3.

You’ll need to choose an appropriate rating, warning, fandom, and language, but (with the exception of language) you don’t have to be specific. When it comes to the Archive’s required tags, using the “Not Rated” rating, “Creator Chose Not To Use Archive Warnings” warning, and “Unspecified Fandom” fandom tag is like saying Here be dragons, and that’s perfectly fine and valid. Of course, you’re also welcome to pick the more specific ratings and warnings, and/or get really detailed in your fandom, character, relationship, and additional tags.

Currently, AO3 hosts approximately 8 million works, created by 4 million users and tagged with over 16 million tags. As a tag wrangler, I help sort and connect all those tags so that users can more easily find—or avoid—particular content. And as part of the Policy & Abuse committee (PAC), I investigate reports about content and behaviors that violate the AO3 Terms of Service. (If you didn’t know, the Report Abuse link is located at the bottom of every AO3 page.)

We only need one report in order to investigate any given case, and the more details about the user and their works or comments you include in that report, the better. A minimum of two real human beings review every single report we receive, to ensure that we are interpreting the Terms of Service consistently and that we only act when the reported user isn’t following the rules.

If the content doesn’t violate the Terms of Service, then the report is rejected and the fanwork remains on the Archive.

But if you post things that aren’t fanworks (like fic searches, prompts, or social media posts), mention anything about making money from your work, reproduce someone else’s work without permission, harass other users, or otherwise violate the Terms of Service, then we may send you an email warning you that what you did isn’t allowed on AO3, and explaining exactly what you need to do to fix the issue and what will happen if you don’t.

All reports are confidential, and all user communication occurs via email, whether that’s the email address associated with your AO3 account or the one you entered into the form when making a report. Please make sure your email is correct and that you check it (and your spam folder) regularly!

What is a typical week like for you as a volunteer?

Every day, I receive hundreds of email/mobile notifications about the latest reports, updates to active cases, and other messages. As a volunteer, I do what I can, when I have the time and spoons to do it. So, if I only have a few minutes here and there, or if I’m on my phone, I’ll do little things: reviewing drafts for typos, reading and contributing to ongoing discussions, browsing through and claiming tickets, or making notes on incoming reports to help whoever eventually takes the case.

When I have a larger block of time, I’ll work on some of the tickets I picked up earlier. For any given case, the first thing I do is collect, organize, and verify all of the relevant information in order to determine whether there’s been a violation and how to handle it. If the case is borderline or particularly complicated, I may need to bring it to the team for discussion or consult with other committees, such as AD&T, Support, Translation, or Legal. Once I’ve decided what the appropriate action should be, I’ll draft all necessary responses and ask another team member to review my work and (if they didn’t find any errors) sign off on the case. If any of my responses need to be translated, I’ll get that done before sending the emails out. If I gave a user a deadline to do something, I’ll follow up after the deadline has passed to see if they did the thing. If they did, great; if not … well, that depends on the case.

On top of all that, I try to do a bit of wrangling every week, whether that’s checking the fandoms I’m assigned to for new tags, evaluating if my fandoms’ existing tags meet current guidelines, or working on large-scale projects with other wranglers. Once a month or so, I help AD&T test the latest releases, which mostly amounts to poking things they’ve coded to make sure they work right (and occasionally finding out that they don’t).

What made you decide to volunteer?

One day I stumbled upon one of the AO3 news posts which was asking for tag wranglers. I had no idea what that was, but it seemed like an interesting way to contribute to fandom, so I applied.

I joined PAC about a year later, after talking with a few friends who were on the team and thinking that the type of work PAC does and the kind of people they are sounded exactly like it’d fit with my interests and personality. While I don’t think I would have had the courage to apply to PAC from the start, I’m very glad I’m here now.

What has been your biggest challenge doing work for the OTW?

Particularly in the last year or so, there’s been a huge increase in site traffic. More users means more content, and more content means more tags to wrangle and more reports to process. On both of my committees, we’ve had to take steps to try and keep up with the higher workload.

I’m just one of over a thousand volunteers from around the world, all of whom are devoting our free time to the OTW’s various projects. Everything we do—research, testing, discussion, coordination, documentation, recruitment, training, policy decisions, procedural changes, guideline reviews, normal day-to-day work—takes time and effort, and not everyone has those to spare on any given day. Misunderstandings are going to happen, so patience and kindness are crucial. Apologize when you mess up, try to figure out where you went wrong, and commit to doing better in the future.

What fannish things do you like to do?

While I will occasionally create fanart or beta fics for friends, I wouldn’t have discovered AO3 if I didn’t read fic, and I read fic nearly every day. Nowadays I get most of my recs from wrangling and reports, lol. I also spend a lot of time chatting with other OTW volunteers, whether about our work, the fandoms we’re in together, interesting things we found online … plus, I’ll never say no to a cute cat pic ^_^

Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in comments. Or if you'd like, you can check out earlier Five Things posts.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

In the next few days, we will be adding a new option that allows work creators to turn off comments. The option will be available on the forms for posting or editing individual works as well as the form for updating multiple works at once, and we've done some minor rearranging of the forms to accommodate the new option.

What turning off comments does

Turning off comments will replace the comment form at the end of your work with a notice that says, "Sorry, this work doesn't allow comments."

If your work already has comments, all existing comments will remain accessible to you and anyone who can access your work. You will still be able to delete any unwanted comments or mark guest comments as spam.

Users who have left logged-in comments on your work will also still be able to delete their comments.

How to turn off comments on individual works

In the "Privacy" section of the posting and editing forms for individual works, you will find a set of options called "Who can comment on this work." It will have three options:

• Registered users and guests can comment
• Only registered users can comment (this is equivalent to the old "Disable anonymous commenting" option)
• No one can comment

By default, it is set to "Registered users and guests can comment." To prevent anyone from commenting on your work, choose "No one can comment" and save your changes.

How to turn off comments on multiple works

If you'd like to change the comment settings for more than one work at a time, you can use the Edit Multiple Works page. (Please refer to "How do I edit multiple works at the same time?" for information on accessing this page and selecting works to edit.)

Once you've chosen the works you want to edit, locate the "Settings" section of the form. There will a set of options called "Who can comment on these works," and it will have four choices:

• Keep current comment settings
• Registered users and guests can comment
• Only registered users can comment (this is equivalent to the old "Disable anonymous comments" option)
• No one can comment

By default, it is set to "Keep current comment settings." To prevent anyone from commenting on the works you are editing, choose "No one can comment" and save your changes.

Other options for controlling comments on your works

Please check out our Comments and Kudos FAQ for more information on controlling comments on your works, including:

• Can I edit or delete a comment someone else left on one of my works?
• What can I do if I receive spam/harassing/offensive comments from an Archive user?
• How do I moderate comments on my works?

Update 15 August 06:22 UTC: These changes are now live!

Do you want to rescue at-risk fan archives? Would you like to assist AO3 users by resolving complaints? The Organization for Transformative Works is recruiting!

We're excited to announce the opening of applications for:

• Open Doors Staff - closing 13 May 2020 at 23:59 UTC or after 30 applications
• Policy & Abuse Staff - closing 13 May 2020 at 23:59 UTC

We have included more information on each role below. Open roles and applications will always be available at the volunteering page. If you don't see a role that fits with your skills and interests now, keep an eye on the listings. We plan to put up new applications every few weeks, and we will also publicize new roles as they become available.

All applications generate a confirmation page and an auto-reply to your e-mail address. We encourage you to read the confirmation page and to whitelist our email address in your e-mail client. If you do not receive the auto-reply within 24 hours, please check your spam filters and then contact us.

If you have questions regarding volunteering for the OTW, check out our Volunteering FAQ.

Open Doors Staff

Are you interested in the rescue and preservation of fanworks? Enjoy coordinating projects and liaising with people? Still guiltily--or not so guiltily--love the first fanwork that opened your eyes to fandom?

Open Doors is a committee dedicated to preserving fanworks in their many native formats, and is looking for staffers to support this goal. The work we do preserves fan history, love, and dedication to fandom: we keep online archives from going down, divert fanzines from the trash, and more.

If you're interested, click on through for a fuller description of what we're looking for and the time commitment.

Please note: You must be 18+ in order to apply for this role.

Applications are due 13 May 2020 at 23:59 UTC

Policy & Abuse Staff

The AO3 Policy & Abuse Committee is dedicated to helping users deal with the various situations that may arise. We also handle any complaints that come in about content uploaded to the Archive of Our Own. The team determines if complaints are about legitimate violations of the Terms of Service, and what to do about them if they are; our major goals are to adhere to the TOS, to make our reasoning and processes as clear and transparent as possible, and to keep every individual case completely confidential. We work closely with other AO3 related committees such as Support and Content.

We are seeking people who are self-motivated, are patient in rephrasing explanations, can make and document decisions, cooperate within and outside of their team, and ask for help when it's needed. Staffers need to be able to handle complex and sometimes-disturbing content, and must be able to commit a sufficient amount of time to the team on a regular basis.

Policy & Abuse staffers are required to spend at least 10-15 hours a week handling committee work, though it often tends to be more. Please be sure you can handle the workload before applying.

Please note: You must be 18+ in order to apply for this role.

Applications are due 13 May 2020 at 23:59 UTC

Apply at the volunteering page!

Today’s post in the Archive of Our Own’s 10th anniversary series is from Matty, who has been with the AO3 since it launched. You’ll read in her contribution about the many departments she has been part of since she began volunteering with us 10 years ago. There have been a lot of long work hours, particularly for the volunteers who were with the OTW in the early days, and we are so grateful for Matty and all of the others who contributed their time to help us make AO3 a reality.

I joined the Organization for Transformative Works as a tag wrangler back in 2009. I had been following the development of the OTW and the Archive since their inception and was thrilled to be able finally to help in a concrete way.

Tag wrangling in those days was both exciting and nerve wracking! One wrong push of the button could cause havoc. Early wranglers may remember the frantic searching when we repeatedly lost the Justin Timberlake tag, the terror of sharing a single spreadsheet that tracked all the fandoms on the Archive and the volunteers who wrangled them (and the screaming when someone sorted the sheet while others were trying to type), and the many, many, many long discussions that took place on our mailing lists while we tried to write our policies.

After Tag Wrangling I moved to Support, before sliding over to the Policy and Abuse committee (PAC). It is funny to compare how much things have changed between now and then. For the first few years PAC received less than 50 tickets a year. Now we sometimes receive 50 tickets in an hour, or more! The types of reports we receive have also changed. Initially, the vast majority of reports were about plagiarism. These days we see more reports about non-fanworks (such as RP ads, fic searches, etc). The size of the committee has also grown enormously; when I joined we had 3-4 active volunteers and now we have over 40! While the work can be overwhelming at times, it has also been incredibly rewarding.

I am so incredibly proud of the Organization and its volunteers for making our projects so successful. While there have been some growing pains over the years, we've built something amazing that we all should feel proud of!