4.3Everyday best practices (emails, client files)
The essentials in 30 seconds
- Grouped external sends = Bcc: never addresses in the clear in To or Cc.
- Less, narrower, shorter: collect less, share to real need, purge the expired.
- Send errors are reported: hiding them makes everything worse — see 4.4.
Running mini-case — Karim adopts the 4 habits of the week
After his well-forwarded erasure request, Karim decides to move into prevention: his next group email to twenty external clients goes in Bcc, he deletes the useless 'date of birth' column from his file, he restricts sharing of his HR table to the two people concerned, and he flags an old applications folder for purging. Four habits, one week: the regulation has become a routine.
Sequel to case 4.1-4.2 — Karim moves from reaction to everyday prevention.
1. The regulation plays out daily
Data protection is not just a DPO matter: it plays out in the daily habits of everyone handling client or HR data. Karim confirms it: 80% of his compliance rests on four weekly reflexes, not complex procedures.
2. Bcc and minimisation
Sending to several external recipients → Bcc (blind carbon copy) (never To or Cc, otherwise addresses leak in the clear: a common and avoidable breach). Karim checks the field before sending, not after.
Minimisation: collect and keep only what is necessary — the 'just in case' file is the anti-model. Karim's 'date of birth' column, never used, disappears from the file.
3. Authorisation and purge
Least access: everyone only accesses the data they need. Sharing an HR file 'with the whole organisation' is a breach in waiting — Karim restricts it to the two people concerned.
Every data item has a retention period: purging is part of the job (old applications, old contacts). And a send error to the wrong recipient is reported (see 4.4): hiding it makes everything worse.
The missed Bcc (a real office scene)
Moral: Bcc, right file, purge — 15 seconds that avoid a week of damage.
🔎 Concrete example — 🔎 Concrete example — The 4 habits of the week
Karim's week, dated and verifiable habits:
Monday — Bcc: email to 20 external clients, Bcc field checked before sending
Tuesday — minimisation: 'date of birth' column removed from the file
Thursday — authorisation: HR table restricted to 2 people instead of 'everyone'
Friday — purge: folder of expired applications flagged to the manager
→ 4 habits, zero new tools, compliance become routineReading: from concept to weekly practice, with no budget.
Lesson: 'the whole organisation' is almost never the right sharing.
Section vocabulary
- Minimisation
- Collect and keep only what is necessary: the 'just in case' file is the anti-model.
Simple example: Karim deletes the never-used 'date of birth' column from his client file.
What it is not: storing all possible data 'for later, you never know'.
Reflex: with each new field: do I really need it?
- Bcc (blind carbon copy)
- Grouped sending to external recipients goes in Bcc: the list of addresses in the clear is a common breach.
Simple example: Karim sends to twenty external clients in Bcc, field checked before clicking.
What it is not: putting external recipients in To or Cc to 'keep it simple'.
Reflex: re-read the recipient field before each grouped send.
- Authorisation
- Everyone only accesses the data they need: sharing an HR file 'with the whole organisation' is a breach in waiting.
Simple example: Karim restricts his HR table to the two people concerned.
What it is not: sharing by default with the whole team to avoid managing access.
Reflex: review the sharing of a sensitive file each quarter.
- Retention period
- Every data item has an expiry date: purging is part of the job.
Simple example: Karim flags the old applications folder for purging instead of keeping it 'just in case'.
What it is not: keeping a pool of rejected CVs indefinitely.
Reflex: date your folders to know when to purge.
- Send error
- The wrong recipient for a personal data file = a breach to handle (see 4.4), not a simple blunder.
Simple example: If Karim sends to the wrong recipient, he reports instead of staying silent.
What it is not: deleting the sent message and hoping nobody saw it.
Reflex: check attachment + recipient before, report after.
In practice — In practice — The 4 habits of the week
- Bcc habit: your next group email to external recipients goes in Bcc — check before sending.
- Minimisation habit: on your next form/file, delete one non-essential field (the 'just in case' date of birth).
- Authorisation habit: check the sharing of ONE file holding personal data — who really has access? Restrict it.
- Purge habit: identify one expired folder (old applications, old contacts) and trigger its deletion (or flag it to the manager).
Ready-to-say script — check before sending (15 s)
'Recipients: external recipients in Bcc, checked. Attachment: it is the right file, with no unnecessary data. Sharing: only the people concerned. Sending.'
Say quietly to yourself before each grouped send; if in doubt, do not send, ask.
Copy-paste template — pre-send checklist for grouped mail
RECIPIENTS (external in Bcc?): _______________
ATTACHMENT (right file? data minimised?): _______________
SHARING (least access?): _______________
RETENTION (folder to purge flagged?): _______________
IF ERROR (report to DPO / IT, see 4.4): _______________Urgent email under pressure
Slow down precisely when it is urgent: 15 seconds of checklist avoid the costliest breach.
Large client file
Prefer a shared link set to real need over an attachment: the link can be revoked, a sent email cannot.
Working in open-plan office
Lock the session before standing up and angle the screen: authorisation also applies to glances.
Inherited old file
Never reuse an old 'just in case' file without first checking content, sharing and age.
✓ Best practices
- Grouped external sends in Bcc.
- Less, narrower, shorter.
- Expired data purged or flagged.
✗ Common pitfalls
- External recipients in To/Cc (address leak).
- Wild client spreadsheets.
- Sharing 'with the whole organisation'.
Key takeaways
- Grouped external sends = Bcc, systematically.
- Collect less, keep for less time, share more narrowly: the core of everyday compliance.
- File sharing is set to real need: 'the whole organisation' is almost never the right setting.
- A send error to the wrong recipient is reported (4.4) — hiding it makes everything worse.
48h challenge — apply tomorrow
Do the 4 habits: 1 checked Bcc send, 1 useless field deleted, 1 sharing restricted, 1 expired folder flagged.
- I can explain Bcc, minimisation and authorisation.
- I know why a send error is reported.
- I have done the 4 habits this week.
Frequently asked questions
Can I keep rejected candidates' CVs 'for later'?
Only for a limited time after the last contact, with the candidate informed — beyond that, purge or explicit consent. The unlimited pool is a classic non-compliance: check the applicable period with your contact.
Can I send a client file to a contractor?
Only within a defined framework: contract with data protection clauses, secure transfer, minimisation. If in doubt, the DPO validates — never a 'quick favour' send.
Karim writes to twenty external clients. What is the right move?