By profession
AI for freelancers
In short
- When you work on a client’s data, you are often their processor under the GDPR: you act on their instructions.
- Having that data processed by an AI service can amount to adding a sub-processor, which requires the client’s written authorisation.
- Your contracts and non-disclosure agreements come on top of the law: reread them before using a tool.
Developer, consultant, translator, designer, assistant: a freelancer often works on what clients entrust to them. Generative AI can speed that work up. But the data and documents remain the client’s, and your contract often says what you may do with them. Three situations to find your way.
A useful precaution before each new assignment: put a few lines about AI tools in your contract, which ones you use and what for. You will know what is allowed, and so will your client.
The rules that apply
-
The processor processes personal data only on documented instructions from the controller, and does not engage another processor without the controller’s prior written authorisation, specific or general.
-
CNIL, controller and processor: 6 good practices
An organisation that processes personal data on behalf of a controller is its processor. The two must sign a contract with the terms of article 28, and the instructions must be set down in writing.
-
Code de commerce (Commercial Code), article L151-5 (trade secrets)
Using or disclosing a client’s trade secret in breach of an obligation not to disclose it, for example a non-disclosure agreement, is unlawful.
-
ANSSI (France’s national cybersecurity agency), recommendation R34
Among the data not to send to consumer AI services, the ANSSI lists IT secrets, such as passwords or access keys to services.
Three everyday situations
Developer: debugging a client’s code
A function crashes at a client’s. You paste the file into an AI assistant, with its configuration file and an extract of the database.
What is the problem
The configuration often contains passwords or access keys, and the database extract personal data about your client’s customers. The code itself may be confidential under your contract.
The right move
Isolate the problem in a small example, with made-up data and no keys at all. Check your contract: some clients forbid or restrict the use of AI tools. If a key was sent by mistake, have it changed.
Consultant or translator: a confidential document
A client gives you a strategy report to translate or summarise, under a non-disclosure agreement.
What is the problem
The agreement forbids you to disclose the document. Submitting it to an AI service means handing it to a third party the client did not choose.
The right move
Ask the client, in writing, whether they accept the use of an AI tool, and which one. Without agreement, work without the tool, or submit only generic passages, with no names, figures or strategic elements.
Freelance assistant: a client’s customer file
For a tradesman, you handle invoice reminders. You want an AI to write personalised reminders from his customer file.
What is the problem
You process this data on the tradesman’s behalf: you are his processor. Having the file processed by an AI service can amount to engaging another processor, which article 28 makes subject to his prior written authorisation.
The right move
Have a reminder template written with fields to fill in, then merge it with the file yourself, in your spreadsheet or software.
What you can still do without special precautions
- Writing your own website, your proposals and your quote templates.
- Learning a technique, a language or a tool with made-up examples.
- Preparing a model contract or clause, to be checked by a professional.
- Organising your schedule and project tracking, without client data.
Try it with a document from this profession
The demo shows, on a fictional document from this profession, what would be sent to the AI, its pseudonymised version, then two answers side by side. The documents are in French. Open the demo.
Key points
- On a client’s data, you act on their instructions.
- Adding an AI tool to the processing may require the client’s written authorisation.
- Never a password or an access key in a request.
- Reread your contracts: they may restrict the use of AI tools.
Sources
- CNIL, Règlement européen sur la protection des données, chapitre 4 (article 28) (in French), consulted .
- CNIL, Responsable de traitement et sous-traitant : 6 bonnes pratiques pour respecter les données personnelles (8 July 2020) (in French), consulted .
- Légifrance, Code de commerce, titre V, de la protection du secret des affaires (articles L151-1 to L154-1) (in French), consulted .
- ANSSI, Recommandations de sécurité pour un système d’IA générative (ANSSI-PA-102, recommendation R34) (in French), consulted .
This page is for information only. It is not legal advice and does not replace a professional’s view of your situation. Rules change: each source is dated with the day it was consulted.