Galera Cluster
GitHub
HAProxy
Hound
reviewdog
Jira
NGINX
Memcached
RSpec
Ruby
RubyMine
Slack
Vagrant- Updated: <%=h @archive_faq.updated_at %> | <%= link_to 'Edit', edit_archive_faq_path(@archive_faq) %> + Updated: <%= h @archive_faq.updated_at %> + <% if Globalize.locale.to_s != "en" || policy(ArchiveFaq).full_access? -%> + | <%= link_to t(".edit"), edit_archive_faq_path(@archive_faq) %> + <% end %>
<%= ts("We're sorry, there are currently no entries in this category.") %>
+ <% if @archive_faq.questions.blank? %> +<%= t(".no_category_entries") %>
<% else %>- <%= ts("Screencast") %>: <%= link_to q.question, q.screencast.to_s %> + <%= t(".screencast") %> <%= link_to q.question, q.screencast.to_s %>
<% end %> <%= raw sanitize_field(q, :content) %> diff --git a/app/views/blocked/users/index.html.erb b/app/views/blocked/users/index.html.erb index 4d00f2877b4..55389bc142a 100644 --- a/app/views/blocked/users/index.html.erb +++ b/app/views/blocked/users/index.html.erb @@ -1,8 +1,8 @@<%= t(".title") %>
- <% end %> @@ -50,9 +40,6 @@ <%= render "bookmarks/bookmark_user_module", bookmark: bookmark %> - <% # recent bookmarks will be loaded up here if requested %> -<%= ts("Bookmark Tags:") %>
<% end %> <% unless bookmark.collections.blank? %><%= ts("Bookmark Collections:") %>
@@ -36,8 +36,8 @@ <% end %> <% if is_author_of?(bookmark) %> - <%= render :partial => 'bookmarks/bookmark_owner_navigation', :locals => {:bookmark => bookmark} %> + <%= render "bookmark_owner_navigation", bookmark: bookmark %> <% elsif logged_in_as_admin? %> - <%= render :partial => 'admin/admin_options', :locals => {:item => bookmark} %> + <%= render "admin/admin_options", item: bookmark %> <% end %> diff --git a/app/views/bookmarks/_bookmark_user_module.html.erb b/app/views/bookmarks/_bookmark_user_module.html.erb index c77b104ebfb..1be517f4d59 100644 --- a/app/views/bookmarks/_bookmark_user_module.html.erb +++ b/app/views/bookmarks/_bookmark_user_module.html.erb @@ -1,5 +1,6 @@ <% # expects "bookmark" %> diff --git a/app/views/chapters/_chapter_form.html.erb b/app/views/chapters/_chapter_form.html.erb index fb09245e1c6..06167adcceb 100644 --- a/app/views/chapters/_chapter_form.html.erb +++ b/app/views/chapters/_chapter_form.html.erb @@ -69,6 +69,11 @@<%= set_format_for_date(collection.updated_at) %>
<% if collection.all_moderators.length > 0%> diff --git a/app/views/collections/_form.html.erb b/app/views/collections/_form.html.erb index 35b79c0546e..07055c3a424 100644 --- a/app/views/collections/_form.html.erb +++ b/app/views/collections/_form.html.erb @@ -66,7 +66,7 @@-
<% unless @collection.new_record? %>
- - <%= image_tag(@collection.icon.url(:standard), size: "100x100", alt: @collection.icon_alt_text, skip_pipeline: true) %> + <%= collection_icon_display(@collection) %> <%= ts("This is the collection's icon.") %> <% end %> @@ -74,9 +74,9 @@
- <%= ts("Icons can be in png, jpeg or gif form") %>
- <%= ts("Icons should be sized 100x100 pixels for best results") %>
<%= link_to_unless_current(@collection.title, @collection) %>
-
<% comments.each do |comment| %>
- - <%= ts("Comment on") %> <%= link_to_comment_ultimate_parent(comment) %> + <%= comment_link_with_commentable_name(comment) %> <%= time_in_zone(comment.created_at) %>
-
diff --git a/app/views/comments/_comment_actions.html.erb b/app/views/comments/_comment_actions.html.erb
index 3a69b9f7f09..aecccb028da 100644
--- a/app/views/comments/_comment_actions.html.erb
+++ b/app/views/comments/_comment_actions.html.erb
@@ -1,6 +1,6 @@
<%= ts("Comment Actions") %>
--
+
- <%= frozen_comment_indicator %> <% end %> <% if can_reply_to_comment?(comment) %> -
- <%= add_cancel_comment_reply_link comment %> +
- <%= add_comment_reply_link comment %> <% end %> <% unless comment.unreviewed? %>
- <%= link_to ts("Thread"), comment %> - <% if comment.depth > 0 %> -
- - <%= link_to ts("Parent Thread"), comment_path(id: comment.thread) %> - - <% end %> + <% end %> + <% if comment.depth > 0 %> +
- <%= link_to ts("Parent Thread"), comment_path(id: comment.thread) %> <% end %> <% if can_freeze_comment?(comment) %>
- <%= freeze_comment_button(comment) %> @@ -35,7 +33,7 @@ <%= tag_comment_as_spam_link comment %> <% end %> - <% if comment.unreviewed? && is_author_of?(comment.ultimate_parent) %> + <% if can_review_comment?(comment) %>
- <%= button_to(ts("Approve"), review_comment_path(comment), method: :put) %> @@ -65,7 +63,7 @@ <% if can_reply_to_comment?(comment) %> <% # This is where the reply-to box will be added when "Reply" is hit, if the user has JavaScript. %> <% # If not, we will render the comment form if this is the comment we are replying to. %> - <% if params[:add_comment_reply_id] && params[:add_comment_reply_id] == comment.id.to_s %> + <% if focused_on_comment(comment) %>
- <%= link_to ts('Back to AO3 News Index'), admin_posts_path %> <% end %> - <% if @work && !is_author_of?(@work) && !blocked_by?(@work) %> + <% if @work && !is_author_of?(@work) && !blocked_by?(@work) && !logged_in_as_admin? %>
-
<%= form_for(:kudo, url: kudos_path, html: { method: 'post', id: 'new_kudo' }) do |kudo_form| %>
<%= kudo_form.hidden_field :commentable_id, :value => @work.id %>
@@ -113,6 +113,10 @@
<%= t(".blocked") %>
+ <% elsif logged_in_as_admin? %> ++ <%= t(".logged_as_admin") %> +
<% else %>diff --git a/app/views/comments/unreviewed.html.erb b/app/views/comments/unreviewed.html.erb index f9693567047..51ad90d82e6 100644 --- a/app/views/comments/unreviewed.html.erb +++ b/app/views/comments/unreviewed.html.erb @@ -1,26 +1,29 @@ -diff --git a/app/views/home/_privacy.html.erb b/app/views/home/_privacy.html.erb new file mode 100644 index 00000000000..066d28adff3 --- /dev/null +++ b/app/views/home/_privacy.html.erb @@ -0,0 +1,236 @@ +<%# IMPORTANT: Also update current_tos_version in application_controller %> +<%# To ensure proper formatting, this must always be rendered inside an element + with the userstuff class. The userstuff element must be inside an element with + the classes "docs system". %> +<%= ts("Unreviewed Comments on") %> <%= link_to(@commentable.commentable_name, @commentable) %>
+<%= t(".page_heading_html", commentable_link: link_to(@commentable.commentable_name, @commentable)) %>
-<%= ts('Please note that comments cannot be unapproved once you have reviewed them. After you delete any comments you do not wish to appear on your work, you can approve all that remain.') %>
+<%# i18n-tasks-use t("comments.unreviewed.note.admin_post") + i18n-tasks-use t("comments.unreviewed.note.work") %> +<%= t(".note.#{@commentable.model_name.i18n_key}") %>
<% if @comments.count > 0 %> <%= will_paginate @comments %> <% @comments.each do |comment| %> - <%= render :partial => 'comments/single_comment', :object => comment %> + <%= render partial: "comments/single_comment", object: comment %> <% end %> <%= will_paginate @comments %> <% else %> -<%= ts("No unreviewed comments.") %>
+<%= t(".no_unreviewed") %>
<% end %> - \ No newline at end of file + diff --git a/app/views/external_works/_blurb.html.erb b/app/views/external_works/_blurb.html.erb index 1a85e33a4e6..e9b33ee4820 100644 --- a/app/views/external_works/_blurb.html.erb +++ b/app/views/external_works/_blurb.html.erb @@ -42,12 +42,12 @@- <%= external_work.language.name %>
<% end %> <% if Bookmark.count_visible_bookmarks(external_work) > 0 %> -- <%= ts("Bookmarks") + ": " %>
-- <%= link_to_bookmarkable_bookmarks(external_work) %>
+- <%= Bookmark.model_name.human(count: :many) %>:
+- <%= link_to_bookmarkable_bookmarks(external_work) %>
<% end %> -- <%= ts("Related Works") + ": "%>
-- <%= link_to external_work.related_works.count.to_s, external_work %>
+- <%= RelatedWork.model_name.human(count: :many) %>:
+- <%= link_to number_with_delimiter(external_work.related_works.count), external_work %>
<% if policy(external_work).show_admin_options? %> diff --git a/app/views/external_works/_work_module.html.erb b/app/views/external_works/_work_module.html.erb index 52c3de7a505..28fc39142d4 100644 --- a/app/views/external_works/_work_module.html.erb +++ b/app/views/external_works/_work_module.html.erb @@ -19,7 +19,7 @@- <%= ts("This work isn't hosted on the Archive so this blurb might not be complete + <%= ts("This work isn't hosted on the Archive so this blurb might not be complete or accurate.") %>
@@ -49,12 +49,12 @@ <% end %> <% if Bookmark.count_visible_bookmarks(external_work) > 0 %> -- <%= ts("Bookmarks:") %>
-- <%= link_to_bookmarkable_bookmarks(external_work) %>
+- <%= Bookmark.model_name.human(count: :many) %>:
+- <%= link_to_bookmarkable_bookmarks(external_work) %>
<% end %> <% if external_work.related_works.count > 0 %> -- <%= ts("Related Works:") %>
-- <%= link_to external_work.related_works.count.to_s, external_work %>
+- <%= RelatedWork.model_name.human(count: :many) %>:
+- <%= link_to number_with_delimiter(external_work.related_works.count), external_work %>
<% end %> diff --git a/app/views/feedbacks/new.html.erb b/app/views/feedbacks/new.html.erb index aecfa301a66..43929090def 100644 --- a/app/views/feedbacks/new.html.erb +++ b/app/views/feedbacks/new.html.erb @@ -42,9 +42,6 @@ <%= form_for(@feedback, html: {class: "post feedback"}) do |f| %><%= t(".intro.archive_description") %>
++ <%= t(".intro.ao3_exists_to_host_html", + personal_information_link: link_to(t(".intro.personal_information"), "#III.A.1")) %> +
+-
+
- <%= t(".intro.host_your_fanworks") %> +
- <%= t(".intro.show_you_works") %> +
- <%= t(".intro.enable_post_information") %> +
+ <%= t(".intro.details_how_and_why_html", + common_questions_bold: tag.strong(t(".intro.answers_common_questions_html", + tos_faq_link: link_to(t(".intro.tos_faq"), tos_faq_path(anchor: "privacy_faq"))))) %> +
+ +<% unless local_assigns[:suppress_toc] %> + +<% end %> + +<%= t(".privacy_policy_heading") %>
+<%= t(".applicability.heading") %>
+-
+
<%= t(".applicability.policy_covers") %>
+ -
+
+ <%= t(".applicability.global_subprocessors_html", + subprocessors_link: link_to(t(".applicability.subprocessors"), + "https://www.transformativeworks.org/otw_tos/organization-for-transformative-works-subprocessor-list/")) %> +
++ <%= t(".applicability.transfers_necessary_html", consent_to_us_processing_bold: tag.strong(t(".applicability.consent_to_us_processing"))) %> +
+
+
<%= t(".information_scope.heading") %>
+-
+
-
+
+ <%= t(".information_scope.information_in_content_html", + content_link: link_to(t(".information_scope.content"), tos_path(anchor: "I.A.1")), + special_categories_link: link_to(t(".information_scope.special_categories"), "https://gdpr-info.eu/art-9-gdpr/")) %> +
+
+ <%= t(".information_scope.collect_through_use") %>
+
<%= t(".types_of_information.heading") %>
+-
+
-
+
<%= t(".types_of_information.emails.heading") %>
+<%= t(".types_of_information.emails.collect_process_retain") %>
++ <%= t(".types_of_information.emails.address_usage_html", + challenge_link: link_to(t(".types_of_information.emails.challenge"), archive_faq_path("glossary", anchor: "challengedef"))) %> +
+<%= t(".types_of_information.emails.unsubscribe") %>
+
+ -
+
+ <%= t(".types_of_information.ip_addresses.heading") %> + <%= t(".types_of_information.ip_addresses.text") %> +
+
+ -
+
+ <%= t(".types_of_information.logs.heading") %> + <%= t(".types_of_information.logs.text") %> +
+
+ -
+
+ <%= t(".types_of_information.cookies.heading") %> + <%= t(".types_of_information.cookies.text") %> +
+
+ -
+
+ <%= link_to t(".types_of_information.fnok.heading"), archive_faq_path("fannish-next-of-kin") %> + <%= t(".types_of_information.fnok.text") %> +
+
+ -
+
+ <%= t(".types_of_information.other_information.heading") %> +
+<%= t(".types_of_information.other_information.to_maintain_integrity") %>
++ <%= t(".types_of_information.other_information.to_make_content_available_html", + tos_faq_link: link_to(t(".types_of_information.other_information.tos_faq"), tos_faq_path(anchor: "feature_information"))) %> +
+
+
<%= t(".aggregate_anonymous_info.heading") %>
+-
+
<%= t(".aggregate_anonymous_info.understand_ao3_usage") %>
+ <%= t(".aggregate_anonymous_info.anonymous_non_personal") %>
+
<%= t(".your_rights.heading") %>
+-
+
-
+
+ <%= t(".your_rights.request_data_html", + applicable_jurisdiction_link: link_to(t(".your_rights.applicable_jurisdiction"), tos_faq_path(anchor: "privacy_rights"))) %> +
+
+ -
+
+ <%= t(".your_rights.potential_other_rights_html", + other_rights_link: link_to(t(".your_rights.other_rights"), tos_faq_path(anchor: "privacy_rights_faq"))) %> +
+
+ <%= t(".your_rights.require_user_specific_proof") %>
+
+
-
+
<%= t(".third_parties.do_not_sell_information") %>
+ <%= t(".third_parties.third_party_tools") %>
+ -
+
<%= t(".third_parties.sharing_exceptions.intro") %>
+-
+
-
+
+ <%= t(".third_parties.sharing_exceptions.external_processing.heading") %> + <%= t(".third_parties.sharing_exceptions.external_processing.html", + subprocessor_list_link: link_to(t(".third_parties.sharing_exceptions.external_processing.subprocessor_list"), "https://www.transformativeworks.org/otw_tos/organization-for-transformative-works-subprocessor-list/")) %> +
+
+ -
+
+ + <%= t(".third_parties.sharing_exceptions.challenge_signup.heading_html", + challenge_link: link_to(t(".third_parties.sharing_exceptions.challenge_signup.challenge"), archive_faq_path("glossary", anchor: "challengedef"))) %> + + <%= t(".third_parties.sharing_exceptions.challenge_signup.text") %> +
+
+ -
+
+ + <%= t(".third_parties.sharing_exceptions.open_doors_import.heading_html", + open_doors_link: link_to(t(".third_parties.sharing_exceptions.open_doors_import.open_doors"), "https://opendoors.transformativeworks.org/")) %> + + <%= t(".third_parties.sharing_exceptions.open_doors_import.text") %> +
+
+ -
+
+ <%= t(".third_parties.sharing_exceptions.handle_complaints.heading") %> + <%= t(".third_parties.sharing_exceptions.handle_complaints.html", + dmca_notice_link: link_to(t(".third_parties.sharing_exceptions.handle_complaints.dmca_notice"), tos_faq_path(anchor: "dmca_complaint")), + pac_confidentiality_policy_link: link_to(t(".third_parties.sharing_exceptions.handle_complaints.pac_confidentiality_policy"), "https://www.transformativeworks.org/committees/policy-abuse-confidentiality-policy/")) %> +
+
+
+ -
+ <%= t(".third_parties.sharing_exceptions.legal_reasons.heading") %>
+ <%= t(".third_parties.sharing_exceptions.legal_reasons.intro") %>
+
-
+
- <%= t(".third_parties.sharing_exceptions.legal_reasons.legally_compelled") %> +
- <%= t(".third_parties.sharing_exceptions.legal_reasons.good_faith_comply") %> +
- <%= t(".third_parties.sharing_exceptions.legal_reasons.cooperating_law_enforcement") %> +
<%= t(".third_parties.sharing_exceptions.legal_reasons.law_enforcement_cooperation_details") %>
+<%= t(".third_parties.sharing_exceptions.legal_reasons.attempt_to_notify") %>
+
+
+ -
+
<%= t(".account_termination.heading") %>
+-
+
-
+
+ <%= t(".account_termination.deletion_after_termination_html", + terminate_your_account_link: link_to(t(".account_termination.terminate_your_account"), archive_faq_path("your-account", anchor: "deleteaccount"))) %> +
+-
+
-
+
+ <%= t(".account_termination.orphans_excluded_html", + orphan_link: link_to(t(".account_termination.orphan"), archive_faq_path("orphaning")), + pseud_link: link_to(t(".account_termination.pseud"), archive_faq_path("pseuds", anchor: "whatisapseud"))) %> +
+
+ -
+
+ <%= t(".account_termination.backup_copies_html", + general_principles_link: link_to(t(".account_termination.general_principles"), tos_path(anchor: "I.E.2"))) %> +
+
+
+ -
+
<%= t(".account_termination.legal_enforcement_retention") %>
+
<%= t(".retention_of_information.heading") %>
+<%= t(".retention_of_information.text") %>
+ +<%= t(".contact_us.heading") %>
++ <%= t(".contact_us.html", + contact_pac_link: link_to(t(".contact_us.contact_pac"), new_abuse_report_path)) %> +
+ +
+<%= t(".effective") %>
++ + <%= t(".license_html", + terms_of_service_link: link_to(t(".terms_of_service"), tos_path), + content_policy_link: link_to(t(".content_policy"), content_path), + privacy_policy_link: link_to(t(".privacy_policy"), privacy_path), + cc_attribution_4_0_international_link: link_to(t(".cc_attribution_4_0_international"), + "https://creativecommons.org/licenses/by/4.0/", + rel: "nofollow")) %> + +
diff --git a/app/views/home/_tos.html.erb b/app/views/home/_tos.html.erb index 629b0dc173c..817776b8fbf 100644 --- a/app/views/home/_tos.html.erb +++ b/app/views/home/_tos.html.erb @@ -1,545 +1,350 @@ -<% # IMPORTANT: Also update current_tos_version in application_controller %> --+<% end %> diff --git a/app/views/home/_tos_navigation.html.erb b/app/views/home/_tos_navigation.html.erb new file mode 100644 index 00000000000..6f325eb2ff5 --- /dev/null +++ b/app/views/home/_tos_navigation.html.erb @@ -0,0 +1,9 @@ + diff --git a/app/views/home/about.html.erb b/app/views/home/about.html.erb index 50fd2578967..bab98d13fd8 100644 --- a/app/views/home/about.html.erb +++ b/app/views/home/about.html.erb @@ -1,17 +1,21 @@ -The Archive of Our Own is a place for fanworks, including fan fiction based on books, TV, movies, comics, other media, and real-person fiction (RPF).
- -What We Believe
--
-
- Our goal is maximum inclusiveness (refer to the ToS FAQ) of content. Our software is open-source and available for others to use if they wish to implement the code elsewhere. -
- We are committed to defending fanworks against legal challenges. Our position on transformative fanworks is detailed in the OTW FAQ. We have legal resources and alliances on which we can draw. However, that is not a guarantee that the organization can or will fight each battle. The Board will take into account a variety of factors, both legal and otherwise, in responding to a legal challenge. Further information is available on the OTW site. -
- We do not sell the data that you post on, submit to or share on "OTW Sites" (transformativeworks.org, archiveofourown.org and fanlore.org) to third parties, and we do not include or accept paid advertisements from third parties. Each of the OTW Sites has Terms of Service and a Privacy Policy that explains what information we collect, how we use it and who we share it with; your use of any of the OTW Sites is governed by that site's Terms and Policy. -
- We strive to make each OTW Site's Terms of Service (ToS) and Privacy Policy readable. We have tried to provide explanations for the more unusual legal terms. If you have terminology questions not covered here, Law.com's glossary may help, though we cannot vouch for the accuracy of outside sources, including those referenced in the ToS. -
There are five parts to the Terms of Service (ToS):
- - -I. General Principles
- -A. The legalese: including where a lawsuit would be filed, when, and under what law
-The ToS constitute the entire agreement between you and the Organization for Transformative Works (OTW) and govern your use of the Archive of Our Own service (hereinafter "Service", "AO3" or "Archive"). It takes the place of all prior agreements between you and the OTW concerning your use of the Service. It does not govern your use of other OTW sites and/or projects including the OTW site itself, Fanlore, or Transformative Works and Cultures, or donations to or membership in the OTW, or OTW elections, all of which are covered under separate agreements hosted on each of the OTW Sites.
-The AO3 ToS, the relationship between you and the OTW, and all disputes arising out of or related to it, shall be governed by the laws of the United States and specifically the State of New York (refer to the ToS FAQ), without regard to its conflict of law provisions.
- -You and the OTW agree to submit to the personal and exclusive jurisdiction of the courts located within New York County (Manhattan), New York, and to waive any objection to the laying of venue there.
-The OTW's failure to enforce any part of the ToS will not waive the OTW's ability to enforce it, and any waiver with regard to a specific instance shall not constitute a waiver of any other breaches of the ToS, even with regard to the same user.
-If any provision of the ToS is found by a court of competent jurisdiction to be invalid, you agree that the court should give effect to the party's intentions as reflected in the provision, and that the other provisions of the ToS remain in full force and effect.
-You agree that, regardless of any statute or law to the contrary, any claim or cause of action arising out of or related to use of the Archive or the ToS must be filed within one (1) year after such claim or cause of action arose or be forever barred.
- -B. You agree to the Terms of Service
--
-
-
-
Archive Of Our Own hosts and shares content created by fans, for fans. Our Privacy Policy is a part of these Terms of Service and is contained in Section III of these Terms of Service. By submitting a work, comment, image, tag, item of information including personally identifying information like an email address, User Name, link, embedded image, audio file or video, or any other form of content ("Content") to the Archive, or by creating a User Account and/or by viewing any Content on the Archive, you affirm, confirm and state that you comply with and assent to the ToS, which incorporates the AO3 Privacy Policy.
-
- -
-
We may update the ToS as necessary. If the ToS change at any time after May 25, 2018, this is how the process will work: Changes in the ToS may be proposed at any time by or to the OTW Board. Proposed changes will be prominently disclosed on the Service, and we will offer at least a two-week comment period for proposed changes. At the end of the comment period, proposed changes will be voted on by the Board. If the Board votes in favor, the changes will become effective at that time. You can learn about changes in the ToS by visiting the Service.
-Subject to amendments of the update process by the OTW Board, this is the only means by which the Terms of Service may be altered. The Terms of Service cannot be changed by, e.g., emails or oral communications with you.
-
-
C. Potential problems with the Service
--
-
-
-
The OTW provides services, including the Archive of Our Own, on an "as is" and "as available" basis. The OTW does not warrant (that is, does not make a legally binding promise) that our services will meet your requirements; that our services will be uninterrupted, timely, secure, or error-free; or that the results you get from using the services will be accurate, reliable, or satisfactory to you. We will endeavor to provide the best possible service to users of the Service, but many things (e.g., possible outages, hackings, etc.) are not within our control and we cannot provide for all eventualities. In the event we learn of a breach of personally identifying information that users have submitted to the Service, we will notify affected users as soon as practicable.
-
- -
-
Any material you download, view, or otherwise access through the Service is at your own risk. You will be solely responsible for any damage or loss of data that results from the download of any such material.
-
- -
-
The OTW expressly disclaims all warranties of any kind, whether express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose and non-infringement. The ToS govern your use of the Service, and therefore no communication from anyone associated with the OTW will create any warranty that isn't expressly stated in the ToS.
-
- -
-
You expressly agree that the OTW shall not be liable to you for any damages of any kind (even if the OTW has been advised of the possibility of such damages) resulting from the Service, including but not limited to your use of or inability to use the Service; unauthorized access to or changes in Content or information you submit; and the acts and statements of third parties who use the Service.
-
- -
-
You agree that the OTW shall not be liable to you or any third party for any termination of or limitation on your access to AO3. The OTW may change, end, or put on hiatus the Service, or parts of its Services, at any time.
-
- -
-
You agree that the OTW shall not be liable to you for any claim arising out of Content you make available, your use of the Service, your connection to the Service, your use of the ToS, or your violation of any rights of another.
-In other words, the OTW is not liable to you for allowing you to post Content, download Content, use the Service, or interact with AO3. The OTW does not assume whatever legal risks you face by posting, viewing, or doing other things with Content.
-
-
D. What you can't do:
-You agree not to use the Service (as well as the e-mail addresses and URLs of OTW sites):
--
-
-
-
to make available any Content or work that violates the Content Policy;
-
- -
-
to impersonate any person or entity, including, but not limited to, an AO3 or OTW representative or volunteer, or falsely state or otherwise misrepresent your affiliation with a person or entity (fiction marked as such, including real-person fiction in first-person format, is not subject to this policy);
-
- -
-
to forge headers or otherwise manipulate identifiers in order to disguise the origin of any Content transmitted to or through the Service or any OTW Content, sites, servers, networks, or services (headers and identifiers are defined as information actually used or intended to be used to route or authenticate Content, and do not include Content that simulates identifiers as part of a story, such as a fictional e-mail exchange);
-
- -
-
to make available any Content that a court has ruled constitutes patent, trademark, trade secret or copyright infringement (please be aware of the OTW's position on fanwork legality);
-
- -
-
to make available any unsolicited or unauthorized advertising (defined as solicitations for direct or indirect commercial advantage), junk mail, spam, chain letters, pyramid schemes, or any other form of solicitation;
-
- -
-
to make available any material that contains software viruses or any other computer code, files or programs designed to interrupt, destroy or limit the functionality of any computer or hardware or telecommunications equipment;
-
- -
-
to interfere with or disrupt the Service, any OTW-hosted Content or sites, servers, Services or networks connected to OTW sites;
-
- -
-
to create an account if you are a resident or national of any country to which the U.S. has prohibited transactions by mandating a trade embargo, as detailed further by the State Department;
-
- -
-
to create an account if you are under the age of thirteen;
-
- -
-
to create an account if you are: between the ages of 13 and 16, and a resident or citizen of a country, including a European Economic Area country that states an age that is older than yours is required to consent to the processing of personal data without our obtaining written permission from a parent or legal guardian under the General Data Protection Regulation ("GDPR").
-A list of countries that apply the GDPR can be found here. Each user is responsible for knowing the laws of their own country.
-
- -
-
to use OTW services to break any law that applies to you, including any rules or regulations having the force of law. Just by way of example, do not use the services to disseminate restricted technologies or violate laws governing the export of technical data. This provision is not intended to deal with matters subject to the Content Policy, but the Content Policy cannot cover every law in every country. As a general matter, the Archive follows US law. Content that is alleged to violate the law of a relevant jurisdiction will be dealt with according to the procedures established in the Abuse Policy.
-
-
E. Content you see through use of the Service:
--
-
-
-
The OTW or users of its services may provide links to or content via sites that are owned or controlled by third parties, and may use such sites, including Twitter and Tumblr, to communicate information about the OTW and its family of sites. The OTW has no control over such sites or their terms of use or privacy policies, and you agree that the OTW is not responsible for and does not endorse their content, terms or availability.
-
- -
-
While we limit the types of embedded content visible or accessible via Archive-hosted Content, some of the content and/or works that you see displayed at the Archive are not hosted on the Archive or by the OTW. Such embedded content can include videos, tweets, images that are hosted by third-party sites, or audio files ("User-Embedded Content"). If you access a page that includes User-Embedded Content, the content file may share data with the hosted site as if you were on or at the hosted site. Although all visible Content, including embedded images or other works, must comply with our Content Policy, User-Embedded Content is not otherwise governed by these Terms of Use or the Archive Privacy Policy, and instead is covered by the Terms of Use and/or Privacy Policy of the service that hosts the User-Embedded Content. The Archive reserves the right to provide an indicator to users that User-Embedded Content is present on or visible via your Content.
-
- -
-
You understand that the OTW does not prescreen Content or review it for purposes of compliance with the ToS. This includes but is not limited to work information, a work's content, text, graphics, comments, or any other material. Content, including User-Embedded Content, is the sole responsibility of the submitter. You understand that using the Archive may expose you to material that is offensive, triggering, erroneous, sexually explicit, indecent, blasphemous, objectionable, grammatically incorrect, or badly spelled.
-
- -
-
You recognize that the OTW does not endorse Content on the Archive in any way, except when material appears as an official statement of the OTW. No committee members, officers, or directors of the OTW are acting in an official capacity when they post fanworks, commentary, or other Content of the type generally provided by site users.
-
- -
-
The OTW is not liable to you for any Content to which you are exposed on or because of the Archive.
-
-
F. Valid e-mail address:
--
-
-
-
As part of your registration, you agree to provide an accurate and current e-mail address and to update the address as necessary. If your e-mail address is inaccurate or not current, the Archive may suspend your account. Content provided by suspended accounts before the suspension will not be removed unless the OTW Board reasonably believes that presence/inclusion of said Content exposes the Archive and/or the OTW to liability.
-
- -
-
We reserve the right to share your e-mail address with the owners and/or moderators of any Challenges that you sign up for, and during Open Doors importation where the email address you provided on your AO3 account matches an email address that you used in connection with a non-AO3 collection that is being imported into AO3, your email address may be shared with the entity that manages the work(s) that is/are being imported onto AO3 through an Open Doors process.
-
- -
-
By registering or otherwise using an e-mail address in connection with the Archive, you assert that the e-mail address is not listed on any child protection registry. (There are child protection registries in Michigan and Utah, and our policy applies to any others that exist or may be adopted, whether local, state, or national, including any outside the U.S.)
-
-
G. What we do with Content:
-The OTW does not claim any ownership or copyright in your Content. Repeat: we do not own your Content. Nothing in this agreement changes that in any way. Running the Archive, however, requires us to make copies, and backup copies, on servers that may be located anywhere around the world.
--
-
-
-
You agree that we can make those copies and show your Content to other people, subject to your privacy settings. Specifically, by submitting Content, you grant the OTW a world-wide, royalty-free, nonexclusive license to make your Content available. "Making available" includes distributing, reproducing, performing, displaying, compiling, and modifying or adapting (refer to the ToS FAQ).
-Modifying and adapting here refer strictly to how your work is displayed—not how it is written, drawn, or otherwise created. But because your Content may be transmitted over various networks, we may have to make changes to the formatting or display of your Content in order to adapt to the technical requirements of different networks or devices. Multimedia content may not display properly on all devices. In some circumstances, we may make changes to improve accessibility. For example, we may automatically convert html tags to our standard forms (e.g., changing "bold" html to "strong"). Or we may make special provisions for accessibility, such as allowing you to use nonstandard fonts but also providing an alternate format for those who cannot read such fonts. We may use an internal search engine whose results display relevant snippets from your Content.
-User-provided tags are subject to organization, which is a process we call tag wrangling; for a full explanation of tag wrangling, refer to the ToS FAQ.
-
- -
-
Subject to the next paragraph of this policy, this license exists only for as long as you choose to continue to include such Content on the Archive and will terminate within a reasonable time after you remove or the OTW removes such Content from the Archive. We will always strive to make your Content unavailable to users as soon as possible should you choose to remove it. Though removed Content will not be publicly available, for legal and disaster recovery purposes we may retain backup copies for longer periods.
-
- -
-
You may provide Content to a part of the Archive that you do not completely control. For example, you may decide to participate in a challenge run by another user. Or you may provide Content to a part of the Archive where your Content can be deleted by other users, for example a Comments page. Where this is the case, by submitting Content to those parts of the Service, you agree to the rules for removing and retaining such Content on those parts of the Service.
-
- -
-
You acknowledge and agree that the OTW may preserve Content and may disclose Content if required to do so by law or in the good faith belief that such preservation or disclosure is reasonably necessary to: comply with legal process; enforce the ToS; respond to claims that any Content violates the rights of third parties; or protect the rights, property, or personal safety of the OTW services' users and the public.
-
-
H. Data and Content Processing
- -AO3 and the OTW exist to host Content by creative people like you. In order to host or share your works, as well as comments, Kudos and whatever you put into your User Profile, we have to process certain data and information including personally identifying information that we collect from Users, and that each User inputs. In order to operate the site, host OTW and user Content, and prevent technical issues and breaches, we need to process (e.g. collect, store, retrieve, disseminate, make available, and delete) certain data and information including personally identifying information, also known as "Personal Data". Personal Data includes your username, your email address, your IP information and any personally identifying information you enter on the Archive, including information that you put into your profile, a work's notes or tags, into the body of a work or other Content itself.
- -By using the site, you consent to our collection, processing, retention and display of your Content as set forth and explained in these Terms of Use so we can operate, manage, display and share the creativity on AO3; if we believe that using, retaining and/or sharing that information is necessary to preserve the integrity of the Archive and the Content that we host; for legitimate legal and/or accounting audit purposes; when we have a good faith belief it is required by law, such as pursuant to a subpoena or other legal process; or when we have a good faith belief that doing so will help prevent imminent harm to someone.
- -II. Archive Age Policy
-This Age Policy covers the Archive's treatment of (a) users who are residents or citizens of the European Union and of the age where consent of a parent or legal guardian is required for the processing of personal data of children including email addresses and IP addresses, as well as certain uses of cookies; and (b) users who are under the age of thirteen (13) and residents or citizens of any other country.
-In compliance with United States regulations regarding online privacy for children, the Archive does not knowingly solicit or collect information from children under the age of thirteen (13). Children under the age of thirteen (13) are therefore not permitted to have an account or upload Content of any type to the Archive. By submitting Content to the Archive, you thereby confirm that you are thirteen (13) years old or older (refer to the ToS FAQ).
-Asking a parent or legal guardian to upload Content does not constitute submitting Content under this policy. If you are under the age of thirteen (13) and not an Age-Barred Individual (as defined below), your parent or legal guardian may upload your Content through their account.
-We as an organization have opted to protect teen users' privacy. As a result, we cannot receive or host Content from individuals that we know are under the age of sixteen (16) and residents/citizens of the European Union, unless they are residents/citizens of the EU countries that allow the collection of Special Categories of Personal Data from those at a younger age and are old enough to consent to the collection of Special Categories of Personal Data in their own country. Any individual who is between the ages of 13 and 16 and a resident or citizen of a country, including a European Economic Area country, that states an age that is older than theirs is required to consent to the processing of personal data without our obtaining written permission from a parent or legal guardian under the GDPR ("Age-Barred Individual") may not maintain accounts or submit Content. AO3 Personnel may, in their reasonable discretion, hide and/or delete accounts held by and/or Content submitted by Age-Barred Individuals.
- -III. Archive Privacy Policy
-A. Who runs the Archive
-The Archive is a project of the Organization for Transformative Works (OTW), which is committed to fan privacy. For more information about how you can support the OTW, please see the OTW Website. This Privacy Policy governs the Archive.
- -B. This TOS, including the Privacy Policy, applies only to the Archive
-This Privacy Policy covers the Archive's treatment of personally identifying information submitted to us, and which we collect when you use our services in the course of ordinary communications. Each site or Service hosted by the OTW has its own Terms of Service and Privacy Policy. The OTW or users of its Services may provide links to or content via sites that are owned or controlled by third parties, and may use such sites, including Twitter and Tumblr, to communicate information about the OTW and its family of sites including the Archive. The OTW has no control over such sites or their terms of use or privacy policies, and you agree that the OTW is not responsible for and does not endorse their content, terms or availability. If you follow links off the Archive, you should review those sites' privacy policies, which may be different, and for which the Archive takes no responsibility.
- -C. About possible changes:
-If these Terms of Service and/or this Privacy Policy change at any point in the future, we will post the policy changes to the Archive of Our Own. Such changes will be used only for information provided by those who have visited, used, or accessed the Service after the effective date of such policy changes. If you are concerned about how your information is used, you should check back at the Archive site periodically to review the policies.
- -D. Archive adherence to the TOS:
-If you feel that this Service is not following its stated information policy, please contact Archive Personnel.
- - -E. What we will do:
--
-
-
-
Any information you include in your work, comment, profile, bookmark, summary, or other Content, including information about your religious views, political views or your sexual identity, or any personally identifying information such as your email address, location, or account User Name for other sites will be accessible by the general public if the Content is marked public, and by Archive users and personnel if the Content is marked accessible to Archive users only. If you save the Content in Draft form, it will be accessible by certain Archive personnel.
-
- -
-
We may collect personally identifying information such as your IP address and e-mail address when you request an Archive invitation, register for a user account with the Archive, visit any of the sites and services that are part of the OTW family of sites, or use any of the Archive's Services. We may use third-party services to store, process, or transmit data, or perform other technical functions related to operating the Service. These services may include spam detectors, backup services, icon hosting, and e-mail services; a list of third-party services is provided in our Subprocessor List. We cannot guarantee other services' performance. We or the services we use may store or process your personally identifying information in data centers which may be located in the United States or other countries.
-
- -
-
We will use your email address internally for purposes of managing AO3 and maintaining site integrity; if you agree to allow your email address to be public, it will be public and you can change that setting any time. You can choose to leave it private, or make it public on the Site; if you opt to make it public, everyone has the ability to access it and use it for any purpose. We may occasionally send emails to you from the Archive about your Content and account, the Archive and our fundraisers, as well as news that we reasonably believe to be of interest to our registered users; we will send you your invitation to register for the Archive via email as well. By creating and maintaining a User Account on and with AO3, you consent to receiving such emails, including fundraising emails. We reserve the right to send you notice of complaints raised against you, or alleged violations by you of the Terms of Service, as well as to reply to any email message you send to the Archive and/or its personnel. If you choose to participate in a Challenge, the Challenge maintainer(s) may have access to your e-mail address for purposes of communicating with you (See Section V.I.a. below for discussion of Challenges).
-
- -
-
We collect, process and retain the following data for the following reasons:
--
-
-
-
E-mail Addresses: We collect email addresses of and from those who communicate with us via email and any Content or Personal Data included in emails to us. We need this information so we can respond to you, and so we can handle complaints about the Service and any users who may have violated the Terms of Use or other policies, and for other legal and accounting/audit reasons including maintaining the integrity of the Archive and the Content that we host;
-
- -
-
User-Specific Information: We collect information about what pages users access or visit including your interactions with integral Archive features such as Kudos, Comments, Bookmarks and the tags that you "favorite", as well as referral information (i.e. data about what site you are coming to the Archive from) and whether there are errors in displaying Content to you. We need this information to maintain the integrity of the site, the Service and the Content that we host; to provide you with the Content that you are seeking; to minimize "gaming" Kudos counts and spam; and for other legal and accounting/audit reasons.
--
-
-
-
You consent to our collection, processing, retention and display of your Content, including personal data, when you upload a work in a manner that is available to all Archive users, or the general public, depending on which you choose. We need such consent because your purpose in and reason for uploading Content to the Archive is for that Content to be visible to users, and if you opt to, for it to be visible to the general public.
-
- -
-
You consent to our collection, processing and retention of your Content, and personal information connected therewith, including display to you and certain Archive personnel when you upload a work in "Draft" form. We need such consent because your purpose in and reason for uploading such Draft Content to the Archive is for that Content to be accessible to you at a later date. In order for that Content to be available to you, it also needs to be accessible to those on the Archive team who have access to our servers, and to the Board, Policy & Abuse and Legal committees if necessary to enforce these Terms of Service and maintain the integrity of the Service.
-
- -
-
You consent to our collection, processing, retention and display of personal information and Content you submit for inclusion on your Profile Page. We need such consent because your purpose in and reason for including information in your Profile is for that Content to be visible to the general public.
-
- -
-
You consent to our collection, processing, retention and display of text that you submit as Comments, as well as your personal information associated therewith. We need such consent because your purpose in and reason for submitting a Comment is for that Content to be visible to the general public.
-
- -
-
When you are logged in, you consent to our collection, processing, retention, display and use of your User Name as well as our association of it with Kudos that you submit. We need such consent because your purpose in and reason for submitting Kudos is for that Content to be visible to the general public.
-
- -
-
Whether you are logged in or not, you consent to our collection, processing, retention and use of your IP address for a limited time, including when you give Kudos. We need this consent because your purpose in and reason for submitting Kudos is to engage publicly with the Content that you enjoyed without publicly associating your Kudos with a User Name, and you wish for such Kudos to be publicly visible and disassociated from your Archive Account, if you have one; and because we endeavour to count only one view of a URL per cookie session on the "Hit" count for a work. Temporarily collecting, processing, and retaining IP addresses permits us to conduct internal management of Kudos and Hits.
-
-
- -
-
-
-
IP Addresses: we collect and process the IP addresses of Archive visitors, including registered users. We need this information so we can provide you with the Content that you are requesting, to allow you to submit Comments, Content and Profile information, and leave Kudos, and for other legal and accounting audit reasons including maintaining the integrity of the Archive and the Content that we host. Certain IP information may be collected by the server for log purposes and used for limited technical assessments of the Service.
-
- -
-
Logs: We collect and process Logs of server interactions, as well as event logs. We need this information for legal and accounting/audit reasons, including maintaining the integrity of the Archive and the Content that we host.
-
- -
-
Cookies: We use cookies to collect and store visitors' preferences; customize web pages' content based on visitors' browser type or other information that the visitor sends; and record activity at the Archive in order to provide better service when visitors return to our site. Cookies must be enabled for the Archive to function properly with your computer. The Archive has no access to cookies set by other sites.
-
- -
-
If for any reason you terminate your user account with us, we will destroy active records containing your Personal Data as soon as reasonably possible. "Reasonably" here means no more than thirty business days from the termination of the account; however, we may have to retain some information for a longer period as legal records or for auditing purposes. If we terminate your service, we may retain enough information to prevent you from signing up for the service in the future. If you delete Content from the Archive, it will not be recoverable.
-
- -
-
If we receive a complaint about a violation of someone's intellectual property rights, we reserve the right to disclose the information provided by the rightsholder or the rightsholder's representative to the subject of the complaint. If we receive a complaint about other matters, such as plagiarism or harassment, we will follow the Abuse Policy, which explains what information provided by the complainant may be disclosed to the subject of the complaint.
-
-
- -
-
F. What we will not do:
--
-
-
-
The OTW will not provide any third party with any of your personal information or any of the information we collect, except as provided under our Terms of Service. We will not use your personally identifying information to market third party products and services to you via the Archive.
-
- -
-
We will not sell, trade, or rent your personally identifying information. Except as provided under this policy, we will not disclose your personally identifying information to any third party without your prior consent unless we (1) are legally compelled to do so, (2) have a good-faith belief that such action is necessary to comply with a current judicial proceeding, a court order, or legal process served on the OTW, or (3) are cooperating with law enforcement authorities. As to (3), we will cooperate with all investigations conducted by law enforcement authorities within the United States of America when legally required to do so. Cooperation with law enforcement authorities from other countries and cooperation when it is not legally required are at our sole discretion. Our discretion looks favorably on freedom and justice, and unfavorably on oppression and violence.
-
- -
-
Unless legally prohibited, we will attempt to notify you any time we disclose your personally identifying information to a third party. In some cases, the information we have, such as an IP address, may be insufficient for us to notify you.
-
-
IV. Content and Abuse Policies
-We recognize that there is no such thing as a popular abuse policy. By their nature, abuse complaints are unpleasant at best. And policy needs to be applied by people, which always complicates matters. We have tried to set out clear procedures to minimize and channel the inevitable conflicts.
-The Content and Abuse Policy covers procedures, spam and commercial promotion, threatening the technical integrity of the site, copyright, plagiarism, personal information and fannish identities, harassment, illegal and non-fanwork content, and ratings and warnings. We have developed a FAQ page to answer additional questions about Content and Abuse (refer to the ToS FAQ).
-The Archive does not prescreen for content. Complaints are investigated only when they are submitted through the appropriate channels and with the appropriate information.
- -A. Procedures
--
-
- Submitting a complaint
-
Complaints may be submitted to our Policy & Abuse team. Except in the case of copyright complaints, a complainant may submit a complaint via the Policy & Abuse web form. Depending on the nature of the complaint, anonymity of the complainant may hinder our ability to examine and/or verify the complaint. In order for personnel to follow up on any allegation, the exact location (URL) and nature of the alleged violation must be supplied in the original complaint. Repeated unverified complaints from the same source may be subject to summary rejection.
-
- - Treatment and investigation of complaints
-
Only people who need to know about a complaint will be informed about it. The details of any individual complaint are confidential and must be used only in resolving that complaint.
-The subject of a complaint may also be among those who need to know about it. Only information provided in the complaint will be passed on. The complainant has complete control over what information is submitted to Policy & Abuse, and can submit a complaint pseudonymously. (Legal names and other information sufficient to identify a person in the physical world will never be disclosed as part of a standard abuse complaint. For further clarification, please refer to our privacy policy.)
-In general, the Policy & Abuse team will only communicate with the subject of a complaint if there appears to be a violation of site policy, or if personnel need more information to resolve the issue.
-The Policy & Abuse team records the IP address from which each complaint is submitted, to prevent misuse of the system and/or Service.
-Subject to obligations of confidentiality about specific complaints, the Policy & Abuse team may release statistics about general trends, such as the number of plagiarism complaints made and the actions taken by the team, in public or to other OTW committees, to facilitate discussions of policies, procedures, and trends in complaints.
-When Policy & Abuse personnel determine that Content needs to be removed for reasons other than violation of the Age Policy by Age-Barred Individuals, the team will identify the nature of the problem with the Content, and set a deadline for voluntary removal of the Content. An administrator may also hide Content from other users where appropriate. If the original poster does not remove the Content within the deadline, the Archive will remove the Content. In addition, we may remove Content immediately, without waiting for a response, if we are contacted by a legitimate law enforcement agency or if we determine that the Content is threatening to an individual or reveals an individual's personal information without consent. In such cases we will inform the original poster as soon as possible. The original poster will then have the option to resubmit with the violating Content removed.
-The Policy & Abuse team may also determine that tags need to be added to or edited in an item of Content. For more information, please see the ratings/warnings section.
-If Content violating the ToS is posted with invalid contact information, it will be removed without prior notice.
-If the complainant requests notification of the resolution of the complaint and provides contact information, we will notify them.
-
- - Submitting an appeal
-
The complainant or the original poster may appeal a decision to the Policy & Abuse team as a whole. During the appeal, the original decision will remain in effect. We will attempt to resolve appeals as speedily as possible, but please remember that the Policy & Abuse team is entirely comprised of volunteers. The team's decisions are final unless overturned by the Board at the Board's sole discretion. There is no right of appeal to the Board. The team, however, may consult with the Board or with committee members authorized by the Board if the team decides that consultation would help resolve an issue.
-
- - Account statuses
-
"Account status" refers to the existence of warnings on an account and whether that account has been suspended, temporarily or permanently (refer to the ToS FAQ).
-The Policy & Abuse team may issue warnings when it determines that a violation of the ToS was minor or unintentional. More serious, intentional, or repeated violations of the ToS will trigger suspensions. A suspension will generally be for a defined period of time, such as a month. The team may also permanently suspend users when it determines that such action is justified. Permanent suspensions for violations other than spam, violation of the Archive's Age Policy by Age-Barred Individuals, or threatening the technical integrity of the site require a majority vote of the team. The team's discretion will be informed by the nature of the violation and the response of the user, including the user's decision to voluntarily remove, modify or edit the Content that violates the ToS.
-A user whose account has been permanently suspended for reasons other than age may not rejoin under another identity.
-Where possible, we encourage users to try mediating disputes before contacting Policy & Abuse. We provide tools for registered users to control Content that is uploaded in their own spaces. For example, users are able to delete comments on their own stories. If you are unable to resolve the problem on your own, you can file a complaint with the Policy & Abuse team.
-In some cases, objectionable Content may have already been deleted before the Policy & Abuse team acts. We appreciate good faith attempts to resolve disputes, and in most such cases will close the complaint with no further action. However, we reserve the right to consider individual circumstances, including whether the poster has engaged in a pattern of such conduct. In such cases, if we verify that the original Content violated the ToS, we may still decide to warn or suspend the original poster.
-Penalties apply to users, not to screen names/pseudonyms. Penalties are not retroactive: a suspended user's nonobjectionable Content will not be automatically removed unless the user is an Age-Barred Individual. Suspended users retain the right to delete or Orphan their fanworks by contacting Archive administrators.
-
-
B. Spam and commercial promotion
-Promotion of commercial products or activities is not allowed. Repeated identical or nearly identical posts in multiple places, e.g., a large number of identical comments promoting a website, will also be considered spam regardless of commercial content.
-Anything we determine is spam will be removed immediately. Users may be permanently suspended for spam the first time they post spam content.
-In general, unsolicited commercial activity is not permitted on the Archive. The Policy & Abuse team has discretion to decide that a fan-related offer was mistakenly disseminated and issue a warning instead of a suspension.
-Any spam- or commercial activity-related penalties may be appealed using the ordinary appeal process.
-We may use automated means to filter out spam. If you submit Content that is erroneously caught in a spam filter, please notify Archive administrators.
- -C. Threatening the technical integrity of the Service
-Conduct that threatens the technical integrity of the Archive, e.g. attempts to hack the Service or spread viruses through it, will result in an immediate account suspension and deletion of any Content that is hazardous to the operation of the Service or to users' computers. Users may be permanently suspended for threatening the technical integrity of the Archive the first time they do so. Such suspensions may be appealed using the ordinary appeal process.
-Uploading technically misnamed files or Content—e.g., non-image files with an image file extension used to disguise their actual format—constitutes a threat to the technical integrity of the site.
- -D. Copyright and Trademark
-Please be aware that the OTW believes that transformative fanworks are legal; therefore, complaints based merely on the existence of fanwork based on copyrighted content or mentioning trademarks will not be pursued.
-If you believe that your content has been reproduced in whole or in part, without transformative use (transformative use is defined by the OTW as adding something new, with a further purpose or different character, altering the source with new expression, meaning, or message), please follow our procedures for reporting copyright infringement.
-The report must clearly and specifically indicate the exact location (URL), nature, and extent of each instance of allegedly infringing content, as well as the exact copyrighted material that is being infringed, as well as full and complete contact information for the copyright holder and/or an authorized agent.
-Epigraphs and short quotations, including quotations from song lyrics and poetry, are allowed. Content that is set within or draws on an existing work is allowed. Reproductions of entire copyrighted works—whether songs, poems, transcripts, or other material—are not allowed without the consent of the copyright owner.
- -E. Plagiarism
-Plagiarism is an often-contested and fuzzy concept, and no definition will satisfy everyone. Our aim is to be transparent and fair in resolving disputes.
-Plagiarism is the use of someone else's words or concepts without properly attributing those words or concepts to their original source. Simply finding and replacing names, substituting synonyms, or rearranging a few words is not enough to make the work original to you. Deliberately writing a work using the same general idea as another work is not plagiarism, but citation is always appreciated. Generally, quotes from the source material (canon) on which the Content is based will not constitute plagiarism, nor will obvious allusions ("Use the Force, Luke!"). However, when in doubt, cite. Be aware that the Policy & Abuse team may decide that your citation is not sufficient to render the work your own; a mere nod to another author whose work you are presenting as your own may result in a judgment of plagiarism.
-Plagiarism is a violation of the ToS and will incur the penalties described in the Abuse Policy. As with all Content that violates the ToS, plagiarized Content must be removed. Depending on the type and amount of plagiarized Content, this might entail removing an entire piece of Content, removing only the plagiarized portions from a longer work while leaving the original material, or adding citations.
-If you believe a fanwork posted on the Archive plagiarizes another work, please report the work to the Policy & Abuse team. In order to allow us to investigate, please provide a link to the work on the Archive, relevant excerpts, and a specific citation of the original material (for example, a URL or a book edition and page number).
- -F. Personal information and fannish identities
--
-
-
-
The OTW is committed to protecting the privacy of our users, including the separation many fans choose to keep between their legal, "real life" names and their fannish pseudonyms. Unauthorized disclosure of a fan's personal information and/or data which is included within the definition of Special Categories of Personal Data violates the Terms of Service. For these purposes, "personal information" may include legal names and other information sufficient to identify a person in the physical world that they have not voluntarily shared on the Archive itself. "Personal information" may also include the identity of the creator of an Orphaned fanwork. The Archive reserves the right to delete, hide, mask or otherwise make unavailable to the general public any personal information and/or data which is included within the definition of Special Categories of Personal Data.
-
- -
-
If you are a resident or citizen of the European Community, you can request that the OTW assemble the data about you that it has in our archive, and provide a copy in electronic format to you; we agree to provide such data to you within a reasonable time.
-
-
G. Harassment
-Harassment is any behavior that produces a generally hostile environment for its target. This includes activities such as bullying and hazing by groups of people as well as personal attacks by individuals. Not everyone agrees about what is offensive and unacceptable. Individual users are encouraged to try to resolve problems on their own before contacting the Policy & Abuse team.
-Harassment is not allowed. Users engaging in this behavior may be warned, suspended, or permanently suspended as described in the general abuse procedure.
-When judging whether a specific incident constitutes harassment, the team will consider factors such as whether the behavior was repeated, whether it was repeated after the offender was asked to stop, whether the behavior was targeted at a specific person, whether that target could have easily avoided encountering the behavior, whether the behavior would be considered unacceptable according to normal community standards, etc. Additionally, making complaints that are both (a) repeated and (b) baseless, particularly those targeting a specific user, can be considered harassing behavior and may be deemed a violation of the ToS.
-While these complaints will be reviewed on a case by case basis, in general, threatening Content will be considered harassment, while Content that is merely annoying will be allowed. Please note that most statements like "X is a terrible actor and should die!" are not death threats. Writing a story where X dies as part of the plot is also not usually a death threat. Content that is harder to avoid (such as comments on the target's fanworks) will be judged more strictly than Content that is easily avoidable (such as stories).
-The behavior of the original poster (the complaint subject) may also affect the team's determination. If the original poster repeatedly contacts the subject of the Content about the Content after being told to stop, harasses the subject, or requests that others harass the subject, the Content may be considered part of a general pattern of harassment and be removed. Please use your best judgment both when producing Content of this type and when reporting it.
- -A special note on RPF (real-person fiction):
-Writing RPF (real-person fiction) never constitutes harassment in and of itself. However, Content that advocates specific, real harmful actions towards real people is not allowed. This includes, but is not limited to, death threats and requests for readers to harass specific people. If you find Content that you believe contains harassing or threatening material, please contact the Policy & Abuse team. As Real-Person Fiction is fictional, generally Archive policy will be that Content in RPF that would be deemed Personal Data and/or Special Categories of Personal Data (e.g. full names, usernames on social media services, city of residence, birth date) will not be considered as such. However, if information that is accurate, non-public and not that of the User is included (i.e. non-public phone numbers, residential addresses, email addresses or hotel room numbers) the work can be removed from public view by the Archive's Policy & Abuse team in its sole discretion.
- -H. Illegal and inappropriate Content
-The Archive of Our Own is a place for fanworks. Content may not be uploaded to OTW's servers if it contains or links to child pornography (images of real children); warez, cracks, hacks or other executable files and their associated utilities; trade secrets, restricted technologies, or classified information; or if it consists entirely of actual instruction manuals, technical data, recipes, or other non-fanwork content, including non-fanwork creative work (refer to the ToS FAQ). Uploading such Content is a violation of the ToS.
-We may determine that we need to remove Content to resolve a threatened or pending lawsuit or mitigate other liability. If so, we will remove the Content. Unless said Content or data otherwise violates the ToS or was submitted by an Age-Barred Individual, removal for such reasons will not lead to a suspension.
-If you believe Content violates a specific law, you may report it to us. Please, however, read our Offensive Content Policy below.
- -I. Offensive Content Policy
-As provided in part I.E.3 of the Terms of Service, the OTW is not liable to you for any Content to which you are exposed on or because of the Service.
-Unless it violates some other policy, we will not remove Content for offensiveness, no matter how awful, repugnant, or badly spelled we may personally find that Content to be. +<%# IMPORTANT: Also update current_tos_version in application_controller %> +<%# To ensure proper formatting, this must always be rendered inside an element + with the userstuff class. The userstuff element must be inside an element with + the classes "docs system". %> +
<%= t(".archive_description") %>
+ +<%= t(".what_we_believe.header") %>
+-
+
- + <%= t(".what_we_believe.our_goal_html", + maximum_inclusiveness_link: link_to(t(".what_we_believe.maximum_inclusiveness"), tos_faq_path(anchor: "max_inclusiveness"))) %> + +
- + <%= t(".what_we_believe.ao3_run_by_html", + defending_fanworks_link: link_to(t(".what_we_believe.defending_fanworks"), "https://www.transformativeworks.org/faq/#faq-legalfaq"), + on_the_otw_site_link: link_to(t(".what_we_believe.on_the_otw_site"), "https://www.transformativeworks.org/legal")) %> + +
- + <%= t(".what_we_believe.we_do_not_sell_html", + ao3_link: link_to("archiveofourown.org", root_path), + fanlore_link: link_to("fanlore.org", "https://fanlore.org/"), + transformativeworks_link: link_to("transformativeworks.org", "https://www.transformativeworks.org/")) %> + +
- + <%= t(".what_we_believe.readability_html", + tos_faq_link: link_to(t(".what_we_believe.tos_faq_html", + faq_abbreviation: tag.abbr(t(".what_we_believe.faq.abbreviated"), title: t(".what_we_believe.faq.full"))), + tos_faq_path)) %> + +
<%= t(".general_principles_heading") %>
+<%= t(".general_terms.heading") %>
+-
+
-
+
+ <%= t(".general_terms.agreement.html", + agreement: tag.strong(t(".general_terms.agreement.agreement")), + content_policy_link: link_to(t(".general_terms.agreement.content_policy"), content_path), + privacy_policy_link: link_to(t(".general_terms.agreement.privacy_policy"), privacy_path), + personal_information_link: link_to(t(".general_terms.agreement.personal_information"), privacy_path(anchor: "III.A.1")), + any_other_form_link: link_to(t(".general_terms.agreement.any_other_form"), tos_faq_path(anchor: "define_content"))) %> +
+
+ -
+
+ <%= t(".general_terms.entirety_of_agreement.html", + entirety_of_agreement: tag.strong(t(".general_terms.entirety_of_agreement.entirety_of_agreement"))) %> +
+
+ -
+
+ <%= t(".general_terms.jurisdiction.html", + jurisdiction: tag.strong(t(".general_terms.jurisdiction.jurisdiction")), + the_state_of_new_york_link: link_to(t(".general_terms.jurisdiction.the_state_of_new_york"), tos_faq_path(anchor: "ny_law"))) %> +
+
+ -
+
+ <%= t(".general_terms.non_severability.html", + non_severability: tag.strong(t(".general_terms.non_severability.non_severability"))) %> +
+
+ -
+
+ <%= t(".general_terms.limitation_on_claims.html", + limitation_on_claims: tag.strong(t(".general_terms.limitation_on_claims.limitation_on_claims"))) %> +
+
+ -
+
+ <%= t(".general_terms.no_assignment.html", + no_assignment: tag.strong(t(".general_terms.no_assignment.no_assignment"))) %> +
+
+
<%= t(".updates_to_the_tos.heading") %>
++ <%= t(".updates_to_the_tos.html", + content_policy_link: link_to(t(".updates_to_the_tos.content_policy"), content_path), + privacy_policy_link: link_to(t(".updates_to_the_tos.privacy_policy"), privacy_path)) %> +
+ +<%= t(".potential_problems.heading") %>
+-
+
<%= t(".potential_problems.service_as_is") %>
+ <%= t(".potential_problems.breach_notification") %>
+ <%= t(".potential_problems.own_risk") %>
+ -
+
+ + <%= t(".potential_problems.disclaim_warranties_html", + merchantability_link: link_to(t(".potential_problems.merchantability"), tos_faq_path(anchor: "merchantability")), + fitness_for_purpose_link: link_to(t(".potential_problems.fitness_for_purpose"), tos_faq_path(anchor: "fitness"))) %> + +
+
+ <%= t(".potential_problems.damage_liability") %>
+ <%= t(".potential_problems.account_termination_liability") %>
+ <%= t(".potential_problems.content_access_liability") %>
+ <%= t(".potential_problems.not_personal_storage_html", sole_backup_responsibility: tag.strong(t(".potential_problems.sole_backup_responsibility"))) %>
+
<%= t(".content_you_access.heading") %>
+-
+
<%= t(".content_you_access.external_links_html", here_link: link_to(t(".content_you_access.here"), "https://www.transformativeworks.org/where-find-us/")) %>
+ -
+
+ <%= t(".content_you_access.third_party_content_html", + hosted_by_third_party_link: link_to(t(".content_you_access.hosted_by_third_party"), tos_faq_path(anchor: "nontextual_fanworks")), + content_policy_link: link_to(t(".content_you_access.content_policy"), content_path), + privacy_policy_link: link_to(t(".content_you_access.privacy_policy"), privacy_path)) %> +
+
+ <%= t(".content_you_access.no_prescreen") %>
+ -
+
+ <%= t(".content_you_access.no_otw_endorsement_html", + official_statement_link: link_to(t(".content_you_access.official_statement"), tos_faq_path(anchor: "official_statement"))) %> +
+
+ <%= t(".content_you_access.otw_not_liable") %>
+
<%= t(".what_we_do_with_content.heading") %>
+<%= t(".what_we_do_with_content.no_copyright_ownership_html", we_repeat: tag.strong(t(".what_we_do_with_content.we_repeat"))) %>
+-
+
-
+
+ <%= t(".what_we_do_with_content.agree_otw_can_copy_html", + worldwide_royalty_free_nonexclusive_license_link: link_to(t(".what_we_do_with_content.worldwide_royalty_free_nonexclusive_license"), tos_faq_path(anchor: "nonexclusive_license")), + modifying_or_adapting_link: link_to(t(".what_we_do_with_content.modifying_or_adapting"), tos_faq_path(anchor: "modify_adapt")), + tag_wrangling_link: link_to(t(".what_we_do_with_content.tag_wrangling"), archive_faq_path("tags", anchor: "wrangling"))) %> +
+
+ <%= t(".what_we_do_with_content.license_duration") %>
+ -
+
+ <%= t(".what_we_do_with_content.content_not_completely_controlled_html", + orphan_link: link_to(t(".what_we_do_with_content.orphan"), archive_faq_path("orphaning")), + challenge_link: link_to(t(".what_we_do_with_content.challenge"), archive_faq_path("glossary", anchor: "challengedef")), + subject_to_moderation_link: link_to(t(".what_we_do_with_content.subject_to_moderation"), "https://www.transformativeworks.org/otw-news-post-moderation-policy/"), + rules_for_removing_such_content_link: link_to(t(".what_we_do_with_content.rules_for_removing_such_content"), tos_faq_path(anchor: "partial_control"))) %> +
+
+ -
+
+ <%= t(".what_we_do_with_content.some_content_open_doors_html", + open_doors_link: link_to(t(".what_we_do_with_content.open_doors"), "https://opendoors.transformativeworks.org/en/")) %> +
+
+ <%= t(".what_we_do_with_content.preserve_for_legal_reasons_html", privacy_policy_link: link_to(t(".what_we_do_with_content.privacy_policy"), privacy_path)) %>
+
<%= t(".what_you_cant_do.heading") %>
+<%= t(".what_you_cant_do.you_agree_not_to") %>
+-
+
-
+
+ <%= t(".what_you_cant_do.content_violating_policy_html", + content_policy_link: link_to(t(".what_you_cant_do.content_policy"), content_path)) %> +
+
+ -
+
+ <%= t(".what_you_cant_do.impersonate_person_or_entity_html", + impersonate_any_person_or_entity_link: link_to(t(".what_you_cant_do.impersonate_any_person_or_entity"), content_path(anchor: "II.G")), + function_link: link_to(t(".what_you_cant_do.function"), tos_faq_path(anchor: "impersonate_function"))) %> +
+
+ <%= t(".what_you_cant_do.forge_identifiers") %>
+ -
+
+ <%= t(".what_you_cant_do.copyright_infringement_html", + infringement_of_a_copyright_link: link_to(t(".what_you_cant_do.infringement_of_a_copyright"), content_path(anchor: "II.D")), + position_on_fanwork_legality_link: link_to(t(".what_you_cant_do.position_on_fanwork_legality"), "https://www.transformativeworks.org/faq/#faq-WhydoestheOTWbelievethattransformativeworksarelegal")) %> +
+
+ -
+
+ <%= t(".what_you_cant_do.commercial_activity_html", + making_available_any_advertising_link: link_to(t(".what_you_cant_do.making_available_any_advertising"), content_path(anchor: "II.C"))) %> +
+
+ <%= t(".what_you_cant_do.software_viruses") %>
+ -
+
+ <%= t(".what_you_cant_do.interfere_disrupt_ao3_html", + interfere_disrupt_ao3_link: link_to(t(".what_you_cant_do.interfere_disrupt_ao3"), content_path(anchor: "technical_integrity"))) %> +
+
+ -
+
+ <%= t(".what_you_cant_do.account_if_age_barred_html", + age_barred_individual_link: link_to(t(".what_you_cant_do.age_barred_individual"), "#age")) %> +
+
+ -
+
+ <%= t(".what_you_cant_do.resident_embargo_country_html", + comprehensive_trade_embargo_link: link_to(t(".what_you_cant_do.comprehensive_trade_embargo"), tos_faq_path(anchor: "trade_embargo"))) %> +
+
+ <%= t(".what_you_cant_do.break_applicable_law") %>
+
<%= t(".registration_and_email_addresses.heading") %>
+-
+
-
+
+ <%= t(".registration_and_email_addresses.agree_current_address_html", + suspend_your_account_link: link_to(t(".registration_and_email_addresses.suspend_your_account"), tos_faq_path(anchor: "invalid_email"))) %> +
+
+ -
+
+ <%= t(".registration_and_email_addresses.email_is_yours_html", + lawfully_communicate_with_you_link: link_to(t(".registration_and_email_addresses.lawfully_communicate_with_you"), privacy_path(anchor: "III.C.1"))) %> +
+
+
<%= t(".age_policy.heading") %>
+<%= t(".age_policy.intro") %>
+-
+
- <%= t(".age_policy.individuals_under_13") %> +
-
+ <%= t(".age_policy.individuals_under_16") %>
+
-
+
- + <%= t(".age_policy.eu_country_html", + special_categories_of_personal_data_link: link_to(t(".age_policy.special_categories_of_personal_data"), "https://gdpr-info.eu/art-9-gdpr/")) %> + +
- <%= t(".age_policy.country_disallowing_childrens_data") %> +
+
+ <%= t(".age_policy.age_barred_not_permitted_html", + not_permitted_account_upload_link: link_to(t(".age_policy.not_permitted_account_upload"), tos_faq_path(anchor: "age_faq"))) %> +
+<%= t(".age_policy.addressing_violations") %>
+<%= t(".age_policy.ask_parent_to_upload") %>
+ +<%= t(".abuse_policy.heading") %>
++ <%= t(".abuse_policy.no_prescreen_html", + content_policy_link: link_to(t(".abuse_policy.content_policy"), content_path)) %> +
++ <%= t(".abuse_policy.answers_common_questions_html", + tos_faq_link: link_to(t(".abuse_policy.tos_faq"), tos_faq_path(anchor: "policy_procedures_faq"))) %> +
+-
+
-
+ <%= t(".abuse_policy.submitting_a_complaint.heading") %>
+
+ <%= t(".abuse_policy.submitting_a_complaint.html", + policy_and_abuse_form_link: link_to(t(".abuse_policy.submitting_a_complaint.policy_and_abuse_form"), new_abuse_report_path), + dmca_policy_link: link_to(t(".abuse_policy.submitting_a_complaint.dmca_policy"), dmca_path)) %> +
+
+ -
+ <%= t(".abuse_policy.treatment_of_complaints.heading") %>
+
+ <%= t(".abuse_policy.treatment_of_complaints.html", + privacy_policy_link: link_to(t(".abuse_policy.treatment_of_complaints.privacy_policy"), privacy_path), + pac_confidentiality_policy_link: link_to(t(".abuse_policy.treatment_of_complaints.pac_confidentiality_policy"), + "https://www.transformativeworks.org/committees/policy-abuse-confidentiality-policy/")) %> +
+
+ -
+ <%= t(".abuse_policy.resolution_of_complaints.heading") %>
+
+ <%= t(".abuse_policy.resolution_of_complaints.administrators_determine_content_removal_html", + determine_removal_link: link_to(t(".abuse_policy.resolution_of_complaints.determine_removal"), + tos_faq_path(anchor: "determine_removal"))) %> +
++ <%= t(".abuse_policy.resolution_of_complaints.potentially_legitimate_fanwork_html", + illegal_and_inappropriate_content_policy_link: link_to(t(".abuse_policy.resolution_of_complaints.illegal_and_inappropriate_content_policy"), + content_path(anchor: "II.K"))) %> +
+<%= t(".abuse_policy.resolution_of_complaints.voluntary_removal") %>
++ <%= t(".abuse_policy.resolution_of_complaints.add_or_edit_tags_html", + mandatory_tags_policy_link: link_to(t(".abuse_policy.resolution_of_complaints.mandatory_tags_policy"), + content_path(anchor: "II.J"))) %> +
+<%= t(".abuse_policy.resolution_of_complaints.immediate_removal") %>
+
+ -
+ <%= t(".abuse_policy.penalties.heading") %>
+
+ <%= t(".abuse_policy.penalties.violations_warnings_suspensions_html", + tos_faq_link: link_to(t(".abuse_policy.penalties.tos_faq"), tos_faq_path(anchor: "penalty"))) %> +
++ <%= t(".abuse_policy.penalties.open_doors_removal_html", + content_policy_ii_k_1_link: link_to(t(".abuse_policy.penalties.content_policy_ii_k_1"), content_path(anchor: "II.K.1"))) %> +
++ <%= t(".abuse_policy.penalties.remove_resolve_lawsuit_html", + age_barred_individual_link: link_to(t(".abuse_policy.penalties.age_barred_individual"), "#age")) %> +
++ <%= t(".abuse_policy.penalties.non_violating_content_html", + illegal_inappropriate_content_policy_link: link_to(t(".abuse_policy.penalties.illegal_inappropriate_content_policy"), + content_path(anchor: "II.K"))) %> +
+<%= t(".abuse_policy.penalties.edit_post_while_suspended") %>
+
+ -
+ <%= t(".abuse_policy.appeals.heading") %>
+
+ <%= t(".abuse_policy.appeals.html", + appeal_decision_link: link_to(t(".abuse_policy.appeals.appeal_decision"), tos_faq_path(anchor: "appeal"))) %> +
+
+
+ +<% unless local_assigns[:suppress_footer] %> +<%= t(".effective") %>
++ + <%= t(".license_html", + terms_of_service_link: link_to(t(".terms_of_service"), tos_path), + content_policy_link: link_to(t(".content_policy"), content_path), + privacy_policy_link: link_to(t(".privacy_policy"), privacy_path), + cc_attribution_4_0_international_link: link_to(t(".cc_attribution_4_0_international"), + "https://creativecommons.org/licenses/by/4.0/", + rel: "nofollow")) %> +
- -J. User Icons
-User icons should be appropriate for general audiences. They should not contain depictions of genital nudity or explicit sexual activity. For more information, please refer to the ToS FAQ.
- -K. Tags
--
-
- Introduction
-
-
-
- We will not require specific ratings or warnings. However, a creator who chooses not to use ratings or warnings on a fanwork must signal this choice (refer to the ToS FAQ). -
- By default, all users will see the Archive warnings and tags the creator has selected. Any logged-in user who wishes to avoid Archive warnings and tags may set preferences to hide them by default. Logged-in users who set their preferences to hide information are proceeding at their own risk and may be exposed to Content they would otherwise wish to avoid. Such users may change their preferences, or reveal information for specific stories, at any time. -
- Logged-in users may set their preferences to indicate that they are willing to see mature or explicit content. -
- Other users, including users who are not registered users of the Service, who follow a link to a fanwork rated mature, explicit, or "not rated," will be asked to agree to see mature, explicit, or unrated Content. The Archive software will remember a non-registered user's choice during that user's visit, but will not retain the setting for future visits. -
- - Ratings
-
-
-
-
-
The Archive uses the following ratings, or the equivalent text as specified on the creator upload form:
--
-
- General audiences. -
- Teen and up audiences. -
- Mature. -
- Explicit. -
- Not rated. -
- -
-
As a rule, the creator controls the rating.
-In response to a complaint, the Policy & Abuse team may decide that a "general" or "teen" rating is misleading. In such cases, the creator may be required to change the rating. If the creator declines or fails to respond, the team may hide the work, set the rating at "not rated," or take any other appropriate action, but it will not add any other rating.
-
- -
-
The meaning of "not rated":
-Fanworks labeled "not rated" may be treated, for purposes of searching, screening, and other Archive functions, like "explicit"-rated fanworks. Thus, users may be asked to agree that they have chosen to access the fanwork before proceeding to the fanwork.
-
-
- -
-
- Warnings and Archive Warnings
-
-
-
-
-
General description:
-There are two components to warnings on the Archive.
--
-
- Archive warnings: Creators can select from a list of Archive warnings. The list also allows creators to select "choose not to use Archive warnings" and "none of these warnings apply," or equivalent text as specified on the creator upload form. -
- Secondary (optional or additional) tags, including warnings: Creators can define their own tags, as seriously or as humorously as they like. These can include specific content warnings. The warnings policy only covers Archive warnings. -
- -
-
As a rule, the creator controls the warnings.
-Selecting "choose not to use Archive warnings," or the equivalent text as specified on the creator upload form, satisfies a creator's obligation under the warnings policy. If a fanwork uses this option, we will not sustain any failure-to-warn complaints. If the Policy & Abuse team receives a failure-to-warn complaint in other circumstances, the team may decide the absence of a specific Archive warning is misleading. In such cases, the creator may be asked to add a warning or to select the choose not to warn option. If the creator declines or fails to respond, the team may hide the work, set the warning to indicate that the creator has chosen not to warn, or take any other appropriate action, but it will not select any other warning.
-
- -
-
The meaning of "choose not to use Archive warnings" or equivalent text:
-The fanwork may or may not contain any of the subject matter on the Archive list. Users who wish to avoid specific elements entirely should not access fanworks marked with "choose not to use Archive warnings." A creator can select both "choose not to use Archive warnings" and one of the Archive warnings in order to warn for some but not all of the Archive warnings.
-
-
- -
-
- Consequence of failure to use an appropriate rating or Archive warning
-
In general, failure to use an appropriate rating or Archive warning is not a violation of the abuse policy.
-It is our policy to defer to creators' categorizations, but we reserve the right to recategorize a fanwork in the situations described above.
-A recategorization decision is appealable through the ordinary appeals process.
-A recategorization of a fanwork will not result in suspension of a user's account, unless it is a repeated pattern for a single user, in which case it may be treated as grounds for a suspension. Moreover, if a creator unilaterally reverses a recategorization, without agreement from the Policy & Abuse team, that will be treated as grounds for a suspension.
-
- - Fanwork types
-
It is our policy to defer to creators' categorizations, but we reserve the right to recategorize a fanwork type.
-A manual recategorization decision made by the Policy & Abuse team is appealable through the ordinary appeals process.
-A manual recategorization of a fanwork will not result in suspension of a user's account, unless it is a repeated pattern for a single user, in which case it may be treated as grounds for a suspension. Moreover, if a creator unilaterally reverses a manual recategorization, without agreement from the team, that will be treated as grounds for a suspension.
-
- - General tags
-
Some tags may be automatically applied to a work. It is our policy to defer to creators' categorizations, but we reserve the right to manually recategorize language and other Archive tags, including fandom tags. A manual recategorization or removal of a tag will not result in suspension of a user's account, unless it is a repeated pattern for a single user, in which case it may be treated as grounds for a suspension. Moreover, if a creator unilaterally reverses a manual recategorization or removal, without agreement from the team, that will be treated as grounds for a suspension.
-
-
V. Assorted Policies
-A. Collections, Challenges, and Exchanges
--
-
-
-
Archive users may create Collections and encourage other users to submit fanworks to those Collections. The Collection maintainer can set any constraints they want on the Collection, including rules about anonymous works (see A.4 below) but must otherwise follow AO3 Content policy (e.g., if the Collection Content is explicit, it should be marked as "explicit" or "choose not to rate"). The Collection maintainer may be able to ask users for suggestions for new fanworks ("prompts"), gather prompts, match participants with prompts (including contacting them via the contact information provided to the Archive or to the Collection maintainer), and show the prompts on the Archive, following the general rules governing works on the Archive. Where Collection rules allow, prompts may be anonymous or limited-visibility, as detailed in A.4 and A.5 below.
--
-
-
-
A Challenge is a form of AO3 Collection. A Challenge maintainer can communicate with Challenge participants. The Challenge maintainer may have access to participants' email addresses for this purpose.
-
-
- -
-
-
-
To be part of a Collection, created on AO3 the fanwork creator has to affirmatively submit the fanwork to the Collection. The Collection maintainer will be able to remove the fanwork from the Collection, but not from the Archive.
-
- -
-
If the Collection maintainer has specified in advance in the Collection rules that submissions cannot later be removed from the Collection, the user who submitted the fanwork may not be able to delete it, but will be able to Orphan the Content it so that the user's identity is no longer associated with the Content.
-
- -
-
In order to implement certain types of Collections, the Archive may allow works to be posted without making the creator generally visible (which we call anonymous works).
--
-
- Anonymous works are not Orphan works, though they can be Orphaned. -
- The creator's pseudonym will not be publicly associated with the work while the anonymity is in place. For non-Orphaned works, the creator's pseudonym will be visible to administrators (including members of the Policy & Abuse team for purposes of resolving complaints), co-creators (if any), and the maintainers of any Collection of which the work is a part. -
- If the Collection of which a work is a part specifies rules regarding anonymity, such as a designated time for revealing authorship, the Collection maintainer may be able to control the work's anonymity consistent with those rules. In other situations, creators may be able to choose anonymity. -
- -
-
In order to implement certain types of Collections, the Archive may allow works to be posted which will not be generally visible until a time set by the Collection maintainer.
--
-
- Once posted, the work will be visible to administrators (including members of the Policy & Abuse team for purposes of resolving complaints), co-creators (if any), and the maintainers of any Collection of which the work is a part. -
- If the collection of which a work is a part specifies rules regarding time of general visibility, the Collection maintainer may be able to control the time at which a work becomes generally visible to Archive users. -
- -
-
In the absence of an independent violation of the abuse policy, the Archive will not intervene in decisions by the Collection maintainer.
-
-
B. Fannish next-of-kin
-Registered Archive users may designate a fannish next-of-kin. A next-of-kin agreement allows the transfer of Content maintenance in the case of a user's permanent incapacitation or death.
-Both parties to the agreement must be registered users of the Archive.
-The Archive's role in this agreement is only to act as a facilitator. If the person designated as the fannish next-of-kin activates the agreement by sending a message to the Archive, the Archive will not do any independent investigation to confirm the necessity for the transfer.
-A fannish next-of-kin agreement is confidential and accessible only by designated members of the Archive team, who may only use it for purposes of implementing the agreement.
- -C. Orphaning Content and Deleting Data
--
-
- Definition of Orphaning
-
One of the goals of the OTW and the Archive is to provide a permanent long-term home for fanworks. We also understand that circumstances can arise in which creators wish to remove their stories from the internet or otherwise dissociate themselves from their work. Our Archive software gives creators the ability to anonymize or "Orphan" fanworks along with the option of deleting them from the Archive. For a more detailed description of Orphaning, please see <%= link_to "About Orphaning", archive_faq_path("orphaning") %>.
-
- - User-controlled Orphaning
-
Users will have the ability to delete or Orphan their Content themselves as long as they have a valid AO3 account, including the account password and/or access to the e-mail address connected with that AO3 account. Users will be able to have passwords e-mailed to them and to change the e-mail addresses associated with accounts. However, a user who has lost a password and has no access to the e-mail associated with the account may be unable to access the account for any purpose, including Orphaning or deletion, unless the user can verify identity in some other way, as described below.
-
- - Caution: Orphaning may be difficult or impossible to reverse.
-
If a user affirmatively Orphans Content, any connection between the user and the work will be removed. It therefore may be difficult or even impossible to restore the link between an Orphaned Content and a user.
-
- - Linking an author with an Orphaned work
-
As part of the OTW's commitment to privacy, users are not allowed to use comments or tags to publicly identify the creator of an Orphaned work after the work has been Orphaned. Users who add public identifying tags or comments after a work has been Orphaned violate the Archive's Terms of Service. Additionally, identifying tags or comments will be removed.
-
- -
-
If the creator has an account, it is the creator's responsibility to delete any comments that personally identify said creator that are associated with the work, prior to Orphaning it, and to inform the Policy & Abuse team of any identifying tags that should be deleted. If the creator does not have an account, it is the creator's responsibility to identify any comments and/or tags that should be deleted as part of a request for Orphaning (see Policy on unverified identities and Orphaning or deletion below).
-
- - Policy on unverified identities and Orphaning or deletion
-
Our policy is that creators should be able to Orphan or delete Content, and they should also be protected against claims by non-creators. Deleting Content is a user's way of withdrawing consent for AO3 to continue hosting said Content. We provide creators with several alternative methods of confirming source, including using the e-mail address associated with the fanwork; using information from a creator's own site or journal; or using an e-mail address or other form of contact associated with a different copy of the fanwork, including on the Internet Archive. We will also consult with the maintainer of any collection of which the fanwork is a part and take any other actions that seem likely to help with verification.
-If the source of the request is confirmed, we will comply with the request. When the link between the source of the request and the fanwork's creator cannot be confirmed, and attempts to contact the fanwork's creator through any existing contact information receive no response, we will Orphan the fanwork.
-
- - Deleting Your Account
-
-
-
-
-
Deletion of an account is a way for a user to withdraw their consent for AO3 to continue hosting their Content. -
-
- -
-
If you delete Content, such Content will be unrecoverable via the Service.
-
-
- -
-
D. Open Doors
-Please note: these terms are designed for agreements between the OTW and owners/maintainers of archives/collections of fanworks that were originally hosted on third-party sites.
-The Open Doors project of the Organization for Transformative Works is dedicated to preserving fanworks for the future.
-We are happy to help maintainers of typical fanfic archives preserve or back up their collections by transferring the contents of their archive into the Archive of Our Own. Other fannish projects that cannot be integrated into the Archive may also be preserved as special collections, resources permitting. Both kinds of projects may be featured on the Open Doors page.
- -ToS for Open Doors projects
--
-
- Maintainer Consent
-
The OTW will only preserve collections with the full consent of the maintainer of the collection. The current maintainer of the project must agree to the Open Doors ToS, agree to any other conditions of the import, and grant us access to a copy of the current contents of the collection. The maintainer must also transfer ownership of the domain name or follow Open Doors' instructions if they want URL redirects, and if such redirects are possible. (Domain name transfer is not necessary if the maintainer is merely backing up an Archive within the Archive of Our Own.)
-
- - Transfer of Project
-
When the Open Doors Committee and the current owner of the collection have decided to import an archive or a special collection under the Open Doors project, the current owner will provide a copy of the current contents and take any other steps necessary to carry out the transfer.
-Typically, fanwork archives will be imported into the Archive of Our Own under a collection named after the original archive.
-
- - URLs for Open Doors Project
-
For collections not hosted on the Archive itself, the special collection or project may be available under subdirectories or subdomains of an OTW site.
-We may also preserve the original project's domain name.
-Archives that have been integrated into the Archive of Our Own will also be listed in the Open Doors gallery.
-
- - Role of Original Maintainer
-
The original maintainer of an archive that has been imported to the Archive of Our Own will be invited to moderate their archive's collection within the Archive of Our Own with all the powers that a collection owner in the Archive usually has; so, for instance, to decide whether a new work fulfills their collection's rules, or should be removed from the collection.
-If the collection's maintainer no longer wants to work on the collection, they can designate a new maintainer for the collection, or close the collection to new submissions. Should someone volunteer or request to maintain a closed collection, Open Doors will attempt to contact the original maintainer to find out if they are interested in transferring the collection. If the original maintainer does not respond with approval, ownership of the collection will not be transferred.
-
- - Collection Policy
-
Where possible, the existing policies of the collection will be preserved, even if they differ from the policies of the Archive of Our Own. Specifically, collections (whether integrated into the Archive of Our Own or preserved as special collections) can have limits on fandom, subject matter, sexual content, etc. that do not apply to Archive Content generally. Open Doors collections may be mixed fan and non-fanworks; when we accept a mixed collection, the entire collection can be added to the Archive, and the standard prohibition on non-fanworks will not apply to the collection. However, the OTW retains the right to remove Content from its servers if the Board deems removal necessary for specific legal reasons, or if the Content violates the Content Policy (other than the prohibition on non-fanwork content).
-Control over individual fanworks contained within a collection rests with their creators. If the verified creator of any individual fanwork contained within a collection requests its removal or alteration, the OTW will always comply with such a request in a reasonable period of time. We will also provide mechanisms allowing creators to claim their fanworks from such a collection and if desired to attach them to a new or existing Archive of Our Own account, edit them, Orphan them, or delete them.
-
- - Parting from the OTW
-
As noted in section 5, control over individual fanworks contained within a collection always rests with their creators. This section applies to collections as a whole. If the collection's original maintainer decides that they no longer want to be affiliated with the OTW, or the OTW board decides they no longer wish to work with the original maintainer, the following procedures for dissolution will apply:
--
-
-
-
Open Doors will delete the imported archive's collection on AO3. Any works imported to the AO3 already claimed, Orphaned, or anonymized by AO3 users will remain in the Archive under control of the creators' accounts, or the Orphan account. Open Doors will work with the original maintainer to delete any unclaimed works.
-
- -
-
OTW will give the original maintainer a copy of the archive backup given to the Open Doors Committee, if available.
-
- -
-
OTW will not be responsible for helping the maintainer set up elsewhere.
-
- -
-
OTW will place an announcement on the Open Doors page indicating that the original maintainer has moved to a new location, with a link to the new location if provided by the maintainer.
-
- -
-
These ToS are written assuming a single maintainer for a collection. If there are multiple active maintainers of a collection, they must all agree before the OTW will bring the collection into Open Doors. If some but not all of the maintainers later wish to part from the OTW, those who wish to do so can continue to work with the collection on the OTW servers, while the OTW will follow provisions b. and c. for any maintainers who wish to move the collection elsewhere. However, the OTW will retransfer any domain names only to maintainers who were formerly registered owners of the domain names at issue. For active collections, maintainers can use whatever dispute resolution procedure they work out between themselves, provided that they otherwise comply with OTW policies.
-
-
The goal of these rules is to be clear about how special collections and other extant fannish projects might come under the OTW umbrella while still preserving the autonomy both of the original maintainer and of the OTW. We want to provide a permanent home to projects, and preserve the results of our efforts, without the original maintainer feeling like they are giving up all control.
-
- -
-
- General provisions
-
Matters not specifically addressed in this Open Doors Agreement will be governed by the OTW Terms of Service.
-
-
-Material in this draft has been drawn from Slashcity, NearlyFreeSpeech.Net, Vox Populli, imeem.
-Approved: 23 May 2018
-<%= ts('About the') %> "><%= ts("OTW") %>
+<%= t(".heading.html", otw: tag.abbr(t(".heading.otw"), title: t(".heading.otw_long"))) %>
-diff --git a/app/views/home/content.html.erb b/app/views/home/content.html.erb new file mode 100644 index 00000000000..86050371429 --- /dev/null +++ b/app/views/home/content.html.erb @@ -0,0 +1,20 @@ + +<%= ts("The Organization for Transformative Works (OTW) is a nonprofit organization, established by fans in 2007, to serve the interests of fans by providing access to and preserving the history of fanworks and fan culture in its myriad forms. We believe that fanworks are transformative and that transformative works are legitimate.") %>
-<%= ts("We are proactive and innovative in protecting and defending our work from commercial exploitation and legal challenge. We preserve our fannish economy, values, and creative expression by protecting and nurturing our fellow fans, our work, our commentary, our history, and our identity while providing the broadest possible access to fannish activity for all fans.") %>
-<%= ts("The Archive of Our Own offers a noncommercial and nonprofit central hosting place for fanworks using open-source archiving software.") %>
-<%= ts("Our other major projects include:") %> +
<%= t(".general") %>
+<%= t(".details") %>
+<%= t(".ao3.html", + github_repository_link: link_to(t(".ao3.github_repository"), "https://github.com/otwcode/otwarchive"), + jira_project_link: link_to(t(".ao3.jira_project"), "https://otwarchive.atlassian.net/browse/AO3")) %>
+<%= t(".major_projects.title") %>
-
-
- <%= ts("%{fanlore}, a fandom wiki devoted to preserving the history of transformative fanworks and the fandoms from which they have arisen.", :fanlore => link_to(ts("Fanlore"), "http://fanlore.org")).html_safe %> -
- <%= ts("%{legal_advocacy} committed to protecting and defending fanworks from commercial exploitation and legal challenge.", :legal_advocacy => link_to(ts("Legal Advocacy"), "http://transformativeworks.org/projects/legal")).html_safe %> -
- <%= ts("%{open_doors}, which offers shelter to at-risk fannish projects.", :open_doors => link_to(ts("Open Doors"), "http://opendoors.transformativeworks.org")).html_safe %> -
- <%= ts("%{twc}, a peer-reviewed academic journal -that seeks to promote scholarship on fanworks and practices.", :twc => link_to(ts("Transformative Works and Cultures"), "http://journal.transformativeworks.org/index.php/twc")).html_safe %> +
- <%= t(".major_projects.fanlore_details_html", fanlore_link: link_to(t(".major_projects.fanlore"), "https://fanlore.org")) %> +
- <%= t(".major_projects.legal_details_html", legal_advocacy_link: link_to(t(".major_projects.legal_advocacy"), "https://transformativeworks.org/projects/legal")) %> +
- <%= t(".major_projects.open_doors_details_html", open_doors_link: link_to(t(".major_projects.open_doors"), "https://opendoors.transformativeworks.org")) %> +
- <%= t(".major_projects.twc_details_html", twc_link: link_to(t(".major_projects.twc"), "https://journal.transformativeworks.org/index.php/twc")) %>
<%= ts("You can find out more about the OTW and its projects at its website, %{transformative_works}, and learn about how your financial support is vital to the continuation and expansion of the OTW's work on its %{faq}. If you have a media or research question, please contact the %{communications_team}.", :transformative_works => link_to(ts("transformativeworks.org"), "http://transformativeworks.org"), :faq => link_to(ts("FAQ page"), "http://transformativeworks.org/faq"), :communications_team => link_to(ts("Communications team"), "http://transformativeworks.org/contact_us/")).html_safe %>
+<%= t(".more_info.html", + transformative_works_link: link_to(t(".more_info.transformative_works"), "https://www.transformativeworks.org"), + faq_page_link: link_to(t(".more_info.faq_page"), "https://www.transformativeworks.org/faq"), + communications_team_link: link_to(t(".more_info.communications_team"), "https://www.transformativeworks.org/contact_us/")) %>
<%= t(".page_heading") %>
+ + + +<%= t("a11y.navigation") %>
+<%= render "tos_navigation" %> + + + +<%= t(".page_content_landmark") %>
++ <%= render "content" %> ++ + + +<%= t("a11y.navigation") %>
+<%= render "tos_navigation", top_link: true %> + diff --git a/app/views/home/diversity_statement.html.erb b/app/views/home/diversity_statement.html.erb index bbc06fe1d3d..f8cf5e0f9e2 100644 --- a/app/views/home/diversity_statement.html.erb +++ b/app/views/home/diversity_statement.html.erb @@ -1,22 +1,47 @@ -<%= ts("You are welcome at the Archive of Our Own.") %>
+<%= t(".welcome_header") %>
-diff --git a/app/views/home/donate.html.erb b/app/views/home/donate.html.erb index 43381eb7631..412f66d8971 100644 --- a/app/views/home/donate.html.erb +++ b/app/views/home/donate.html.erb @@ -3,10 +3,14 @@<%= ts("No matter your appearance, circumstances, configuration or take on the world: if you enjoy consuming, creating or commenting on fanworks, the Archive is for you.") %>
+<%= t(".archive_for_you") %>
-<%= ts("This archive is a permanent, panfandom place for fanworks, built by fans for fans. Whichever way you use the Archive, you're part of this, powering it, shaping it through your use and") %> <%= link_to ts("your feedback"), new_feedback_report_path %>.
++ <%= t(".archive_description_html", + your_feedback_link: link_to(t(".your_feedback"), new_feedback_report_path)) %> +
-<%= ts("We,") %> <%= link_to ts("the Archive team"), admin_posts_path %><%= ts(", know that we won't get everything right on the first try, and we won't be able to make everyone equally happy. But we strive to find a good balance, and we promise to respectfully consider your feedback and to take it seriously.") %>
++ <%= t(".what_we_do_html", + archive_team_link: link_to(t(".archive_team"), admin_posts_path)) %> +
-<%= ts("You are free to express your creativity within the") %> <%= link_to ts("few restrictions"), tos_path %> <%= ts("needed to keep the service viable for other users. The Archive strives to protect your rights to free expression and privacy; you can read about the details in our") %> <%= link_to ts("Terms of Service"), tos_path %>.
++ <%= t(".you_can_html", + few_restrictions_link: link_to(t(".few_restrictions"), content_path), + terms_of_service_link: link_to(t(".terms_of_service"), tos_path)) %> +
-<%= ts("We know that there are") %> <%= link_to ts("some essential parts"), "/admin_posts/295" %> <%= ts("that are still missing to make the Archive truly panfandom: the ability to host fanworks other than text, an interface in languages other than English, and more ways for you to connect with each other, to name just a few. But with your support, we'll get there.") %>
++ <%= t(".still_missing_html", + some_essential_parts_link: link_to(t(".some_essential_parts"), admin_post_path(295))) %> +
-<%= ts("We are building this archive because we believe it's possible for people of all opinions and persuasions to come together and share with each other.") %>
+<%= t(".why_we_build") %>
-<%= ts("We are building this archive for you. Come be a part of it.") %>
+<%= t(".we_build_for") %>
-<%= ts("This is a remix of") %> <%= link_to ts("Dreamwidth's"), "http://www.dreamwidth.org" %> <%= link_to ts("Diversity Statement"), "http://www.dreamwidth.org/legal/diversity" %>.
- -
+
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.+ <%= t(".dreamwidth_remix_html", + dreamwidth_link: link_to(t(".dreamwidth"), "http://www.dreamwidth.org"), + diversity_statement_link: link_to(t(".diversity_statement"), "http://www.dreamwidth.org/legal/diversity")) %> +
+ ++ +
" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/88x31.png" /> + +
+ <%= t(".license.html", + creative_commons_by_sa_link: link_to(t(".license.creative_commons_by_sa"), + "http://creativecommons.org/licenses/by-sa/3.0/")) %> +<% end %> diff --git a/app/views/home/privacy.html.erb b/app/views/home/privacy.html.erb new file mode 100644 index 00000000000..af20944647f --- /dev/null +++ b/app/views/home/privacy.html.erb @@ -0,0 +1,20 @@ + +<%= t(".time.title") %>
-<%= t(".time.details_html", - otw_link: link_to(t(".time.otw"), "http://www.transformativeworks.org"), - projects_link: link_to(t(".time.projects"), "http://www.transformativeworks.org/our-projects"), - volunteer_link: link_to(t(".time.volunteer"), "http://www.transformativeworks.org/volunteer")) %>
+<%= t(".time.info_html", + otw_link: link_to(t(".time.otw"), "https://www.transformativeworks.org"), + projects_link: link_to(t(".time.projects"), "https://www.transformativeworks.org/our-projects")) %>
+<%= t(".time.contribute_html", + github_repository_link: link_to(t(".time.github_repository"), "https://github.com/otwcode/otwarchive"), + jira_project_link: link_to(t(".time.jira_project"), "https://otwarchive.atlassian.net/browse/AO3"), + volunteer_listings_link: link_to(t(".time.volunteer_listings"), "https://www.transformativeworks.org/volunteer"), + news_by_email_link: link_to(t(".time.news_by_email"), "https://www.transformativeworks.org/you-can-now-subscribe-to-otw-news-by-email")) %>
<%= t(".money.title") %>
<%= t(".money.details_html", diff --git a/app/views/home/first_login_help.html.erb b/app/views/home/first_login_help.html.erb index fe9658d4c75..d6f7458f907 100644 --- a/app/views/home/first_login_help.html.erb +++ b/app/views/home/first_login_help.html.erb @@ -1,233 +1,155 @@ -<% # Expects current_user %> +<%# Expects current_user %>
diff --git a/app/views/home/index.html.erb b/app/views/home/index.html.erb index 2071c0001ee..7228b2e19e7 100644 --- a/app/views/home/index.html.erb +++ b/app/views/home/index.html.erb @@ -36,11 +36,11 @@- <%= ts('Welcome to the %{app_name}!', app_name: ArchiveConfig.APP_NAME) %> + <%= t(".welcome_header", app_name: ArchiveConfig.APP_NAME) %>
-<%= ts('Here are some tips to help you get started.') %>
+<%= t(".tips_to_start") %>
-<%= ts('Table of Contents') %>
+<%= t(".table_of_contents") %>
-
-
- <%= link_to ts('Logging In and Logging Out'), '#logging_in' %> +
- <%= link_to t(".logging_in_out.header"), "#logging_in" %> +
- <%= link_to t(".editing_profile.header"), "#edit_profile" %> +
- <%= link_to t(".pseuds.header"), "#pseuds" %> +
- <%= link_to t(".posting_works.header"), "#posting" %> +
- <%= link_to t(".browsing.header"), "#browsing" %> +
- <%= link_to t(".tags.header"), "#tags" %> +
- <%= link_to t(".warnings.header"), "#warnings" %> +
- <%= link_to t(".bookmarking_works.header"), "#bookmarking" %> +
- <%= link_to t(".preferences.header"), "#preferences" %>
- - <%= link_to ts('Editing Your Profile, Password, and Preferences'), - '#edit_profile' %> - -
- <%= link_to ts('Pseuds'), '#pseuds' %> -
- <%= link_to ts('Posting Works'), '#posting' %> -
- <%= link_to ts('Browsing'), '#browsing' %> -
- <%= link_to ts('Tags'), '#tags' %> -
- <%= link_to ts('Warnings'), '#warnings' %> -
- <%= link_to ts('Bookmarking Works'), '#bookmarking' %> -
- <%= link_to ts('Preferences'), '#preferences' %> -
-
- <%= link_to ts('Additional Browsing Information'), '#additional' %>
+ <%= link_to t(".additional_info.header"), "#additional" %>
-
-
- <%= link_to ts('History and Mark for Later'), '#history' %> -
- <%= link_to ts('Subscriptions'), '#subscriptions' %> +
- <%= link_to t(".additional_info.history_mark_later.header"), "#history" %> +
- <%= link_to t(".additional_info.subscriptions.header"), "#subscriptions" %>
- - <%= link_to ts('Terms of Service'), '#legal_stuff' %> -
- <%= link_to ts('Support and Feedback'), '#support' %> +
- <%= link_to t(".tos.header"), "#legal_stuff" %> +
- <%= link_to t(".support_and_feedback.header"), "#support" %>
- <%= ts('Logging In and Logging Out') %> -
-<%= ts('To log in, locate the login link and fill in your Username and - Password. The link will be located at the top right of the screen and as - indicated by your screenreader if you\'re using one. If you forget your - password, then select "%{forgot_password}". To log out, select "Log Out" on - the top right corner in the default browser skin.', - forgot_password: (link_to ts('forgot your password'), new_user_password_path) - ).html_safe %>
+<%= t(".logging_in_out.header") %>
++ <%= t(".logging_in_out.html", + forgot_password_link: link_to(t(".logging_in_out.forgot_password"), new_user_password_path)) %> +
-- <%= ts('Editing Your Profile, Password, and Preferences') %> -
-<%= ts('To add your info, go to %{dashboard}, select the - "%{profile}" tab, and select "%{edit_profile}" from the range of - options at the end of the page. Here, you can enter some basic personal - information. It\'s also where to go to change your password. Refer to the - %{profile_faq} for more information.', - dashboard: (link_to ts('your Dashboard'), user_path(current_user)), - profile: (link_to ts('Profile'), user_profile_path(current_user)), - edit_profile: (link_to ts('Edit My Profile'), edit_user_path(current_user)), - profile_faq: (link_to ts('Profile FAQ'), archive_faqs_path + '/profile') - ).html_safe %>
+<%= t(".editing_profile.header") %>
++ <%= t(".editing_profile.html", + your_dashboard_link: link_to(t(".editing_profile.your_dashboard"), user_path(current_user)), + profile_link: link_to(t(".editing_profile.profile"), user_profile_path(current_user)), + edit_my_profile_link: link_to(t(".editing_profile.edit_my_profile"), edit_user_path(current_user)), + profile_faq_link: link_to(t(".editing_profile.profile_faq"), archive_faq_path("profile"))) %> +
-- <%= ts('Pseuds') %> -
-<%= ts('Pseuds are like pen names linked to your account. You can use - different pseuds to post your works under the appropriate name while still - managing them through the same account. You can %{manage_pseuds} through - your profile page. For more information, please visit the - %{pseuds_faq}.', - manage_pseuds: (link_to ts('manage your pseuds'), - user_pseuds_path(current_user)), - pseuds_faq: (link_to ts('Pseuds FAQ'), archive_faqs_path + '/pseuds'), - ).html_safe %>
+<%= t(".pseuds.header") %>
++ <%= t(".pseuds.html", + manage_your_pseuds_link: link_to(t(".pseuds.manage_your_pseuds"), user_pseuds_path(current_user)), + pseuds_faq_link: link_to(t(".pseuds.pseuds_faq"), archive_faq_path("pseuds"))) %> +
-- <%= ts('Posting Works') %> -
-<%= ts('To open the Post New Work page, just select the %{post} link - from the menu of the Post tab located at the top right of the page in the - default browser skin. Visit the %{posting_faq} or check out our - %{post_tutorial} for more information.', - post: (link_to ts('Post New'), new_work_path), - posting_faq: (link_to ts('Posting and Editing FAQ'), - archive_faqs_path + '/posting-and-editing'), - post_tutorial: (link_to ts('Tutorial: Posting a Work on AO3'), - archive_faqs_path + '/tutorial-posting-a-work-on-ao3') - ).html_safe %>
+<%= t(".posting_works.header") %>
++ <%= t(".posting_works.html", + post_new_link: link_to(t(".posting_works.post_new"), new_work_path), + posting_editing_faq_link: link_to(t(".posting_works.posting_editing_faq"), + archive_faq_path("posting-and-editing")), + tutorial_link: link_to(t(".posting_works.tutorial"), + archive_faq_path("tutorial-posting-a-work-on-ao3"))) %> +
-- <%= ts('Browsing') %> -
-<%= ts('You can start browsing works by going to the "%{fandoms}" tab at - the top of any Archive page in the default skin and selecting either - "%{all_fandoms}" or one of the subsets such as "%{movies}". Alternatively, you - can use the %{search} to look for specific fandoms, works, or users. You can - use the "Sort and Filter" form to narrow down the results in any fandom page. - For more instructions, please visit %{search_faq} and the - %{search_tutorial}.', - fandoms: (link_to ts('Fandoms'), menu_fandoms_path), - all_fandoms: (link_to ts('All Fandoms'), media_path), - movies: Media.find_by_name('Movies') ? (link_to ts('Movies'), - medium_fandoms_path( - Media.find_by_name('Movies'))) : - ts('Movies'), - search: (link_to ts('search feature'), search_works_path), - search_faq: (link_to ts('Search and Browse FAQ'), - archive_faqs_path + '/search-and-browse'), - search_tutorial: (link_to ts('Searching and browsing tutorial'), - admin_posts_path + '/259'), - ).html_safe %>
+<%= t(".browsing.header") %>
++ <% media_movie = Media.find_by_name("Movies") %> + <%= t(".browsing.html", + fandoms_link: link_to(t(".browsing.fandoms"), menu_fandoms_path), + all_fandoms_link: link_to(t(".browsing.all_fandoms"), media_path), + movies_link: if media_movie + link_to(t(".browsing.movies"), medium_fandoms_path(media_movie)) + else + t(".browsing.movies") + end, + search_feature_link: link_to(t(".browsing.search_feature"), search_works_path), + search_browse_faq_link: link_to(t(".browsing.search_browse_faq"), archive_faq_path("search-and-browse")), + search_browse_tutorial_link: link_to(t(".browsing.search_browse_tutorial"), admin_post_path(259))) %> +
-- <%= ts('Tags') %> -
-<%= ts('All tags on the Archive—including those for fandoms, relationships, - and characters—start out user-created. You can always use the existing tags by - selecting from the autocomplete list. If you cannot find the tags you want to - use, feel free to create new tags for your works. Behind the scenes, our tag - wrangling team will match the tags up with their synonyms, so that people can - find your work whether you tag it "AMTDI", "Aliens Made Them Do - It", or "Sex Pollen". Refer to the %{tags_faq} to learn more.', - tags_faq: (link_to ts('Tags FAQ'), archive_faqs_path + '/tags') - ).html_safe %>
+<%= t(".tags.header") %>
++ <%= t(".tags.html", + tags_faq_link: link_to(t(".tags.tags_faq"), archive_faq_path("tags"))) %> +
-- <%= ts('Warnings') %> -
-<%= ts('The Archive defines four "primary" %{warnings_tos}: "Graphic - Depictions Of Violence", "Major Character Death", "Rape/Non-Con", and - "Underage". When posting a work, you have the option to explicitly select - warnings for this content, deny the presence of such content ("No Archive - Warnings Apply"), or choose not to apply warnings regardless of whether or not - these warnings are applicable ("Creator Chose Not To Use Archive Warnings"). - Remember, "No Archive Warnings Apply" only refers to the listed primary - warnings.', - warnings_tos: (link_to ts('Archive-specific warnings'), tos_path + '#IV.K.3') - ).html_safe %>
-<%= ts('When browsing the Archive, warnings will be displayed in the blurb - of each work. Official warning tags are displayed in bold. A four square grid - in the top left corner of each work\'s blurb indicates the work\'s rating, - completion status, pairing category, and any Archive warnings that apply to - it. Refer to the %{symbols_key} for more information.', - symbols_key: (link_to ts('Symbols Key Chart'), '/help/symbols-key.html') - ).html_safe %>
+<%= t(".warnings.header") %>
++ <%= t(".warnings.description_html", + archive_specific_warnings_link: link_to(t(".warnings.archive_specific_warnings"), + tos_faq_path(anchor: "warnings_list"))) %> +
++ <%= t(".warnings.symbols_html", + symbols_key_chart_link: link_to(t(".warnings.symbols_key_chart"), "/help/symbols-key.html")) %> +
-- <%= ts('Bookmarking Works') %> -
-<%= ts('You can bookmark works on the Archive as well as works hosted on - other sites. You can choose to make your bookmarks public or private. You can - also mark a public bookmark as a rec (recommendation). Additionally, you can - add notes and tags to the bookmark, and/or add it to a collection. For more - instructions on managing your Bookmarks, please visit the %{bookmarks_faq}.', - bookmarks_faq: (link_to ts('Bookmarks FAQ'), archive_faqs_path + '/bookmarks') - ).html_safe %>
+<%= t(".bookmarking_works.header") %>
++ <%= t(".bookmarking_works.html", + bookmarks_faq_link: link_to(t(".bookmarking_works.bookmarks_faq"), archive_faq_path("bookmarks"))) %> +
-- <%= ts('Preferences') %>
-<%= ts('"%{set_preferences}" is located next to the "%{edit_profile}" - button, and allows you to adjust certain settings to personalize your - experience on the site. The Preferences area controls both the Archive\'s - behavior (such as whether your history is saved) and the Archive\'s - appearance. Go to the %{preferences_faq} for more details.', - set_preferences: (link_to ts('Set My Preferences'), - user_preferences_path(current_user)), - edit_profile: (link_to ts('Edit My Profile'), edit_user_path(current_user)), - preferences_faq: (link_to ts('Preferences FAQ'), - archive_faqs_path + '/preferences') - ).html_safe %>
-<%= ts('For more information on how to customize the skins and interface of - the Archive, refer to the %{skins_faq} and %{tutorial_list}.', - skins_faq: (link_to ts('Skins and Archive Interface FAQ'), - archive_faqs_path + '/skins-and-archive-interface'), - tutorial_list: (link_to ts('List of Tutorials'), - archive_faqs_path + '/tutorials') - ).html_safe %>
+<%= t(".preferences.header") %>
++ <%= t(".preferences.html", + set_my_preferences_link: link_to(t(".preferences.set_my_preferences"), user_preferences_path(current_user)), + edit_my_profile_link: link_to(t(".preferences.edit_my_profile"), edit_user_path(current_user)), + preferences_faq_link: link_to(t(".preferences.preferences_faq"), archive_faq_path("preferences"))) %> +
++ <%= t(".preferences.skins_detail_html", + skins_faq_link: link_to(t(".preferences.skins_faq"), + archive_faq_path("skins-and-archive-interface")), + tutorials_list_link: link_to(t(".preferences.tutorials_list"), + archive_faq_path("tutorials"))) %> +
-- <%= ts('Additional Browsing Information') %> -
-- <%= ts('History and Mark for Later') %>
-<%= ts('You can access and manage your history by going to %{dashboard} and - selecting the "%{history}" link in the side menu in the default browser skin - or on top of the page in mobile devices. You can clear your history, or delete - individual entries if you don\'t want these entries to show up in your - history. You can also add works to the "Marked for Later" list in your - history. For more information on History, please visit the %{history_faq}.', - dashboard: (link_to ts('your Dashboard'), user_path(current_user)), - history: (link_to ts('History'), user_readings_path(current_user)), - history_faq: (link_to ts('History and Mark for Later FAQ'), - archive_faqs_path + '/History-and-mark-for-later') - ).html_safe %>
+<%= t(".additional_info.header") %>
+<%= t(".additional_info.history_mark_later.header") %>
++ <%= t(".additional_info.history_mark_later.html", + your_dashboard_link: link_to(t(".additional_info.history_mark_later.your_dashboard"), user_path(current_user)), + history_link: link_to(t(".additional_info.history_mark_later.history"), user_readings_path(current_user)), + history_faq_link: link_to(t(".additional_info.history_mark_later.history_faq"), + archive_faq_path("History-and-mark-for-later"))) %>
-- <%= ts('Subscriptions') %> -
-<%= ts('You can subscribe to a work, collection, series of works, or user - by selecting the "Subscribe" link at the top or bottom of a work, or at the - top or bottom of a collection or series page, or the user\'s profile page. You - can check your subscriptions from %{dashboard} by selecting the - "Subscriptions" link. For more information on Subscriptions, please visit the - %{subscription_faq}.', - dashboard: (link_to ts('your Dashboard'), user_path(current_user)), - subscription_faq: (link_to ts('Subscriptions and Feeds FAQ'), - archive_faqs_path + '/subscriptions-and-feeds') - ).html_safe %>
+<%= t(".additional_info.subscriptions.header") %>
++ <%= t(".additional_info.subscriptions.html", + your_dashboard_link: link_to(t(".additional_info.subscriptions.your_dashboard"), user_path(current_user)), + subscriptions_feed_faq_link: link_to(t(".additional_info.subscriptions.subscriptions_feed_faq"), + archive_faq_path("subscriptions-and-feeds"))) %> +
-- <%= ts('Terms of Service') %> -
-<%= ts('You can keep up to date with the policies and procedures for the - site listed in the current %{tos}, and find explanations for some of the more - common questions in the %{tos_faq}. If you still have questions about a - specific work, please %{contact_abuse}. If you have general policy questions, - you can either contact Abuse or %{contact_support}.', - tos: (link_to ts('Terms of Service'), tos_path), - tos_faq:(link_to ts('Terms of Service FAQ'), tos_faq_path), - contact_abuse: (link_to ts('contact Abuse'), new_abuse_report_path), - contact_support: (link_to ts('contact Support'), new_feedback_report_path) - ).html_safe %>
+<%= t(".tos.header") %>
++ <%= t(".tos.info_html", + tos_link: link_to(t(".tos.tos"), tos_path), + content_policy_link: link_to(t(".tos.content_policy"), content_path), + privacy_policy_link: link_to(t(".tos.privacy_policy"), privacy_path), + tos_faq_link: link_to(t(".tos.tos_faq"), tos_faq_path)) %> +
++ <%= t(".tos.additional_questions_html", + contact_abuse_link: link_to(t(".tos.contact_abuse"), new_abuse_report_path)) %> +
-- <%= ts('Support and Feedback') %> -
-<%= ts('Some frequently asked questions about the Archive are answered in - the broader %{faq}. You may also like to check out our %{known_issues}. If you - need more help, please %{contact_support}. If you want to know more about some - user-created tools that work with the Archive, please visit the - %{tools_faq}.', - faq: (link_to ts('Archive FAQ'), archive_faqs_path), - known_issues: (link_to ts('Known Issues'), known_issues_path), - contact_support: (link_to ts('contact Support'), new_feedback_report_path), - tools_faq: (link_to ts('Unofficial Browser Tools FAQ'), - archive_faqs_path + '/unofficial-browser-tools') - ).html_safe %>
+<%= t(".support_and_feedback.header") %>
++ <%= t(".support_and_feedback.html", + archive_faq_link: link_to(t(".support_and_feedback.archive_faq"), archive_faqs_path), + known_issues_link: link_to(t(".support_and_feedback.known_issues"), known_issues_path), + contact_support_link: link_to(t(".support_and_feedback.contact_support"), new_feedback_report_path), + unofficial_tools_faq_link: link_to(t(".support_and_feedback.unofficial_tools_faq"), + archive_faq_path("unofficial-browser-tools"))) %> +
<%= t(".readings.note") %>
--
+
-
<% @homepage.readings.each do |reading| %>
<%= render "readings/reading_blurb", work: reading.work, reading: reading %>
<% end %>
-
<%= t(".page_heading") %>
+ + + +<%= t("a11y.navigation") %>
+<%= render "tos_navigation" %> + + + +<%= t(".page_content_landmark") %>
++ <%= render "privacy" %> ++ + + +<%= t("a11y.navigation") %>
+<%= render "tos_navigation", top_link: true %> + diff --git a/app/views/home/site_map.html.erb b/app/views/home/site_map.html.erb index 6bb292a4758..bb9a2f0f3c1 100644 --- a/app/views/home/site_map.html.erb +++ b/app/views/home/site_map.html.erb @@ -1,57 +1,69 @@ -<%= t('.site_map', :default => 'Site Map') %>
+<%= t(".page_heading") %>
-diff --git a/app/views/home/tos.html.erb b/app/views/home/tos.html.erb index aa6f91069c1..36f288fb26b 100644 --- a/app/views/home/tos.html.erb +++ b/app/views/home/tos.html.erb @@ -1,3 +1,20 @@ -Explore
--
-
- <%= link_to t('.homepage', :default => "Homepage"), root_path %> -
- <%= link_to t('.fandoms', :default => "Fandoms"), media_path %> -
- <%= link_to t('.recent_works', :default => "Recent Works"), works_path %> -
- <%= link_to t('.people', :default => "People"), search_people_path %> -
- <%= link_to t('.bookmarks', :default => "Bookmarks"), bookmarks_path %> -
- <%= link_to t('.freeform_tag_cloud', :default => "Additional Tags Cloud"), tags_path %> -
- <%= link_to t('.languages', :default => "Languages"), languages_path %> -
- <%= link_to t('.collections', :default => "Collections and Challenges"), collections_path %> -
<%= t(".explore.header") %>
+-
+
- <%= link_to t(".explore.homepage"), root_path %> +
- <%= link_to t(".explore.fandoms"), media_path %> +
- <%= link_to t(".explore.recent_works"), works_path %> +
- <%= link_to t(".explore.people"), search_people_path %> +
- <%= link_to t(".explore.bookmarks"), bookmarks_path %> +
- <%= link_to t(".explore.additional_tags_cloud"), tags_path %> +
- <%= link_to t(".explore.languages"), languages_path %> +
- <%= link_to t(".explore.collections_and_challenges"), collections_path %> +
About the Archive of Our Own
--
-
- <%= link_to t('.terms_of_service', :default => "Terms of Service"), tos_path %> -
- <%= link_to t('.archive_faq', :default => "Archive FAQ"), archive_faqs_path %> -
- <%= link_to t('.ao3_news', :default => "AO3 News"), admin_posts_path %> -
- <%= link_to t('.known_issues', :default => "Known Issues"), known_issues_path %> -
- The Archive of Our Own is a project of the OTW -
<%= t(".about.header") %>
+-
+
- <%= link_to t(".about.terms_of_service"), tos_path %> +
- <%= link_to t(".about.content_policy"), content_path %> +
- <%= link_to t(".about.privacy_policy"), privacy_path %> +
- <%= link_to t(".about.tos_faq"), tos_faq_path %> +
- <%= link_to t(".about.archive_faq"), archive_faqs_path %> +
- <%= link_to t(".about.ao3_news"), admin_posts_path %> +
- <%= link_to t(".about.known_issues"), known_issues_path %> +
- + <%= t(".about.project_of_otw_html", + otw_link: link_to(content_tag(:acronym, t(".otw.abbreviated"), title: t(".otw.full")), + "https://transformativeworks.org")) %> + +
Access your account
--
-
- <%= link_to t('.my_home', :default => "My Home"), user_path(current_user) %> -
- <%= link_to t('.post_new', :default => "Post New"), new_work_path %> -
- <%= link_to t('.my_works', :default => "My Works"), user_works_path(current_user) %> -
- <%= link_to t('.my_drafts', :default => "Drafts"), drafts_user_works_path(current_user) %> -
- <%= link_to t('.my_series', :default => "My Series"), user_series_index_path(current_user) %> -
- <%= link_to t('.my_bookmarks', :default => "My Bookmarks"), user_bookmarks_path(current_user) %> -
- <%= link_to t('.my_collections', :default => "My Collections and Challenges"), user_collections_path(current_user) %> -
- <%= link_to t('.my_inbox', :default => "My Inbox"), user_inbox_path(current_user) %> - <% if current_user.preference.history_enabled? %> -
- <%= link_to t('.my_history', :default =>"My History"), user_readings_path(current_user) %> - <% end %> -
- <%= link_to t('.my_subscriptions', :default =>"My Subscriptions"), user_subscriptions_path(current_user) %> -
- <%= link_to t('.set_preferences', :default => "Set My Preferences"), user_preferences_path(current_user) %> -
<%= t(".access_your_account.header") %>
+-
+
- <%= link_to t(".access_your_account.my_home"), user_path(current_user) %> +
- <%= link_to t(".access_your_account.post_new"), new_work_path %> +
- <%= link_to t(".access_your_account.my_works"), user_works_path(current_user) %> +
- <%= link_to t(".access_your_account.drafts"), drafts_user_works_path(current_user) %> +
- <%= link_to t(".access_your_account.my_series"), user_series_index_path(current_user) %> +
- <%= link_to t(".access_your_account.my_bookmarks"), user_bookmarks_path(current_user) %> +
- <%= link_to t(".access_your_account.my_collections_and_challenges"), user_collections_path(current_user) %> +
- <%= link_to t(".access_your_account.my_inbox"), user_inbox_path(current_user) %> + <% if current_user.preference.history_enabled? %> +
- <%= link_to t(".access_your_account.my_history"), user_readings_path(current_user) %> + <% end %> +
- <%= link_to t(".access_your_account.my_subscriptions"), user_subscriptions_path(current_user) %> +
- <%= link_to t(".access_your_account.set_my_preferences"), user_preferences_path(current_user) %> +
Change your account settings
--
-
- <%= link_to t('.edit_user_profile', :default =>"Edit My Profile"), edit_user_path(current_user) %> -
- <%= link_to t('.my_profile', :default => "My Profile"), user_profile_path(current_user) %> -
- <%= link_to t('.manage_pseuds', :default => "Manage My Pseuds"), user_pseuds_path(current_user) %> -
- <%= link_to ts("Delete My Account"), user_path(current_user), data: {confirm: ts('This will permanently delete your account and cannot be undone. Are you sure?')}, :method => :delete %> -
<%= t(".change_your_account_settings.header") %>
+-
+
- <%= link_to t(".change_your_account_settings.edit_my_profile"), edit_user_path(current_user) %> +
- <%= link_to t(".change_your_account_settings.my_profile"), user_profile_path(current_user) %> +
- <%= link_to t(".change_your_account_settings.manage_my_pseuds"), user_pseuds_path(current_user) %> +
- + <%= link_to t(".change_your_account_settings.delete_my_account"), + user_path(current_user), + data: { confirm: t(".change_your_account_settings.delete_account_confirmation") }, + method: :delete %> + +
Contact Us
--
-
- <%= link_to t('.support_and_feedback', :default => "Technical Support & Feedback"), new_feedback_report_path %> -
- <%= link_to t('.report_abuse', :default => "Policy Questions & Abuse Reports"), new_abuse_report_path %> -
- <%= link_to t('.donate', :default => "Donations"), donate_path %> -
<%= t(".contact_us.header") %>
+-
+
- <%= link_to t(".contact_us.technical_support_and_feedback"), new_feedback_report_path %> +
- <%= link_to t(".contact_us.policy_questions_and_abuse_reports"), new_abuse_report_path %> +
- <%= link_to t(".contact_us.donations"), donate_path %> +
<%= ts("Terms of Service") %>
+ +<%= t(".page_heading") %>
+ -<%= render "home/tos" %> + +<%= t("a11y.navigation") %>
+<%= render "tos_navigation" %> + + + +<%= t(".page_content_landmark") %>
++ <%= render "tos" %> ++ + + +<%= t("a11y.navigation") %>
+<%= render "tos_navigation", top_link: true %> + diff --git a/app/views/home/tos_faq.html.erb b/app/views/home/tos_faq.html.erb index e590acf96e0..bb4bfd25f0f 100644 --- a/app/views/home/tos_faq.html.erb +++ b/app/views/home/tos_faq.html.erb @@ -1,498 +1,1247 @@ -Terms of Service FAQ
-- -+ + + +-+ +General Principles
-Why does the Archive have a goal of maximum inclusiveness?
-There are a number of wonderful specialized archives. Our aim with this Archive is to provide a place to preserve as many fanworks as possible. At the same time, the Archive software can be used by anyone to create their own archives, including archives limited to particular topics, fandoms, or ratings. -
-Why is the agreement between the Archive and Archive users governed by the laws of New York?
-Given the great variation among laws in different places, we want our agreement with you to be governed by predictable and consistent laws. -
-What is an implied warranty of merchantability?
-An implied warranty of merchantability is a legal agreement between a seller and a buyer that goods will be reasonably fit for the general purpose for which they are sold. In the United States this warranty is governed by the Uniform Commercial Code (UCC), which allows sellers to disclaim it, thereby shifting the risk back to the buyer. -
-What is an implied warranty of fitness for a particular purpose?
-An implied warranty of fitness for a particular purpose is a legal agreement that exists when a buyer relies upon the seller to provide goods to fit a specific request. This warranty requires that the seller know or have reason to know of a specific purpose to which the goods are going to be put, and know that the buyer is relying on the seller's expertise or judgment. In the United States this warranty is governed by the Uniform Commercial Code (UCC), which allows sellers to disclaim it, thereby shifting the risk back to the buyer. -
-Under what circumstances would you suspend an account for an out-of-date e-mail address?
-If we need to communicate with you to resolve an abuse complaint, and the e-mail bounces, we will have to resolve it without your participation, which means you won't be able to tell your side of the story. If your e-mail continues to bounce, we will suspend your account because we need to be able to communicate with you if necessary. -
-In that situation, you can get your account reinstated by associating it with a working email address and, if necessary, dealing with whatever problem led to the abuse complaint in the first place. -
-Suspension for bouncing isn't a strike. Suspension for bouncing would never lead to permanent suspension, though a sufficient number of sustained abuse complaints while the email was bouncing could lead to permanent suspension. -
-If we send a routine e-mail about general site policies and it bounces, that will not lead to account suspension, though whatever policies we announce will still apply to all account holders. We will only suspend accounts when individual abuse-related communications bounce. -
-I am a non-US resident. What does the Archive policy on US law mean for me?
-The Archive welcomes fans from all over the globe, but it is set up under US law. We believe that US law governs the Archive, which includes the relationship between the Archive and its users and the definitions of terms in the ToS. Other laws may govern your behavior, however, and you are responsible for knowing them and complying with them. -
-What do you mean by banning "impersonation"? Can I archive first-person real-person fiction? Can I use a celebrity name as a pseudonym?
-Roleplay is permitted when the assumption of such a persona is clearly disclosed (e.g., in a user profile or in another manner appropriate under the circumstances) and it doesn't otherwise violate the Content Policy, including the harassment policy. Fiction marked as such, including real-person fiction in first-person format, is not impersonation. Please consult the - <%= link_to ts("content policy"), tos_path(:anchor => "content") %> for further information. -
-What do you mean by "world-wide, royalty-free, nonexclusive license"?
-This means the Archive can make your content available to other people (subject to any login requirements that apply) without paying you. We will never charge for access to the Archive or otherwise sell your content. You can put your content anywhere else you want, too. -
-Age Policy
-Why are children under the age of 13 not permitted to have an account or upload Content?
-In the U.S., the Children's Online Privacy Protection Act governs the collection of personal information (which can include things like usernames) from children under 13. Requiring users to be over 13 is the easiest way for us to comply with this law. -
-Privacy Policy
-Why do you use cookies?
-Cookies may be required to customize your experience of the site. If you do not accept cookies, you may not be able to use the site. There are many good ways to remove both browser history and cookies between sessions, and we encourage people who are concerned about privacy to investigate more global solutions. For example, Firefox can clear all your private data between sessions. -
-Content Policies and Abuse Procedures
-What sort of things would lead to permanent suspension?
-It's impossible to define everything in advance. We are most concerned with people who are actively and deliberately hostile to the community. Repeated upheld copyright complaints involving nontransformative works may lead to a permanent suspension. Wholesale plagiarism and deliberate disclosure of another person's real-life name or other identifying information readily justify permanent suspension, whereas a personal conflict that gets out of control may justify temporary suspension. Small and honest mistakes, even if they are annoying, are more likely to draw warnings. -
-What constrains the abuse team's discretion?
-Our commitment is to build a community that welcomes anyone with a willingness to learn the rules but defends itself against people who deliberately flout them. Our discretion is aimed at that objective. Procedurally, permanent suspensions for violations other than spam or threatening the technical integrity of the site require a majority vote of the abuse team. Majority rule builds in checks on individual discretion without trying to resolve every possible situation in advance. -
-What do you mean by "only people who have a need to know" about a complaint will be informed of it?
-Abuse and complaint information is kept confidential. The abuse team guards all such information carefully, and all members of the abuse team have agreed to an industry-standard confidentiality policy. On occasion, the abuse team may need to consult with the Systems committee, to request specific technical or log information to aid our investigation, for example, or the Legal committee, to discuss precise legal requirements. We may also contact the subject of a complaint, to request their perspective or to inform them of penalties their actions have incurred. For information about what details we would release to the subject of a complaint, please see our - <%= link_to ts("Privacy Policy"), tos_path(:anchor => "privacy") %> and - <%= link_to ts("other Abuse FAQs"), tos_path(:anchor => "content") %>. -
-What happens if someone who's a friend of someone on the abuse team is involved in a complaint?
-We expect the members of the abuse team to behave professionally, even though OTW is entirely volunteer-staffed. We take the responsibilities of serving on the abuse team seriously, and a member of the team with a personal relationship to either party in an abuse situation is expected to recuse themselves entirely from the case, and, of course, to maintain our standards of confidentiality at all times; failure to do so may be grounds for dismissal from the team. -
-What do the different account statuses mean?
-We define account statuses the following way:
-Warning
-At its discretion, the abuse team may issue a warning, rather than a suspension, in the instance of minor violations of the ToS. A user who has recently received a warning and who violates the ToS again, especially in the same or a similar manner, is likely to incur a suspension. -
-Suspension
-The abuse team may issue a time-limited ban on the uploading of new content and creation of new accounts; suspension occurs as the result of strikes incurred for violating the Archive's ToS. During this time, the suspended user can remove, but not edit, content uploaded prior to the suspension. -
-Permanent Suspension
-The abuse team may issue a permanent ban on the uploading of new content. Permanently suspended users cannot create new accounts or upload content to Archive, though they retain the right to remove, but not edit, content uploaded prior to the permanent suspension. -
-If I complain non-anonymously, will the subject be told who complained?
-Only people who need to know about a complaint will be informed about it. The subject of a complaint may be among those who need to know. No information other than that provided in the complaint will be passed on, and the complainant has complete control over what information is submitted to Abuse. Complaints can be submitted anonymously. Legal names and other information sufficient to identify a person in the physical world will never be disclosed as part of a standard abuse complaint. For further clarification, please see our - <%= link_to ts("Privacy Policy"), tos_path(:anchor => "privacy") %>. -
-Will I be informed of complaints against me?
-In general, the abuse team will only communicate with the subject of a complaint if there appears to be a violation of the abuse policy, or if the abuse team needs more information to resolve the issue. -
-How would the suspended user control their nonobjectionable content without an account?
-Non-objectionable fanworks are not removed from the site when a user is suspended. Suspended users who wish to delete or orphan their fanworks may contact the Abuse team to have this done for them. -
-What information is available about a permanently suspended or deleted account? Can I reuse a userID that belonged to a deleted account?
-Permanent suspension doesn't delete accounts; unless deleted by the user, any existing content that doesn't violate the content policy or other parts of the Terms of Service remains. It is possible that a userID that has been deleted by the user will be available to other people. -
-How do I appeal the resolution of a complaint?
-The person against whom a complaint was resolved can submit an appeal the same way as one would submit a complaint, by contacting Abuse.
-Spam and Commercial Promotion
-How strict is the "no commerce" rule?
-We want the Archive to remain a non-commercial space. That means that it isn't the right place for offering merchandise, even fan-related merchandise. Linking to your personal page (not, for example, an Amazon author page) is fine, even if the personal page includes some items for sale, but the Archive is not advertising space. If the abuse team issues a warning or sustains a complaint about commercial activities, the original poster can always appeal. -
-What about charity drives?
-The Archive will host fanworks of any origin, including fanworks created in response to charity drives or other challenges. A link to a charity drive to explain the origin of a fanwork is appropriate. Solicitation itself, however, should take place outside the Archive. We concluded that this policy was the easiest to apply fairly to everyone, given the wide range of possible solicitation activities. -
-What's this about the spam filter? Can I be permanently suspended if I fail the filter?
-If you're logged in, you shouldn't see a spam filter, so the situation shouldn't arise. If we find that accounts are being created simply to spam other users, we will permanently suspend those accounts. If you're a human being reading this FAQ, you shouldn't worry about the automated spam-control measures. -
-Technical integrity
-What do you mean by "attempting to interfere with the technical integrity of the site"?
-Basically, we mean attempts to hack the site or spread viruses or other unwanted programs through it. If a user deliberately exploits a code vulnerability in order to install unwanted programs, redirect users to spam sites, or other destructive behavior, that's attempting to interfere with the technical integrity of the site. -
-Does that mean I can't have nifty formatting in my story?
-No, this is just a security policy. As for formatting: you will be able to have plenty of nifty formatting, but not everything imaginable. As a practical security matter, we will not be allowing javascript on the Archive, and only a limited subset of HTML. Something elaborately custom-coded would have to go on your own webspace. That is just because there is no secure way to allow people to start uploading unfiltered code. Our limits are designed in part to improve accessibility for all users, but we aren't trying to impose any editorial standard. The basic reason is simply that it's not technically safe to allow unfiltered code. -
-Do you have a policy on bots or scraping? These are ways of extracting information from or indexing websites.
-Using bots or scraping is not against our Terms of Service unless it relates to our guidelines against spam or other activities. However, we do reserve the right to implement robots.txt or other protocols limiting what bots can do, or to notify you and ask you to discontinue if a bot or scraping program is causing problems for the site. -
-Harassment
-Does the harassment policy cover everyone, or just Archive users?
-Both Archive users and non-users might potentially complain about harassment. In today's online environment, the line between non-user and user can be blurry, and so our policy covers both users and non-users. Writing RPF (real-person fiction), however, never constitutes harassment in and of itself, even if the content is objectionable. Please see the - <%= link_to ts("harassment policy"), tos_path(:anchor => "IV.G.") %> for more information. -
-Plagiarism
-Can a person submit a plagiarism complaint anonymously, or without being the author of the plagiarized work?
-Yes. Except in the case of - <%= link_to ts("copyright complaints"), tos_path(:anchor => "IV.D.") %>, a complaining person may submit a complaint via the web form, which does not require identifying information. -
-Pseudonyms
-Why would I want to have different pseudonyms connected to the same account?
-We distinguish between usernames and pseudonyms, allowing multiple pseudonyms for each username. Pseudonyms are useful when more than one person wants to use a particular name; they allow multiple Sarahs or Kittens to coexist but be distinguished. Also, if you have used different fannish names over time or in different fandoms, you can keep them all on the Archive using pseudonyms. -
-User Icons
-Why are the rules for user icons more restrictive than the general Archive rules?
-Right now, user icons appear on pages, such as user profiles, that are entirely unrated. The design provides for only one user icon per pseudonym, rather than multiple icons, which means that whatever icon a user picks will be visible to any browser. If there is substantial interest in changing the system, we may revise the Archive so that a user may have multiple icons and/or may rate their profile just as a fanwork may be rated, in which case we will change the user icon policy. The icon policy is not the general fanart policy. We presently allow embedding various kinds of files hosted elsewhere. We do anticipate eventually hosting images created by fans and treating them like textual fanworks, governed mainly by ratings and warnings rather than by content restrictions. -
-Profiles
-What can be on a user profile?
-User profiles can contain information about the user, including information about the user's preferences and links to other sites on which the user can be found. User profiles must comply with the Archive's policies on harassment, impersonation, plagiarism, commercial promotion, and other conduct that threatens the integrity of the site. Users should not use their profiles to encourage the purchase of their other works (e.g., linking to a Kindle page). Linking to a personal page on another service is fine, even if the personal page offers some items for sale (e.g., the personal page includes links to an Etsy page), but the Archive is not advertising space. -
-Ratings and Warnings
-What kind of content do you allow?
-We will not remove content from the Archive because it contains explicit material, as long as it doesn't violate any other part of the content policy (e.g., the harassment policy). -
-One basic consequence is that users are responsible for reading and heeding the warnings provided by the creator. Risk-averse users should keep in mind that not all content will carry full warnings. If you want to know more, you may also wish to consult the bookmarks that people other than the creator have used to categorize the fanwork. -
-Some creators do not want to put specific ratings or warnings on their works. Our policy aims to enable creators to choose appropriate labels or to opt not to use ratings and warnings, with the understanding that some users will avoid unrated or unwarned content. -
-Though creators are not required to use ratings or warnings, they are often extremely useful to users. Ratings or warnings can attract some readers who are looking for specific content, and they can also warn off readers who are trying to avoid that content. Because fanworks may deal with controversial and painful issues, we encourage creators to choose ratings and warnings that help users make decisions about what to read. The "not rated" and "choose not to use Archive warnings" options will, of course, help users make decisions as well, though without much detail. -
-What sort of information do I need to provide for my fanworks?
-The aim of the Archive is to let fanwork creators and audiences find each other. Choosing at least one fandom is therefore the basic requirement. If we don't have your fandom listed, you can always add it. After that, you can add characters, relationships (if you want), a summary, and other information. -
-The Archive also uses rating and warning tags. Our goal is to provide the maximum amount of control and flexibility for all users of the Archive, both creators and audiences, so that each user can customize their experience. It's always possible for creators to use "not rated" or "choose not to use Archive warnings," but audiences will always be able to avoid unrated or unwarned fanworks if that's how they want to use the Archive. -
-From the user's perspective, users who wish to avoid warnings will be able to hide them. Author-supplied warnings are displayed by default unless and until a user changes their preferences. -
-Users who wish to serve as filters for other users may also use bookmarks and recommendation tags. These will serve as an extra source of information for other users who are trying to determine whether or not to access a work. Users will have to choose to use other users' bookmarks and recommendations. -
-This system is designed to offer numerous different ways to customize the experience on the Archive, which should in general accommodate users' desires for warnings or to avoid warnings, along with authors' ability to choose the appropriate warning or to choose not to provide warnings. In most cases, users can control their experiences by accessing only fanworks that have ratings and warnings that are acceptable to them, and creators can use their artistic judgment about what ratings and/or warnings, if any, ought to be on a fanwork. -
-If I don't choose, what's the default?
-The default is "not rated" and "choose not to use Archive warnings."
-What's the consequence of a violation of the ratings/warnings policy?
-Please see the - <%= link_to ts("Content Policy"), tos_path(:anchor => "content") %> for details. If we sustain a complaint about ratings, the fanwork will remain available on the Archive, but it will have the "not rated" label. If we sustain a complaint about warnings, the fanwork will remain available on the Archive, but it will have the "choose not to use Archive warnings" label. -
-The ratings/warnings policy is really minimal. Why is this?
-We believe that appropriate ratings and warnings are often in the eye of the beholder. Users who feel that a fanwork lacks an appropriate rating/warning are encouraged to try to resolve the issue with the creator. Users may also add tags of their own to on-site bookmarks of a fanwork, which other users can consult for more information. When those tags are present, you can click on the "Bookmarks" link at the top of the work to see them. -
-What's the difference between ratings and warnings?
-Ratings are a measure of the intensity of overall content. Warnings refer to more specific subjects and can be used to complete the sentences: -
-I prefer not to read works that contain X
-I search out and enjoy works that contain X
-Do the Archive maintainers screen works as they're uploaded for compliance with the ratings/warnings policy?
-No.
-How will this work while the Archive is in beta?
-Since many features will not yet be available in the early version of the Archive, the Content Policy only applies to active features. Because we're just getting started, we will emphasize communication and dialogue about policies; everyone, including the Archive maintainers, will be learning how this works. -
-Can chapters of a larger work be rated/warned separately from each other?
-Not in the initial version of the Archive, but we have put it on the roadmap for later addition.
-Can I use "not rated" but not "choose not to use Archive warnings," or vice versa?
-Yes, absolutely. So you could use "not rated" for a story that has a warning for rape, or you could rate a story "explicit" or "general" but choose not to give specific warnings. -
-Do you distinguish between same-sex and opposite-sex relationships or activities for ratings purposes?
-No. Please note that the creator's choice of rating is presumed appropriate. In assessing abuse complaints, we will not treat slash any differently than het. -
-What's the difference between "general" and "teen and up" or "mature" and "explicit"?
-This is left to the creator's judgment. People disagree passionately about the nature and explicitness of content to which younger audiences should be exposed. The creator's discretion to choose between "general" and "teen and up" or between "mature" and "explicit" is absolute: we will not mediate any disputes about those decisions. Instead, we encourage creators to consider community norms, whether fandom-specific or more general (such as how you'd expect a video game or movie with similar content to be rated), in selecting a rating. -
-What's the difference between "teen and up" and "mature"?
-Likewise, this is almost entirely up to the creator's judgment. In response to valid complaints about highly explicit content, the abuse team may redesignate a fanwork marked "general" or "teen and up" to "not rated," as explained in the - <%= link_to ts("abuse policy"), tos_path(:anchor => "content") %>, but our policy is generally to defer to the creator's decision. -
-Suppose I'm searching for explicit fanworks. How will "not rated" Fanworks be treated in my search?
-You can include or exclude "not rated" Fanworks from a ratings-based search. -
-What are "Archive" and "additional" tags?
-In addition to ratings, the Archive provides two separate lists of tags for creators to choose from when uploading a fanwork. These tags allow creators to ensure that their stories are accurately labeled. They are also helpful for many users in finding and categorizing work, or avoiding work which they may not want to see. -
-When uploading a fanwork to the Archive, creators must choose at least one item from the Archive tags list. Along with some specific warnings, the list allows creators to select "choose not to use Archive warnings," and "none of these warnings apply." It is also possible to choose multiple Archive warning combinations, e.g. both "underage" and "graphic description of violence" if a fanwork contains both elements, or "choose not to use Archive warnings" and "underage" if the creator wants to disclose the underage content but doesn't want to say whether the work contains major character death. It's a little messy in that type of rare case, but trying to express that concept in other ways led to significant confusion. -
-Creators may also choose to add additional tags to their work. These tags can be serious or humorous. They can be warnings or promises, or whatever else the creator chooses. Tags may be made synonymous for purposes of filtering by our Tag Wranglers, but your tags will continue to appear in their original form on your work. -
-Please see - <%= link_to ts("our ratings and warnings policy"), tos_path(:anchor => "IV.K.2") %> for more information. -
-What's the purpose of the Archive tags?
-The purpose is to identify subjects that have been the subject of substantial, recurring debate in many sectors of fandom and provide an easy way to warn for those subjects (though a choice not to warn is always acceptable as well). We also decided to limit the Archive tags to a small number of subjects out of concerns for enforcement. Concepts like "dubious consent" vary substantially from person to person, and we decided that we could not reasonably expect fair enforcement of a rule requiring warnings (or a signal that the author chose not to warn) for concepts beyond those listed in the Archive warnings. -
-What do you mean by "underage" in the Archive tags?
-Underage refers to descriptions or depictions of sexual activity by characters under the age of eighteen (18). In general, we rely on authors to use their judgment about the line between reference and description or depiction. Sexual activity does not include dating activity such as kissing, but again, we rely on authors to use their judgment about what is generally understood to be sexual activity. An author may always specify the age of the characters. -
-Why is "underage" defined as "under 18"?
-Though there is no international consensus, there is a trend to focus on 18 as an important age in regulating depictions of sexual activity (as opposed to actual sexual activity/age of consent, which is regulated in many more varied ways). Thus, we decided that 18 would be helpful for the maximum number of users, including audiences as well as creators, though we recognize that no solution is perfect for everyone. We encourage creators and recommenders to be more specific in tags or summaries where this would be useful to potential audiences. -
-Note from the Content Policy committee: With the exception of user icons, the Archive hosts only text, but we do plan to expand over time, and we do allow embeds of certain types of files <%= link_to ts("hosted elsewhere"), archive_faq_path("posting-and-editing", anchor: "hostsites") %>, which are also subject to the Content Policy. Because regulations of sexually explicit content are generally concerned with visual depictions, there is potentially more flexibility for textual depictions. The current rule is for 18 across the board, but we welcome suggestions on alternatives, especially from people with an interest in fan art. -
-What about robots, computer simulations, elves, aliens, vampires who are three hundred years old but were turned into vampires at age 12, etc.?
-The core use of the underage label is to identify fanworks depicting sexual activity by humans under the age of eighteen as measured in Earth years. Please use your judgment for other situations. If the fanwork does not include a depiction of sexual activity with a human under the age of eighteen as measured in Earth years, then we will not generally consider it "underage," though creators may use the tag if they feel it accurately represents their intent. As always, we encourage creators and recommenders to be more specific in tags or summaries where this would be useful to potential audiences. -
-What about when a vignette or other fanwork doesn't specify the characters' ages?
-The presumption is that the characters are of age unless the fanwork's creator indicates otherwise. -
-What if there's only a brief reference to rape in a story–am I required to use either "rape" or "choose not to use Archive warnings," or can I still choose "none of these warnings apply" if I think that's a better description?
-This is the kind of decision that is up to the discretion of authors. In general, we will not recategorize a fanwork in response to a complaint when the content at issue is a reference or is otherwise not graphic. -
-You say that logged-in users can hide warnings. Why is that?
-Some people consider warnings as spoilers and try to avoid them. This is part of our attempt to make the Archive user-customizable. -
-If I'm not logged in, what can I see?
-You can see anything rated "general" or "teen" without logging in or clicking anything else. For the other ratings ("mature," "explicit," and "not rated") you will be asked to agree that you are willing to see such content. -
-Something that I consider really immoral, dangerous, triggering, or outrageous is not on the Archive list for warnings.
-We're very sorry. We encourage you to use the additional tags, summaries, and user-provided bookmarks and recommendations to screen for fanworks you'll enjoy, and you may wish to comment to creators when you feel that further warnings would be desirable. The content policy committee would also like to hear your suggestions for the tag system. -
-How will you apply the ratings and warnings policy to embedded images, videos, etc.?
-In making rating/warning decisions, creators should take into account anything visible, including embedded images and videos. As with all other content, creators' decisions are presumed reasonable, and using "not rated" or "chose not to use Archive warnings" will always be sufficient. -
-How will the ratings/warnings policy apply to fanworks that come in through Open Doors?
-We will import the original ratings, warnings, and other associated information as part of Open Doors as best we can. However, the rating and warning systems used by older archives preserved through Open Doors may differ from our system. Therefore, an Open Doors work that can't be mapped to an Archive rating will be treated as if it were marked "not rated" and "choose not to use Archive warnings" unless the maintainer of the collection (or the original creator, if they "claim" the work) specifically selects other ratings and warnings for it. -
-How explicit or graphic can the summaries and tags on my fanworks be?
-Explicit or graphic content in itself does not violate the content policy. Please use your judgment about what will best identify and describe your fanworks. -
-Someone has added a tag I hate to a bookmark of one of my fanworks!
-We're very sorry. In general, user-provided tags can be positive or negative. Like any other content, tags are subject to the content policy, so if the tag violates the harassment, personal information, or other content policies, please report it. User-provided tags will not automatically be displayed on fanworks, in order to allow you to avoid them. -
-So user-added tags will be displayed differently than creator-added tags? How does that work?
-The tags displayed on the fanwork itself will only be the creator-placed tags. As a site user, you will see user tags in several different situations. These are the current plans: -
--
-
- If you use Tag Search, you'll be able to find fanworks that anyone, whether creator or user, has labelled with a particular tag. -
- If you use Work Search, you'll see tags from the creator. -
- You will be able to see when other people have publicly bookmarked a work. When you're looking at a given user's bookmark for a particular fanwork, you'll be able to see that user's tags. -
- You will be able to see a list of a user's public bookmarks, with associated tags, and a list of the public bookmarks for a fandom or other canonical tags, with associated tags. -
What kinds of fanworks can I post?
-You can post any noncommercial, non-ephemeral fanwork. Here are some examples of allowed content:
--
-
- An audio performance of a fannish essay about vampire biology across sources, or the same essay in text form. -
- Short clips of footage from existing sources, edited over a song to make an argument or tell a story. -
- A comic telling the romantic adventures of the protagonist of a video game. -
- Photographs of a knitted character. -
- An alternative version of a Jane Austen novel in which there's a zombie apocalypse. -
- The supporting text for an original adventure for a tabletop roleplaying game. -
What if what I want to post isn't similar to one of the examples listed in the Terms of Service FAQ?
-In general, you can post any non-ephemeral, transformative content that is fannish in nature. If you have doubts about any particular examples and you don't want to risk posting it, you can always contact our Abuse team to ask, using the Abuse form. -
-Can I archive original fiction?
-Yes and no. Although some users may want a place for all their creative work, our current vision of the Archive is of a place dedicated to fanworks in particular. The Archive was designed to serve the mission of the Organization for Transformative Works (OTW), which was "established by fans to serve the interests of fans by providing access to and preserving the history of fanworks and fan culture in its myriad forms." -
-- Because our long-term plans include hosting fanworks of all kinds, not just fan fiction, we concluded that it was better to draw a line between fanworks and non-fanworks and only host the former, in order to avoid becoming a general repository for all sorts of creative works. In addition, we will enforce the noncommercialization policy strictly, including a ban on works posted to promote the sale of the author's other works, even if those are not hosted on the site. -
-- However, there are a number of varieties of works produced by fans that do not fit comfortably into a narrow definition of fanfiction, fanart, vids, or other types of fanworks. Some of these do fall within our mission. In particular, original fiction that is part of an Open Doors project is allowed, as are types of original fiction and quasi-original fiction produced within a fandom context. Examples include such things as anthropomorfic, original fiction that is produced as part of a fandom challenge, exchange, or charity event, and genres such as Original Slash, Original BL, and Regency romances produced in Jane Austen fandom. -
-- At such time as we are able to host art and vids, we anticipate similar policies will apply to those mediums: Art and vids will be considered fannish even in cases where they do not directly depict characters and elements from or use footage from an existing media source if they were created in a fandom context for a fandom audience. This may include such things as fanart that is intended to be for a particular canon but which does not contain readily identifiable canon characters or elements, art and vids produced as part of a fandom challenge, exchange, or charity event, illustrations of fanfiction, and vids that comment on a particular canon without using any clips from it (e.g., fan-produced videos set in a particular universe). -
-- We presume that, by posting the work to the Archive, the creator is making a statement that they believe it's a fanwork. As such, unless the work doesn't meet some other criterion, it will be allowed to remain. -
-Can I archive nonfiction?
--Fannish nonfiction, which includes what is called 'meta' by some fans, is allowed. Where we provide a specific function (search, bookmarking, challenges) we will ask you to use the specific methods we provide for those activities rather than create separate works. So, for example, a request for recommendations for particular kinds of fanworks would not be an appropriate work. That search should be carried out by searching works and/or bookmarks. A list of recommended works on a particular topic would also not be an appropriate work. Recommendations should be done by using our bookmarking function. A description of a challenge for other creators would also not be an appropriate work. That should be carried out by using our challenge function. -
--In addition, as an Archive whose goal is preservation, we want permanent, nonephemeral content. To the extent that your content is designed to be ephemeral, such as liveblogging episode reactions, it should go on a journaling service and not the Archive.
-How will 'ephemeral' be defined?
-'Ephemeral' applies to the nature of the work–designed to be experienced in a particular time period rather than the creator's desire to have a permanent record of their reaction, such as can be found on a journaling or blogging service. Our resources and database structure make it difficult for us to plan to host content of this type. -Please use your best judgment; our general policy is to defer to creators in cases of doubt. Ephemeral content could include, for example, a single short sentence, a single unedited image or .gif with or without a short caption, a short unedited video clip, or a short unedited sound clip. Ephemeral content is generally meant to be read at a particular time: for example, a message about a particular challenge or a reaction meant to be read while or just after a particular episode airs. -
--Our policies are designed to focus on our mission of preserving fanworks within our resource constraints, including the constraints on our hardworking, all-volunteer Abuse team.
-What falls within the definition of fannish nonfiction?
-Fannish nonfiction can be discussions of fannish tropes, essays designed to entice other people into a fandom, commentary on fandoms, hypothetical casting for alternate versions of works, documentaries, podcasts about fandom, explanations of the creative process behind a fanwork or works, tutorials for creating fanworks, guides for fan-created gaming campaigns, or many other things. -
--However, the nature of the Archive and the limitations of our resources mean that, while we will endeavor to host as much fannish content as possible, we need to put some limits on allowable works. In particular, the Archive is not a journaling service and it is not designed to host ephemeral content. -
--In addition, we have a separate project, Fanlore, which is a wiki designed to chronicle fandom history. Some fannish content, especially discussions of specific fandom-related events such as conventions or debates over particular incidents, may be more appropriate for Fanlore than for the Archive. -
--We will, in general, defer to the creator's characterization of a work as fannish nonfiction as long as it has a reasonably perceptible fannish connection, either to a specific source or to fandom in general, and takes the form of an independent, nonephemeral commentary. For example, an analysis of or commentary on multiple fanworks falls within our definition (and must comply with our other policies, including our harassment policy). An essay on a particular character's narrative arc in canon or of the interaction between film and comics versions of a source is also within our definition. -
--We understand that, as with many things, there are hard cases at the edges of categories, but we nonetheless need some limits in order to keep the Archive manageable for our hard-working volunteers as well as for other users.
-What isn't fannish nonfiction?
-The examples are potentially limitless, but here are some examples that we believe, based on our experience so far, do not qualify as fandom nonfiction and should not be posted as a work:
--
-
- episode transcripts and other non-transformative fandom material; -
- primarily autobiographical or non-fandom-related essays (e.g., essays on bike lanes, even if they contain a single reference to a fannish source); -
- general complaints about behavior towards a particular creator (e.g., a post stating that a work was deleted due to lack of feedback); -
- suggestions that other fans contact the creator through email or other social networks; -
- a single word or pairing name repeated hundreds of times; -
- offers and giveaways. -
As with all works, we presume good faith on the part of our users, and ask that you do the same for the fans who make up our Support and Abuse teams.
+ +Terms of Service FAQ
+ -How will you draw the line between fanworks and non-fanworks?
-The presumption is that a work is a fanwork, but if it's clear from context—tags, author's notes, etc.—that it's not, it may be removed for violating the Content Policy. Please note that alternate universes/alternate realities or fanworks set in the distant past/future of a particular canon are still fanworks. Original works that are not based on a specific media source (canon) may also count as fanworks so long as they are fannish in nature. Please see "Can I archive original fiction?" above for more detail. -
-What about nontextual works (like pictures of Daleks I crocheted)?
-We currently don't host nontextual works other than user icons, though <%= link_to ts("you can embed various kinds of files that are hosted elsewhere"), archive_faq_path("posting-and-editing", anchor: "hostsites") %>. If it's a fannish transformative work or part of one, and otherwise complies with the content policy including the rating/warning policy, embeds are fine. Just be aware that we don't allow all kinds of embeds, for technical reasons, and that embeds may break for various reasons including trouble with the host site. -
+ +<%= t("a11y.navigation") %>
+<%= render "tos_navigation" %> + -What is a fanwork's 'type'?
-We expect to define a fanwork's type partly by its medium, and partly by its content. Thus, a fanwork can be text, audio, images or video (all different types), and it can be fiction or non-fiction.
-How does tagging apply to work type, such as textual content, and podfics, vids, and other nontextual content? Do I need to use particular tags?
-Please use tags that you think will help people identify works of the type you're posting; this can include fanwork types (e.g., podfic, vid, essay). Anything visible on the Archive should also follow the ratings/warnings policy.
-Later versions of the Archive will have specific work types that can be selected on posting. No one will be penalized for having posted a work that, because of the implementation of work type, becomes technically "mislabeled." However, we may try some automated solutions for detecting work type and/or ask creators to change a work type when they posted before work type was introduced. Part of the transition may thus be to automatically set work type based on the presence or absence of certain tags or other work content, then notify the creators and allow them to change the work type if the automated process made a mistake. Administrators will also have the ability to correct an obvious miscategorization of work type (that is, a case that is not borderline even after deference to the creator) if the creator fails to respond to an inquiry after a reasonable time.
-What kinds of mis-tagging does Abuse handle?
-We encourage direct dialogue with the creator. However, Abuse also handles complaints about work language (e.g., Chinese mistagged as French); Archive warnings; Archive ratings; fandom categorization and work type (once work type is implemented). Tag recategorization policies are about required tags. Abuse will not recategorize any optional tags, though optional tags are subject to relevant principles of the general content policy, including the harassment policy. Unless a tag violates some other policy, such as the harassment policy, Abuse will not mediate disputes about general tagging (e.g., whether a particular relationship tag should or should not be present).
-What do you mean by recategorizing a fanwork type?
-For technical reasons relating to how our database is planned to evolve, we need for Archive administrators to have the ability to change a work type where it is clearly appropriate (e.g., a review essay or fanvid mistakenly or inadvertently categorized as textual fiction). Because work type will be a new addition (and we may create new categories over time), we understand that users won't necessarily go back and change the work type on previously uploaded works. Inaction on already-existing works will not be grounds for any penalty for users, even if we do later ask that the work type be changed to reflect what it is. People will also make mistakes when work type is in place.
-As part of the transition to formal work types, we may automatically set work type based on the presence or absence of certain tags or other work features, then notify the creators and allow them to change the work type if the automated process made a mistake.
-Once work type is in place, our general policy when a recategorization is clearly appropriate will be to ask the user to recategorize the work, and change the work type if we receive no response. In addition, our general policy is to defer to the creator's choices in borderline cases.
-What do you mean by a manual recategorization?
-A manual recategorization is an individualized determination that a specific work has been miscategorized, made as the result of a specific complaint. By contrast, any automatic process we use to detect work type will operate outside the abuse process, not as a manual recategorization.
-When will you change a language tag?
-When Abuse determines that there is no reasonable dispute that the work is not properly categorized, subject to ordinary Abuse procedures.
-When will you remove a fandom tag?
-When Abuse determines that there is no reasonable dispute that the work is not properly categorized, subject to ordinary Abuse procedures. Please note that we will apply this rule restrictively. We will not intervene in cases of disagreement over, for example, whether movie-based works can be tagged using comics/graphical works fandoms when there are both movie and comics versions of a source. This is the kind of decision a creator is best suited to make and falls within our policy of deference to the creator.
-A fandom tag may be removed where there is no relationship between the particular fandom itself and the work. E.g., a fanwork that discusses vampire physiology and uses only examples from Buffy the Vampire Slayer and The Vampire Diaries fanworks should not add in fifteen additional fandoms that also feature vampires (though it can use "various", "fandom", or "fandom-general").
-Will you recategorize or remove other tags, such as relationship tags?
-Because our Abuse and Support resources are limited, and because different people interpret tags in many different ways, we don't think that we can fairly define or enforce specific rules about relationship or other similar tags, including the additional/freeform tags. We encourage users to engage with each other on these issues. However, our general harassment and anti-spam policies apply to tags, as they do to all Archive content.
- - -What should I do about recs/commentary on fanworks?
-<%= link_to ts("Our bookmarking feature"), archive_faq_path("bookmarks") %> is designed for your recommendations or commentary on specific works by other creators. You can bookmark fanworks hosted on the Archive or fanworks hosted elsewhere. Many creators also welcome discussion in the comments to the work, which is another appropriate place for such commentary. As always, while criticism of a fanwork is not itself harassment, content must comply with our other policies, including our harassment policy. -
-I would like to create a list of recommendations or a list of works that use certain tropes.
-Please use our bookmarking and recommending feature for this purpose. Any user with an account can create bookmarks and mark them as recommendations if they so desire. Bookmarks and recommendations can also be tagged, and filtered by those tags, creating groups of bookmarks or recommendations that can be linked to by using the URL of the resulting filtered list.
-What counts as a recommendation that should be in a bookmark versus a more general discussion or analysis of multiple fanworks?
-Please use your judgment on the best way to categorize a commentary. Our general policy is to defer to creators.
-How does the harassment policy apply to reviews?
-The Terms of Service state 'When judging whether a specific incident constitutes harassment, the abuse team will consider factors such as whether the behavior was repeated, whether it was repeated after the offender was asked to stop, whether the behavior was targeted at a specific person, whether that target could have easily avoided encountering the behavior, whether the behavior would be considered unacceptable according to normal community standards, etc.' This policy applies to reviews. Again, criticism of a fanwork, even harsh criticism, is not itself harassment. Calling a creator evil, wishing harm to them, and repeatedly posting negative commentary in a manner designed to be seen by the creator are potential examples of harassment.
-What about 'directors' cut' or 'commentary' versions of my own fanworks?
-We consider those versions of your fanworks, so post them as you would any other fanwork, though we suggest that you distinguish them from non-commentary versions, for example by adding [Directors' Cut] in the title or tagging them to indicate the difference between the original and the 'DVD-style' version. -
-What about 'characters read' or DVD commentary-style/MST3K-style versions of other works?
-If you have permission from the author or if the work is in the public domain, you're fine. In other cases, if you are reproducing a substantial part of the original (rather than just having your characters react to their reading or using occasional quotes) in a way that someone could just ignore your additions and read a substantial, continuous part of the original, then that's beyond what we're prepared to host. -
-I am looking for a particular story. Can I create a work explaining what I'm looking for?
--Please use our search functions for this rather than creating a separate work.
-What about a fanwork prompt?
-Please use our challenge function for this rather than creating a separate work.
-What about a letter to someone I've been anonymously matched with for a challenge?
-Since this content is designed to be ephemeral/nonpermanent and directed at a particular person, please do not create a separate work for it. If the challenge is hosted on the Archive, please put them in the optional details for the challenge. If not, and these are your general preferences, you can put them in your profile.
-May I post the full lyrics of a song or an entire poem that isn't in the public domain without the author's permission?
-No. -
-What about character playlists or fanmixes?
-You may use streaming sites such as Spotify, 8tracks, or YouTube, but you may not provide links that could deliver individual music file downloads, or a single zipped file containing music files, unless you have the right to distribute downloads (for example, a fan song or filk you composed and sang, a work in the public domain, or a Creative Commons-licensed download). Please also keep in mind that you may quote lyrics as part of a transformative work, but you may not reproduce the entire song text unless you have the right to do so.
-May I post someone else's fanworks, giving them credit?
-If you are an archivist seeking to back up your archive of works submitted by other creators, you can do this, but only by using our Open Doors project, which can assist you with importing and/or backing up your archive within the Archive of Our Own. Importing others' works without the involvement of Open Doors risks suspension or termination of your account. If you are not an authorized archivist, you may not post another creator's fanworks without permission. -
-How do I report a violation of the Terms of Service?
-Please use the <%= link_to ts("Report Abuse form") , new_abuse_report_path %> and provide the specific link, as well as any other information required to investigate the violation. You can report a violation both anonymously and under a email address, but take into account you will not be contacted about the case if you report it anonymously.
-Do you have a DMCA (Digital Millennium Copyright Act) notice and takedown policy?
-Yes. Please read <%= link_to ts("our DMCA policy"), dmca_path %> carefully.
-Tags and Warnings
- -Archive Tags
-Authors must choose at least one of these tags. The default is "choose not to use Archive warnings." -
+ +Main Text
++-This document addresses common questions about the AO3 Terms of Service and how our policies are implemented. If you have any questions not answered by this FAQ, you can contact the Policy & Abuse committee.
+- + Privacy Policy FAQ + +
+ + +General Principles FAQ
+Answers to common questions about the General Principles of the AO3 Terms of Service are available below. If you have additional questions that are not covered here, you can contact the Policy & Abuse committee.
+ +General Questions
++++
+Table of Contents
+-
+
- Why does the Archive of Our Own (AO3) have a goal of maximum inclusiveness of fanwork content? +
- What does it mean for AO3's Terms of Service (TOS) to be governed by the laws of New York? What if I am a resident of a different state or country? +
- What is an "implied warranty of merchantability"? +
- What is an "implied warranty of fitness for a particular purpose"? +
- Why are you talking about buyers and sellers? Are you selling things? +
- What counts as an official statement from the OTW? +
- What do you mean by "a worldwide, royalty-free, nonexclusive license"? +
- What do you mean by modifying or adapting content? +
- What are the rules for removing and retaining content on various parts of AO3 that are not fully controlled by the original poster? +
- How can I check if my country is under a comprehensive trade embargo by the US? +
- Under what circumstances would you suspend an account for an invalid email address? +
- Why did you license the Terms of Service under the Creative Commons Attribution 4.0 International License? What does that mean? +
- Does AO3's Terms of Service use material or inspiration from documents by other people? +
Why does the Archive of Our Own (AO3) have a goal of maximum inclusiveness of fanwork content?
+AO3 was founded partly in response to a growing trend of fanworks being removed from websites that had previously allowed them. Commercial entities have frequently permitted fanworks in the early stage of their existence in order to expand their userbase, only to later prohibit certain types of fanworks from being shared on their platform. This pattern has been observed numerous times throughout fandom history. We want AO3 to be a non-commercial space where creators are able to permanently preserve and freely share as many of their fanworks as possible.
+What does it mean for AO3's Terms of Service (TOS) to be governed by the laws of New York? What if I am a resident of a different state or country?
+AO3 operates under the jurisdiction of Manhattan, New York in the United States. As such, the interactions between AO3 and its users, as well as the definitions in the TOS, will comply with U.S. legislative interpretations. If you reside in a different state or country, it is your responsibility – not AO3's – to know about and follow the laws in your local jurisdiction. For example, if certain content on AO3 is restricted under your local laws, it is not AO3's duty to delete that content for you; instead, it is your responsibility to avoid accessing that content.
+What is an "implied warranty of merchantability"?
+An implied warranty of merchantability is a legal agreement between a seller and a buyer that goods will be reasonably fit for the general purpose for which they are sold. For example, if you buy a toaster, it should be able to toast bread. It doesn't have to be perfect, but it should function as a typical toaster would.
+This warranty is governed in the United States by the Uniform Commercial Code (UCC), which allows sellers to "disclaim" it. Disclaiming a warranty cancels the promise, which means the buyer takes on the risk that the product may not work as expected. By disclaiming this warranty about AO3, we are saying that you cannot hold us legally responsible if AO3 does not work as expected (in other words, you can't sue us).
+What is an "implied warranty of fitness for a particular purpose"?
+An implied warranty of fitness for a particular purpose is a legal agreement that exists when a buyer relies upon the seller to provide goods to fit a specific request. For example, if you ask a salesperson for a pair of boots to hike in the snow, and they sell you boots based on that request, they are making a promise (warranty) that those boots will be good for hiking in the snow. The seller has to know two things: 1) the buyer has a specific need, and 2) the buyer is relying on their recommendation. If both of those conditions are met, this warranty applies.
+This warranty is governed in the United States by the Uniform Commercial Code (UCC). Like the implied warranty of merchantability, sellers can disclaim it, thereby shifting the risk back to the buyer. By disclaiming this warranty about AO3, we are saying that you cannot hold us legally responsible if AO3 does not suit the purpose you wanted to use it for, even if we know why you wanted to use it and you are relying on our recommendation to use it. For example, if you want to use AO3 to post your fanworks, but you find that you don't like AO3's posting interface and prefer to use another fanwork site, you can't sue us because our site doesn't meet your needs.
+Why are you talking about buyers and sellers? Are you selling things?
+No, AO3 is and always will be free to use. We don't sell anything. We don't sell products to you, and we also don't sell advertisement space or user data to third parties. AO3 is run by the Organization for Transformative Works (OTW), a non-profit which is funded by donations, not sales or advertisements. However, U.S. law regarding services and contracts generally assumes that one party is a buyer and one party is a seller, even if the service being "sold" is free (as in our case). We use this standard language to make sure that we aren't promising you something that we can't provide.
+What counts as an official statement from the OTW?
+Official statements are communications made by volunteers while they are fulfilling their formal volunteering responsibilities. These can include news posts and comments from official accounts.
+Comments from official accounts are only official OTW statements when the volunteer is both acting in their official OTW role and providing information about the OTW or any of its projects or policies. For example, a news post moderator using an official account to reply to a question about a news post is acting in an official capacity; however, a volunteer who is using an official account to reply to a comment on a "Five Things" post about them (which is about that volunteer's personal opinions) is not acting in an official capacity.
+What do you mean by "a worldwide, royalty-free, nonexclusive license"?
+This means that we can make the content you post on AO3 available to other people who use AO3, without paying you. We will never charge for access to AO3 or otherwise sell your content. You can also put your content on other sites if you want, or remove it from AO3 if you no longer want it here.
+What do you mean by modifying or adapting content?
+This refers to how your work is displayed on the site, not how it is written, drawn, or otherwise created. For example, we may display portions of your content on some pages of the site, such as by showing your work's summary and tags in search results. We may also make changes to the formatting or display of your content in order to adapt to the technical requirements of different networks or devices, or to improve accessibility. For example, we may automatically convert HTML tags to our standard forms (for example, changing <bold> html tags to <strong>) or allow you to use nonstandard fonts and formatting while providing an alternate format for accessibility.
+What are the rules for removing and retaining content on various parts of AO3 that are not fully controlled by the original poster?
+-
+
- Orphaning a work: Orphaned works will not be edited or removed unless they contain unauthorized information which may identify the creator or otherwise violate the Terms of Service. +
- Participation in a Challenge: The maintainer(s) of the challenge may edit or delete the sign-up or prompt, or remove a work from their collection, at any time. +
-
+ Comments on someone else's work:
+
-
+
- The creator(s) of the work may freeze or delete comments on their work at any time and for any reason. They may also enable comment moderation and choose to leave comments unreviewed, or mark guest comments as spam. +
- Registered users can delete their own comments at any time. Guest users cannot delete their own comments. +
- The Policy & Abuse committee may delete comments in situations where a violation of the Terms of Service has occurred. +
+ - Comments on an official AO3 or OTW post: Comments on official AO3 or OTW posts may be frozen, hidden, marked as spam, or deleted in accordance with the OTW News Post Moderation Policy. +
How can I check if my country is under a comprehensive trade embargo by the US?
+The U.S. Office of Foreign Assets Control (OFAC) provides up-to-date details regarding all current embargoes (including but by no means limited to comprehensive trade embargoes) on their website. Princeton University has a list of countries that are comprehensively sanctioned by OFAC.
+Under what circumstances would you suspend an account for an invalid email address?
+If we need to communicate with you to resolve an Abuse report, we will email you at the address associated with your AO3 account. If you do not check your email, or if you cannot receive emails because your email address is inaccurate or invalid, then we will have to resolve the complaint without your input. A sufficient number of sustained Abuse reports that fail to be delivered ("bounce") or do not receive a response could lead to permanent suspension.
+If our emails to you repeatedly bounce, then we may suspend your account because we need to be able to communicate with you if necessary. In that situation, you can log in and get your account reinstated by associating it with a working email address. Then, if necessary, you can deal with whatever problem led to the Abuse report in the first place.
+Having an invalid email address will not necessarily cause you to be suspended. However, if you violated the Terms of Service in other ways, those violations will not be excused just because you didn't receive our emails. It is your responsibility to ensure your email address is accurate and messages can be delivered to it. Repeated violations of the Terms of Service may result in a temporary suspension or a permanent ban, regardless of whether or not you were able to receive our emails warning you about the violations.
+If we send a routine email about general site policies and it bounces, that will not lead to account suspension, but whatever policies we announce will still apply to all account owners. We will only suspend accounts with invalid email addresses when individual Policy & Abuse–related communications bounce.
+Why did you license the Terms of Service under the Creative Commons Attribution 4.0 International License? What does that mean?
+Creative Commons licenses allow people to use others' works under certain predefined conditions. The Creative Commons Attribution 4.0 International License (CC BY 4.0) permits you to use material from our Terms of Service (including the Content Policy and Privacy Policy) for any purpose, as long as you meet all of the following requirements:
+-
+
- Give appropriate credit: You need to say that the material was created by us and provide a link to the CC license. +
- Indicate if changes were made: If you changed something from our original material, say so when crediting us. +
- Don't suggest we endorse your use: While you're free to adapt our material for your own use, you can't claim that we reviewed or authorized your specific work. +
- Don't impose additional restrictions: You may not apply legal terms or technological measures that restrict others from doing anything that this license permits. +
An example of appropriate attribution would be: "This work uses material from AO3's Terms of Service, which was released under a CC BY 4.0 license."
+Does AO3's Terms of Service use material or inspiration from documents by other people?
+Material in AO3's Terms of Service has been drawn from imeem and NearlyFreeSpeech.NET.
+Back to Top | General Questions
+
+Age Policy
++++
+Table of Contents
+-
+
- Why are children under the age of 13 not permitted to have an AO3 account or upload content? +
- Why are children under the age of sixteen (16) who are residents/citizens of certain countries not permitted to have an account or upload content? +
- What happens to an account or its content if the account owner is reported for violating the Age Policy? +
- Why are children in the EU not allowed to ask their parent or legal guardian to upload content for them? Does this apply to children elsewhere, such as in the UK or the EEA? +
Why are children under the age of 13 not permitted to have an AO3 account or upload content?
+In the United States, the Children's Online Privacy Protection Act (COPPA) governs the collection of personal information, including usernames and email addresses, from children under 13. Because the Organization for Transformative Works is a non-profit and does not sell any data, COPPA does not apply to AO3; however, we adhere to the same restriction as a matter of policy.
+Why are children under the age of sixteen (16) who are residents/citizens of certain countries not permitted to have an account or upload content?
+In some countries in Europe, the General Data Protection Regulation (GDPR) governs the collection and processing of personal data, including email addresses and IP addresses, as well as certain uses of cookies. Other countries may have similar data privacy laws. The age at which someone can consent to the collection of personal data without written permission from their parent or legal guardian may be higher than 13, depending on their country of residence. We do not want to store the type of detailed personal information about users that would be required to verify and accept such permission. Therefore, children who wish to create an account or upload content to AO3 must meet their country's minimum age requirements to legally consent to personal data collection without written permission.
+What happens to an account or its content if the account owner is reported for violating the Age Policy?
+If the Policy & Abuse committee determines that a violation of the Age Policy has occurred, the account will be suspended and content on the account may be removed. If the content is not removed, the suspended user or their parent or guardian can contact the Policy & Abuse committee to request deletion of the content associated with the account.
+If you were previously suspended because of your age and you are now old enough to have an account, you may contact the Policy & Abuse committee to regain access to your account.
+Why are children in the EU not allowed to ask their parent or legal guardian to upload content for them? Does this apply to children elsewhere, such as in the UK or the EEA?
+AO3 adheres to the GDPR's requirements for handling the content and information of children within the GDPR's jurisdiction. Accordingly, the parents or legal guardians of children within the European Union are not allowed to upload their child's content under their own (the parent or guardian's) account.
+This restriction does not apply to children in the United Kingdom or the European Economic Area (unless the child is also a resident or citizen of an EU country).
+ +
+Abuse Policy and Procedures
++++
+Table of Contents
+-
+
- How do I report a violation of the Terms of Service (TOS)? +
- What language should I select when submitting a report? +
- Why aren't Digital Millennium Copyright Act (DMCA) notices covered by the Abuse Policy? What's the difference between a DMCA notice and an Abuse report? +
- Can I submit an Abuse report even if I don't have an AO3 account? +
- Will I receive notification that my complaint was resolved? How long will it take? +
- Do you monitor content on AO3 for violations of the Terms of Service? +
- I'm not sure whether something is against the rules. What happens if I report something that doesn't violate the Terms of Service? +
- How do you determine whether content needs to be removed? +
- Would a work be removed if enough people reported it? What if someone repeatedly or intentionally submits complaints about something that doesn't violate the Terms of Service? +
- What if the content I reported was deleted or edited before the Policy & Abuse team can investigate? +
- The instructions on the Policy & Abuse form say to include the username of the person I'm reporting. What if I want to report a guest comment or an anonymous or orphaned work? +
- If I submit an Abuse report, will the subject be told who reported them? +
- Will I be informed if an Abuse report is filed about me or my work? +
- How do I find out who reported or complained about me? +
- What happens if a report is made about me and the Policy & Abuse committee determines that the complaint is valid? +
- Will I be notified if my work is hidden or deleted, or if I get suspended? +
- I received an email from the Policy & Abuse committee, but I don't agree with or understand their decision. How do I appeal? +
- Are there any appeals that you will not grant? +
- If I disagree with the Policy & Abuse committee's decision, can I appeal to someone else, like the Support committee or the OTW Board? +
- I was given a deadline to edit or delete my work, and I have done so. What happens next? +
- I was given a deadline to edit or delete my work, but I'm not going to make it in time. Can I have an extension? +
- My work was removed by the Policy & Abuse committee. Can I repost it? +
- What if the violating content was posted years ago? +
- What do the different penalties mean? +
- What happens to a user's works or other content when they are temporarily suspended? +
- What happens to a user's works or other content when they are permanently suspended/banned? +
- What sort of things would lead to each type of penalty? +
- What constrains the Policy & Abuse committee's discretion? +
- What happens if someone who's a friend of someone on the Policy & Abuse committee is involved in a complaint? +
- AO3 is still being actively developed. How will the Abuse Policy apply to planned future features? +
How do I report a violation of the Terms of Service (TOS)?
+Please contact the Policy & Abuse committee. You must provide your email address and a direct link to the specific content you want to report. In the subject and description of your report, please briefly describe the content you are reporting, explain why you are reporting it, and include any additional links or other details that could help us investigate the violation. If you don't provide this information in your report, we may not be able to investigate or act upon your complaint.
+If you are reporting a specific comment or comment thread, you can get the direct link by selecting the "Thread" button on the comment and copying the URL of that page.
+If you are reporting multiple works or comments posted by the same user, please compile all relevant links and other information into a single report, rather than reporting each link individually.
+If you wish to report content posted by multiple unrelated users (such as two different works by different people in the same fandom), please submit separate reports for each user.
+What language should I select when submitting a report?
+In general, if you are not comfortable with reading and writing in English, you should use the language you are most fluent in. If you are fluent in English and you are reporting something written in another language, you can either select English or choose the language of the content you are reporting.
+Why aren't Digital Millennium Copyright Act (DMCA) notices covered by the Abuse Policy? What's the difference between a DMCA notice and an Abuse report?
+A DMCA takedown notice is a legal mechanism that a copyright owner can use to request removal of their copyrighted material from a hosting site. The takedown notice must meet certain legal requirements. For example, you must declare under penalty of perjury that you are the copyright owner or are legally authorized to act on their behalf. As such, DMCA notices are assessed by the Legal committee, and valid notices may be forwarded to the user who posted the work. We reserve the right to make public all DMCA notices that we receive, though some information may be redacted for privacy. DMCA notices are not subject to the procedures described in the Abuse Policy, nor are they governed by the Policy & Abuse confidentiality policy.
+Abuse reports, on the other hand, are held to a very high standard of confidentiality. They can be about any violation of the Terms of Service, including copyright infringement, harassment, commercial promotion, etc. Abuse reports are evaluated by the Policy & Abuse committee, who will never publish the details of a report or reveal any information about who submitted it.
+Please do not submit an Abuse report if you intend to file a DMCA notice. Submitting both an Abuse report and a DMCA notice about the same content may delay the processing of both requests.
+Can I submit an Abuse report even if I don't have an AO3 account?
+Yes, but your report will be screened by our automated spam filters. If your report is rejected as spam, try using a different email address or removing extra links from your report description. Please also enter a valid email address so that we can contact you to request any additional evidence.
+Reports from registered users are not subject to the spam filter, so long as you are logged in and the email address entered into the form is the one associated with your AO3 account (this will be prefilled for you).
+Will I receive notification that my complaint was resolved? How long will it take?
+We will make a reasonable attempt to accommodate a complainant's reply preferences. However, we may choose not to reply to complaints at our discretion, particularly if it is a non-urgent matter or if the complainant submits frequent, duplicate, or baseless reports.
+Whether or not we reply to the complainant, our volunteers do evaluate all reports and act upon them as necessary. Complaints will generally be prioritized based on urgency, but because the Policy & Abuse committee is a small team of volunteers, we cannot guarantee any particular timeframe for the resolution of a complaint.
+Do you monitor content on AO3 for violations of the Terms of Service?
+No. We do not prescreen content on AO3, nor do we review content that has not been reported. If you believe you have encountered content that violates our Terms of Service, you will need to submit an Abuse report.
+Please refrain from seeking out works that are in violation of the Terms of Service for the sole purpose of reporting or mass-reporting them. We investigate every report we receive, so submitting duplicate reports will only serve to delay the processing of the original complaint.
+I'm not sure whether something is against the rules. What happens if I report something that doesn't violate the Terms of Service?
+You can submit a report even if you aren't sure something is a violation. If the Policy & Abuse committee determines that what you reported is not in violation, you will receive an email letting you know and explaining why that type of content is allowed on AO3.
+If you repeatedly submit reports about similar non-violating material, your subsequent reports may not receive a reply.
+How do you determine whether content needs to be removed?
+Abuse reports are reviewed by humans, not algorithms or bots. After a report is submitted, the Policy & Abuse committee reviews the reported content and independently evaluates whether or not it complies with our Terms of Service. If we determine that the content is in violation of the Terms of Service, only then do we take action to resolve the matter.
+Would a work be removed if enough people reported it? What if someone repeatedly or intentionally submits complaints about something that doesn't violate the Terms of Service?
+Multiple complaints about the same issue increases the time it takes for us to investigate, but we don't make decisions based on how many times something is reported. Mass reporting will not change whether or not the reported content is in violation of the Terms of Service, nor will it cause an issue to be addressed faster.
+You don't need to worry that anyone's works will be taken down due to a baseless report or a mass-reporting campaign. We will only contact the subject of a complaint if they have in fact violated the Terms of Service. If we receive a report about something that isn't a violation, we will let the reporter know and close the report. If someone attempts to abuse our reporting system, such as by intentionally submitting baseless complaints, we may consider that harassment and take appropriate action.
+What if the content I reported was deleted or edited before the Policy & Abuse team can investigate?
+We appreciate good-faith attempts to resolve disputes, and in most such cases will close the complaint with no further action. However, we reserve the right to consider individual circumstances, including whether the poster has engaged in a pattern of such conduct. In such cases, if we verify that the original content violated the TOS, we may still decide to warn or suspend the original poster.
+The instructions on the Policy & Abuse form say to include the username of the person I'm reporting. What if I want to report a guest comment or an anonymous or orphaned work?
+You can mention in your report that the content was posted anonymously or orphaned. Content that violates the Terms of Service will be removed regardless of whether the original poster's name is publicly displayed. Penalties may be applied to the accounts of users responsible for posting violating content.
+If I submit an Abuse report, will the subject be told who reported them?
+In general, no. Abuse reports are kept strictly confidential. We do our best not to reveal any information about the identity of a complainant (such as a username), though in some circumstances it may be impossible to keep the source of the report completely anonymous. We do not ever disclose information that would be sufficient to identify a person in the physical world, such as an email address or legal name. For more information, please refer to the Policy & Abuse Confidentiality Policy.
+Complaints can be submitted anonymously, but an email address is required. If you do not provide a valid email address and the complaint requires follow-up, we may be unable to take action.
+Will I be informed if an Abuse report is filed about me or my work?
+In general, the Policy & Abuse committee will only contact the subject of a complaint if there appears to be a violation of the Terms of Service, or if the team needs more information to resolve the issue.
+If someone files an invalid report against you, we will inform them that their complaint has not been upheld. You will not be told about the complaint and no action will be taken against your account or content.
+If we determine that you have in fact violated the Terms of Service, an email will be sent to the address associated with your account.
+How do I find out who reported or complained about me?
+Anonymity and privacy are essential to maintaining a fair reporting system. The Policy & Abuse committee will not disclose the identity of any complainant as part of an Abuse case.
+All users are responsible for following the Terms of Service, and all users have the right to file a complaint if they witness someone violating the Terms of Service.
+The Policy & Abuse committee will not uphold a complaint without investigating and confirming that a violation of the Terms of Service has occurred. This means that if the Policy & Abuse committee contacts you, their investigation has independently concluded that you have violated the Terms of Service.
+What happens if a report is made about me and the Policy & Abuse committee determines that the complaint is valid?
+The Policy & Abuse committee will send an email to the address associated with your AO3 account. That email will explain what the violating content or behavior is, where it occurred, and (if applicable) what you need to do to resolve it. If you cannot locate the email notifying you of your violation (please check your spam folder), you can submit an Abuse report and we will resend the original email to you.
+What happens when a complaint is upheld depends greatly on the severity of the violation. For very minor issues, such as tag miscategorizations, we will simply ask you to fix the problem on your work. Violations of other portions of the Content Policy may result in content being temporarily hidden or permanently deleted, and/or a penalty being applied to your account.
+Will I be notified if my work is hidden or deleted, or if I get suspended?
+If your work is hidden, you'll receive an automatic email informing you that it's been hidden and providing you with a direct link to the work. You must be logged in to your account to access the hidden work.
+If your work is deleted, you'll receive an automatic email informing you that it's been deleted. A copy of the work will be attached to that email.
+In addition, the Policy & Abuse committee will also separately email you to explain why your work was hidden or deleted. If you've received an automatic "your work was hidden" or "your work was deleted" notification without also receiving an explanatory email from the Policy & Abuse committee, please check your spam folder. If you still can't find it, please contact the Policy & Abuse committee to let us know that you didn't receive our explanation.
+If you are suspended, the email from the Policy & Abuse committee will inform you why you are suspended and how long your suspension will last. You will be further reminded automatically by the site if you attempt to post, edit, or delete content during the suspension period. If you were asked to edit or delete violating content on your account, you must wait until your suspension has ended in order to do so. You will not receive an email notification when your suspension is over.
+I received an email from the Policy & Abuse committee, but I don't agree with or understand their decision. How do I appeal?
+If you were contacted about something you did that is in violation of the AO3 Terms of Service, you can appeal the decision or request clarification by replying directly to the original email. If you cannot locate the email notifying you of your violation (please check your spam folder), you can submit an Abuse report, but please do not submit multiple appeals before receiving a response to the first one. Submitting multiple appeals will delay the processing of your appeal, because it creates more paperwork for us to handle before we can respond to you.
+If you submitted a complaint and were told that the subject of your complaint is not in violation of the Terms of Service, then you can appeal the decision by replying directly to that email.
+At least one Policy & Abuse administrator who was not previously involved with the original investigation will evaluate all information provided in an appeal to determine whether or not the appeal should be granted. Additional reviewers may be involved at the discretion of the Policy & Abuse committee. Please note that it may take some time to process your appeal and inform you of the result. The Policy & Abuse committee's decisions are final.
+Are there any appeals that you will not grant?
+In general, we do not email users or respond to complaints until after we have investigated the reported content and determined whether or not a violation of the Terms of Service has occurred. In order to appeal successfully, you will need to provide evidence demonstrating that our original decision was incorrect or did not adhere to the Terms of Service. If you only tell us "I want to appeal", then you haven't provided enough information for us to overturn our original ruling.
+If you are notified that your content was removed in order to resolve a lawsuit or mitigate other liability, an appeal is unlikely to succeed. These cases are extremely rare, and are thoroughly discussed and reviewed at multiple levels before any action is taken.
+If I disagree with the Policy & Abuse committee's decision, can I appeal to someone else, like the Support committee or the OTW Board?
+No. If your appeal to the Policy & Abuse committee was rejected, you cannot appeal to any other committee. The Policy & Abuse committee is the final authority on TOS violations. To protect user privacy, other committees such as the Support committee and the OTW Board of Directors do not have information about Policy & Abuse cases. If you file an appeal with a different committee, they will simply forward the complaint to the Policy & Abuse committee or tell you to contact Policy & Abuse directly.
+I was given a deadline to edit or delete my work, and I have done so. What happens next?
+After the deadline, a member of the Policy & Abuse committee will review your work. The following situations may occur:
+-
+
- If you have already deleted your work, then there is no further action you need to take. +
- If you sufficiently edited your work, we will verify your edits. If your work was hidden, we will unhide the work. You will not receive a notification when your work is unhidden. +
- If you didn't sufficiently edit your work, and the work was not already hidden, we may hide the work. Please review the original email you received from us and contact us promptly if you don't understand what further edits you need to make. Failure to make all required edits may result in the deletion of your work. +
- If your work was hidden and you did not edit or delete all violating content, we will delete the work. You will automatically be emailed a copy of the work. +
As a general rule, we will not review content in advance of any stated deadlines. While we strive to review content promptly after the deadline, the Policy & Abuse committee is composed entirely of volunteers. We therefore cannot guarantee a timeframe in which your content will be reviewed.
+I was given a deadline to edit or delete my work, but I'm not going to make it in time. Can I have an extension?
+If you need an extension on a deadline, please reply to the email the Policy & Abuse committee sent you. The Policy & Abuse committee will accommodate requests for extensions, within reason. Note that any hidden content will usually remain hidden during any extensions.
+My work was removed by the Policy & Abuse committee. Can I repost it?
+Works that have been hidden or deleted due to violations of the Terms of Service may not be reposted as-is. If you don't understand why your work was removed, do not re-upload the work. Instead, contact the Policy & Abuse committee to request clarification.
+If you know what the original problem with the work was, you may be able to edit the work and upload a non-violating version. However, if you have not sufficiently edited your work and the new work is still in violation, you may be reported again. Violating the Terms of Service in a manner similar to a previous violation is grounds for suspension.
+What if the violating content was posted years ago?
+Content that is in violation of the Terms of Service may be reported and removed regardless of how long it has been since it was posted. The user responsible for uploading the violating content may be warned or suspended, subject to the discretion of the Policy & Abuse committee.
+What do the different penalties mean?
+Penalties are issued by the Policy & Abuse committee as a result of violating the Terms of Service. They are defined as follows:
+-
+
-
+
Warning: A warning is a formal notification to a user who has posted content that violates the TOS. Warnings do not affect the function of the user's account, but they are a permanent administrative record and a reminder not to repeat the behavior. At the discretion of the Policy & Abuse committee, a warning may be issued as a result of minor or unintentional violations of the TOS. A user who has previously received a warning and who violates the TOS again, especially in the same or a similar manner, is likely to incur a suspension.
+
+ -
+
Temporary Suspension: A temporary suspension is a time-limited restriction on the uploading of new content and creation of new accounts. During this time, the suspended user cannot upload new content, nor can they edit or delete content uploaded prior to the suspension. The duration of each suspension is subject to the discretion of the Policy & Abuse committee. A user who has previously been suspended and who violates the TOS again, especially in the same or a similar manner, may incur a longer temporary suspension or a permanent ban.
+
+ -
+
Permanent Suspension: A permanent suspension is a permanent ban on the uploading of new content and creation of new accounts. Permanently suspended users retain the right to remove, but not edit, content uploaded prior to their suspension.
+
+
What happens to a user's works or other content when they are temporarily suspended?
+In general, non-violating content is not removed from the site when a user is suspended. If a user is temporarily suspended, then they will be able to edit or delete their content after their suspension is over. Otherwise, suspended users who wish to delete their fanworks may contact the Policy & Abuse committee to have this done for them.
+A user who has been temporarily suspended is not permitted to upload new content while they are suspended. Any new content uploaded to AO3 during the suspension would automatically be in violation. Such content may be removed and/or the alternate account(s) may be suspended. The duration of the original suspension may also be extended at the discretion of the Policy & Abuse committee.
+After the suspension has ended, the user will have full access to their account(s) again.
+What happens to a user's works or other content when they are permanently suspended/banned?
+Permanent suspension doesn't delete someone's account or content. In general, any content that doesn't violate the Content Policy or other parts of the Terms of Service will remain on the account unless the user deletes it themselves or requests that the content be deleted by the Policy & Abuse committee.
+A user who has been permanently suspended is not permitted to create a new account or upload new content to AO3. Any new content or accounts created by a permanently suspended user would automatically be in violation. The content may be removed and/or the alternate account(s) may be permanently suspended.
+What sort of things would lead to each type of penalty?
+It's impossible to define everything in advance. We are most concerned with people who are actively and deliberately hostile to the community. Small and honest mistakes are likely to result in warnings, especially on a first offense. More serious or deliberate violations of the Terms of Service may justify temporary suspension on a first or subsequent offense. Repeated and/or particularly severe TOS violations may result in permanent suspension.
+What constrains the Policy & Abuse committee's discretion?
+We are committed to building a community that welcomes anyone with a willingness to learn the rules while also safeguarding against those who intentionally violate them. Our discretion is aimed at that objective. We strive to handle all Abuse reports consistently, no matter which volunteer is doing the work. Procedurally, appeals undergo review by multiple Policy & Abuse committee members, and we require consensus or majority vote for major decisions. Our internal decision-making processes are designed to build in checks on individual discretion without trying to resolve every possible situation in advance.
+What happens if someone who's a friend of someone on the Policy & Abuse committee is involved in a complaint?
+We expect the members of the Policy & Abuse committee to behave professionally, even though the Organization for Transformative Works is an all-volunteer organization. We take the responsibilities of serving on the Policy & Abuse committee seriously, and a member of the team with a personal relationship to any party in a complaint is expected to recuse themselves entirely from the case, and, of course, to maintain our standards of confidentiality at all times. Failure to do so is grounds for dismissal from the Policy & Abuse committee.
+AO3 is still being actively developed. How will the Abuse Policy apply to planned future features?
+Since new features may be added at any time, the Abuse Policy only applies to active features. As we develop features, we will strive to be transparent and communicate with users about our policies as much as possible.
+Back to Top | Abuse Policy and Procedures FAQ
+
+Content Policy FAQ
+Answers to common questions about the Content Policy are available below. If you have additional questions that are not covered here, you can contact the Policy & Abuse committee.
+-
+
- General Questions about the Content Policy +
- Offensive Content vs Illegal Content +
- Fanworks and Non-Fanwork Content +
- Commercial Promotion +
- Copyright Infringement and Plagiarism +
- Fannish Identities and Impersonation +
- Harassment +
- Usernames, Icons, and Profiles +
- Ratings and Archive Warnings +
- Other Tags +
- Spam and Technical Integrity +
General Questions about the Content Policy
++++
+ +Table of Contents
+What is "content"?
+Content is anything that you post on AO3 or otherwise submit to us. This includes, but is not limited to:
+-
+
- works +
- bookmarks +
- comments +
- tags +
- collections +
- links +
- icons +
- embedded text, image, audio, or video files +
- usernames and pseuds +
- profile and pseud descriptions +
- fannish next-of-kin information +
- Personal Information, such as an email address +
- any other item of information or type of content +
All content on AO3 must comply with our Content Policy.
+What happens if someone posts content that violates the Content Policy?
+We do not prescreen content on AO3, nor do we review content that has not been reported to us. If you believe you have encountered content that violates our Terms of Service, you will need to submit an Abuse report.
+The Policy & Abuse committee will investigate each report and independently determine whether a violation of the Terms of Service has occurred. Penalties may be applied to the accounts of users responsible for posting violating content. For more information, please refer to the Abuse Policy and Procedures FAQ.
+Back to Top | General Questions about the Content Policy
+
+Offensive Content vs Illegal Content
++++
+Table of Contents
+-
+
- Why doesn't AO3 remove extremely offensive content? +
- Why does AO3 allow fanworks about things that are illegal in real life? +
- What does banning "sexually explicit or suggestive photographic or photorealistic images of real children" mean, particularly for works featuring sexual content with underage characters? +
- Does AO3 screen for quality? +
- How can I avoid works that contain content I don't want to encounter? +
- How can I avoid encountering works or other content by a specific user? What about anonymous or orphaned works? +
- How can I prevent a user from commenting on my works or interacting with me? +
Why doesn't AO3 remove extremely offensive content?
+The Archive of Our Own was created in 2008 as a response to several challenges fandom faced at the time.
+One common challenge was that platforms would unilaterally remove content without warning. The decisions were often shaped by the platform owner's preferences or determined by what was more friendly to advertisers. This meant that platforms frequently banned explicit sexual content.
+Such prohibitions were often disproportionately enforced against minorities and marginalized groups. For example, fanworks featuring LGBT+ characters were (and still are) more likely to be reported and removed for having "sexual content". This is due to societal bias: a story featuring a romantic relationship between two women would be considered more sexual or adult than one with an equivalent relationship between a man and a woman. Such works would either be required to have a higher rating or were often removed entirely.
+Biased enforcement of content rules has been shown to occur even when the purpose of the rule is to push back against discrimination. For example, rules intended to reduce racial hate speech on social media often end up being disproportionately enforced against racial minorities speaking out against racism or discussing their own lived experiences. To date, the problem of unbiased content moderation hasn't been solved by any large internet site.
+Challenges such as these led AO3 to adopt a policy that welcomes all forms of fictional, transformative fanwork content. Our mission is to host transformative fanworks without making judgments based on morality or personal preferences. If it's a fictional fanwork that is legal to post in the United States, then it is welcome on AO3. This approach is intended to reduce the risk that content will be removed as a result of cultural or personal bias against marginalized communities.
+We recognize that there are works on AO3 that contain or depict bigotry and objectionable content. However, we are dedicated to safeguarding all fanworks, without consideration of any work's individual merits or how we personally feel about it. We will not remove works from AO3 simply because someone believes they are offensive or objectionable.
+All users who would like to avoid encountering particular types of content are recommended to make use of our filters and muting features.
+Why does AO3 allow fanworks about things that are illegal in real life?
+AO3's Terms of Service are designed to comply with United States law. 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 child sexual abuse, rape, incest, or bestiality. AO3 allows users to post and access fiction about all of these topics.
+In accordance with U.S. law, AO3 prohibits Child Sexual Abuse Material (sexually explicit photorealistic images of real children). However, stories and non-photorealistic artwork are allowed, both under U.S. law and on AO3. Fiction about real people is still fiction, and therefore it is allowed on AO3.
+Depending on your country of residence or citizenship, the laws that apply to you may be more restrictive than those of the United States. All users are responsible for following the laws that apply to them. If certain content on AO3 is illegal for you to access, then you should ensure you carefully observe all relevant ratings and warnings, and avoid opening any work that indicates it may contain such content.
+What does banning "sexually explicit or suggestive photographic or photorealistic images of real children" mean, particularly for works featuring sexual content with underage characters?
+Sexually explicit photographs, videos, and other photorealistic images of children (also known as Child Sexual Abuse Material, or CSAM) are prohibited in the United States and on AO3. Users who embed, link to, solicit, distribute, or otherwise provide access to such material will be banned and reported to the appropriate authorities.
+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 carry the appropriate Archive Warning. However, photographic or photorealistic images of humans may not be used to illustrate works featuring underage sexual content. This includes (but is not limited to) photographs of children, porn gifs, photo manipulations, computer-generated or "AI" images, or other linked or embedded images that could potentially be mistaken for photographs of real humans.
+We understand that not all photorealistic images of humans are actually documenting the real-life abuse of a child or derived from illegal material, but we decided to use a guideline that can be uniformly applied without relying on subjective judgment. 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 the Policy & Abuse committee may require all photographic or photorealistic images of humans, regardless of age, to be removed from the work.
+Does AO3 screen for quality?
+No. We welcome creators and fanworks of all skill levels, and we will never remove a work on account of its quality, grammar, spelling, or punctuation.
+How can I avoid works that contain content I don't want to encounter?
+When browsing a tag, you can use the Filters sidebar to filter out works. If you are on a mobile device, select the "Filters" button at the top of the page to bring up this sidebar. Adding tags under the Exclude section will remove all works that use an excluded tag. For example, you can exclude any ratings and Archive Warnings that you don't want to encounter (make sure to also exclude the non-specific Rating and Archive Warning tags). You can also exclude other types of tags that users have chosen to add to their works.
+You can use the Search within results box to filter works using keywords. This searches the metadata (title, summary, tags, and beginning/end notes) of a work, but not the chapter notes or body text. You can also use the following symbols to refine your search:
+-
+
- A minus sign (
-) in front of a word (or a phrase in quotes) in the "Search within results" box will filter out all works that have the word anywhere in their metadata.
+ - An asterisk (
*) before or after your search term will allow you to look for partial matches.
+ - If your search term has multiple words, using straight double quotation marks (
"like this") on either side of your search term will allow you to search for the exact phrase. Single and/or curly “smart” quotation marks will not work.
+
For example, if you enter
+-sex*into the "Search within results" box, your results will exclude any works with metadata that contains words beginning with "sex" (including "sex", "sexual", "sexy", etc).Once you have a search setup that works for you, you can bookmark the page in your browser in order to return to it later. If there's content you want to avoid on AO3, we recommend using filter keywords and browser bookmarks to exclude that content from what you encounter while browsing.
+If you need help using filters, please contact the Support committee.
+How can I avoid encountering works or other content by a specific user? What about anonymous or orphaned works?
+Mute a specific user
+If you want to avoid all content by a specific user, you should mute the user. To mute a user, go to their dashboard by following the link in their username. Then select the "Mute" button in the top-right corner, and confirm that you want to mute them on the next page. Muting a user means you will no longer be shown their works, series, bookmarks, or comments while browsing AO3. Please note that muting is a separate function from blocking.
+Mute a specific work
+If you want to hide a specific work (for example, a specific anonymous or orphaned work), you can mute it with a site skin. To do so, create a site skin and add
+.work-000 { display: none !important; }to it, replacing000with the ID of the work you want to mute. The work ID number can be found in the work's URL immediately after/works/. For example,000would be the work ID ofhttps://archiveofourown.org/works/000/chapters/123. Make sure to apply your site skin after you've created it. You can contact the Support committee if you have any problems using site skins.How can I prevent a user from commenting on my works or interacting with me?
+Block a registered user
+If you want a registered user to stop interacting with you, you can block the user. To block a user, select the "Block" button on any of the user's comments or on their user profile or dashboard, then confirm that you want to block them on the next page. Blocking a user means they cannot comment on or kudos your works, reply to your comments elsewhere, or give you gifts outside of a Challenge. Please note that blocking is a separate function from muting.
+Block guest (anonymous) users
+If you want to prevent a guest user from commenting on your works, you can disable guest comments or only allow registered users to access your works. You may also want to enable comment moderation.
+To prevent guest users from replying to your comments on other users' works, go to your Preferences page and enable "Do not allow guests to reply to my comments on news posts or other users' works (you can still control the comment settings for your works separately)". Remember to select the "Update" button at the bottom of the page to save any changes to your preferences.
+Back to Top | Offensive Content vs Illegal Content FAQ
+
+Fanworks and Non-Fanwork Content
++++
+Table of Contents
+-
+
- What kinds of fanworks can I post? +
- What if what I want to post isn't similar to one of the examples listed above? +
- How will "ephemeral" be defined? +
- Can I post original fiction? +
- Can I post nonfiction? +
- What falls within the definition of fannish nonfiction? +
- What are some examples of non-fanwork content that should not be posted as works on AO3? +
- How will you draw the line between fanworks and non-fanworks? +
- Can I post a "placeholder" work to tell other fans that I intend to post my story soon? +
- Can I post fancastings for my story as a separate work? What about character notes or profiles? +
- Can I post "incorrect quotes"? +
- Can I post non-textual works (such as fanart, fanvids, or podfic)? +
- Can I post "directors' cut" or "commentary" versions of my own fanworks? +
- Can I post announcements or status updates as separate works? What about if I post it as a chapter of my fanwork? +
- Can I post roleplay ads? +
- I am looking for a particular story. Can I post a work explaining what I'm looking for? +
- I have an idea that other people might want to write. Can I post my prompt or challenge as a work? +
- Does that mean I can't write a short story scene or snippet and suggest that others continue where I left off? +
- I want other people to give me prompts or requests for fanworks they'd like to see. Can I post a work so that they'll have a place to do that? +
- Can I post a letter to someone I've been anonymously matched with for a challenge? +
- Can I create a list of recommendations or a list of works that use certain tropes? If I want to include commentary on the fanworks I am recommending, would that count as meta? +
- Are there any limits to what I can use AO3 bookmarks for? +
What kinds of fanworks can I post?
+AO3 allows a wide range of fanworks other than fanfiction, including but not limited to art, videos, crafts, games, fanmixes, authorized podfics, authorized translations, fannish nonfiction, original fiction, and more. You can post any non-commercial, non-ephemeral fanwork. Here are some examples of allowed fanwork content:
+-
+
- A retelling of an existing story from another character's point of view +
- An original fantasy story about a modern person traveling to medieval times +
- An alternative version of a published novel in which there's a zombie apocalypse +
- The supporting text for an original adventure for a tabletop roleplaying game +
- A fannish essay about vampire biology, or the same essay in audio or video form +
- Short clips of footage from existing sources, edited over a song to make an argument or tell a story +
- Artwork (such as a drawing) of an iconic scene from a book, movie, or TV show +
- A comic about the romantic adventures of a playful thief +
- Photographs of a crocheted (amigurumi) character you made +
What if what I want to post isn't similar to one of the examples listed above?
+In general, you can post any non-commercial, non-ephemeral, transformative content you created that is fannish in nature. If you're uncertain if your work can be posted on AO3, you can always contact the Policy & Abuse committee to ask.
+How will "ephemeral" be defined?
+Ephemeral content is material that exists primarily to share someone's impressions, reactions, or feelings about a current event, fandom, or trend. If the content contains limited analytical or interpretive content, or lacks any artistic material, it is likely to be classified as ephemeral. Some examples of ephemeral content include live reactions, announcements about upcoming fanworks, and requests for prompts.
+While it may benefit general fannish history to keep a record of such moments, AO3 is not intended to host all content that is fannish in nature. This type of content is often better suited for social media, personal sites, or blogging services. The Organization for Transformative Works also runs Fanlore, a wiki about fanworks and fan communities, including fandom trends and current events.
+Please use your best judgment. Our general policy is to defer to creators in cases of doubt; however, the Policy & Abuse committee has final discretion in determining ephemerality.
+Can I post original fiction?
+Yes. Original works are allowed, unless the work would be in violation of some other part of the Terms of Service.
+Our vision of AO3 is for all fanworks, including those beyond traditional fanfiction, fanart, and fanvids. Original stories and artwork, including those imported as part of an Open Doors project, are permitted. Some examples of original fiction that we host include original slash, anthropomorphic works, and Regency romance. However, works intended for commercial publication are not suitable for AO3. The Policy & Abuse committee has final discretion in maintaining AO3's focus on non-commercial fannish works.
+We generally presume that, by posting the work to AO3, the creator is making a statement that they believe it's a fanwork. As such, original work will be allowed to remain unless the work is in violation of some other part of the Terms of Service, such as our plagiarism or non-commercialization policies.
+Can I post nonfiction?
+Fannish nonfiction, which includes what is called "meta" by some fans, is allowed. However, it must still be fannish in some way and contain some kind of analytical or creative content. In addition, as an Archive whose goal is preservation, we want permanent, non-ephemeral content. If the content is meant to be ephemeral, such as a liveblog of episode reactions, it should be posted on a social media account rather than on AO3.
+Examples of fannish nonfiction and things that are not fanworks are available below.
+What falls within the definition of fannish nonfiction?
+Examples of fannish nonfiction allowed on AO3 include:
+-
+
- Discussions of fannish tropes +
- Essays designed to entice other people into a fandom +
- Commentary on fandoms +
- Documentaries or podcasts about fandom +
- Explanations of the creative process behind one or more fanworks +
- Tutorials for creating fanworks +
- Guides for fan-created gaming campaigns +
- Detailed analyses of multiple fanworks +
- Essays on characters' narrative arcs in canon +
- Comparisons of the film and comics versions of a source +
This isn't an exhaustive list – fannish nonfiction may take many other forms.
+We will generally defer to the creator's characterization of a work as fannish nonfiction as long as it has a reasonably perceptible fannish connection, either to a specific source or to fandom in general, and takes the form of an independent, non-ephemeral commentary. However, not all nonfiction falls within our mandate. Please consider what isn't fannish nonfiction before posting your work. While we acknowledge the complexity of certain cases that may fall on the boundaries of categories, setting limits is necessary to maintain AO3's manageability for our dedicated volunteers and users.
+What are some examples of non-fanwork content that should not be posted as works on AO3?
+The examples are potentially limitless, but here are some examples that do not fall under AO3's definition of fannish fiction or nonfiction and should not be posted as a work:
+-
+
- ephemeral content (including personal journal or diary entries, reactions, or blog posts) +
- episode transcripts, reposted canon material, and other non-transformative fandom content +
- primarily autobiographical or non-fandom-related essays (for example, your science, math, or philosophy homework, even if it contains a reference to a fannish source) +
- lists of names, titles, or statistics (such as information about a character's name, age, pronouns, and personality traits) that contain little to no other analytical, narrative, or descriptive content +
- discussions of specific fandom-related events (such as conventions or debates over particular incidents), which are considered more appropriate for Fanlore +
- general statements, questions, or complaints about a person or group +
- suggestions that other fans contact the creator through email or other social networks +
- links, lists, or requests for recommendations, whether of fanworks or published works +
- ads for roleplaying partners, sessions, servers, sites, or games +
- advertisements, offers, and giveaways +
- technical instructions (for example, a recipe for making ice cream, or a list of steps explaining how to assemble an ice cream machine) +
- faceclaims, fancastings, or other reference lists (such as collections of photographs, media, or other resources) +
- a single word or phrase repeated hundreds or thousands of times +
- prompts or requests for prompts +
- announcements, placeholders, or updates about future, existing, or deleted works +
- an explanation of why a work was removed from AO3 +
Works that incorporate fannish content in clearly bad faith are not fanworks. For example, a work primarily composed of fic search requests is not a fanwork even if there are a few sentences of fandom-specific content.
+In general, we presume good faith on the part of our users, and ask that you do the same for the fans who make up our Support and Policy & Abuse committees. The Policy & Abuse committee will exercise its discretion, which is final, in the service of maintaining AO3 as a place focused on non-ephemeral fanworks.
+How will you draw the line between fanworks and non-fanworks?
+The presumption is that a work is a fanwork, but if it's clear from context (summary, tags, notes, etc.) that it's not, it may be removed for violating the Content Policy. The Policy & Abuse committee will consider many factors when determining if something is a fanwork, such as whether the reported content is transformative, ephemeral, or fannish in nature.
+Additionally, original works that are not based on a specific media source (canon) are considered fanworks. Please see Can I post original fiction? for more detail.
+Can I post a "placeholder" work to tell other fans that I intend to post my story soon?
+Placeholders are not allowed on AO3. This includes works in progress that do not have any story content, works where only the summary and tags have been posted, and lists of ship names, character profiles, or ideas for what you plan to publish. You can create a draft to edit your tags or preview your work before posting it publicly, but please don't post the work unless you have at least one chapter of your fanwork that is ready to be shared with other people.
+Can I post fancastings for my story as a separate work? What about character notes or profiles?
+A work that is simply a collection of actors' photos paired with character names would not be considered a fanwork, nor would a work that only consists of statistics or summaries of canon elements (such as what you might find on a fannish wiki). However, if you include more in-depth analytical, descriptive, or narrative content, then we would likely consider that fannish analysis (meta), which is allowed. An example would be an extended analysis of the character traits that led you to choose that particular fancasting.
+If you would like to post fancastings, statistics, or a summary about your own fanwork, you can include it in the fanwork's notes or post it as an extra chapter inside the fanwork.
+Can I post "incorrect quotes"?
+No. The incorrect quotes meme format involves a collection of quotes where the names have been substituted with the names from a different source. While the amount of quoted text is relatively small, replacing names and minor rewording of quotations is not sufficiently transformative to make the resulting content a fanwork.
+Can I post non-textual works (such as fanart, fanvids, or podfic)?
+We currently don't host multimedia content other than user icons, though you can embed various kinds of files that are hosted elsewhere if it's a fannish transformative work (or part of one) and otherwise complies with the Content Policy. However, for technical and legal reasons we don't allow all kinds of embeds. Please read our policies about embedding images that you did not create, podfics of stories that you did not write, images that depict explicit content, and images in works featuring underage sexual content. In addition, keep in mind that embeds may break for various reasons, including trouble with the hosting site.
+Can I post "directors' cut" or "commentary" versions of my own fanworks?
+We consider those versions of your fanworks, so you may post them as you would any other fanwork. We suggest that you distinguish them from non-commentary versions, for example by adding "[Directors' Cut]" in the title or tagging them to indicate the difference between the original and the "DVD-style" version.
+Can I post announcements or status updates as separate works? What about if I post it as a chapter of my fanwork?
+No, you cannot post announcements or other blog-style updates as separate works. Status updates and other author notes are considered ephemeral content. If you want to discuss a fanwork you've posted or plan to post on AO3, we suggest including such information on your profile page or in the notes or comment sections of your existing fanworks.
+In general, adding several announcement chapters to an existing fanwork will not cause your entire work to become a non-fanwork. However, if you want to talk extensively about your works or personal life, then we recommend linking to a social media site in the notes of your fanworks instead of posting announcement chapters.
+Can I post roleplay ads?
+No. Requests or calls for roleplay partners are not fanworks. We encourage you to seek and advertise for roleplaying partners or servers on your preferred social media platform(s) instead.
+I am looking for a particular story. Can I post a work explaining what I'm looking for?
+No. Please use our search functions for this rather than creating a separate work. You can use our Work Search or Bookmark Search, or select a particular tag and then use the Filters sidebar to further refine the results.
+Should you find that this is not sufficient to locate the work you are seeking, your preferred internet search engine (such as Google or DuckDuckGo) may be able to search for distinctive phrases within the work text itself. You can perform an AO3-specific sitewide search by adding the search term
+site:archiveofourown.org, which will limit your results to pages on AO3.If you require assistance from other users, we advise seeking out fandom-specific or pairing-specific fic-finding communities on social media platforms such as Tumblr, Reddit, or Discord, whose members will be more than happy to help you locate the works you are looking for.
+I have an idea that other people might want to write. Can I post my prompt or challenge as a work?
+No. Please create a prompt meme to offer suggestions or challenges to other people, rather than posting a work.
+Does that mean I can't write a short story scene or snippet and suggest that others continue where I left off?
+A short, distinct piece (such as a drabble or vignette) would be considered a fanwork. If you have written a full scene or outlined the plot in enough detail that it could count as a fanwork in and of itself, that would also be allowed.
+However, if you only have a handful of sentences or bullet points and there isn't much plot or characterization, that may be considered a non-fanwork placeholder or prompt. If your primary reason for posting the work is to offer ideas or suggestions for other people, please create a prompt meme instead of posting a work.
+I want other people to give me prompts or requests for fanworks they'd like to see. Can I post a work so that they'll have a place to do that?
+No, you cannot post a work that is only a request for other people to give you prompts. Please create a prompt meme instead. You can share the link to your prompt signup form on social media or in the notes of your fanworks.
+Can I post a letter to someone I've been anonymously matched with for a challenge?
+No. Since this content is designed to be ephemeral (it is directed at a particular person for a particular event), please do not create a separate work for it. If the challenge is hosted on AO3, please put your letter in the optional details for the challenge. If you want to share your general preferences such as your favorite fandoms or tropes, you can put that information in your profile.
+Can I create a list of recommendations or a list of works that use certain tropes? If I want to include commentary on the fanworks I am recommending, would that count as meta?
+Posting a "rec list" (one or more recommendations as a work) may be a violation of our non-fanwork policy. Please use our bookmark feature for this purpose instead. Bookmarks can include commentary, be marked as recommendations, and organized with tags or into collections.
+Criticism of a fanwork is permitted in the tags or notes of a bookmark and will not be considered harassment. However, no matter its location on the site, all commentary must comply with our other policies, including our harassment policy.
+The difference between a recommendation versus a general meta-discussion or analysis of a fanwork is determined through several factors, such as whether the content is ephemeral in nature or if it contains analytical or interpretive content. A work is more likely to be a non-fanwork if it's just a list of titles and summaries (such as a "Top 10 List" or "Recs for Fluff Fics") or if it's similar to a product review (for example, "This is the best slow burn fic in the fandom and here's why you should read it"). If the work contains extended commentary or analysis about the nature of the recommended work, it is more likely to be considered a fanwork and allowed on AO3.
+Please use your judgment on the best way to categorize such commentary.
+Are there any limits to what I can use AO3 bookmarks for?
+On AO3, bookmarks are intended for organizing and recommending fanworks hosted on any site (not just AO3). For example, you can bookmark fanfic from FanFiction.Net, fanart on DeviantArt, fanvids on YouTube, or meta posts on Tumblr. However, you should not create a bookmark for something that isn't a fanwork. Bookmarking a news article, meme, or reaction gif would be in violation of our non-fanwork policy because those aren't fanworks.
+In addition, please keep in mind that bookmarks are also subject to all of our general content rules, including our policies against harassment, commercial promotion, and copyright infringement. For example, you cannot use bookmarks to link to illegally distributed copies of copyrighted material.
+As offsite ("external") bookmarks are described by users, their actual content may differ from the descriptions offered. Please exercise caution when following any links away from AO3, including external bookmarks.
+Back to Top | Fanworks and Non-Fanwork Content FAQ
+
+Commercial Promotion
++++
+Table of Contents
+-
+
- Why is commercial promotion prohibited on AO3? +
- What kinds of things are considered "promotion, solicitation, and advertisement of commercial products or activities"? +
- What do you mean by "commercial platform"? +
- What do you mean by "monetization features of a non-commercial platform"? +
- Can I link to my Tumblr, Discord, Linktree, Wordpress, or other social media account or personal website? What if my profile or pinned post on that site has a link to a commercial platform? +
- I am a published author. Can I let people know what my pen name is or what my books' titles are? +
- Can I ask for donations or tips on my account profile or my original works? +
- Can I post the first chapter of my published original novel on AO3? +
- I post all of my fanworks on AO3 for free, but I also have paid supporters on another site who get new chapters a week early. Can I let readers know that these "early access" chapters exist, if I don't explain how or where they can subscribe? +
- The stories posted on my Patreon are free for anyone to read, even if they're not one of my Patrons. Can I link to one of these stories from AO3? +
- I would like to thank one of my clients or patrons (someone who supported me monetarily). Can I acknowledge them in the notes of my work? +
- This creator's work is amazing! Can I leave a comment telling them they should set up a tipping or subscription service, publish their work commercially, or otherwise get paid for it? +
- I paid someone else to create a story, artwork, or podfic. Can I post or link to their work, or suggest that other people commission them too? +
- I take paid commissions on another site. Can I post the fanworks I create on AO3 and say that they were commissioned? Can I invite other people to commission me? +
- Can I post a work that was created for a charity drive or auction? +
- Does that mean I can't ask people to support a charity or non-profit organization? +
- Can I post a work that was originally part of a for-sale or charity zine, and if so, can I name the zine? +
- What if a zine or other merchandise is available on an optional "pay what you want" basis? On sites like Gumroad, it's possible to access or download the content completely for free. +
- I created merch for one of my fanworks. I'd like to hold a giveaway and send it to one of my readers for the cost of shipping. Since I'm not making money off of it, can I advertise this on AO3? +
- I bought some fan merch. Can I post an image of what I bought and talk about it in my work notes or comments? +
- I've created a mobile app with features that make AO3 easier to navigate and use. Can I charge people to use my app? +
- Can I talk about prohibited commercial activities on AO3 if I don't include any direct links or name any commercial platforms? +
- Do the rules against commercial promotion mean that I can't write fanworks that reference real-world businesses or feature characters engaging in commercial activities? +
Why is commercial promotion prohibited on AO3?
+The Organization for Transformative Works is committed to the defense and protection of fans and fanworks from commercial exploitation and legal challenges. AO3 was created to give fan creators a non-commercial space to share their works.
+It is part of AO3's mission to remain a non-commercial space, so all forms of commercial promotion and activities are prohibited. AO3 isn't the right place for offering merchandise or requesting donations, whether for yourself or others. We enforce the non-commercialization policy strictly.
+What kinds of things are considered "promotion, solicitation, and advertisement of commercial products or activities"?
+Some examples of commercial activities include:
+-
+
- linking to or referencing the use of a commercial platform or the monetization features of a non-commercial platform +
- providing a "tip jar", bank information, or other method for people to give you money +
- offering paid commissions or other content in exchange for money, gift cards, or similar +
- stating that a fanwork was created as a result of a donation or paid commission +
- encouraging donations to a person or cause +
- listing potential benefits of a paid membership or subscription +
- posting free previews for paywalled content +
- advertising a paid service or product (linking to an item's product page, suggesting that others purchase an item, etc.) +
- selling merchandise, even if the merchandise is fannish in nature +
- discussing the sale of the creator's other works, even if that paid content is not itself hosted on AO3 +
- creating or promoting an app or website that charges money to access works posted on AO3 +
In general, if a financial transaction is involved, you cannot discuss it on AO3. Commercial activity is prohibited regardless of the reason why the commercial activity is occurring.
+What do you mean by "commercial platform"?
+A commercial platform is a site whose primary purpose is to facilitate the exchange of money. This includes online storefronts as well as tipping, patronage, subscription, and crowdfunding services. Linking, discussing, or referencing someone's presence (including your own) on a commercial platform is prohibited.
+Examples of commercial platforms include, but are by no means limited to:
+-
+
- Amazon, Etsy, Redbubble, and other online storefronts +
- Patreon, Ko-fi, and other patronage, tip-jar, or subscription services +
- Kickstarter, GoFundMe, and other crowdfunding services +
- PayPal, Venmo, and other money transfer services +
As stated, this list is non-exhaustive. If the primary function of the platform involves allowing someone to give someone else money, then you should not advertise your presence on it in any way.
+What do you mean by "monetization features of a non-commercial platform"?
+Sometimes sites mainly dedicated to some other purpose (such as social media or image/audio/video hosting) will also have features or subsections of their platform dedicated to monetization. For example, DeviantArt is primarily a free-to-use art gallery and social media website, but it does have some specific sections of its platform that are commercial in nature, such as DeviantArt's Shop, Commissions, Premium Galleries, and Core Memberships. In such cases, you are allowed to link to content on the "free" portion of the website, so long as the page you are linking to is non-commercial in nature. However, linking to or mentioning the monetized content is not allowed.
+Can I link to my Tumblr, Discord, Linktree, Wordpress, or other social media account or personal website? What if my profile or pinned post on that site has a link to a commercial platform?
+In general, linking to your social media accounts or personal website is fine, even if you sometimes post about commercial activities on that site. However, you may not link to accounts, posts, sites, or pages that reference commercial activity in the URL, or that are primarily commercial in nature (such as a Carrd that lists your published novels and explains where to buy them). In addition, you may not provide instructions anywhere on AO3 for finding your commercial content elsewhere (for example, stating that information about your paid commissions is available on a specific webpage even if you don't link directly to that page).
+I am a published author. Can I let people know what my pen name is or what my books' titles are?
+Stating in general terms that you have written a book or providing your pen name is fine, even if you use that pen name for commercial works. However, you may not use AO3 to promote your commercial works, tell people where they can find or buy those works, or otherwise advertise your commercial works in a manner that could encourage others to seek out and purchase the works.
+Can I ask for donations or tips on my account profile or my original works?
+No. Our non-commercialization policy applies everywhere on AO3, including user profiles, comments, fanworks, and works in the "Original Work" fandom. Asking for donations or tips is considered engaging in commercial activities and is not allowed anywhere on the site.
+Can I post the first chapter of my published original novel on AO3?
+Posting a preview or advertisement for a commercial work is not allowed. This includes uploading only a "snippet" to promote a larger paid work, as well as removing significant portions of a fanwork that has been "pulled to publish" professionally. Even if it contains some fannish content, sharing excerpts intended to promote or sell paid content is prohibited.
+I post all of my fanworks on AO3 for free, but I also have paid supporters on another site who get new chapters a week early. Can I let readers know that these "early access" chapters exist, if I don't explain how or where they can subscribe?
+No. If you provide an "early access" service in exchange for money, you cannot reference it on AO3. This includes stating that additional "bonus content" is available elsewhere, regardless of whether you plan to make the content available to the public in the future. Advertising paywalled content is not allowed even if you don't provide instructions, include links, or name a specific commercial platform.
+The stories posted on my Patreon are free for anyone to read, even if they're not one of my Patrons. Can I link to one of these stories from AO3?
+No. Sites like Patreon are considered commercial platforms because their primary purpose is to enable creators to receive funding from their fans. Linking to commercial platforms is not allowed, even if some content on the platform is free.
+I would like to thank one of my clients or patrons (someone who supported me monetarily). Can I acknowledge them in the notes of my work?
+You may not indicate anywhere on AO3 that other people are financially supporting you due to your fanworks. This includes stating that they paid for a commission, donated money to you or others, or are a patron or paid subscriber. However, you are allowed to name someone in a non-commercial manner, such as by crediting them for a prompt or by using the Gift feature to dedicate your work to them.
+This creator's work is amazing! Can I leave a comment telling them they should set up a tipping or subscription service, publish their work commercially, or otherwise get paid for it?
+No. Our non-commercialization policy applies to the entirety of AO3, including the comments section of other users' works. Encouraging other users to engage in commercial activity is prohibited.
+I paid someone else to create a story, artwork, or podfic. Can I post or link to their work, or suggest that other people commission them too?
+You may not encourage commercial activity on behalf of someone else, which includes encouraging people to purchase a commission. If you are embedding commissioned images, audio, or videos, you must ensure that there are no ads, links, or watermarks for any commercial platforms. In addition, you may only upload someone else's work if you have their explicit permission to do so.
+I take paid commissions on another site. Can I post the fanworks I create on AO3 and say that they were commissioned? Can I invite other people to commission me?
+Offering paid commissions is not allowed. This includes posting links to pricelists or payment request forms. However, you are allowed to post fanworks that were created upon request and credit the person who made the request. If you do so, you must not indicate that you received payment for the commission or that you are available to create other paid commissions. 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.
+Can I post a work that was created for a charity drive or auction?
+Yes. AO3 will host fanworks of any origin, including fanworks created in response to charity events or other challenges. A link to a charity to explain the origin of a fanwork is appropriate, but please do not link directly to any fundraising sites or pages. You may state that a work was produced for a particular charity event, project, or other entity, as long as you do not mention donating, bidding, or any specific contribution amounts or donation platforms.
+Does that mean I can't ask people to support a charity or non-profit organization?
+You are allowed to link to a charity's website, encourage people to learn more about the charity, or explain why you believe in its mission. However, you may not link directly to the charity's donation form, promote their fundraisers, or request that people donate to them.
+Can I post a work that was originally part of a for-sale or charity zine, and if so, can I name the zine?
+Yes. However, you may not encourage users to buy the zine or its merchandise, such as by linking to an advertisement or to a sales or orders page.
+What if a zine or other merchandise is available on an optional "pay what you want" basis? On sites like Gumroad, it's possible to access or download the content completely for free.
+Links to product purchase pages are not allowed, even if payment is optional. If the content is hosted on a non-commercial site that doesn't offer payment options, you can link to that site instead.
+I created merch for one of my fanworks. I'd like to hold a giveaway and send it to one of my readers for the cost of shipping. Since I'm not making money off of it, can I advertise this on AO3?
+No. Since this involves an exchange of money, it is considered a commercial activity regardless of whether you personally make a profit.
+I bought some fan merch. Can I post an image of what I bought and talk about it in my work notes or comments?
+In general, yes. However, you cannot encourage other users to go and buy it themselves. This includes providing links or directions to the place where you purchased the merchandise. You may want to take your own photographs in order to avoid linking to the product page.
+I've created a mobile app with features that make AO3 easier to navigate and use. Can I charge people to use my app?
+No. It is a violation of the Terms of Service to charge users money for access to content on AO3. That includes, for example, operating an app that restricts access to works on AO3 behind a paywall, or copying works from AO3 to sell.
+Can I talk about prohibited commercial activities on AO3 if I don't include any direct links or name any commercial platforms?
+No. Both direct and indirect references to commercial platforms or activities are not allowed.
+Do the rules against commercial promotion mean that I can't write fanworks that reference real-world businesses or feature characters engaging in commercial activities?
+No. You are allowed to create fanworks in which the characters engage in or reference commercial activities as part of the fictional story. For example, you could create a fanwork in which one character is an OnlyFans creator and another subscribes to them or buys their merchandise. However, you cannot link to or otherwise promote any real-world subscription, merchandise, or other commercial activity.
+Please keep in mind that all Abuse reports are reviewed by the human volunteers on our Policy & Abuse committee. In general, we presume good faith on the part of our users. However, if we conclude that someone is deliberately trying to circumvent our rules by having fictional characters discuss commercial activities, then the fanwork may be deemed commercial in nature and unacceptable to post on AO3.
+Back to Top | Commercial Promotion FAQ
+
+Copyright Infringement and Plagiarism
++++
+Table of Contents
+-
+
- What makes a fanwork "transformative"? Why is a "transformative work" not a copyright violation? +
- Do I own the copyright for my fanworks? +
- May I post someone else's fanworks, giving them credit? +
- Can I post a translation or a podfic of someone else's work? +
- Can I post a conversion or adaptation of someone else's work? This is a type of work where the original content is modified slightly to fit a different fandom, ship, character, or format. +
- Can I post a sequel, prequel, or continuation of another fanwork? What about a recursive fic that's completely different from the original fanwork? +
- What if the original creator deleted or orphaned their work, or posted it anonymously? +
- How can I obtain permission to post, convert, podfic, or translate someone else's work? +
- Can I post a transcript of a movie or a TV show? +
- Can I post "reaction fic" or "MST3K or DVD-commentary–style" versions of other works? This is a type of fanwork where characters read/watch another work (such as the original canon or a popular fanwork) and "live react" to scenes or dialogue. +
- May I post the full lyrics of a song or an entire poem that isn't in the public domain without the copyright holder's permission? +
- Can I post a fanvid that uses a full song without the copyright owner's permission? +
- Can I post character playlists or fanmixes? +
- Can I embed someone else's artwork or photos to accompany a work that I wrote, or post someone else's story to accompany the art I created for it? +
- How do these rules apply to works that are in the public domain? +
- If I want to file a plagiarism or copyright infringement complaint, is there anything in particular I should include in my report? +
- Can I submit a plagiarism complaint even if I am not the original creator whose work was stolen? +
- Can I submit a plagiarism or copyright infringement complaint even if the original work is not hosted on AO3? +
- Do you have a Digital Millennium Copyright Act (DMCA) notice and takedown policy? +
- What happens if someone reposts my fanwork to another site without my permission? +
What makes a fanwork "transformative"? Why is a "transformative work" not a copyright violation?
+Copyright protects an individual's expression of an idea, not the idea itself. "Expression" refers to the work created, such as the wording of a paragraph in a book, while an "idea" covers general plots or tropes. For example, posting a transcript of a movie without permission constitutes copyright infringement, as it replicates a significant part of the original work (the spoken dialogue) exactly. In comparison, a transformative fanwork reframes existing material in a unique manner, such as retelling a superhero movie from the perspective of civilians.
+The Supreme Court of the United States has explained transformative use as "add[ing] something new, with a further purpose or different character, altering the first [work] with new expression, meaning, or message." Essentially, by significantly reinterpreting the original material, the creator of a transformative work makes a new, distinct creation that does not require the copyright owner's permission to create or share.
+Do I own the copyright for my fanworks?
+Yes. AO3 maintains that fanworks are transformative and that a fanwork's creator owns the rights to the expressions in their work that are unique to them. A fanwork creator holds the rights to their own content, just the same as any professional author, artist, or other creator.
+May I post someone else's fanworks, giving them credit?
+You may only post someone else's fanworks if they granted you permission to do so. If you do not have the creator's permission, you cannot post their work. Including a disclaimer that the work is not yours or crediting the original creator is not sufficient. Posting and then anonymizing or orphaning the work is also not allowed. Please use our bookmark feature to share other people's fanworks instead of reposting their works.
+If you do have the creator's permission, you can upload their fanwork as long as you provide appropriate credit. For example, you could add the creator's name and include links to the work on the original site and to the place where they gave you permission.
+If you created or moderate a fanwork archive or mailing list, you may be eligible to become an authorized Open Doors archivist and import your archive to AO3. The Open Doors committee will work with approved moderators to contact and fully credit the original creators of the fanworks, giving the creators as much control over their fanworks as possible.
+Can I post a translation or a podfic of someone else's work?
+Translations and podfics can be posted only if you have permission from the copyright owner (usually the creator or publisher) of the original work. If you do not have permission, then you may not post your work.
+Under United States copyright law, translations and audiobooks are considered "derivative" works – not transformative works. Derivative works cannot be posted without the copyright holder's consent. AO3 adheres to U.S. law, so if you want to post a translation or podfic of a fanwork, you need the fanwork creator's permission.
+If the original work is no longer under copyright because it is old enough that it has entered the public domain, refer to How do these rules apply to works that are in the public domain?
+Can I post a conversion or adaptation of someone else's work? This is a type of work where the original content is modified slightly to fit a different fandom, ship, character, or format.
+While you are welcome to create a fanwork that is based on or inspired by another work, you may not take someone else's work and only make minor changes to it (such as swapping out the names, changing the formatting, or rewording the original text). Unless the fanwork creator or copyright owner granted you permission to modify, convert, or adapt their work in this manner, posting this kind of work is a violation of our Terms of Service, even if you provide credit.
+Can I post a sequel, prequel, or continuation of another fanwork? What about a recursive fic that's completely different from the original fanwork?
+Yes. Fanworks based on other fanworks are also transformative, and are allowed. You can use the "Inspired By" feature to link to the original creator's work. Unlike with reposts, conversions, podfics, and translations, you don't need permission to create a recursive fanwork. However, you cannot include large excerpts from the original work unless the original creator gave you permission to do so.
+What if the original creator deleted or orphaned their work, or posted it anonymously?
+Even if someone deletes or orphans their work, or posts it anonymously, they still hold the copyright to their own work. If the original creator has chosen to remove their fanwork from the internet, or cannot be contacted, then please respect their decision. You cannot post, convert, podfic, or translate someone else's work without their explicit permission, even if you credit them or disclaim credit for yourself.
+How can I obtain permission to post, convert, podfic, or translate someone else's work?
+Some fanwork creators may list "blanket permission" statements in their profile or in the tags or notes of their work. An example of a blanket permission statement would be "Anyone can translate my works so long as they provide me credit and link back to the original here on AO3." In such cases, you have permission if and only if you meet the conditions of the permission statement.
+If a creator doesn't have a blanket permission statement, then you can try to contact them directly and ask. This could be by commenting on their work or asking them via social media or email (if they have shared that information publicly). If the creator responds and gives you permission, then you're good to go. If they refuse or do not respond, then you do not have their permission and you may not post the work.
+Can I post a transcript of a movie or a TV show?
+Scripts of movies, TV shows, and plays are subject to copyright, just like published books, songs, poems, photographs, artwork, and other works. Transcribing and posting the content of a copyrighted work is not allowed. However, you may include a limited number of short quotes in your fanwork.
+Can I post "reaction fic" or "MST3K or DVD-commentary–style" versions of other works? This is a type of fanwork where characters read/watch another work (such as the original canon or a popular fanwork) and "live react" to scenes or dialogue.
+If you have permission from the copyright owner or if the work is in the public domain, then your fanwork can include as many quotes from the original work as you like.
+If the work is still under copyright and you don't have permission from the copyright owner, then you can describe or paraphrase scenes to allude to what the characters are reacting to and include timestamps, page numbers, or occasional short quotes from the original. However, you cannot quote or otherwise reproduce large amounts of dialogue, lyrics, text, or other copyrighted material. If someone could access a substantial portion of the original material by skipping over your additions, your work likely violates our Terms of Service.
+May I post the full lyrics of a song or an entire poem that isn't in the public domain without the copyright holder's permission?
+No. Posting large portions of text from a song or poem is not allowed, unless it is in the public domain or you have the copyright owner's permission. You are only allowed to quote a limited amount of material from a copyrighted work, even if the lyrics or stanzas are broken up by your own original text. You can link to a licensed site such as Genius or Poetry Foundation instead.
+Can I post a fanvid that uses a full song without the copyright owner's permission?
+Fanvids where the audio is an entire song are allowed, so long as you have added or remixed a substantial number of visuals to accompany the song such that the video becomes a transformative work. For example, simply posting the text of the song's lyrics to accompany the song would not be considered transformative. A video consisting of an entire song accompanied by two or three long, unedited clips from a movie would also not be considered a transformative work.
+Can I post character playlists or fanmixes?
+A "fanmix" is a thematic compilation of songs curated by a fan to reflect a character, chapter, setting, theme, or other element of a work. If you wish to post character playlists or fanmixes, you may use licensed streaming sites such as Spotify, 8tracks, or YouTube. You may not provide links that could deliver individual music file downloads (such as a single zipped file containing music files) unless you have the right to distribute downloads (for example, a fan song or filk you composed and sang, a work in the public domain, or a Creative Commons-licensed download). Please also keep in mind that you may quote lyrics as part of a transformative work, but you may not reproduce the entire song text unless you have the right to do so. In addition, if you just post a list of song titles without including any way to listen to the songs, then your work may not be considered a transformative fanwork.
+Can I embed someone else's artwork or photos to accompany a work that I wrote, or post someone else's story to accompany the art I created for it?
+If you have the artist's or writer's permission, then you may embed or upload their work alongside your own as long as you credit them appropriately. If you do not have the creator's permission, you cannot repost their work, even if you credit them. We recommend that you instead provide a link to wherever the original creator has chosen to host it.
+How do these rules apply to works that are in the public domain?
+If a work is in the public domain, then it is no longer copyrighted. In this case, you can use as many excerpts from it in your fanwork as you like.
+However, a public domain work is not in and of itself a fanwork. You cannot simply upload a public domain work to AO3 or make minor alterations such as replacing names or synonyms. You need to add your own content in order for your work to be considered a fanwork.
+If you create your own fan translation or podfic of a public domain work, you can post your work on AO3. However, you can't repost someone else's translation or podfic without their explicit permission. Translations and audio recordings have their own copyright separate from the source work's. The translator or podficcer has ownership over their own specific translation or recording, even if the underlying work is in the public domain.
+If I want to file a plagiarism or copyright infringement complaint, is there anything in particular I should include in my report?
+Yes – please make sure you provide a link to the original work as well as a link to the infringing work in your report description. If you don't tell us what the original source is and which work is infringing upon it, then we may not be able to uphold your complaint.
+If you want to report multiple instances of plagiarism or copyright infringement by a single user, please submit only one report rather than reporting each link individually. We'll be able to process your complaint faster if you take the time to compile all relevant links, excerpts, and other information into a single report and correctly pair each infringing work with the original source.
+If you are reporting multiple works by different users, please submit a separate report for each user.
+Can I submit a plagiarism complaint even if I am not the original creator whose work was stolen?
+In general, yes, as long as you include a link to the alleged source work. If we cannot compare the two works, we will not be able to uphold your complaint. However, in some cases, we may require a report or other evidence from the original creator.
+Can I submit a plagiarism or copyright infringement complaint even if the original work is not hosted on AO3?
+Yes. However, such reports must include a link to the alleged source work. If we cannot compare the two works, we will not be able to uphold a complaint of plagiarism or copyright infringement.
+Do you have a Digital Millennium Copyright Act (DMCA) notice and takedown policy?
+Yes. Before filing a DMCA takedown notice, please read our DMCA Policy carefully. If you have any questions, contact the Legal committee.
+DMCA takedowns and counternotices are not handled by the Policy & Abuse committee. Please do not submit both an Abuse report and a DMCA notice about the same content, as this may delay the processing of both requests.
+What happens if someone reposts my fanwork to another site without my permission?
+The Organization for Transformative Works does not hold the copyright to your fanworks, so we cannot contact other sites or organizations on your behalf. Because you are the copyright owner, you will have to contact the other site yourself to request that they remove the unauthorized copy of your work.
+Back to Top | Copyright Infringement and Plagiarism FAQ
+
+Fannish Identities and Impersonation
++++
+Table of Contents
+-
+
- I posted a guest comment that contained information about me. Can you delete it? +
- I orphaned a work, and later realized that it contained my personal information. Can you delete it? +
- What does banning "impersonation" mean? Does this mean I can't post first-person real-person fiction (RPF)? +
- Can I use a celebrity name as a pseudonym, or is that impersonation? +
- What do you mean by banning impersonation of a "function"? Does this mean I can't have fake Tumblr or TikTok messages in my fanwork? +
I posted a guest comment that contained information about me. Can you delete it?
+If the comment contained personal information sufficient to identify you in the real world (such as a full legal name, an email address, or a phone number) then you can contact the Policy & Abuse committee to request its removal. However, we will not remove guest comments simply because they contain a first name, username, or online handle.
+I orphaned a work, and later realized that it contained my personal information. Can you delete it?
+We will not delete orphaned works that don't violate our Terms of Service. However, if you left identifying information on an orphaned work (such as your name, email address, or social media account) and you would no longer like that information to be public, then you can contact the Support committee to request the removal of that specific information from the work.
+What does banning "impersonation" mean? Does this mean I can't post first-person real-person fiction (RPF)?
+We do not permit users to misrepresent themselves as another person or entity (such as a corporation or government agency), particularly in order to deceive others, violate our Terms of Service, or otherwise cause harm.
+Roleplay is permitted when the assumption of such a persona is clearly disclosed (such as in a user profile or in another manner appropriate under the circumstances) and it doesn't otherwise violate the Terms of Service, including the harassment policy. Fiction (including RPF in first-person format) clearly marked as such will not be considered impersonation. Please consult our RPF policy for further information.
+Can I use a celebrity name as a pseudonym, or is that impersonation?
+In general, you can use a joke celebrity pseudonym, or roleplay as a celebrity, so long as you clearly disclaim that you are not actually that person.
+What do you mean by banning impersonation of a "function"? Does this mean I can't have fake Tumblr or TikTok messages in my fanwork?
+You're allowed to mimic functions inside fictional content, so long as the content is clearly fictional – fiction is not impersonation. However, if you're posting content outside of a fictional context, then you can't do so in an impersonating manner. For example, using the username "orphaned_account" is not allowed, as that could cause users to confuse your user page with AO3's official orphan_account.
+Back to Top | Fannish Identities and Impersonation FAQ
+
+Harassment
++++
+Table of Contents
+-
+
- Does the harassment policy cover everyone, or just AO3 users? +
- Does the harassment policy apply to every part of AO3? +
- Is criticizing fanworks allowed? Is criticism a violation of the harassment policy? +
- How does the harassment policy apply to comments? +
- Is it harassment if someone deletes my comment? My comment wasn't criticizing or attacking them. +
- Is it harassment if someone blocks me? They had no reason to do it. +
- Somebody bookmarked my fanwork and added a note to it that is really negative about my work. Is that harassment? +
- There's a person in my fandom who is harassing other people. Can I post a work, chapter, comment, or author's note to inform other people in my fandom who they are and that they should stay away? +
- Someone in my fandom is posting really disgusting content that is against the boundaries of the canon creators. Can I comment on their work and ask them to stop? +
- There are some people in my fandom who ship things I think are disgusting or dangerous. I don't want them to comment on my works. Is it harassment if I tell them to stay away? +
- What if the tag I want to use is technically threatening, but it's actually a joke? I promise I'm not serious! +
- Is it harassment if someone reports me for violating the Terms of Service? +
Does the harassment policy cover everyone, or just AO3 users?
+Both AO3 users and non-users can complain about harassment. The line between user and non-user can be blurry, so our policy covers both. However, writing RPF (real-person fiction) never constitutes harassment in and of itself, even if the content is objectionable. Please refer to our RPF policy for more information.
+Does the harassment policy apply to every part of AO3?
+Yes. This includes works, tags, comments, usernames, pseuds, profiles, icons, and every other type of content that can be submitted to, hosted on, or embedded on AO3, now or in the future. The harassment policy applies to everything a user does on AO3 and all communications with AO3 volunteers.
+The use of any tool or feature could constitute harassment if it's being used to create a hostile environment. When investigating harassment, we will consider relevant context. For example, someone who has a username, pseud, or icon that is negative towards an individual or group could harass those people by leaving comments on their works, even if that same username, pseud, or icon would not be harassing in other contexts.
+Is criticizing fanworks allowed? Is criticism a violation of the harassment policy?
+Criticism is allowed on AO3 and is not considered harassment. This includes negative commentary in comments, bookmark notes, bookmark tags, and other locations. Criticizing a work is not a personal attack against the person who created that work, nor against people who enjoy that work. Issuing personal attacks or threats against other users for creating or enjoying a work is harassment and is not allowed.
+How does the harassment policy apply to comments?
+Criticism of a fanwork, even harsh criticism, is not by itself harassment. All creators have control over the comments on their works, and can delete comments or block users for any reason.
+Calling a creator evil, wishing them harm, and repeatedly posting negative commentary in a manner designed to be seen by the creator (such as by posting multiple negative comments on their work) are potential examples of harassment.
+Is it harassment if someone deletes my comment? My comment wasn't criticizing or attacking them.
+No. Fanwork creators have control over the comments posted on their work. They can remove, freeze, moderate, or restrict comments as they please. This is never considered to be harassment.
+Is it harassment if someone blocks me? They had no reason to do it.
+No. Being blocked by someone is never harassment. If you are blocked by someone or if they told you to leave them alone, you are expected to stop interacting with them. Attempting to interact with someone after they have blocked you may be considered harassment.
+Somebody bookmarked my fanwork and added a note to it that is really negative about my work. Is that harassment?
+Criticism of a fanwork, even harsh criticism, is not by itself harassment. We do not consider criticism of a fanwork to be a personal attack against its creator. However, if the bookmark note includes harassing elements such as personal attacks or threats towards the creator of the work, then that would be considered harassment.
+There's a person in my fandom who is harassing other people. Can I post a work, chapter, comment, or author's note to inform other people in my fandom who they are and that they should stay away?
+No. Creating or sharing a "callout post" about another individual, or encouraging other users to shun them, is harassing behavior. We encourage you to mute and block anyone you don't want to interact with. If you witness or experience harassment on AO3, you should contact the Policy & Abuse committee. If you witness or experience harassment on a different platform, you should contact the moderators or Trust & Safety team for that platform.
+Someone in my fandom is posting really disgusting content that is against the boundaries of the canon creators. Can I comment on their work and ask them to stop?
+We recommend that you avoid engaging with content that you do not like. If you encounter content on AO3 that you find upsetting or disturbing, you should navigate away from the content and use filters or muting to avoid encountering it again. Users are allowed to post fanworks about any topic, regardless of how offensive it is to other users or if the canon creators would approve. If the content doesn't violate a specific clause of our Terms of Service, the fanwork is allowed – we do not remove content for offensiveness. In addition, be aware that joining in on group bullying to force someone to remove their works is likely to be deemed harassment.
+There are some people in my fandom who ship things I think are disgusting or dangerous. I don't want them to comment on my works. Is it harassment if I tell them to stay away?
+If you don't want people to comment on your works, then you should block them. You are allowed to make polite requests that other groups of fans do not interact with you. If you insult those people, or threaten them in any way, you are in violation of our harassment policy.
+What if the tag I want to use is technically threatening, but it's actually a joke? I promise I'm not serious!
+You may not threaten other groups of fans. There is no exception for jokes or memes.
+Is it harassment if someone reports me for violating the Terms of Service?
+As an AO3 user, it is your responsibility to ensure that you are following our Terms of Service. If we receive a report about you, you will only be told about it if our investigation reveals that you did in fact violate our Terms of Service. In such cases, we will let you know about your violation regardless of who reported it.
+While malicious reporting is harassment, such reports are rarely about content that actually violates the Terms of Service. Most reports about violating content are submitted by users who happen to encounter such content during the course of their normal browsing. We do not generally consider a valid report to be harassment of the subject of the report.
+ +
+Usernames, Icons, and Profiles
++++
+Table of Contents
+-
+
- Are there any rules about what I can choose as my username? +
- Can I reuse a username that belonged to a deleted account? +
- Someone is using a username on AO3 that I've used on a different site. Can you make them stop or make them give me the username? +
- Why are the rules for user icons more restrictive than the general content rules? +
- What can be on a user profile? +
Are there any rules about what I can choose as my username?
+Yes. Aside from technical limitations on your username, all of the regular content rules also apply to usernames. This means that (for example) you can't choose a username that impersonates someone else, or that violates our commercial promotion or harassment policies. Because usernames are highly visible content, we enforce our policies very strictly on usernames.
+Can I reuse a username that belonged to a deleted account?
+Yes, it is possible that a username that is no longer used by its original user will be available to you.
+Someone is using a username on AO3 that I've used on a different site. Can you make them stop or make them give me the username?
+Usernames on AO3 aren't reserved, even if you've used that name before on AO3 or another site. In general, we won't consider the mere existence of a similar or identical username to be impersonation. If another AO3 account is already using your desired username, then you can create a pseud with that name, but you can't make the other person give up their username. However, if someone starts claiming to be you on AO3, or otherwise starts behaving in a harassing manner, then you can submit an Abuse report.
+Why are the rules for user icons more restrictive than the general content rules?
+User icons appear on pages that don't have rating filters, such as user profiles and comments. This means that other users have little ability to avoid encountering them. Therefore, user icons operate under more restrictive rules than rated, tagged, and warned-for content.
+The user icon policy is not the general fanart policy. Although AO3 does not have native media hosting, images and other file types can be embedded in a work. For more information about what is allowed in fanart, please refer to Can I embed explicit images in my fanworks?
+What can be on a user profile?
+User profiles can contain information about the user, such as their fandom preferences and links to other sites on which the user can be found. User profiles must comply with AO3's policies on commercial promotion, harassment, impersonation, copyright, and other general content rules.
+Back to Top | Usernames, Icons, and Profiles FAQ
+
+Ratings and Archive Warnings
++++
+Table of Contents
+-
+
- What kind of content do you allow? +
- What kind of ratings or warnings must be present on works? +
- What do you mean by non-specific Rating or Archive Warning tags? +
- What is the Ratings system? +
- Are there any rules about how I must rate my work? +
- If I don't choose a rating, what's the default? +
- What does the "Not Rated" label mean? +
- What's the difference between "General" and "Teen"? +
- What's the difference between "Teen" and "Mature"? +
- What's the difference between "Mature" and "Explicit"? +
- There's an explicit sex scene in one chapter of my work, but all of the other chapters are really fluffy material that would be suitable for general audiences. Which rating should I choose? +
- Does the gender or sexual identity of a character matter when determining what rating to use? +
- Do you ever require a rating change on works rated "Mature" or "Explicit"? +
- If I want to avoid explicit fanworks, what ratings should I exclude in my search? +
- What is the Archive Warnings system? +
- Are there any rules about applying Archive Warnings to my work? +
- Why is the number of Archive Warning tags so limited? +
- Something that I consider really upsetting or unpleasant is not on the list of Archive Warnings. +
- My work includes content that I want to warn other users about, but it's something that's not on the list of Archive Warnings. How can I warn them? +
- If I don't choose an Archive Warning, what's the default? +
- What does the "Creator Chose Not To Use Archive Warnings" label mean? +
- Can I include multiple Archive Warnings? +
- Can a work have both "No Archive Warnings Apply" and one or more other Archive Warnings? +
- If a story has only a brief reference to an Archive Warning topic, am I required to use either that warning or the "Creator Chose Not To Use Archive Warnings" label? Or can I still choose "No Archive Warnings Apply" if I think that's a better description? +
- What does the "Underage Sex" Archive Warning mean? +
- Why is "underage" defined as "under 18"? +
- What if the age of consent in my local jurisdiction is something other than 18, or if the age of majority in the fictional setting is under 18? +
- What about robots, computer simulations, elves, aliens, vampires who are three hundred years old but were turned into vampires at age 12, etc.? +
- What about when a fanwork isn't set during the canon timeline and doesn't specify the characters' ages? +
- Is "Rape/Non-Con" or "Creator Chose Not To Use Archive Warnings" required for works featuring adult/minor relationships? In real life, that would be considered statutory rape in many jurisdictions, regardless of whether the underage participant was willing. +
- If consent is unclear or dubious, is the "Rape/Non-Con" or "Creator Chose Not To Use Archive Warnings" label needed? +
- When is the "Major Character Death" warning needed? What makes a character "major"? +
- If a major character dies in my fanwork but later returns to life, does the "Major Character Death" warning apply? +
- What about vampires, zombies, sentient robots, and other characters that aren't "alive"? +
- What if a major character's death is ambiguous or unclear? +
- Will you ever require that an Archive Warning be removed? +
- What's the difference between ratings and warnings? +
- What sort of rating and warning information am I required to provide for my fanworks? +
- Can I use "Not Rated" but not "Creator Chose Not To Use Archive Warnings," or vice versa? +
- How do the ratings and warnings policies apply to embedded images, videos, etc.? +
- Can I embed explicit images in my fanworks? +
- How explicit or graphic can the summaries and tags on my fanworks be? +
- Do AO3 personnel prescreen works as they're uploaded to ensure that they comply with the ratings and warnings policies? +
- What's the consequence of a violation of the ratings or warnings policies? +
- What do you mean by "not all works will carry full warnings"? +
- What type of rating and warning information will be provided when I am browsing fanworks? +
- If I'm not logged in, what can I see? +
What kind of content do you allow?
+AO3 was designed to be a permanent home for all transformative fanworks. We will not remove content from AO3 solely because it contains explicit, offensive, or upsetting material, as long as it doesn't violate any other part of the Content Policy (such as the harassment policy or the non-fanwork policy).
+We allow content of any rating, and all kinds of fictional topics. Users are responsible for reading and heeding the ratings and warnings provided by the creator. If there is a type of content that you don't want to encounter, you should avoid opening any work tagged or rated to indicate that it may contain such content. Risk-averse users should keep in mind that not all content will carry full warnings. If you want to know more about a particular fanwork, you may also want to consult the bookmarks that people other than the creator have used to categorize it.
+What kind of ratings or warnings must be present on works?
+AO3 has a Ratings system and an Archive Warnings system. These provide basic information about the intensity and type of content that may be present in a work. The only rating or warning information AO3 requires is listed within these two systems. Creators may add more information in the summaries, notes, or Additional tags of their works, but they are not required to do so.
+If a creator doesn't want to put a specific Rating and/or Archive Warning on their works, then they can opt out of one or both systems by applying a non-specific Rating and/or Archive Warning.
+What do you mean by non-specific Rating or Archive Warning tags?
+Non-specific tags indicate that the creator has chosen not to use a more specific tag in that field. Any user who wants to avoid a particular rating and/or type of content should also avoid any work labeled with a non-specific Rating and/or Archive Warning. The non-specific Rating tag is "Not Rated", and the non-specific Archive Warning is the "Creator Chose Not To Use Archive Warnings" label. (Tags are also sometimes referred to as labels.)
+What is the Ratings system?
+AO3 has five different rating tags that creators can apply to their works:
+-
+
- General Audiences: The content should be suitable for all ages. +
- Teen and Up Audiences: The content may be inappropriate for audiences under 13. +
- Mature: The content may contain adult themes (sex, violence, etc.) that aren't as graphic as Explicit-rated content. +
- Explicit: The content may contain explicit adult themes, such as detailed sex scenes, graphic violence, etc. +
- Not Rated: This non-specific rating tag means that the creator has chosen not to rate their work. It may contain content that is general, explicit, or anything in between. +
If a creator doesn't want to apply a specific rating to their work, they are always welcome to use the non-specific "Not Rated" label.
+Are there any rules about how I must rate my work?
+If your work contains graphic or detailed sex, violence, gore, or other adult content, then you may not rate it "General" or "Teen". Whether you choose to rate the work "Mature", "Explicit", or "Not Rated" is up to you.
+If I don't choose a rating, what's the default?
+The default rating is the non-specific "Not Rated" tag.
+What does the "Not Rated" label mean?
+"Not Rated" means that the work may contain content of any rating – the creator has declined to choose a specific rating. A "Not Rated" work could contain anything from a very fluffy coffeeshop meet-cute to extremely graphic sexual content.
+What's the difference between "General" and "Teen"?
+This is left entirely up to the creator's judgment. People disagree passionately about the nature and explicitness of content to which younger audiences should be exposed. Therefore, the creator's discretion to choose between "General" and "Teen" is absolute: we will not mediate any disputes about those decisions. Instead, we encourage creators to consider community norms, whether fandom-specific or more general (such as how you'd expect a video game or movie with similar content to be rated), when selecting a rating.
+What's the difference between "Teen" and "Mature"?
+If the work contains graphic adult content, it should not be rated "General" or "Teen". In response to valid complaints about a misleading rating, the Policy & Abuse committee may redesignate a fanwork marked "General" or "Teen" to "Not Rated", but in other cases, we will defer to the creator's decision. In general, we will not recategorize a fanwork in response to a complaint when the content at issue is a reference or is otherwise not graphic.
+What's the difference between "Mature" and "Explicit"?
+This is left entirely up to the creator's judgment. Both of these ratings require a user to accept the adult content warning and agree to access adult content in order to access the work. The creator's discretion to choose between "Mature" and "Explicit" is absolute: we will not mediate any disputes about those decisions. Instead, we encourage creators to consider community norms, whether fandom-specific or more general (such as how you'd expect a video game or movie with similar content to be rated), when selecting a rating.
+There's an explicit sex scene in one chapter of my work, but all of the other chapters are really fluffy material that would be suitable for general audiences. Which rating should I choose?
+Individual chapters of a work cannot be rated separately, so the rating chosen should be sufficient to cover the highest-intensity content in the work. If you do not want to use a rating of "Mature" or "Explicit" in such a situation, then you can always opt out of the Ratings system by labeling your work as "Not Rated".
+Does the gender or sexual identity of a character matter when determining what rating to use?
+No. The Policy & Abuse committee will not treat works differently on account of the genders or sexual identities of the characters or the types of relationships featured in the work. Please also note that in general, the creator's choice of rating is presumed to be appropriate.
+Do you ever require a rating change on works rated "Mature" or "Explicit"?
+No. Choosing a rating of "Mature" or "Explicit" is always acceptable. We will not require that ratings be lowered, even if there is no intense or explicit content in the work.
+If I want to avoid explicit fanworks, what ratings should I exclude in my search?
+To avoid all fanworks that may contain explicit content, you should exclude or filter out the "Mature", "Explicit", and "Not Rated" labels.
+What is the Archive Warnings system?
+The Archive Warnings system consists of several warning tags, which creators are able to choose from when posting their fanwork. At least one of the following options must be chosen before a work can be posted:
+-
+
- Graphic Depictions of Violence: The work may contain detailed descriptions of gore or graphic violence. +
- Major Character Death: The work may include the death of a character who is prominently featured. +
- Rape/Non-Con: The work may contain non-consensual sexual activity. +
- Underage Sex: The work may contain descriptions or depictions of sexual activity involving characters under the age of eighteen. +
- Creator Chose Not To Use Archive Warnings: This non-specific warning tag means that the work may contain content pertaining to any of the Archive Warnings. +
- No Archive Warnings Apply: If this warning tag is used in the absence of other Archive Warnings, it means that the work does not contain detailed content pertaining to any of the four specific Archive Warnings. However, the work may briefly reference an Archive Warning topic and/or contain other intense or unpleasant content that is not covered by any of the Archive Warnings. +
If a creator doesn't want to apply a specific Archive Warning to their work (for example, if they wish to avoid giving spoilers), they are always welcome to use the non-specific "Creator Chose Not To Use Archive Warnings" label.
+Are there any rules about applying Archive Warnings to my work?
+If your work contains graphic depictions of violence, major character death, depictions of rape or non-consensual sex, or depictions of underage sexual activity, then you must use either the relevant specific Archive Warning or the non-specific "Creator Chose Not To Use Archive Warnings" label.
+Why is the number of Archive Warning tags so limited?
+We wished to limit the number and type of Archive Warnings so that they could be easily used by creators from a wide variety of fandoms, and so that each Archive Warning could be fairly and consistently enforced by our all-volunteer Policy & Abuse committee. We decided that we could not reasonably expect fair enforcement of a rule requiring warnings for concepts beyond those listed in the Archive Warnings.
+Something that I consider really upsetting or unpleasant is not on the list of Archive Warnings.
+Because the Archive Warnings policy is deliberately minimal, this may be the case. We encourage you to use the Additional tags, summaries, and user-provided bookmarks and recommendations to screen for fanworks you'll enjoy, and you may wish to comment on a creator's work when you feel that further tags would be desirable. Please be respectful when you do, and keep in mind that they may choose not to add such extra tags.
+My work includes content that I want to warn other users about, but it's something that's not on the list of Archive Warnings. How can I warn them?
+Creators can add additional information about what their works contain in the Additional tags field. You can also add this type of information to the notes or summary of your work, including the notes and summaries on individual chapters. Doing so is entirely voluntary: the Policy & Abuse committee will not enforce the presence of any warnings outside of the Archive Warnings.
+If I don't choose an Archive Warning, what's the default?
+There is no default Archive Warning, so creators have to choose one or more of the Archive Warning options. A creator can opt out of using a specific Archive Warning by selecting "Creator Chose Not To Use Archive Warnings" instead.
+What does the "Creator Chose Not To Use Archive Warnings" label mean?
+"Creator Chose Not To Use Archive Warnings" means that the creator has opted out of using the Archive Warnings system. A work with this warning may or may not contain content covered by any of the specific Archive Warnings. Users who access a work labeled "Creator Chose Not To Use Archive Warnings" proceed entirely at their own risk, regardless of any other tags on the work.
+Can I include multiple Archive Warnings?
+Yes, you can. For example, you could select both "Major Character Death" and "Underage Sex" if a fanwork contains both elements, or "Creator Chose Not To Use Archive Warnings" and "Underage Sex" if you want to disclose the underage sexual content but don't want to say whether the work contains major character death.
+Can a work have both "No Archive Warnings Apply" and one or more other Archive Warnings?
+Yes. The "No Archive Warnings Apply" label can be added to a work regardless of any other Archive Warnings, so it only has meaning when no other Archive Warnings are present on the work.
+If you would like to avoid encountering works with content pertaining to a specific Archive Warning when browsing AO3, then you should exclude the specific Archive Warning as well as the "Creator Chose Not To Use Archive Warnings" label.
+If a story has only a brief reference to an Archive Warning topic, am I required to use either that warning or the "Creator Chose Not To Use Archive Warnings" label? Or can I still choose "No Archive Warnings Apply" if I think that's a better description?
+This is the kind of decision that is up to the creator's discretion. In general, we will not recategorize a fanwork in response to a complaint when the content at issue is a reference or is otherwise not portrayed in explicit detail.
+What does the "Underage Sex" Archive Warning mean?
+Underage Sex refers to descriptions or depictions of sexual activity involving characters under the age of eighteen (18). In general, we rely on creators to use their judgment about the line between reference and description or depiction. Sexual activity does not include dating activities such as kissing; but again, we rely on creators to use their judgment about what is generally understood to be sexual activity. Creators may always specify the age of the characters in their work.
+Why is "underage" defined as "under 18"?
+Though there is no international consensus, there is a trend to focus on 18 as an important age for depictions of sexual activity. Thus, we decided that 18 would be helpful for the maximum number of users, including audiences as well as creators, though we recognize that no solution is perfect for everyone. We encourage creators and bookmarkers to be more specific in tags or notes where this would be useful to potential audiences.
+What if the age of consent in my local jurisdiction is something other than 18, or if the age of majority in the fictional setting is under 18?
+The "Underage Sex" warning on AO3 is used for fanworks depicting sexual activity involving humans under 18 as measured in Earth years, regardless of the fictional setting or users' local laws.
+What about robots, computer simulations, elves, aliens, vampires who are three hundred years old but were turned into vampires at age 12, etc.?
+The primary use of the "Underage Sex" warning is to identify fanworks depicting sexual activity involving humans under the age of 18 as measured in Earth years. Please use your judgment for other situations. If the fanwork does not include a depiction of sexual activity with a human under 18 years old, then we will not generally consider it "underage sex", though creators may use the Archive Warning if they feel it accurately represents their intent. As always, we encourage creators and bookmarkers to be more specific in tags or summaries where this would be useful to potential audiences.
+What about when a fanwork isn't set during the canon timeline and doesn't specify the characters' ages?
+If the characters' ages in the fanwork are ambiguous, then we will assume the characters have been "aged up", even if they are underage in the canon setting.
+Is "Rape/Non-Con" or "Creator Chose Not To Use Archive Warnings" required for works featuring adult/minor relationships? In real life, that would be considered statutory rape in many jurisdictions, regardless of whether the underage participant was willing.
+No. Archive Warnings apply to the fictional content depicted in the work, so a work featuring a sexual relationship between an adult and a minor would need to use the "Underage Sex" Archive Warning. However, unless a character is clearly depicted in the work as unwilling to engage in sexual activity, then the "Rape/Non-Con" warning (or the "Creator Chose Not To Use Archive Warnings" label) is not required, regardless of the age of any of the characters.
+If consent is unclear or dubious, is the "Rape/Non-Con" or "Creator Chose Not To Use Archive Warnings" label needed?
+The primary use of the "Rape/Non-Con" warning is to identify fanworks depicting characters who are clearly unwilling or otherwise forced to engage in sexual activities. Please use your judgment for other situations. When a fanwork features unclear or dubious consent ("dubcon"), we will defer to the creator's decision on how to categorize their work.
+When is the "Major Character Death" warning needed? What makes a character "major"?
+If a character has a significant presence in the fanwork, and they die during the course of the story, then the work would require the "Major Character Death" warning (or the "Creator Chose Not To Use Archive Warnings" label). This warning is also required when the fanwork is focused on the character's death, even if it happened prior to the start of the work. It doesn't matter whether the character is a main character or a side character in canon – it's what is in the fanwork that counts. For example, even if a character has only one line in canon, a fanwork that is primarily about that character's funeral and how much their partner misses them would merit this warning.
+If a major character dies in my fanwork but later returns to life, does the "Major Character Death" warning apply?
+If the character returns to life or is revealed to not be dead within the same fanwork, then you don't need to apply the "Major Character Death" warning (or the "Creator Chose Not To Use Archive Warnings" label) for this character.
+Keep in mind that Archive Warnings apply to the entirety of an individual fanwork's posted content, not to any drafts or sequels. If you appear to have killed off a significant character in a specific work, but plan for them to return in a future chapter or sequel, we suggest using "Creator Chose Not To Use Archive Warnings" as the content currently posted does feature character death.
+What about vampires, zombies, sentient robots, and other characters that aren't "alive"?
+Please use your best judgment for characters who are or become undead, mechanized, or otherwise non-human. If the character is generally still able to think or act in a somewhat human fashion throughout the course of the story, then the "Major Character Death" warning is not needed. When in doubt, we will defer to the fanwork creator's discretion about whether a character has meaningfully died.
+What if a major character's death is ambiguous or unclear?
+This is the kind of decision that is up to the creator's discretion. In general, we will not recategorize a fanwork in response to a complaint when the content at issue is a reference or is otherwise not graphic.
+Will you ever require that an Archive Warning be removed?
+No. The presence of an Archive Warning indicates that the work may contain such content, but it is not a guarantee. This includes works marked with "No Archive Warnings Apply". If this warning is accompanied by another Archive Warning (including the non-specific "Creator Chose Not To Use Archive Warnings" label), then the other warning has precedence.
+What's the difference between ratings and warnings?
+Ratings are a measure of the intensity of overall content. Warnings refer to a specific type of content that is present.
+For example, a work may be rated Explicit because it describes an extended, violent torture scene, or because it has a detailed depiction of consensual sex – or both. The rating tells you only that there may be adult content, and does not inform you what type of adult content it is. A warning indicates the work may contain an "onscreen" depiction of a specific type of content, and does not inform you of the level of detail in which it is described. For example, a work rated "Teen" might also carry the "Major Character Death" warning.
+What sort of rating and warning information am I required to provide for my fanworks?
+Some users may prefer not to read works with particular ratings and/or warnings, while others may search out works with those same ratings and/or warnings. Our goal is to provide the maximum amount of control and flexibility possible for all users of AO3, both creators and audiences alike, so that each user can customize their own experience. Creators can choose to provide a specific rating and/or Archive Warning(s), or they can choose to opt out of providing a specific rating and/or Archive Warning by using "Not Rated" and/or "Creator Chose Not To Use Archive Warnings", respectively.
+Can I use "Not Rated" but not "Creator Chose Not To Use Archive Warnings," or vice versa?
+Yes, absolutely. For example, you could use "Not Rated" and "Rape/Non-Con" for a work that has an explicit rape scene. Or you could rate a work "General" but choose not to warn about the main character dying by using "Creator Chose Not To Use Archive Warnings".
+How do the ratings and warnings policies apply to embedded images, videos, etc.?
+When making rating/warning decisions, creators should take into account any content within the work, including embedded images and videos. As with all other content, creators' decisions are presumed reasonable, and using "Not Rated" or "Creator Chose Not To Use Archive Warnings" will always be sufficient.
+Can I embed explicit images in my fanworks?
+Explicit drawings and other non-photorealistic artwork are generally allowed to be embedded in a work, as long as the work's rating and warnings appropriately describe both the embedded and the textual content. If you are using other people's images to illustrate your fanwork, you must embed from a source authorized by the creator and provide appropriate credit.
+You may not embed sexually explicit or suggestive photographic or photorealistic images in works that contain underage sexual content or any other contextual indication (such as in the tags, notes, or text of the work) that the characters may be under the age of 18. This includes (but is not limited to) porn gifs, photo manipulations, and computer-generated or "AI" images.
+How explicit or graphic can the summaries and tags on my fanworks be?
+Explicit or graphic content in a summary or tag does not violate the Content Policy, as long as the work is appropriately rated and warned. Please use your judgment about what will best identify and describe your fanworks. The summary and tags are part of your work, and your choice of rating and warnings must reflect all parts of your work.
+Do AO3 personnel prescreen works as they're uploaded to ensure that they comply with the ratings and warnings policies?
+No. We will only review a work that has been reported to us for potentially violating the ratings or warnings policies.
+What's the consequence of a violation of the ratings or warnings policies?
+Please see the Mandatory Tags policy for details. If we uphold a complaint, we will ask the creator to amend the rating or warning as necessary. If the creator fails to do so, the Policy & Abuse committee may add the non-specific "Not Rated" and/or "Creator Chose Not To Use Archive Warnings" labels as appropriate. In general, a fanwork will not be removed from AO3 merely for not being correctly labeled. However, repeated or deliberate mislabeling may result in additional consequences.
+What do you mean by "not all works will carry full warnings"?
+Some creators prefer not to assign specific ratings or warnings to their works, or may not be certain if some content in their work "counts" for a required Archive Warning. Our policy aims to enable creators to opt in or out of using specific ratings or warnings while still allowing users to filter out unwanted content. Works for which creators have opted out of providing specific ratings and/or warnings will be labeled "Not Rated" and/or "Creator Chose Not To Use Archive Warnings". These options aid users in decision-making, albeit with more limited detail than a specific rating or warning tag would.
+What type of rating and warning information will be provided when I am browsing fanworks?
+Users who wish to avoid works labeled with specific ratings or Archive Warnings can filter them out or exclude them from searches. Users trying to avoid all possibility of encountering specific ratings or warnings should also avoid works marked as "Not Rated" or "Creator Chose Not To Use Archive Warnings" in the same way, because these works may contain content pertaining to any rating or warning, respectively.
+Beyond the Archive Warnings, Additional tags can also be used to filter and/or search for works. Users who wish to screen works for other users may also add tags, notes, or recommendations to their bookmarks to warn other users about the subject matter contained in the bookmarked works. This can serve as an extra source of information for users who are trying to determine whether or not to access a work. However, please be aware that Additional tags are not mandatory.
+If a user does not want to see Archive Warnings and/or Additional tags (for example, if they wish to avoid potential spoilers), then they can hide those tags in their preferences. Doing so will not hide any works that carry warning labels, only the warning labels themselves.
+All users are responsible for reading and heeding the warnings provided by the creator. Risk-averse users should keep in mind that our ratings and warnings policies are deliberately minimal, and not all content will carry full warnings. If you want to know more about a particular fanwork, you may also wish to consult the bookmarks that people other than the creator have used to organize it.
+If I'm not logged in, what can I see?
+You can see the summary and tags (including Archive Warnings) of any work whose creator has not restricted access to AO3 users only. In addition, you can access any unrestricted work rated "General" or "Teen" without logging in or clicking anything else. For the other ratings ("Mature", "Explicit", and "Not Rated"), you will be asked to agree that you are willing to see adult content before you can access the work.
+Back to Top | Ratings and Archive Warnings FAQ
+
+Other Tags
++++
+Table of Contents
+-
+
- What are the minimum criteria for tags in mandatory fields? +
- What is a non-specific tag? +
- What should I do if no language tag exists for the primary language used in my work? +
- Will you require an incorrect language tag to be changed? +
- In what circumstances will you remove a fandom tag from a work? +
- This work is about a fandom that the creator hasn't tagged. Will you require them to add the fandom tag to their work? +
- Why do some tags have "RPF" on the end? What's the difference between a fandom tag with RPF and without? +
- Am I allowed to use an RPF fandom tag if my work is about the reader, or if it contains a self-insert character? +
- I'm posting a work that will contain content for a particular fandom in a future chapter that I haven't posted yet. Can I use that fandom tag to advertise the upcoming content of my work? +
- A work is appearing in my fandom's tag even though it's not tagged with or about my fandom. I think the tag the creator used was linked to my fandom by mistake. Can I report that? +
- I want to report a work that has a wrong language tag and inapplicable fandom tags. Who should I report it to? +
- What if a work has an incorrect category, relationship, character, or additional tag? +
- Can other users add tags to my fanworks? How does that work? +
- Someone has added a tag I hate to a bookmark of one of my fanworks! +
- Where can I find more information about tags? +
What are the minimum criteria for tags in mandatory fields?
+The tags on your work must meet the following criteria:
+-
+
- Rating: If the work contains graphic adult content, you must rate the work as either "Mature" or "Explicit", or use the "Not Rated" tag. +
- Archive Warnings: If the work contains depictions of content described by one of the four specific Archive Warnings, you must apply that Archive Warning tag or the "Creator Chose Not To Use Archive Warnings" tag. +
- Fandoms: The work may only use fandom tags that directly relate to content currently present in the work. +
- Language: The language tag must indicate a language used in a major portion of the work text, unless no such language tag is available. +
If you wish to provide other users with more information about your work, you are welcome to do so using the non-mandatory tag fields (such as Additional tags), your work summary, and/or the notes of your work.
+What is a non-specific tag?
+Some mandatory fields may have non-specific tags, such as "Not Rated", "Creator Chose Not To Use Archive Warnings", or "Unspecified Fandom". These tags indicate that the creator has deliberately chosen not to provide more specific information in the mandatory tag field. For example, sometimes creators aren't certain whether a specific tag would apply, or want to avoid using a specific tag because they believe it would reveal spoilers. Using a non-specific tag is always sufficient tagging for that tag field. The Policy & Abuse committee will not require any work that bears a non-specific tag to have more tags added to that field. Users who wish to avoid certain types of content should avoid all works that use non-specific tags.
+What should I do if no language tag exists for the primary language used in my work?
+If the language is one that you or someone else created, you can use the "Uncategorized Constructed Language" tag. If the language is not a constructed language ("conlang"), please contact the Support committee.
+Will you require an incorrect language tag to be changed?
+In general, we will assume good faith from creators. However, if it is clear that the language tag used does not apply to the work, then we may update the work's language tag.
+In order to report a work that uses an incorrect language tag, please contact the Support committee and make sure to include a link to the work in your report.
+In what circumstances will you remove a fandom tag from a work?
+The Policy & Abuse committee may remove a fandom tag when there is no relationship between the particular fandom itself and the work. For example, a fanwork that discusses vampire physiology and uses only examples from Buffy the Vampire Slayer and The Vampire Diaries should not add in fifteen additional fandom tags simply because those fandoms also feature vampires.
+Note that we will apply this rule restrictively. We will not intervene in cases of disagreement over, for example, whether a movie-based work can use the fandom tag for a comic when there are both movie and comics versions of a source. This is the kind of decision a creator is best suited to make and falls within our policy of deference to the creator.
+If you believe a work's tags are misleading, then we encourage direct, polite conversation with the creator. However, if the work has fandom tags that aren't represented in the work, then you can report that to the Policy & Abuse committee.
+This work is about a fandom that the creator hasn't tagged. Will you require them to add the fandom tag to their work?
+No, we will not require that a creator add a specific fandom tag to their work. However, we may apply the non-specific "Unspecified Fandom" tag if the creator has not applied any suitable fandom tags themselves. If you would like to avoid encountering a particular work, then we recommend that you mute the creator or the work.
+Why do some tags have "RPF" on the end? What's the difference between a fandom tag with RPF and without?
+RPF stands for Real Person Fiction. "RPF" is often used to distinguish fandom tags intended for fanworks about a canon's real-life creators (actors, directors, voice actors, authors, etc.), as opposed to fanworks about the fictional characters that appear in any books, movies, or other canons.
+When you are posting your work, you may find that entering the name of a canon into the fandom tag field results in two canonical tags appearing in the autocomplete, one with "RPF" at the end and one without. If your work is about the real people who created the canon, rather than about the fictional canon itself, then you should use the RPF fandom tag for your work. If your work is about the fictional characters or universe, you should use the non-RPF fandom tag instead.
+In some cases, RPF fandoms and works don't have fandom tags with "RPF" at the end. For example, canonical fandom tags about musicians or bands may consist of the names of those individuals or groups. Fandom tags that consist of the name(s) of real people are also considered RPF fandom tags and can be used on works about those people.
+For more information about RPF and non-RPF tags, please refer to the Tags FAQ. The Policy & Abuse committee may remove fandom tags from your work if you've used a non-RPF tag for RPF content, or vice versa.
+Am I allowed to use an RPF fandom tag if my work is about the reader, or if it contains a self-insert character?
+You should not use RPF fandom tags unless your work is about the real people who contributed to the creation of the fictional canon. If the reader or self-insert character is interacting with the fictional characters from the canon and not with the canon's writers, actors, etc., then the work is not RPF and should only be tagged with the non-RPF fandom tag.
+I'm posting a work that will contain content for a particular fandom in a future chapter that I haven't posted yet. Can I use that fandom tag to advertise the upcoming content of my work?
+No. To use a specific fandom tag, the work must currently contain fanwork content pertaining to that fandom. Once you post a chapter featuring characters from or set in the universe of that fandom, you may add the fandom tag to the work. Until then, you can use the notes, summary, or Additional tags to let other users know about your plans.
+A work is appearing in my fandom's tag even though it's not tagged with or about my fandom. I think the tag the creator used was linked to my fandom by mistake. Can I report that?
+Our volunteer tag wranglers connect tags to each other to help users locate fanworks. However, at times this can lead to unexpected search results. If you believe that a tag has been incorrectly wrangled, you can contact the Support committee with a brief explanation of why these tags shouldn't be connected together.
+I want to report a work that has a wrong language tag and inapplicable fandom tags. Who should I report it to?
+If the language tag is the only miscategorization on the work, you may report it to the Support committee. If there is any other type of miscategorization or violation of the Terms of Service (for example, if the work is not a fanwork or is incorrectly rated), you should report it to the Policy & Abuse committee instead, whether or not there is an incorrect language tag on the work.
+What if a work has an incorrect category, relationship, character, or additional tag?
+The Policy & Abuse committee will only evaluate the accuracy of tags in mandatory fields. We will not add, edit, or remove incorrect category, relationship, character, or additional tags. Our resources are limited and it would be challenging to impartially and fairly establish or enforce accuracy rules for these types of tags. However, our general policies against harassment and spam apply to all tags, as they do to any content posted on AO3.
+Can other users add tags to my fanworks? How does that work?
+The only tags displayed on the fanwork itself will be the tags that the creator added to it. If another user bookmarks the work, they may add tags to the bookmark. Users can search for bookmarks with Tag Search or Bookmark Search. Bookmark tags are also visible when viewing a user's public bookmarks. However, bookmark tags will not impact or appear in results when using Work Search or browsing works listings.
+Someone has added a tag I hate to a bookmark of one of my fanworks!
+We recommend that you mute the bookmarker. In general, tags and notes on bookmarks can be positive or negative. Like any other content, tags are subject to the Content Policy, so if the tag violates our harassment, personal information, or other policies, please report it. However, criticism of a fanwork is not considered harassment in and of itself. Bookmark tags and notes will not automatically be displayed on fanworks, in order to allow you to avoid them.
+Where can I find more information about tags?
+Please check out our Tags FAQ for more information about how tags function and how they are generally used.
+ +
+Spam and Technical Integrity
++++
+Table of Contents
+-
+
- What's this about the spam filter? Can I be permanently suspended if I fail the filter? +
- What do you mean by "conduct that threatens the technical integrity of AO3"? +
- Does that mean I can't have nifty formatting in my work? +
- Do you have a policy on bots or scraping? These are ways of extracting information from or indexing websites. +
What's this about the spam filter? Can I be permanently suspended if I fail the filter?
+You shouldn't encounter the spam filter if you're logged in. If we discover accounts created solely to post spam, we will permanently suspend those accounts, but such cases are always reviewed by members of the Policy & Abuse committee. If you're a human being reading this FAQ, you shouldn't worry about the automated spam-control measures.
+What do you mean by "conduct that threatens the technical integrity of AO3"?
+Basically, we mean attempts to hack the site or deliberately exploit a code vulnerability in order to engage in destructive behavior on AO3. Spreading viruses or other unwanted programs, redirecting users to spam sites, or trying to undermine or evade compliance with our Terms of Service through technological means are all examples of attempting to interfere with or threaten the technical integrity of the site.
+Does that mean I can't have nifty formatting in my work?
+No, this is just a security policy. You will be able to have plenty of nifty formatting, but not everything imaginable. As a practical security matter, we do not allow JavaScript in works posted on AO3, and only allow a limited subset of HTML and CSS. This is because there is no secure way to allow people to start uploading unfiltered code. For content that uses a lot of custom code, we recommend hosting it on your own website. You can make a bookmark or post a simpler version on AO3 and link to the fancier version in the notes.
+Do you have a policy on bots or scraping? These are ways of extracting information from or indexing websites.
+The use of bots or scraping for spam, commercial promotion, or other purposes that violate our policies is forbidden. This includes scraping AO3 for the purposes of obtaining material for commercial generative AI or creating an app that hosts or paywalls AO3 content.
+The use of bots or scraping for purposes that do not violate our policies is generally allowed. However, we reserve the right to implement robots.txt or other protocols limiting what bots can do, or to notify you and ask you to discontinue if a bot or scraping program is causing problems for the site. At our discretion, we may also ban specific bots or other programs from accessing AO3.
+Back to Top | Spam and Technical Integrity FAQ
+
+Privacy Policy FAQ
+Answers to common questions about the Privacy Policy are available below. If you have additional questions that are not covered here, you can contact the Policy & Abuse committee.
+ +Information Collection and Use
++++
+Table of Contents
+-
+
- Why do you use cookies? +
- Which AO3 features collect, process, retain, and/or display my content or personal information, and how do they use it? +
- Why do AO3 features need to collect, process, retain, and/or display my content or information in the ways that they do? +
- What happens if I change the privacy settings on my work? +
- What information can a co-creator access? What privacy settings can they change? +
- What information can a challenge or collection maintainer access? What privacy settings can they change? +
- If a new feature is introduced, how will it handle my content and personal information? +
Why do you use cookies?
+Cookies may be required to facilitate and customize your site experience, such as by allowing you to log in to your AO3 account. If you do not accept cookies, you may not be able to use the site. There are many ways to remove both browser history and cookies, and we encourage people who are concerned about privacy to investigate broader solutions. For example, most internet browsers can be set to clear your private data automatically between sessions.
+Which AO3 features collect, process, retain, and/or display my content or personal information, and how do they use it?
+Some AO3 features may display your content to the public, to other AO3 users, and/or to yourself and AO3 administrators.
+Display to the public
+We may collect, process, retain, and display your content to the general public, including any personal information you've included in that content, when you use the following AO3 features:
+-
+
- Post or edit a work or chapter, when the work is available to the general public +
- Create or edit a work skin that is applied to a work that is available to the general public +
- Edit information about a series, when any work in that series is available to the general public +
- Create or edit a bookmark, when the bookmark is not marked private +
- Choose a username or pseud +
- Edit your profile page +
- Edit the description for one of your pseuds +
- Upload an icon +
- Give kudos, both when you are logged in and when you are not logged in +
- Create or edit information about a Challenge or other type of Collection +
- Submit a prompt to a Prompt Meme Challenge +
- Submit a sign-up to a Gift Exchange Challenge (note: the owners and moderators of the Challenge will have access to your email address) +
- Post or edit a comment, when you comment on a news post or on a work that is available to the general public +
We also collect, process, and retain personal information that is associated with the content, including your IP address. We may display this information to AO3 administrators for the purposes of managing the site and enforcing the Terms of Service.
+Display to other AO3 users
+We may collect, process, retain, and display your content to other AO3 users, including any personal information you've included in that content, when you use the following AO3 features:
+-
+
- Save a work in draft form, when you have a co-creator on that work +
- Post or edit a work or chapter, when you choose to make the work available to other AO3 users +
- Create or edit a work skin, which you then apply to a work that is available to other AO3 users +
- Edit a series, when all works in the series are available to other AO3 users only and not to the general public +
- Add a work to a Collection owned or moderated by someone else +
- Post or edit a comment, when you comment on a work that is available to other AO3 users +
We also collect, process, and retain personal information that is associated with the content, including your IP address. We may display this information to AO3 administrators for the purposes of managing the site and enforcing the Terms of Service.
+Display to yourself and/or to AO3 administrators
+We may collect, process, retain, and display your content and preferences to yourself and/or to AO3 administrators, including any personal information you've included in that content, when you use the following AO3 features:
+-
+
- Request an account invitation, whether or not you choose to create an account +
- Create an account +
- Save a work in draft form +
- Create or edit a private bookmark +
- Update your preferences +
- Mark a work for later +
- Favorite a tag +
- Block a user +
- Mute a user +
- Create or edit a site skin +
- Create or edit a work skin, even without applying it to a work +
We also collect, process, and retain personal information that is associated with the content, including your IP address. We may display this information to AO3 administrators for the purposes of managing the site and enforcing the Terms of Service.
+Why do AO3 features need to collect, process, retain, and/or display my content or information in the ways that they do?
+Because you want your content or information to be available to other people
+AO3 is a site for fans to share fanworks. When you post a work and set it to be available to the general public, you are agreeing to make that content available to everyone. Similarly, the purpose of using other public-facing AO3 features is because you want that content to be available to the public. When you post a work and set it to be available to registered AO3 users only, you are agreeing to make that content available to those users.
+Similarly, other AO3 features or content may be accessible by all registered AO3 users or only accessible to specific registered AO3 users (such as the co-creator(s) of a work or the maintainer(s) of a collection). The purpose of using these features is because you want that content to be available to those people. For example, if you're collaborating with someone else on a draft work where you have added them as a co-creator, then you want your co-creator to be able to access the draft. If you have submitted a work to a collection, then you have chosen to submit content to a part of AO3 that the collection maintainer controls. In all cases, we need to collect, process, and retain certain information about you and your content in order to make it available to those people.
+Because you want your content or information to be associated with your identity
+Usernames and pseudonyms allow you to develop your account as a fannish identity on AO3. When you take actions while using a username or pseud (as opposed to not being logged in, or not using a pseud), it's because you want your username or pseud to be associated with those actions and/or the content that you've uploaded. In order to connect your actions and content to your AO3 account and/or pseud, we need to collect, process, and retain the associated personal information about your account, including the text you entered for your username or pseud.
+Because you want your content or information to be available to yourself
+Some of our features are designed to let you upload content that you want to access later. For example, when you create a draft work or a private bookmark, use the "Mark for Later" feature, or favorite a tag, your purpose is to be able to return to them later. In order to allow you to do so, we need to collect, process, and retain the content that you provided and the associated information.
+To allow you to customize your AO3 experience
+Several of our features are designed to let you customize the way AO3 is displayed to you or the ways in which other users can interact with you. We need the data collected by these features in order to customize your AO3 experience in the ways you've requested. For example, we need access to your blocklist in order to ensure that users you have blocked can't leave comments or kudos on your works or reply to your comments; and we need access to your mutelist to ensure that you won't be shown works, bookmarks, comments, or series by users you've muted. Similarly, when you update your preferences, we need to collect, process, and retain the content and/or information that you provided in order to implement those preferences for you.
+To operate, maintain, and protect AO3
+In order to be able to enforce the Terms of Service, ensure we are compliant with applicable legislation, and handle any legal matters that may arise, AO3 administrators (such as the Policy & Abuse committee, the Legal committee, and the OTW Board of Directors) may need to view content that was uploaded, or the associated data, even if that content is not visible to the general public or to other AO3 users.
+We also need the data collected by each feature to internally manage AO3. For example, we want to count only one view of a URL per cookie session on the "Hit" count for a work. Temporarily collecting, processing, and retaining the IP addresses of users who leave kudos while logged out permits us to conduct internal management of kudos and avoid duplication of kudos, without requiring you to log in and associate your username with the kudos. Our systems and administrators need the data to manage our services, prevent abuse or spam, and maintain the integrity of AO3.
+To assist you with using AO3
+It's possible you may need assistance with your account. In such cases, the Support committee or other AO3 administrators may need to look at your content or associated data in order to troubleshoot a problem you're having, assist you with using a particular AO3 feature, or diagnose or solve a possible bug. For example, if you're having difficulty with not receiving emails about comments on your works, an administrator may need to check whether your Preferences are set correctly.
+What happens if I change the privacy settings on my work?
+When you post or edit a work on AO3, you can choose to restrict access to other logged-in users only. You can change this setting at any time. If the work was originally accessible to AO3 users only, and you (or a co-creator) update the work to make it accessible to the general public, then the work and any content associated with the work (such as bookmarks, comments, or series) will become accessible to the general public at that time. Similarly, if your work was previously set to be accessible to the general public, and you update the work to make it accessible to AO3 users only, then the content associated with the work will no longer be accessible to the general public.
+If you have a series where all works in the series are only accessible to other AO3 users, and you (or a series co-creator) add to the series a work that is accessible to the general public, then the series content will also become accessible to the general public at that time. This applies to the series content only, and not to specific works in the series, which are all controlled separately.
+You (or a co-creator) can add your work to a collection that is maintained by yourself and/or someone else. Adding your work to an anonymous and/or unrevealed collection will limit some information about and/or access to the work to yourself and to the collection maintainers. The collection maintainers can change the collection settings or remove your work from their collection at any time. You can remove your work from a collection at any time.
+What information can a co-creator access? What privacy settings can they change?
+When you invite a co-creator to a work you've uploaded to AO3, you are giving them the ability to edit or delete the work, add or remove the work from a series or collection, or delete any of its comments at any time, regardless of whether the work has been posted or is still in draft form. Any co-creators of a work can change the privacy settings for that work at any time, without notifying you. If the co-creators of a work have different account preferences regarding their works' accessibility or permissions, the work will adhere to the least restrictive preference. For example, if one co-creator allows their works to be invited to collections, and another co-creator does not, it will be possible to invite the co-created work to a collection.
+When you invite a co-creator to a series you've created, you are giving them the ability to edit or delete the series (but not any works in the series, unless they are also a co-creator of the work(s) in question). If all works in the series are only accessible to other AO3 users, and your co-creator adds to the series a work that is accessible to the general public, then the series content will also become accessible to the general public at that time. This applies to the series content only, and not to specific works in the series, which are all controlled separately.
+We recommend that you do not invite anyone as a co-creator of your work unless you are comfortable with giving that person equal access to and control over that work and the content and settings associated with it. You cannot remove a co-creator from your work after you have invited them. Co-creators can remove themselves from a work at any time.
+What information can a challenge or collection maintainer access? What privacy settings can they change?
+If you add your work to a collection, the owners and moderators of the collection ("collection maintainers") will be able to access (but not edit or delete) the content of the work. They will also know the usernames and pseuds of all creators associated with the work, even if the work is in a collection marked as anonymous or unrevealed. You can remove your work from a collection at any time. A collection maintainer can remove a work from their collection at any time, or remove the "anonymous" and/or "unrevealed" status provided by their collection, without notifying you. When this occurs, the creators' usernames and/or the content of the work will become accessible either to other AO3 users or to the general public, depending on the work settings.
+A maintainer of a Gift Exchange challenge can access sign-ups as well as the usernames and email addresses that participants use to sign up. This is in case the maintainer needs to communicate with the exchange's participants. Maintainers of other types of collections do not have access to other users' email addresses.
+Please note that using this information in any way other than to manage the collection or challenge is a violation of our Terms of Service and may result in the permanent suspension of the maintainer's account.
+If a new feature is introduced, how will it handle my content and personal information?
+If the feature is designed to display content to other users or to the general public, then when you choose to use that feature, your content may be displayed to other users or to the general public. Any personal information or other data we collect will be used to operate that feature and other integrated features on AO3, maintain AO3, and prevent spam and abuse of the feature or AO3. Administrators may have access to any content uploaded with the feature, and associated data, for these purposes.
+AO3 is committed to protecting the privacy of our users. We will never sell your personal information, data, or other content. If you have a specific question about how your content and/or information is collected or used, please contact the Policy & Abuse committee.
+Back to Top | Information Collection and Use FAQ
+
+User Privacy Rights
++++
+Table of Contents
+-
+
- What information do you sell, trade, or rent to third parties? +
- What legal rights do I have under data privacy laws? +
- What lawful grounds does AO3 rely upon to process personal information from users in the EU and the UK? +
- How do I exercise my rights under data privacy laws such as the General Data Protection Regulation (GDPR) or the California Consumer Privacy Act (CCPA)? +
- What is the procedure for requesting details about the information you sell, trade, or rent to third parties for direct marketing purposes under the California Consumer Privacy Act (CCPA)? +
- Do you recognize and comply with Do Not Track signals or opt-out preference signals? +
What information do you sell, trade, or rent to third parties?
+None. We do not and will not sell, trade, or rent information, including your personal information.
+What legal rights do I have under data privacy laws?
+If you are located in the European Union, the United Kingdom, or parts of the United States, you may have rights regarding your personal information or personal data that qualifies as such under the laws of your jurisdiction.
+As provided by the laws of your applicable jurisdiction, these rights may include:
+-
+
- The right to know what personal information we have collected about you +
- The right to request that we provide access to, correct, or delete your personal information +
- The right to request that your personal information be provided in portable form +
- The right to not be discriminated against for exercising your legal rights +
- The right to not be subject to a decision that would affect your legal rights based solely on automated processing of your personal information +
What lawful grounds does AO3 rely upon to process personal information from users in the EU and the UK?
+We rely on the following lawful grounds to process personal information from users in the EU and the UK:
+-
+
- It is necessary for the performance of a contract with you +
- Our or a third party's legitimate business interest +
- Your consent +
If we are processing your personal information based on the grounds that you consented to it, you have the right to withdraw your consent for such processing at any time. Withdrawing your consent does not affect the lawfulness of consent-based processing that occurred prior to when your consent was withdrawn.
+These protections are not limited specifically to users from the EU and the UK. We limit our data processing in this way for all users. If you have questions regarding the protection of your personal information, you can contact the Policy & Abuse committee.
+How do I exercise my rights under data privacy laws such as the General Data Protection Regulation (GDPR) or the California Consumer Privacy Act (CCPA)?
+To exercise the rights available to you as a data subject or consumer under applicable data privacy laws, contact the Policy & Abuse committee. In order for us to confirm your request, the email address you enter must be the one associated with your account (if applicable) and you must be able to send and receive emails from that address. In the subject and description of your request, please specify which data privacy law (GDPR, CCPA, etc.) applies to you, and clearly state what kind of data request you are making (for example, you can request a copy of your personal information). We may require you to submit additional personal information necessary to verify your identity and status as a data subject. Repeated requests within a 1-year timeframe may incur a fee.
+Please note that you may be able to exercise some of these rights without our intervention. For example, if you are a registered user, you can access and update certain personal information via your account preferences.
+What is the procedure for requesting details about the information you sell, trade, or rent to third parties for direct marketing purposes under the California Consumer Privacy Act (CCPA)?
+The CCPA only applies to for-profit entities. Because the Organization for Transformative Works is a non-profit, we are not required to have such a procedure. More importantly, we do not have such a procedure because we do not sell, trade, or rent information to third parties for any reason, including for direct marketing purposes.
+Do you recognize and comply with Do Not Track signals or opt-out preference signals?
+Some web browsers, mobile applications, and operating systems allow users to signal their preferences regarding the tracking of their personal information. These are known as Do Not Track (DNT) signals or opt-out preference signals. AO3 does not respond to DNT or opt-out preference signals because we do not use, sell, or share your personal information for targeted advertising purposes. In addition, we collect only the minimum data necessary to operate the site and/or that you have consented to provide to us. Without this minimum data, you can't access the site.
+If a standard for online tracking is adopted that we must follow in the future, we will inform you about that practice in a revised version of the Privacy Policy.
+ +<%= t("a11y.navigation") %>
+<%= render "tos_navigation", top_link: true %> + diff --git a/app/views/invite_requests/_index_open.html.erb b/app/views/invite_requests/_index_open.html.erb index 5726e4c7a9b..06cd0674d20 100644 --- a/app/views/invite_requests/_index_open.html.erb +++ b/app/views/invite_requests/_index_open.html.erb @@ -1,25 +1,18 @@- <%= ts("Invitation Requests") %> + <%= t(".page_heading") %>
- <%= ts("To get a free Archive of Our Own account, you need an Invitation. - By submitting your email address to our invitation queue, you confirm - that you are at least 13 years old, and if you're in a country whose - residents/citizens have to be of an age older than 13 to consent, - you are old enough to consent to the processing of your personal data - without our obtaining written permission from a parent or legal guardian. - We will use the email address you submit only to send you an Invitation - and to process/manage your account activation. Please don't request an Invitation - unless you've read the %{tos} and agree to abide by those Terms.", - tos: link_to(ts("Terms of Service"), tos_path) - ).html_safe %> + <%= t(".details_html", + tos_link: link_to(t(".tos"), tos_path), + content_policy_link: link_to(t(".content_policy"), content_path), + privacy_policy_link: link_to(t(".privacy_policy"), privacy_path)) %>
-<%= ts("Request an invitation") %>
+<%= t(".request_invitation_header") %>
<%= form_for(@invite_request, html: { class: "simple" }) do |f| %> <%= error_messages_for @invite_request %> @@ -27,17 +20,14 @@<%= f.label :email %> <%= f.text_field :email %> - <%= f.submit ts("Add me to the list") %> + <%= f.submit t(".add_to_list") %>
<% end %> -- <%= ts("If you have already requested an invitation, you can %{status}. There are currently %{count} people on the waiting list. We are sending - out %{invites} invitations per day.", - status: link_to("check your position on the waiting list", - status_invite_requests_path), - count: InviteRequest.count, - invites: AdminSetting.current.invite_from_queue_number).html_safe %> +
+ <%= t(".already_requested_html", check_status_link: link_to(t(".check_waitlist_position"), status_invite_requests_path)) %> + <%= t(".waiting_list_count", count: InviteRequest.count) %> + <%= t(".invitations_per_day", count: AdminSetting.current.invite_from_queue_number) %>
diff --git a/app/views/known_issues/index.html.erb b/app/views/known_issues/index.html.erb index acd5616f914..6d550cdb5e6 100644 --- a/app/views/known_issues/index.html.erb +++ b/app/views/known_issues/index.html.erb @@ -1,5 +1,5 @@ -<% if logged_in_as_admin? %> +<% if policy(KnownIssue).admin_index? %> <%= render :partial => "admin_index" %> <% else %><%= ts("Known Issues") %>
diff --git a/app/views/kudo_mailer/batch_kudo_notification.html.erb b/app/views/kudo_mailer/batch_kudo_notification.html.erb index 97b1776b1bd..3dded0b680d 100644 --- a/app/views/kudo_mailer/batch_kudo_notification.html.erb +++ b/app/views/kudo_mailer/batch_kudo_notification.html.erb @@ -12,13 +12,13 @@ # kudos are present. givers = names.dup givers << t(".guest", count: guest_count) unless guest_count.zero? - givers_list = givers.map { |k| style_bold(k) }.to_sentence.html_safe + givers_list = to_sentence(givers.map { |k| style_bold(k) }) %> <% if kudo_count == 1 && guest_count == 1 %> - <%= t(".html.single_guest.left_kudos", giver_list: style_bold(t(".html.single_guest.giver_list")).html_safe, commentable_link: commentable_link.html_safe).html_safe %> + <%= t(".single_guest.html", giver: style_bold(t(".single_guest.giver")), commentable_link: commentable_link) %> <% else %> - <%= t(".html.left_kudos", givers_list: givers_list, commentable_link: commentable_link.html_safe, count: kudo_count).html_safe %> + <%= t(".left_kudos.html", givers_list: givers_list, commentable_link: commentable_link, count: kudo_count) %> <% end %> <% if (index < @commentables.length - 1) %> diff --git a/app/views/kudo_mailer/batch_kudo_notification.text.erb b/app/views/kudo_mailer/batch_kudo_notification.text.erb index dd56a2c9415..a79104b9649 100644 --- a/app/views/kudo_mailer/batch_kudo_notification.text.erb +++ b/app/views/kudo_mailer/batch_kudo_notification.text.erb @@ -12,13 +12,13 @@ # present. givers = names.dup givers << t(".guest", count: guest_count) unless guest_count.zero? - givers_list = givers.to_sentence + givers_list = to_sentence(givers) %> <% if kudo_count == 1 && guest_count == 1 %> -<%= t(".text.single_guest", commentable_title: commentable_title, commentable_url: commentable_url) %> +<%= t(".single_guest.text", commentable_title: commentable_title, commentable_url: commentable_url) %> <% else %> -<%= t(".text.left_kudos", givers_list: givers_list, commentable_title: commentable_title, commentable_url: commentable_url, count: kudo_count) %> +<%= t(".left_kudos.text", givers_list: givers_list, commentable_title: commentable_title, commentable_url: commentable_url, count: kudo_count) %> <% end %> <% if (index < @commentables.length - 1) %> diff --git a/app/views/languages/_form.html.erb b/app/views/languages/_form.html.erb index 0634721c16b..cdaff60f3fa 100644 --- a/app/views/languages/_form.html.erb +++ b/app/views/languages/_form.html.erb @@ -2,51 +2,50 @@ <%= form_for(@language, html: { class: "post" }) do |f| %> -* <%= t('.required_notice', default: "Required information") %>
+* <%= t(".required_notice") %>
<% end %> - diff --git a/app/views/layouts/_footer.html.erb b/app/views/layouts/_footer.html.erb index 3f6e73ca1ce..fd64780d04e 100644 --- a/app/views/layouts/_footer.html.erb +++ b/app/views/layouts/_footer.html.erb @@ -1,14 +1,14 @@ diff --git a/app/views/users/_header_navigation.html.erb b/app/views/users/_header_navigation.html.erb index b5aae64b82b..5dbcf4a8a79 100644 --- a/app/views/users/_header_navigation.html.erb +++ b/app/views/users/_header_navigation.html.erb @@ -1,8 +1,8 @@ <% # expects @user to be set %> diff --git a/app/views/users/_sidebar.html.erb b/app/views/users/_sidebar.html.erb index 429c8ebcc95..a6a8a0295d2 100644 --- a/app/views/users/_sidebar.html.erb +++ b/app/views/users/_sidebar.html.erb @@ -1,30 +1,30 @@" role="navigation region"> -<%= ts("Choices")%>
+<%= t(".landmark.choices") %>
-<%= ts("Pitch")%>
+<%= t(".landmark.pitch") %>
-<% if @user == current_user %> -<%= ts("Catch")%>
+<% if @user == current_user || policy(:inbox_comment).show? %> +<%= t(".landmark.catch") %>
<% end %> -<%= ts("Switch")%>
+<%= t(".landmark.switch") %>
diff --git a/app/views/users/edit.html.erb b/app/views/users/edit.html.erb index 55508d1d3b8..9f308eb0c11 100644 --- a/app/views/users/edit.html.erb +++ b/app/views/users/edit.html.erb @@ -1,48 +1,40 @@ -<%= ts("Edit My Profile") %>
+<%= t(".page_heading") %>
<%= error_messages_for :user %> <%= error_messages_for @user.profile %> -<%= render 'edit_header_navigation' %> +<%= render "edit_header_navigation" %>- <%= ts("Any personal information you post on your public AO3 profile, - including your religious or political views, health, racial background, - country of origin, sexual identity and/or personal relationships, - will be accessible by the general public. Read more about our updated - Age and Privacy policies, and see how the AO3 collects data when - you're on the site and why we don't sell it to third parties, - in the %{tos}.", - tos: link_to(ts("Privacy section of the AO3 Terms of Service"), tos_path(anchor: "privacy")) - ).html_safe %> + <%= t(".public_information_notice_html", privacy_policy_link: link_to(t(".privacy_policy"), privacy_path)) %>
-<%= ts("Change Profile") %>
-<%= form_for(@user) do |f| %> +<%= t(".change_profile_landmark") %>
+<%= form_for(@user) do |f| %>-
<%= fields_for :profile_attributes, @user.profile do |p| %>
-
- <%= p.label :title, "Title" %> +
- <%= p.label :title, t(".title") %>
- <%= p.text_field :title, class: "observe_textlength" %> <%= live_validation_for_field("profile_attributes_title", presence: false, maximum_length: Profile::PROFILE_TITLE_MAX) %> <%= generate_countdown_html("profile_attributes_title", Profile::PROFILE_TITLE_MAX) %> -
- <%= p.label :location, "Location" %> +
- <%= p.label :location, t(".location") %>
- <%= p.text_field :location, class: "observe_textlength" %> <%= live_validation_for_field("profile_attributes_location", presence: false, maximum_length: Profile::LOCATION_MAX) %> <%= generate_countdown_html("profile_attributes_location", Profile::LOCATION_MAX) %> -
- <%= p.label :date_of_birth, "Date of Birth" %> +
- <%= p.label :date_of_birth, t(".date_of_birth") %>
- <%= p.date_select :date_of_birth, start_year: 12.years.ago.year, end_year: 90.years.ago.year, include_blank: true %> -
- <%= p.label :about_me, "About Me" %> +
- <%= p.label :about_me, t(".about_me") %>
-
<%= allowed_html_instructions %>
<%= p.text_area :about_me, class: "observe_textlength" %> @@ -55,12 +47,12 @@- <%= p.text_field :ticket_number, class: "required" %> <%= live_validation_for_field("profile_attributes_ticket_number", numericality: true) %> -
<% end %> -<%= ts("Numbers only.") %>
+<%= t(".admin.ticket_number.numbers_only") %>
- <%= p.text_field :ticket_number, class: "required" %> <%= live_validation_for_field("profile_attributes_ticket_number", numericality: true) %> -
- <%= p.label :update, "Update" %> -
- <%= f.submit "Update" %> +
- <%= p.label :update, t(".update") %> +
- <%= f.submit t(".update") %> <% end %>
<%= t("mailer.general.greeting.formal", name: style_bold(@resource.login)).html_safe %>
+<%= t("mailer.general.greeting.formal_html", name: style_bold(@resource.login)) %>
<%= t(".intro") %>
-<%= style_link t(".link_title"), edit_user_password_url(reset_password_token: @token).html_safe %>
+<%= style_link t(".link_title"), edit_user_password_url(reset_password_token: @token) %>
<%= t(".expiration") %>
<%= t(".unrequested") %>
<% end %> diff --git a/app/views/users/mailer/reset_password_instructions.text.erb b/app/views/users/mailer/reset_password_instructions.text.erb index fe2cf2de7a9..3e265bb7273 100644 --- a/app/views/users/mailer/reset_password_instructions.text.erb +++ b/app/views/users/mailer/reset_password_instructions.text.erb @@ -1,5 +1,5 @@ <% content_for :message do %> -<%= t("mailer.general.greeting.formal", name: @resource.login) %> +<%= t("mailer.general.greeting.formal_html", name: @resource.login) %> <%= t(".intro") %> diff --git a/app/views/users/registrations/_legal.html.erb b/app/views/users/registrations/_legal.html.erb index bf113887bf1..65db354f42c 100644 --- a/app/views/users/registrations/_legal.html.erb +++ b/app/views/users/registrations/_legal.html.erb @@ -1,23 +1,33 @@ -- <%= ts('You need to be at least 13 years old to become a registered member of the Archive.') %> - <%= ts("(Sorry to anyone younger! You'll be more than welcome when the time comes.)") %>
+<%= t(".over_thirteen_required") %>
<%= f.check_box :age_over_13 %> - <%= f.label :age_over_13, ts("Yes, I am at least 13.") %> + <%= f.label :age_over_13, t(".over_thirteen_confirm") %>
- <%= ts("And - really important - we need you to agree to our") %> - <%= link_to "Terms of Service (opens new window)", tos_path, :target => '_blank' %>: + <%= t(".agreement_required_html", + terms_of_service_link: link_to(t(".terms_of_service"), tos_path, target: "_blank", rel: "noopener"), + content_policy_link: link_to(t(".content_policy"), content_path, target: "_blank", rel: "noopener"), + privacy_policy_link: link_to(t(".privacy_policy"), privacy_path, target: "_blank", rel: "noopener")) %>
- style="display:none;"<% end %>>
<% # The effect is "Frozen" replaces "Reply." We can't do that in the helper
# method for the reply link because that would prevent "Frozen" from
# appearing on the Unreviewed Comments page for works with moderated
@@ -9,15 +9,13 @@
"> <%= render 'comments/comment_form', :comment => Comment.new, diff --git a/app/views/comments/_comment_form.html.erb b/app/views/comments/_comment_form.html.erb index e6af2d9d9d8..9dcf3adcd03 100644 --- a/app/views/comments/_comment_form.html.erb +++ b/app/views/comments/_comment_form.html.erb @@ -5,9 +5,9 @@<%= form_for value_for_comment_form(commentable, comment), remote: !comment.new_record?, authenticity_token: true, html: { id: "comment_for_#{commentable.id}" } do |f| %> <% end %>diff --git a/app/views/comments/_commentable.html.erb b/app/views/comments/_commentable.html.erb index 971098077bc..7fbd1bbdbb7 100644 --- a/app/views/comments/_commentable.html.erb +++ b/app/views/comments/_commentable.html.erb @@ -28,7 +28,7 @@
<%= search_header(@comments, nil, "Comment") %>
+ <%= render "comments/comment_abbreviated_list", comments: comments %> + <%= will_paginate(comments, param_name: "comments_page", params: { anchor: "comments-summary" }) %> +