A data breach at the firm: managing the first 72 hours
When to notify the AEPD of a data breach, how to count the 72 hours and what to record if the firm does not notify or must contact affected people.

An email containing documents sent to the wrong recipient can be a personal data breach even if no attacker has entered the firm's systems. Losing a device, altering case records or losing access to personal data after an incident may also qualify. The first decision is not to issue a public explanation or wait for the final technical report. It is to establish what happened, whether personal data are involved and who must assess risk and activate any required communications.
This guide organises a Spanish firm's internal response under articles 33 and 34 of the General Data Protection Regulation (GDPR) and the Spanish Data Protection Agency's guidance. It does not treat every incident as notifiable or confuse notification to the authority with communication to affected people. Record templates and allocations of work are organisational recommendations; legal duties are identified by their source. Explanations of Spanish source material are the publication's own translations.
First distinguish an incident from a personal data breach
The AEPD defines a breach as an incident causing accidental or unlawful destruction, loss or alteration of personal data, or unauthorised disclosure or access. It is not limited to a public leak: losing or altering data matters too. A technical fault with no effect on personal data does not, by itself, activate articles 33 and 34, although other technical or contractual action may still be needed.
For the firm, a useful first step is a record separating confirmed facts from hypotheses. Record the affected system, the documents it held, when the incident was detected and which checks remain open. For a suspected misdirected email, establish who actually received it, which attachments it contained and whether there is evidence of access. Asking the recipient to delete it can reduce risk, but does not replace assessment or establish automatically that a breach never occurred.
Controllers and processors have different duties
Article 33(1) assigns notification to the competent supervisory authority to the controller. Under paragraph 2, a processor must tell the controller without undue delay after becoming aware of a breach. The GDPR does not give a processor its own 72-hour period in which to wait before reporting it. The AEPD guide explains that a processor should not delay this report to conduct the risk assessment that belongs to the controller.
The firm must identify its role in the affected processing rather than assume it always has the same one. Where a provider processes data on the firm's behalf, activate the agreed contact and gather the provider's information. Where the firm acts as a processor for another controller, the reporting route differs. The technology provider's identity alone does not determine who is the controller: the actual relationship and purpose of processing need examination.
When the 72 hours begin
Article 33 requires notification without undue delay and, where feasible, no later than 72 hours after awareness, unless the breach is unlikely to result in a risk to individuals' rights and freedoms. The AEPD clarifies that weekends and public holidays count. This is not a period of three working days and does not start when a committee meets on Monday.
As a record-keeping recommendation, retain both the time the alert was detected and the point at which the organisation had awareness that personal data were affected, together with the reasons supporting that assessment. This chronology helps explain the calculation without reconstructing it from memory. Where notification occurs after 72 hours, article 33 requires reasons for the delay. Changing the date on which an internal incident file was opened cannot correct late notification.
When the authority must be notified
The article 33 exception does not depend on whether the firm considers the incident important for its reputation. The criterion is risk to people's rights and freedoms. Assess which data were involved, the consequences that could follow and the measures reducing those consequences. Health information, family circumstances or financial details in a case file may call for a different analysis from a list of professional contact details.
The AEPD offers ASESORA BRECHA to support this decision. Using it does not transfer responsibility for deciding and documenting. The guidance must be applied to the actual case: neither all email errors nor every lost device can be assigned the same answer in advance. For cross-border processing, the competent authority must also be established. This guide does not assign every incident involving an organisation with a Spanish client to the AEPD.
The minimum content of a notification
Article 33(3) requires a description of the breach's nature and, where possible, the categories and approximate number of affected people and personal data records. It also requires contact details for the data protection officer or another information point, the likely consequences and the measures taken or proposed to address the breach, including measures to mitigate adverse effects. Saying merely that there was an IT problem does not describe its known scope.
Where all the information cannot be supplied together, paragraph 4 permits it to be provided in phases without undue further delay. The firm should therefore not wait for a completed forensic report before considering the initial notification that is required. The AEPD states that notifications must be submitted electronically through its specific form. An internal document containing facts, categories and measures supports preparation, but is not a substitute for submission through the indicated route or for the resulting receipt.
Telling affected people is a separate decision
Article 34 requires communication to the individual without undue delay where the breach is likely to result in a high risk to rights and freedoms. The communication must use clear and plain language and describe the breach, a contact point, likely consequences and measures. That article does not create a separate 72-hour period allowing the firm deliberately to wait until the end after communication has become necessary.
Specific exceptions apply: appropriate measures applied to the affected data rendering them unintelligible to unauthorised people, such as encryption; subsequent measures ensuring the high risk is no longer likely to materialise; or disproportionate effort, in which case a public or similarly effective communication is required instead. These are not general exemptions from notifying the authority. The authority can require communication to individuals or determine that one of these conditions is met.
What to retain even if no notification is made
Article 33(5) requires documentation of every personal data breach, including its facts, effects and remedial action. This includes breaches found not to require notification. As a management practice, retain the risk assessment, the decision-maker, the information available and the reasons, alongside technical evidence and receipts for communications that were made.
Closing the incident should identify which control failed and who will correct it. The firm's approval matrix can help allocate responsibility. Subsequent storage can follow the matter-closing checklist, without confusing incident records with client marketing messages. The matter-opening checklist helps establish from the outset who needs access to documents and for which purpose.
Dates and sources
GDPR articles 33 and 34, read directly in the Official Journal PDF; AEPD notification page, modified 14 September 2026; and its June 2021 breach notification guide. Consulted 17 November 2026. The current page and legislation support the rules; statistics from news bulletins are not used as proof of a legal duty.