A locked neutral document envelope beside a secured archive box on a dark desk
UKICOdata protectionprivacyincident response

ICO Data Breach: A UK Therapy-Practice Incident Evidence Record

Photo of Dr. Sofia Reyes
Dr. Sofia Reyes Clinical Documentation & Compliance Editor 10 min read
Outline

The printable pack adds an ICO fee outcome and renewal record, a breach risk and reporting worksheet, and a client notification decision sheet alongside this incident log.

Record your ICO breach response

Use the sheets this week to capture the fee check, breach evidence, risk decision, and client-notification plan.

  • ICO fee outcome and renewal record for the controller, checker result, tier, payment route, and evidence
  • Personal data breach incident log for discovery, awareness, containment, affected data, risk, and follow-up
  • Risk and reporting worksheet for the ICO 72-hour clock and separate notification decision
  • Client notification decision sheet with high-risk assessment and safe communication fields

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

An ICO data breach is a security failure involving personal data, including accidental disclosure, loss, alteration, destruction, or unauthorized access. A note attachment sent to the wrong recipient can qualify even when nobody intended harm. Start by protecting the people involved and preserving a reliable account of what happened.

This is an educational record template for a UK private practice. It is not legal, regulatory, insurance, or clinical advice. The ICO pages used here were checked in November 2026. The ICO marks its 72-hour small-organization guidance as under review after changes made by the Data (Use and Access) Act, so confirm the current position with the ICO and qualified privacy advice.

For the broader UK privacy workflow around lawful basis, privacy notices, access requests, and AI vendors, see GDPR for therapists in the UK.

Contain without creating a second disclosure

Name one incident lead and one secure place for the log. Keep the log out of the client chart unless your records policy and qualified advice require a cross-reference. Use the minimum information needed to coordinate the response.

First actionRecord in the logDo not do
Stop the access or transmissionTime, person, system, and control usedForward the exposed material to make the issue easier to explain
Ask the recipient or processor to delete or return it securelyRequest, response, and evidence receivedAdd a real recording, transcript, or full session note
Preserve access and message evidenceExport or reference, owner, and storage locationChange logs or overwrite the original evidence
Assign a human reviewerName, role, time assigned, and conflict checkLet an automated workflow decide reportability

Treat containment as a privacy action. If a file went to the wrong person, contact that person through a safe channel and ask for deletion or secure return. If a processor is involved, preserve the processor’s notice, access records, and response. Do not assume that a sent message was opened, and do not assume that a deletion request proves there was no copy. These first actions create the evidence base for the ICO data breach decision.

Once the immediate path is contained, you can see how Emosapien works for the separate job of keeping reviewed session-note drafts organized. Emosapien does not investigate, contain, notify, or decide an ICO data breach.

Record notes, recordings, and extracts without copying them

A therapy incident log needs enough detail to support a decision, not enough detail to become a second disclosure. Describe the data category and sensitivity. Do not paste the client’s words, upload the exposed chart, or attach the raw recording to a demonstration.

BranchMinimal fact descriptionScope questions
Note attachment to wrong recipientDraft or signed note attachment, recipient relationship, delivery channelWas it opened, downloaded, forwarded, or deleted?
Recording or transcript exposedSession recording or transcript, system, access path, time windowWho could access it, and do logs show access or export?
Supervisor extract misdirectedExtract containing selected documentation fields, intended supervisor, actual recipientDid the extract include direct identifiers or sensitive content?

For each branch, distinguish the awareness time from the discovery time. The incident may have happened earlier than you know. Write the times with a time zone, name the source of each fact, and mark estimates as estimates.

When session documentation comes up, see how notes are drafted and reviewed without treating a reviewed note as an incident record. A clinician reviews and signs every Emosapien note. That workflow does not change your UK GDPR duties, your incident log, or your notification decision.

Preserve the timeline and the unknowns

A clean timeline lets another qualified reviewer see what was known at each decision point. Keep unknowns visible rather than filling them with a guess.

Time or stateWhat to writeEvidence owner
Incident occurredKnown or estimated event time and source[name or system owner]
Practice became awareExact awareness time and person[incident lead]
First containmentAction, result, and remaining exposure[action owner]
Scope checkedSystems, recipients, records, and logs checked[reviewer]
Decision madeRisk conclusion, advice, and notification reason[named human reviewer]
New fact foundFact, time found, and whether the decision changes[follow-up owner]

The ICO says you should keep a record of personal data breaches whether or not you notify the regulator. Your record should show the facts available, the likely risk to individuals, and why you did or did not notify. The record is part of accountability, not a place to make the incident look smaller.

Assess harm and reportability with a named human reviewer

The question is not whether the practice feels embarrassed. Assess the likely adverse consequences for the individuals whose data was involved and the likelihood of those consequences. Therapy material may carry high sensitivity because it can reveal health information, trauma history, relationship details, safeguarding concerns, or other confidential material. A defensible ICO data breach assessment names the evidence behind both severity and likelihood.

Assessment questionEvidence to collectDecision note
What data was involved?Category, sensitivity, identifiers, and volumeState what is confirmed and what remains unknown
Who could receive or access it?Recipient role, access window, logs, and onward sharingRecord whether access is confirmed or only possible
What could happen to the person?Distress, loss of confidentiality, discrimination, safety, or other harmExplain severity and plausible pathway
How likely is the harm?Recipient response, safeguards, exposure duration, and recoveryExplain why likelihood is low, medium, or high if you use labels
What advice was sought?Privacy counsel, data protection adviser, insurer, or professional bodyName the advice source, date, and unanswered question

Do not let an AI tool determine reportability. A named clinician, practice owner, data protection lead, or qualified adviser should review the case and sign the decision. If you cannot resolve a legal or regulatory question, write “confirm with the ICO” or “confirm with qualified UK privacy counsel” and keep the question in the follow-up list.

Separate ICO notification from affected-person notification

These are different decisions. The ICO guide says notification to the regulator is required when the breach is likely to result in a risk to individuals’ rights and freedoms. If the breach is likely to result in a high risk, affected individuals must be informed without undue delay. Document each decision separately.

DecisionWhat your record should showIf you notify
ICO notificationRisk conclusion, awareness time, reasons, and information still missingNotification time, reference, information supplied, and follow-up plan
Affected-person notificationHigh-risk assessment, protective advice, and communication ownerClear description, likely consequences, protective steps, and contact route
Neither notificationWhy the breach is unlikely to create the relevant riskEvidence retained and review trigger if new facts appear

The ICO says you should report within 72 hours of becoming aware where notification is required and feasible, even if all details are not yet available. Record the missing information and send follow-up information when it is available. Because the ICO says its small-organization guidance is under review, confirm the current process and deadline before relying on this summary. Do not let uncertainty about scope erase the ICO data breach timeline.

Preserve processor evidence and corrective action

If a vendor, transcription service, hosting provider, or other processor is involved, write down when it learned of the breach, what it checked, who owned the next action, and what evidence it supplied. Do not treat a vendor’s assurance as a completed investigation.

Processor evidenceOwnerFollow-up proof
Incident notice and awareness timePractice incident leadOriginal notice and acknowledgment
Systems, accounts, and access window checkedProcessor contactAccess or export log reference
Containment action and resultNamed action ownerDeletion, revocation, or recovery evidence
Scope still unknownJoint reviewerDate for the next evidence check
Corrective actionPractice ownerCompleted change and review date

After the decision, preserve the reason and the corrective action. A changed sharing setting, revised recipient check, access review, staff coaching, or processor escalation should have an owner and a completion date. Do not describe a planned action as complete.

If your England practice handles NHS patient data, accesses NHS systems, or has a relevant NHS contract, check the separate NHS DSPT scope and incident-readiness evidence map; completing an incident log is not DSPT publication or an ICO notification.

What to keep out of the incident log

Keep the record useful and safe. Do not include a full chart, a session transcript, raw audio, a copied email chain with unrelated clinical content, passwords, or speculative diagnoses. Do not circulate the log to the whole practice. Limit access to the people who need it for containment, advice, decision-making, or required follow-up.

A short, factual record is easier to review than a long narrative. Put sensitive evidence in its approved restricted location and reference it by controlled identifier. If the incident concerns a client safety risk, follow your safeguarding and clinical escalation procedures as well as the privacy response.

For the wider record-keeping workflow that sits alongside this incident log, see the UK therapy documentation guide.

For a separate US framework, see the HIPAA breach notification response path. It does not replace UK GDPR or ICO guidance, but it shows why notification, evidence preservation, and affected-person communication should be recorded as separate decisions.

After the incident, review the record as a system

Use the completed log to ask what failed and what will change. A corrective action should reduce recurrence without adding a new disclosure path. Test the change, record the result, and set a review date.

Review areaQuestion for the practiceProof to retain
Recipient controlsCan staff check the recipient before sending?Updated workflow and test result
Recording and transcript accessAre raw materials restricted to a real need?Role review and access evidence
Supervisor extractsDoes the extract contain only the fields needed?Revised template and sample test with fictional data
Processor responseDo contracts and contacts support rapid escalation?Current contact and processor record
Human reviewIs a named person accountable for the decision?Role assignment and review log

Reviewed notes are not an incident-response service

An incident record helps you contain a disclosure, assess risk, document a decision, and preserve follow-up evidence. Emosapien is a separate workspace for AI-drafted therapy notes that the clinician reviews and signs. It is not an EHR, practice-management system, breach-response service, cyber-insurance product, or regulator portal. It does not make a practice compliant with UK GDPR or ICO requirements.

Evaluate reviewed session-note drafts after the incident is contained

When containment is complete, keep documentation moving with clinician-reviewed session-note drafts in a separate workflow.

Review note drafts
  • Free plan
  • No credit card
Note review workspace
Fictional clinician · Post-incident

Session detail

The clinician reviews and signs the draft before it is used.

Draft for review

Session note draft ready for clinician review and sign-off.

Ask about note drafts… →

References

Free PDF: ICO Fee Record and Data Breach Log for UK Therapy Practices

A printable practice pack for recording the ICO fee decision, responding to a personal data breach, and deciding whether affected clients need notification.

  • ICO fee outcome and renewal record for the controller, checker result, tier, payment route, and evidence
  • Personal data breach incident log for discovery, awareness, containment, affected data, risk, and follow-up
  • Risk and reporting worksheet for the ICO 72-hour clock and separate notification decision
  • Client notification decision sheet with high-risk assessment and safe communication fields

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

Ready to transform your practice?

Join 10,000+ therapists using Emosapien.