What must not go in

Some things have no place in a conversation, however secure the tool. A password, an access key to a service, a two-factor authentication code or a recovery code are secrets. Writing them in a request copies them to a place where they do not belong.

Both the revised FADP and the GDPR require processing only the data needed for the purpose pursued. Applied to working with an assistant, this becomes a simple habit: before uploading a document, ask yourself what the task really needs.

• To correct the style of a letter, the recipient’s name is not needed.
• To analyse trends, aggregated data is often enough.
• To prepare a template reply, an anonymised real case works just as well.
• To summarise a file, attach the relevant documents rather than the whole file.

Learnya can help you prepare a document before you share it more widely. It replaces names, addresses and numbers with neutral placeholders, and you keep the mapping on your side. Always review the result: a contextual detail is sometimes enough to identify a person.