Regelgeving

    AI and privacy: how to use customer data safely under the GDPR

    Tergem team

    Published

    Updated

    3 min read

    Yes, you may process customer data with AI, as long as you follow the GDPR. AI does not change the basic rules; it only makes them more important because AI systems can process a lot of data simultaneously. With these seven rules, you're on the right track.

    This article is general information and not legal advice.

    For every processing, you need a reason recognized by the GDPR. For most SME applications, that is the performance of a contract (your customer wants an appointment) or a legitimate interest (you want to follow up on requests properly). For marketing, you often need consent.

    2. Do not use more data than necessary

    Only link the systems and fields necessary for the purpose. A daily turnover briefing does not need BSNs (Citizen Service Numbers) or medical data. Less data means less risk.

    3. Sign a data processing agreement with every supplier

    Every party that processes personal data for you (the AI supplier, the hosting party, the voice service) is a processor. You need a data processing agreement (DPA) with each of them. A good AI partner provides this as standard and specifies which sub-processors they use.

    4. Pay attention to where the data is located

    Storage and processing in the EU is the simplest. If a supplier is in the US, check if they fall under the EU-US Data Privacy Framework or have signed standard contractual clauses.

    5. Agree on retention periods

    Do not keep recordings, transcriptions, and chat conversations longer than necessary. Common practice is:

    DataExample retention period
    Call recordings30 – 90 days
    Summaries and notesAs long as the customer relationship lasts
    Invoices and administration7 years (fiscal retention obligation)

    6. Secure it well

    Encrypted connections, two-step verification, access only for those who need it, and a logbook of who views what. Ask your supplier how this is organized.

    7. Be transparent in your privacy statement

    Mention that you use AI, for what purpose, which data, and who your processors are. If you use an AI receptionist or chatbot, it must also state at the beginning of the conversation that it is an AI, according to the EU AI Act. See The EU AI Act for SMEs.

    When do you need a DPIA?

    A DPIA (data protection impact assessment) is mandatory if a processing is likely to result in a high risk for individuals. Think of processing health data on a large scale, systematic tracking of people, or combining many data sources about individuals. The Data Protection Authority publishes a list of processing operations for which a DPIA is mandatory. If you work in healthcare, also read AI in healthcare practice.

    How a good AIOS builds in privacy

    An AI Operating System brings data together, so privacy should be in the design: only linking the sources that are necessary, excluding sensitive fields, storage in the EU, roles and rights per employee, and fixed retention periods. At Tergem, your AIOS runs on your own accounts, so the data remains yours. Ask your privacy question in a non-binding conversation.

    Frequently asked questions

    Preferably not in a free or personal account. Use a business version with a data processing agreement, and only put in data that is necessary for the task.

    Not necessarily, but transfer outside the EU requires safeguards, such as the EU-US Data Privacy Framework or standard contractual clauses. Storage in the EU is the simplest route.

    That depends on the scale and the type of data. For sensitive data (such as health) or large-scale processing, a DPIA is often mandatory. Have this assessed per situation.

    Related articles

    Book a free demo

    Discover what an AIOS or AI receptionist can do for your business. Free, with no obligation.

    Book a free demo