Skip to content
Floskool

Chapter 1 · The checklist

What your chatbot must not ask for or keep

Free lesson 9 minGroup Flopia

Follow this course in your space: your progress is saved, and the community answers your questions.

Follow for free

The best way to protect a piece of data is never to have it. That's the GDPR principle of data minimization: only collect what's necessary for what you do. For a chatbot, it comes down to two settings: what it asks for, and what it keeps.

What it can ask for: the bare minimum

Ask yourself one question for each piece of information: do I need this to answer or call back? If the answer is "it would be handy," that's a no.

BusinessEnough for a requestToo much
PlumberFirst name, phone, town, type of problemFull address before the callback, date of birth
Hair stylistFirst name, phone or email, desired serviceAge, photo of their face
Vacation rentalFirst name, email, dates, number of guestsID number, credit card
Physical therapist, osteopathFirst name, phone, preferred timeDetailed medical reason, doctor's name, social security number
CoachFirst name, email, goal in one sentenceWeight, medical history
Auto shopFirst name, phone, make and modelLicense plate and registration number before the quote

And contact details last: first understand the request (3 to 5 questions are enough, ideally with buttons rather than free text), and only then ask for a first name and a way to call back. A request understood before it's identified means less unnecessary data.

What it must never ask for

Spell it out in its instructions:

FORBIDDEN DATA
You NEVER ask for:
- a credit card number, PIN, IBAN or bank account details;
- a password or a code received by text message;
- a social security number or ID document;
- health information, beyond what the person chooses to say to
  explain their request (and you don't follow up on it);
- information about religion, political opinions, sexual orientation,
  ethnic origin or criminal record.
For a payment, you point to [planned payment method: secure payment
link, payment on site...].

Credit cards are a no, no exceptions. A chat window isn't a payment terminal. If your business requires a deposit, it goes through a real payment tool, never through a message.

When the person shares too much

You don't control what people type. A customer may describe their surgery, another may paste their card number "to speed things up." That's the case the CNIL has in mind when it talks about sensitive data typed in freely: measures must be in place to limit the risks. Three simple measures:

  1. Warn beforehand: the privacy line (lesson 2) asks people not to share health or banking information.
  2. React in the moment: the chatbot never follows up on sensitive data, and politely reminds the person it isn't needed.
If the person shares sensitive information (health, banking,
identity), you don't repeat it, you don't ask questions about it,
and you reply: "Thanks, but there's no need to share that kind of
information here. For your request, I only need [useful data]."
  1. Clean up afterward: ask your provider whether there's automatic masking of card numbers, or a way to delete a conversation manually. If so, delete the conversation in question.

What it must not keep: the retention period

The CNIL advises keeping data for as long as the purpose requires. When nothing justifies keeping a conversation, it can be deleted at the end of the conversation. Keeping it longer is justified if there's a specific purpose, for example handling a complaint.

Set your period in three steps:

  1. Why would you keep a conversation? To call the person back, to find what they asked for in case of a dispute, to improve the chatbot's answers? Write down your reasons.
  2. How long does each reason really last? A callback often happens within a few days; a complaint may come later, after the service. Pick the shortest period that covers your real reasons.
  3. Can the tool do it? Ask your provider whether automatic deletion after a set period exists (lesson 4).

Then disclose that period: in the privacy line and in your privacy policy. The CNIL asks that people be informed of the retention period.

Watch the difference between the conversation and the customer record. If the person becomes a customer, their contact details go into your customer file, with your usual retention period. The raw conversation doesn't need to follow.

Example: the wedding photographer

Before: the chatbot asked for both partners' names, the date, the venue, the budget, the email addresses, the phone numbers and the number of guests, starting with the second message. Conversations were kept indefinitely. After: three button questions (type of shoot, month, region), then a first name and an email. Conversations are deleted after a short period set with the provider, and the period is disclosed under the input box.

Your turn

  1. Fill in the table for your business: what's enough, what's too much.
  2. Paste the "FORBIDDEN DATA" block into your chatbot's instructions, with your payment method.
  3. Write down your reasons for keeping a conversation and the period that covers them.
  4. Note that period: you'll carry it over to the privacy line and the policy from lesson 2.