top of page

AO3 Security Incident: Do GDPR Breach Rules Apply?

5 hours ago
19 min read

Introduction


Archive of Our Own (AO3) returned online on November 15, 2026, after approximately 17 days of disruption associated with a security incident. The AO3 security incident raised concerns about the safety of user accounts, possible unauthorized access to personal information, and the legal responsibilities of the nonprofit organization operating the archive. Although the service has resumed, its restoration does not mean that every question about the incident has been resolved.


The Organization for Transformative Works (OTW), which operates AO3, has stated that it has no current reason to believe its user database was compromised. It has also acknowledged that unauthorized access cannot yet be excluded. No confirmed theft of account information has been publicly established in the organization's incident announcements as of November 15.


The legal position depends on facts that remain under investigation. The European Union's General Data Protection Regulation (GDPR) and the United Kingdom's separate UK GDPR can apply to certain activities of organizations established abroad. Both regimes impose security obligations and, in specified circumstances, require notification of personal data breaches. Neither automatically converts every cybersecurity incident or website outage into a legal violation.


For AO3's international users, the immediate questions concern whether their information was exposed and what precautions remain appropriate. The broader legal inquiry concerns the circumstances in which a US-based digital archive becomes subject to European data-protection rules, particularly when an incident affects the confidentiality, integrity, or availability of personal information.


1. AO3 Security Incident: From Shutdown to Partial Return


AO3 is a nonprofit, noncommercial archive for fan-created works, including fiction and other creative material associated with books, films, television, music, games, and other subjects. Its parent organization, OTW, is a US nonprofit operated with substantial volunteer participation. The archive serves an international community whose activities include publishing works, maintaining bookmarks, leaving comments, and participating in collections.


The scale of that community makes account security a substantial concern. On June 19, 2026, AO3 announced that it had reached 11 million registered users. That figure describes the platform's registered membership at the time of the announcement; it does not establish how many individuals, if any, were affected by the subsequent security incident.


The interruption began with an operational announcement rather than a public disclosure of unauthorized access. OTW initially described AO3 as undergoing maintenance. The organization's later statements identified evidence of a security incident and explained that the service would remain unavailable while technical work continued. The distinction between the first public description and the later security disclosure is essential to understanding the chronology.


1.1 The October 29 Outage and Security Disclosure


At 07:13 UTC on October 29, OTW's status service reported that AO3 was down for maintenance. A subsequent announcement estimated that the interruption would last at least 12 hours. Later that day, the expected recovery period was extended substantially, with the organization indicating that restoration might require between two and four weeks.


At 01:27 UTC on October 30, OTW publicly disclosed that evidence of a security incident had been detected. It stated that the incident's scope was still being determined and that AO3 would remain offline while the organization investigated and addressed the findings. The announcement did not identify a responsible actor or provide a definitive technical explanation of the incident.


OTW simultaneously assured users that their published works, bookmarks, kudos, and other archived material had not been deleted. It also acknowledged uncertainty concerning the account database. The organization did not believe that database had been stolen, but it was unable to exclude that possibility.


These statements establish the existence of a security investigation, not the precise nature of the underlying intrusion or failure. The date of the public disclosure should not be mistaken for the date on which a possible unauthorized act began. Nor does the disclosure establish that the organization had already identified a personal data breach within the meaning of the GDPR.


1.2 AO3 Back Online on November 15


OTW announced AO3's return at 08:00 UTC on November 15, 2026. Access was restored with temporary restrictions designed to permit the service to resume before all recovery measures were completed. The official status record continued to describe limitations affecting normal operation.


User and collection icons were temporarily disabled, although OTW stated that the underlying images had not been deleted. Importing works from external websites remained unavailable. Users could download works in HTML format, while other download formats were temporarily suspended.


The organization also warned that high traffic could cause delays when loading the archive. According to its announcement, traffic-management measures were being used deliberately to control demand during the initial return. Users encountering a downtime page were advised to refresh and try again.


Draft preservation received particular attention because unpublished AO3 drafts ordinarily have a limited retention period. OTW reported that automatic deletion had been suspended during the interruption and that no drafts had been deleted while the site was unavailable. It announced that normal deletion would resume on November 29, when drafts reaching the ordinary 30-day threshold would again become eligible for removal.


The restoration announcement also confirmed that OTW had engaged an external security firm to assist with reviewing the incident and the site's security. Its statement did not announce a completed forensic investigation or establish that unauthorized access to the account database had been definitively ruled out.


2. What AO3 Has Said About Its User Data


The most significant unresolved factual issue is whether information associated with AO3 accounts was accessed or copied without authorization. OTW has acknowledged this possibility without confirming that it occurred. That position must be distinguished from a finding that user information was stolen.


Personal information held by an online archive can take several forms. Account registration records are one category. Technical information generated when people access the service is another. Users may also disclose information about themselves through profiles, comments, published works, or other interactions.


These categories present different privacy risks. Unauthorized access to an email address may expose a user to phishing attempts. The association between an account identifier and a person's offline identity may create separate concerns, especially where someone maintains a pseudonymous presence. Publicly available material and restricted account records also require different treatment when assessing unauthorized disclosure.


The protection of personal information intersects with the broader legal recognition of privacy and data protection as digital rights. In the present incident, however, identifying a potential privacy interest is not equivalent to demonstrating that the interest was violated.


2.1 Account Records, Password Hashes, and Public Content


In its October 30 announcement, OTW explained that AO3's account database may contain usernames, email addresses, IP addresses, and hashed passwords. It did not confirm that these records had been obtained by an unauthorized party. The identified categories describe information potentially at issue, not an established list of compromised records.


OTW stated that it uses industry-standard methods to store passwords in hashed form. A password hash is a representation produced by a mathematical process rather than the ordinary readable password itself. Such protection can reduce the consequences of database exposure, but it does not make every password immune to recovery attempts, particularly when a password is weak or reused.


The organization also stated that AO3 does not collect real names as part of its ordinary account records and that donor information is maintained in a separate system. Those assurances concern the organization's stated data-handling arrangements. They should not be understood as proof that an account can never be associated with an identifiable person.


Users sometimes disclose identifying details through content they choose to publish. A username may also be connected to an individual's offline identity through information available elsewhere. The legal significance of a possible disclosure depends on the information involved, its relationship to an identifiable person, and the circumstances of access.


The Court of Justice of the European Union addressed the identification of individuals through technical information in Breyer v Bundesrepublik Deutschland (Case C-582/14), decided on October 19, 2016. Interpreting Directive 95/46/EC, the predecessor to the GDPR, the Court held that a dynamic IP address could constitute personal data for a website operator where that operator had legal means enabling identification through additional information held by an internet service provider.


The judgment does not establish that every IP address in every operational context automatically identifies an individual. Its continuing relevance lies in the principle that information need not contain a person's name to qualify as personal data. The current GDPR likewise defines personal data by reference to an identified or identifiable natural person.


3. When Does a Security Incident Become a GDPR Breach?


A cybersecurity incident and a personal data breach are related but legally distinct concepts. A system may experience suspicious activity, attempted intrusion, service interruption, or defensive shutdown without the available facts establishing that personal data was compromised. The legal classification depends on what happened to the information and the systems processing it.


Article 4(12) of Regulation (EU) 2016/679 defines a personal data breach by reference to a security failure affecting personal information through specified forms of loss, destruction, alteration, unauthorized disclosure, or unauthorized access. The definition is broader than the ordinary expression “data leak,” which commonly suggests that information was exposed or copied.


The European Data Protection Board (EDPB), in its Guidelines 9/2022 on personal data breach notification under GDPR, explains that personal data breaches may affect confidentiality, integrity, or availability. These are different dimensions of information security, and an incident may involve more than one.


3.1 Confidentiality, Integrity, and Availability


A confidentiality breach occurs when personal information becomes accessible to someone who is not authorized to receive or examine it. An attacker obtaining account records would present a potential example. Whether that happened at AO3 has not been established in the organization's public announcements.


An integrity breach concerns unauthorized or accidental alteration of information. The legal issue is whether records have been changed or corrupted in circumstances falling within the GDPR definition. OTW's statement that archived content remained preserved provides relevant reassurance, but it is not a published technical determination addressing every possible form of data alteration.


An availability breach concerns the loss of access to personal information. The EDPB recognizes that such a loss can be temporary. Data may remain stored and eventually be recovered while nevertheless having been unavailable during a security incident.


This distinction is also relevant to major technology disruptions more generally. The legal treatment of an international technology-service outage depends on the services affected, the applicable legal rules, and the consequences of the interruption. The same factual event can raise questions under several regulatory frameworks without satisfying the requirements of every framework.


3.2 Was AO3's Downtime a Loss of Data Availability?


AO3's extended interruption makes availability an appropriate subject of legal examination. Users could not access the archive normally for approximately 17 days, and the disruption affected their ability to retrieve, manage, or publish material. Some of that material may qualify as personal data when it relates to an identified or identifiable person.


The EDPB's guidance recognizes that a security incident causing personal data to become unavailable for a period may constitute a personal data breach. It also expressly distinguishes such incidents from planned system maintenance, which does not become a breach merely because access is temporarily suspended.


That distinction is particularly significant here. OTW kept AO3 offline while investigating and responding to a security incident. The public record does not establish whether a security failure independently deprived the organization of access to personal data, whether authorized personnel retained access while public access was suspended, or how the technical recovery process affected the relevant records.


The duration of the outage is relevant to assessing potential consequences but cannot resolve these factual questions. A temporary inability to use a public website is not necessarily identical to a loss of availability of personal data resulting from a breach of security.


If an availability-related personal data breach occurred, the organization would have to assess its effects on individuals under the applicable legal regime. The EDPB distinguishes disruptions producing substantial risks to individuals from interruptions causing limited inconvenience. The classification and potential notification duties depend on the nature of the data, the circumstances of the interruption, and its likely consequences.


4. Does the EU GDPR Apply to Archive of Our Own?


AO3 is operated by a US nonprofit organization, but the GDPR's territorial reach is not limited to entities incorporated or headquartered within the European Union. Article 3 establishes circumstances in which processing performed by organizations established outside the Union falls within the regulation.


The relevant legal inquiry concerns the organization's activities and the relationship between particular processing operations and individuals in the Union. The nationality of a user is not the controlling criterion. Nor does the absence of a subscription fee create a general exemption from the GDPR.


These rules form part of a broader category of extraterritorial jurisdiction in international law, in which states or regional legal systems apply regulatory requirements to conduct connected with their territories or protected interests. The GDPR supplies its own statutory conditions for such application.


The existence of those conditions must be demonstrated rather than presumed from the international character of a website. AO3's substantial international audience makes the question significant, but audience size alone does not settle the applicable territorial test.


4.1 Article 3 and the Limits of Extraterritorial Reach


Article 3(2) applies to certain processing activities of controllers or processors not established in the Union when those activities relate to offering goods or services to individuals in the Union or monitoring their behavior there. The provision expressly covers qualifying services whether or not payment is required.


Recital 23 explains that the mere accessibility of a website within the Union is insufficient to establish an intention to offer services there. Indicators of targeting may include language choices, references to users in Member States, and other circumstances demonstrating that the provider envisages serving individuals in the Union.


For AO3, an assessment would need to consider the actual organization and provision of the service, the processing activities concerned, and the evidence connecting those activities to individuals in EU Member States. The presence of European users is relevant but does not, standing alone, demonstrate every element of Article 3(2).


A further distinction concerns legal coverage and enforcement. A regulator's ability to apply data-protection legislation to foreign processing reflects an exercise of prescriptive authority. The practical enforcement of regulatory decisions against an organization abroad raises additional issues. The distinction between prescriptive jurisdiction and enforcement jurisdiction remains important even where legislation expressly provides for extraterritorial application.


The geographic location of a server is not, by itself, a complete answer to the territorial question. Data may be stored, accessed, or otherwise processed across different jurisdictions, and international transfers can engage separate legal requirements. Those questions should not be confused with the specific territorial conditions established by Article 3.


Accordingly, the possible application of EU data-protection law to AO3 is a legitimate legal question. The available public information does not support a definitive finding that every AO3 processing activity falls within the GDPR or that the organization has violated obligations under that regulation.


5. GDPR Data Breach Notification and the 72-Hour Rule


The GDPR establishes separate obligations concerning security, notification to regulators, and communication with affected individuals. These obligations are related, but their legal triggers are not identical.


Article 32 requires controllers and processors, within their respective responsibilities, to implement technical and organizational measures appropriate to the risks of processing. The provision expressly concerns the confidentiality, integrity, availability, and resilience of relevant systems and services. It also addresses the ability to restore access to personal data following a physical or technical incident.


Article 33 concerns notification after a personal data breach has occurred. It does not require every technical disruption to be reported. Once the GDPR applies and a personal data breach is established, the notification assessment depends on the likelihood of risk to individuals' rights and freedoms.


The international character of cross-border data flows can complicate the identification of applicable supervisory authorities. A service may process information relating to individuals in several jurisdictions, while the controller responsible for that processing is established elsewhere. The GDPR contains specific rules governing which authorities must receive notifications in those circumstances.


The fact that an investigation remains incomplete does not necessarily suspend every reporting obligation. The rules contemplate notification before all details are available, while permitting additional information to follow as the relevant facts become clearer.


5.1 Notification to Authorities and Affected Users


Under Article 33(1), a controller generally must notify the competent supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of a personal data breach. Notification is not required under that provision when the breach is unlikely to result in a risk to the rights and freedoms of natural persons.


The starting point is awareness of the personal data breach, not necessarily the beginning of a technical disruption or the date of a public announcement. The EDPB's guidance addresses how an organization determines that a breach has occurred and how uncertainty should be handled during an investigation.


Article 33(4) permits notification information to be provided in phases when it cannot all be supplied at once. Article 33(5) separately requires the controller to document personal data breaches, including relevant facts, effects, and remedial action. Recordkeeping remains significant even where notification is not required.


For controllers established within the European Union, the GDPR's one-stop-shop mechanism may allow a lead supervisory authority to coordinate certain cross-border matters. A different position applies to controllers established outside the Union whose processing falls within Article 3(2).


In its Guidelines 9/2022, the EDPB explains that the appointment of an EU representative under Article 27 does not, by itself, establish access to the one-stop-shop mechanism. A foreign controller may consequently have to notify several national supervisory authorities when a reportable breach affects individuals residing in different Member States.


The obligation remains the controller's responsibility, although an appointed representative may assist where its mandate permits. The EDPB's guidance does not imply that every foreign organization must notify every EU authority after any incident. The applicable territorial requirements, existence of a personal data breach, notification threshold, and geographic distribution of affected individuals must first be considered.


Communication to affected individuals is governed by Article 34. Its threshold is higher: the breach must be likely to result in a high risk to individuals' rights and freedoms. Where that threshold is met, communication must generally occur without undue delay, subject to the exceptions specified in the provision.


An incident involving possible exposure of account identifiers and password hashes would require an assessment of the likelihood and consequences of misuse. Relevant circumstances could include the security of the affected records, the sensitivity of associated information, and the possibility that exposure would enable account compromise or identification of pseudonymous users.


For AO3, the public record does not establish whether personal data was compromised, whether a notification threshold was met, or whether any notification was submitted to an EU authority. Those questions cannot be resolved from the length of the outage or the organization's public status announcements alone.


The EU's proposed Digital Omnibus reforms do not change this assessment under the law currently in force. The proposal includes an extension of the supervisory-authority notification period from 72 to 96 hours and changes to the notification-risk threshold. The EDPB and European Data Protection Supervisor discussed those proposals in their February 2026 joint opinion, and the Council adopted a negotiating position in October. As of November 15, the proposals had not replaced the existing GDPR requirements.


5.2 UK GDPR and the Information Commission


The United Kingdom operates a separate data-protection regime following its withdrawal from the European Union. The UK GDPR retains a territorial framework capable of reaching certain activities of organizations established outside the UK, including qualifying services offered to individuals there.


Its breach-notification provisions also generally use a 72-hour period following awareness of a notifiable personal data breach. As under the EU framework, notification to the regulator and communication to affected individuals depend on different levels of risk.


The identity of the British regulator changed shortly before the AO3 incident. On September 30, 2026, the Information Commission formally succeeded the former Information Commissioner under reforms introduced by the Data (Use and Access) Act 2025. The organization continues to use the abbreviation ICO, referring to the Information Commission's Office.


The transition changed the regulator's governance structure without removing its core data-protection responsibilities. Its guidance continues to explain the distinction between reportable personal data breaches and incidents that do not meet the notification threshold.


Whether the UK GDPR applies to particular AO3 processing activities requires its own territorial assessment. A conclusion about EU GDPR coverage does not automatically establish UK jurisdiction, and the reverse is also true.


6. Security Standards, Liability, and Judicial Guidance


Even where a personal data breach is established, it does not follow that a controller necessarily failed to implement appropriate security measures. The GDPR uses a risk-based framework rather than imposing an absolute guarantee that no incident will ever occur.


Article 32 requires consideration of factors including the state of the art, implementation costs, the nature and context of processing, and risks to individuals. Appropriate safeguards may include measures concerning confidentiality, resilience, recovery, testing, and organizational procedures. Whether particular measures are sufficient depends on the processing activity and the circumstances.


For AO3, the absence of a detailed public technical account limits any assessment of compliance. OTW's engagement of an external security firm and its restoration work are relevant operational developments. They do not independently establish that all applicable security obligations were satisfied, nor do they demonstrate that those obligations were breached.


6.1 Accountability Under Article 32 and C-340/21


The Court of Justice examined the relationship between a cybersecurity incident and the adequacy of security measures in VB v Natsionalna agentsia za prihodite (Case C-340/21), decided on December 14, 2023. The proceedings concerned unauthorized disclosure of personal information following a cyberattack against Bulgaria's National Revenue Agency.


The Court held that unauthorized disclosure or access by a third party does not, by itself, establish that the controller's technical and organizational measures were inappropriate under Articles 24 and 32. A court must assess those measures concretely, considering the risks associated with the processing and the nature, content, and implementation of the safeguards.


The judgment also addressed proof of compliance in actions for compensation under Article 82. In that procedural setting, the controller bears the burden of demonstrating that its security measures were appropriate under Article 32. This allocation does not mean that every claimant automatically establishes infringement, damage, or causation upon showing that a cyberattack occurred.


The Court further rejected the proposition that an organization necessarily escapes liability merely because a third party caused the unauthorized disclosure. The responsibility analysis requires examination of the applicable obligations and the relationship between the alleged infringement and the damage claimed.


These principles limit premature conclusions about AO3. A security incident cannot be treated as conclusive proof of inadequate protection. Equally, the possibility of an external attacker would not, without more, exclude legal responsibility if an applicable obligation were breached.


6.2 Compensation, Personal Harm, and User Rights


Article 82 of the GDPR provides for compensation where a person suffers material or nonmaterial damage as a result of an infringement of the regulation. Compensation is not automatic upon the occurrence of a technical incident.


In Österreichische Post (Case C-300/21), decided on May 4, 2023, the Court of Justice identified three cumulative conditions: an infringement of the GDPR, damage suffered by the claimant, and a causal connection between the infringement and that damage. The Court rejected a separate minimum-seriousness threshold for nonmaterial damage while preserving the requirement to establish that damage occurred.


The Court's subsequent judgment in VB clarified that a well-founded fear of future misuse of personal information can, depending on the circumstances, constitute nonmaterial damage. The claimant must still establish the relevant infringement, the harm relied upon, and the required causal connection. An unsupported concern about a possible future breach does not itself establish a right to compensation.


For AO3 users, these principles distinguish understandable anxiety from a legally established claim. The possibility that account information might have been accessed is not equivalent to proof that the information was obtained or misused. The absence of confirmed misuse does not make every possible claim legally impossible, but the applicable requirements must be satisfied.


Where the GDPR applies, individuals may also exercise relevant data-protection rights and, under Article 77, lodge complaints with a competent supervisory authority. Those mechanisms are separate from a damages action. Their availability and practical application depend on the applicable law and the circumstances of the processing.


7. What AO3 Users Can Do Following Its Return


OTW's November 15 guidance recommended that users consider changing their AO3 passwords and ensure that their account email addresses remain current. It also advised changing passwords on other services where the same password had been reused. These recommendations were precautionary; they were not an announcement that passwords had been stolen.


Using a strong, unique password for AO3 reduces the consequences of password reuse across different services. Where credentials are shared between accounts, an exposure affecting one service may create opportunities for attempts to access others. A reputable password manager can help users maintain separate credentials without relying on repeated passwords.


Users should also be cautious about messages claiming that an account has been compromised or requesting credentials. A prolonged outage and public uncertainty can create opportunities for impersonation and phishing. A message referring to the AO3 incident should not be treated as authentic merely because it uses the correct terminology or mentions an actual disruption.


OTW stated on November 6 that certain delayed notification emails had been released after accumulating before the outage. It identified those communications as genuine. That explanation does not mean that every later email mentioning AO3 should be trusted without examining its origin and purpose.


Authors with unpublished drafts should pay particular attention to the November 29 deletion schedule announced by OTW. The organization said draft deletion had been paused and that ordinary retention rules would resume after the additional period. Saving a personal copy or publishing a completed draft before the relevant deadline can reduce the risk of losing material through normal expiration.


Users should distinguish the security of the service from the final outcome of the investigation. AO3's availability demonstrates that public access was restored. It does not establish that every technical question has been answered. The organization has indicated that further information will be provided as its review proceeds.


Conclusion


AO3 returned online on November 15, 2026, following a prolonged interruption associated with a confirmed security incident. OTW has reported that archived content was preserved and that the account database is not currently believed to have been compromised. The organization has nevertheless acknowledged that unauthorized access cannot conclusively be excluded while the investigation continues.


The EU GDPR and UK GDPR may impose obligations on a US-based archive when their territorial requirements are satisfied. Their provisions cover more than unauthorized disclosure: certain security failures affecting personal-data availability can also qualify as breaches. Whether those rules apply to AO3's particular circumstances depends on the affected processing activities, the nature of any security failure, and the risks to individuals.


The evidence available on November 15 does not establish that AO3's user database was stolen, that a reportable personal data breach occurred, or that OTW violated European data-protection law. The immediate practical response for users is to maintain secure, unique credentials and follow the organization's recovery guidance. The legal assessment remains dependent on the technical findings and their relationship to the obligations imposed by the applicable data-protection regimes.


References


Council of the European Union (2026) ‘Digital rulebook: Council agrees position to simplify data protection, privacy and cyber reporting rules’ [online]. 21 October 2026. Available at: https://www.consilium.europa.eu/en/press/press-releases/2026/10/21/digital-rulebook-council-agrees-position-to-simplify-data-protection-privacy-and-cyber-reporting-rules/ (Accessed: 15 November 2026).


Court of Justice of the European Union (2016) Patrick Breyer v Bundesrepublik Deutschland, Case C-582/14, judgment of 19 October 2016, ECLI:EU:C:2016:779. Available at: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62014CJ0582 (Accessed: 15 November 2026).


Court of Justice of the European Union (2023a) UI v Österreichische Post AG, Case C-300/21, judgment of 4 May 2023, ECLI:EU:C:2023:370. Available at: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62021CJ0300 (Accessed: 15 November 2026).


Court of Justice of the European Union (2023b) VB v Natsionalna agentsia za prihodite, Case C-340/21, judgment of 14 December 2023, ECLI:EU:C:2023:986. Available at: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62021CJ0340 (Accessed: 15 November 2026).


Data (Use and Access) Act 2025 (2025) 19 June 2025, 2025 c. 18. Available at: https://www.legislation.gov.uk/ukpga/2025/18/contents (Accessed: 15 November 2026).


Department for Digital, Culture, Media and Sport (2026) ‘Information Commission succeeds the ICO as UK’s data protection regulator’ [online]. 30 September 2026. Available at: https://www.gov.uk/government/news/information-commission-succeeds-the-ico-as-uks-data-protection-regulator (Accessed: 15 November 2026).


Directive 95/46/EC (1995) Directive of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data. Official Journal of the European Communities, L 281, 23 November 1995, pp. 31–50. Available at: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:31995L0046 (Accessed: 15 November 2026).


European Data Protection Board (2019) Guidelines 3/2018 on the territorial scope of the GDPR (Article 3). Version 2.1, adopted 12 November 2019, with formatting revisions dated 7 January 2020. Available at: https://www.edpb.europa.eu/system/files/documents/files/file1/edpb_guidelines_3_2018_territorial_scope_after_public_consultation_en_1.pdf (Accessed: 15 November 2026).


European Data Protection Board (2023) Guidelines 9/2022 on personal data breach notification under GDPR. Version 2.0, adopted 28 March 2023. Available at: https://www.edpb.europa.eu/system/files/documents/2023-04/edpb_guidelines_202209_personal_data_breach_notification_v2.0_en.pdf (Accessed: 15 November 2026).


European Data Protection Board and European Data Protection Supervisor (2026) Joint Opinion 2/2026 on the Proposal for a Regulation as regards the simplification of the digital legislative framework (Digital Omnibus). Adopted 10 February 2026. Available at: https://www.edpb.europa.eu/system/files/documents/2026-02/edpb_edps_jointopinion_202602_digitalomnibus_en.pdf (Accessed: 15 November 2026).


Information Commission’s Office (n.d.-a) ‘Personal data breaches: a guide’ [online]. Available at: https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/ (Accessed: 15 November 2026).


Information Commission’s Office (n.d.-b) ‘Who does the UK GDPR apply to?’ [online]. Available at: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/personal-information-what-is-it/who-does-the-uk-gdpr-apply-to/ (Accessed: 15 November 2026).


Organization for Transformative Works (2026a) ‘AO3 celebrates 11 million registered users’ [online]. 19 June 2026. Available at: https://www.transformativeworks.org/ao3-celebrates-11-million-registered-users/ (Accessed: 15 November 2026).


Organization for Transformative Works (2026b) ‘AO3 down for maintenance’ [online]. Official incident record, 29 October–15 November 2026. Available at: https://otwstatus.statuspage.io/incidents/g12jnxck9g6h (Accessed: 15 November 2026).


Regulation (EU) 2016/679 (2016) Regulation of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). Official Journal of the European Union, L 119, 4 May 2016, pp. 1–88. Available at: https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng (Accessed: 15 November 2026).


United Kingdom General Data Protection Regulation (UK GDPR) (2016) Regulation (EU) 2016/679, as incorporated into and amended under United Kingdom domestic law. Consolidated version as at 30 September 2026. Available at: https://www.legislation.gov.uk/eur/2016/679/body/2026-09-30 (Accessed: 15 November 2026).

bottom of page