DRHUGGER JOURNAL · HUMAN CONNECTION

A short session check-in without unnecessary personal information

Distinguishing practical clarification from intrusive questions, and useful communication from an unnecessary record.

A fountain pen and an open notebook
Illustrative stock photo: Aaron Burden / Unsplash

Session check-in privacy: purpose, not a long form

An opening check-in can be a short conversation about what is proposed and what has not been agreed. It need not become an account of someone’s life. In a nontherapeutic role, the useful question is not ‘What else could I learn?’ but ‘What information is actually needed for the very next practical decision?’

ICO guidance on data minimisation connects collection to a defined purpose. This is a useful reference when designing questions, not certification of DrHugger’s compliance or an interpretation of Greek law. The suggestions below do not describe an installed records system.

Ask about a preference, not a diagnosis

Practical questions include ‘Is there anything you do not want today?’, ‘How will you ask for a pause?’ and ‘Is anything unclear before we decide whether to proceed?’ Do not present these questions as a suitability test or a complete safety assessment. If a clear framework cannot be agreed, the particular activity should not proceed.

A hypothetical example: someone asks for a particular area not to be touched. Respecting that boundary does not require asking for medical history, previous experiences or other people’s names. You can repeat the boundary to confirm it. If continuing would require information beyond your competence, do not improvise a clinical assessment.

Spoken clarification does not mean automatic recording

Something being said does not automatically mean it should be copied into a notebook, message or spreadsheet. Before any record is created, there needs to be a defined purpose and a clear process for informing the person, controlling access, storing information and deciding retention. Do not invent your own deletion periods or rules that have not been approved.

Avoid labels such as ‘difficult client’ or guesses about personality. Do not move conversations into colleagues’ personal chats or upload notes to artificial intelligence tools for summarising. If a complaint or incident arises, follow the operator’s specific procedure; minimising information is not an instruction to conceal or destroy necessary evidence.

Complete the communication loop

Before beginning, summarise what has been agreed in straightforward language and invite correction if you misunderstood anything. The other person does not need to repeat their whole story. A check-in remains open: an initial preference can change, and a conversation at the beginning does not give permanent permission for everything that follows.

If you are considering the practitioner pathway, ask which questions and tools are actually used before handling other people’s information. Read the code of conduct and the complaints and incident pathway. A minimal check-in does not promise absolute privacy; it limits what you ask for and requires you to understand what happens to that information.

Sources and further reading

ICO: Principle (c), data minimisation