GDPR-Compliant Chatbot: Step-by-Step Guide (2026)

Bartek Kuban
Published Updated 21 min read
Thumbnail for Building a GDPR-Compliant Chatbot: Your Step-by-Step Guide to Security, User Trust, and Navigating the AI Act

A GDPR-compliant chatbot requires a lawful deployment, not just a particular model or hosting location. Define the purpose and lawful basis for each use of personal data, map where that data goes, establish the parties’ roles and contracts, provide information and rights processes, and implement security appropriate to the risks. A vendor’s compliance label cannot establish that every customer use meets those requirements.

You do not automatically need consent for every support conversation, EU-only hosting, or a separate model for European visitors. You do need evidence that the choices made for your particular workflow satisfy the applicable rules. The same assessment extends to the model provider, CRM, analytics, channel integrations and operational logs.

This guide was checked against official sources on 4 November 2026. It provides an assessment framework and implementation examples; it does not certify a deployment or replace advice on its specific legal circumstances.

DecisionWhat to establish
Purpose and lawful basisIdentify why each category of personal data is processed and which basis applies. Consent is one possible basis.
Data flows and responsibilitiesRecord the controller, processors, recipients, processing locations and onward transfers.
SecuritySelect and verify measures appropriate to the data, access paths and potential harm.
Individual rights and retentionProvide a usable request route, justified retention periods and a verifiable deletion process.
Vendor evidenceReview the actual contract, subprocessors, settings, security scope and operational limits.
AI Act obligationsCheck the intended use, provider/deployer role and current application dates alongside GDPR.

Optional example checks

  • Preview metadata keys. Check how supplied field names become variable keys, including duplicate names and reserved-key errors. This does not inspect values or account-specific permissions.
  • Validate a test dataset. Check a small supplied dataset against the supported format without running your AI Agent.

These checks do not assess legal compliance.

A 10-step launch checklist for chatbot privacy and security

Give each item an owner and keep evidence of the decision or test:

  1. Define the workflow. Separate public information, account-specific support, transactions, marketing and model improvement.
  2. Map personal data. Include prompts, replies, metadata, files, retrieved records, logs and connected systems.
  3. Choose lawful bases. Assess each purpose before processing; add a valid consent flow where consent is required.
  4. Identify roles and contracts. Establish who determines purposes and who processes on instructions. Review applicable processor terms and transfers.
  5. Minimise collection. Remove unnecessary fields and avoid sending complete customer records when a limited result is sufficient.
  6. Define retention and rights handling. Include identity checks, access, correction, erasure, portability where applicable, and downstream follow-through.
  7. Assess risks. Determine whether a Data Protection Impact Assessment (DPIA) is required and complete it before the relevant processing begins.
  8. Secure access and integrations. Apply appropriate encryption, authentication, permissions, monitoring and incident procedures.
  9. Inform users. Publish accurate privacy information, provide required AI disclosure and assess widget storage separately.
  10. Test and assign ongoing responsibility. Exercise failure cases, train staff and review the assessment when purposes, providers or features change.

GDPR principles and their effect on chatbot design

GDPR applies to relevant processing in the context of an EEA establishment. It can also cover organizations outside the EEA when they offer goods or services to people there or monitor their behavior there. The test concerns the processing and territorial connection, not simply a person’s citizenship. The EDPB explains the territorial scope and core principles.

Names, contact details, online identifiers and identifiable conversation content can be personal data. A public FAQ interface may still collect identifiers or free text containing personal information.

RequirementChatbot implementation consequence
Lawfulness, fairness and transparencyEstablish a basis and explain the actual processing in understandable terms.
Purpose limitationDefine permitted uses and assess additional uses, such as marketing or training, separately.
Data minimisationCollect, retrieve and disclose only what the stated purpose needs.
AccuracyProvide a way to correct inaccurate personal data and prevent unsupported information about people being treated as fact.
Storage limitationSet justified retention periods or criteria, then enforce and review them.
Integrity and confidentialityProtect personal data against unauthorized processing, loss and damage.
AccountabilityKeep evidence of decisions, responsibilities, contracts and implemented measures.
Protection by design and defaultLimit collection, use, retention and access from the design stage onward.
Lawful basis for each purposeAssess consent, contractual necessity, legitimate interests or another applicable Article 6 basis.

For specified higher-tier infringements, maximum fines can reach €20 million or, for an undertaking, 4% of worldwide annual turnover in the preceding financial year, whichever is higher. Actual enforcement depends on the circumstances; see the EDPB explanation of supervisory powers.

Terms used in this guide

  • Controller: the organization determining processing purposes and essential means.
  • Processor: a separate entity processing personal data on the controller’s behalf. Roles depend on the actual activity, not just the contract’s label.
  • Pseudonymisation: reducing direct linkability, for example by replacing a name with an identifier. It does not automatically make data anonymous.
  • DPIA: an assessment required where processing is likely to result in high risks to people’s rights and freedoms. Relevant factors include scale, sensitive data, vulnerable people and significant automated decisions. Using AI alone does not settle the test. Consult the EDPB’s DPIA guidance and applicable supervisory-authority lists.

Turning GDPR requirements into operational workflows

Start with the actual journey from a visitor’s message to its final deletion. The following designs are illustrative implementation patterns, not a list of built-in Quickchat AI features.

Data minimisation by design

Define a required_fields schema for each task. An appointment enquiry might need a preferred time and contact method; a public opening-hours question should not require a customer profile.

The website chatbot lead-capture walkthrough gives a concrete configuration to evaluate: answer general questions first, then collect contact details for a requested follow-up. Review the fields and recipients against your own purposes before using it for customers.

Check more than the visible form. A CRM lookup could retrieve an entire record even when the answer needs only an order status. Limit the fields returned and the data passed to the model. Keep credentials and unrelated customer information out of prompts.

Input masking protects what someone nearby can see. It does not establish that the underlying value was never collected, logged or transmitted. Redaction can reduce accidental disclosure, but test what it misses, including identifiers embedded in ordinary sentences.

The European Commission’s lawful-basis guidance identifies several possible bases. Necessary processing to fulfill a contract, legitimate interests after the required assessment, and consent have different conditions. Choose the basis before processing rather than adding a consent box to every task.

When relying on consent, make the purpose specific and the choice freely given, informed and unambiguous. Allow withdrawal as easily as consent was given. Separate optional marketing from support the customer needs. An acknowledgement that someone has read a privacy notice is not itself consent to every use described there.

Double opt-in can help establish evidence in some contexts. It is not a universal GDPR requirement. The EDPB consent guidelines distinguish ordinary consent from explicit consent and describe two-stage verification as one possible method.

If consent is your basis, record the purpose, notice version, affirmative action, time and relevant identifier. Protect that evidence and apply a justified retention policy. Special-category data, such as health information, requires an applicable Article 9 condition as well as an Article 6 basis.

Handling access, erasure and portability requests

Provide an accessible request route and a person or team responsible for completion. A custom /my_data command or /delete_my_data command could open a request, but neither command is a verified built-in Quickchat AI feature. A conversational acknowledgement is not evidence that a request has been fulfilled.

A workable process is to verify identity proportionately, locate relevant records, assess the requested right and any exceptions, coordinate processors, complete the action, and record the response. Use authenticated delivery for exports and prevent one visitor from requesting another person’s data.

The controller must act without undue delay and normally within one calendar month. A permitted extension of up to two further months requires informing the individual, with reasons, within the first month. Erasure has grounds and exceptions, including some legal retention duties. Access and portability also differ: Article 20 portability applies under specified conditions to automated consent- or contract-based processing of data provided by the individual. See the EDPB rights guide.

Quickchat AI deletion routes have different effects. Deleting an AI Agent makes its conversations inaccessible but does not erase them. Deleting an account erases conversations of its current agents in a background process; the documentation lists exclusions such as previously deleted agents’ conversations, attachments, exports, search indexes and external records. Contact support for the applicable erasure process. Disconnecting a Meta channel stops future authorized processing but does not automatically delete historical conversations.

For the wider support workflow, our customer-service assistant setup guide is separate from this rights-request process.

Storage limitation and retention scheduling

There is no universal GDPR limit of 30 or 90 days for chatbot transcripts. Define retention by purpose and data category, including any applicable legal obligations. Distinguish active conversations, exports, consent evidence, security logs and backups.

This conceptual pseudocode illustrates scheduling and verification, not a complete deletion implementation or an existing product setting:

function scheduleRetention(record, policy) {
  return {
    recordId: record.id,
    purpose: record.purpose,
    reviewOrDeleteAt: policy.dateFor(record),
  };
}

function processDueRecord(item) {
  if (requiresRetentionReview(item)) {
    return queueManualReview(item);
  }
  queueErasureAcrossRecordedSystems(item);
  recordVerificationPending(item.recordId);
}

Document the policy owner, retention criteria, permitted exceptions, deletion method and evidence of completion. Monitor failures instead of assuming that a scheduled job reached every system.

Backups need explicit treatment. The EDPB’s February 2026 erasure report identifies practical difficulties and the need to account for erasure when systems are restored. It does not establish that either immediate removal from every backup or waiting for any normal expiry always meets the law. Describe the actual restrictions, deletion schedule and restoration procedure without promising universal erasure within one month.

Article 22 and meaningful human review

Article 22 concerns decisions based solely on automated processing that produce legal or similarly significant effects. A routine FAQ answer is not automatically such a decision. Credit eligibility, admissions or access to essential services need closer assessment.

Identify these decision points before building the workflow. Where the provision applies, assess the applicable exception and safeguards. For contractual-necessity or explicit-consent exceptions, safeguards include the ability to obtain human intervention, express a view and contest the decision. Special-category data has additional restrictions.

A reviewer must have the information and authority to reconsider the result. Adding a handoff button while leaving the outcome effectively fixed is insufficient. Record the actual decision criteria, inputs and review outcome proportionately; a model’s generated explanation is not proof of how a consequential decision was made.

Security measures appropriate to chatbot risks

Article 32 requires appropriate technical and organisational measures. It does not prescribe one universal encryption algorithm or authentication product. Use the EDPB security guidance to connect safeguards with the likely harm, processing context and available technology.

Encryption in transit and at rest

Protect network connections and stored records with suitable encryption and key management. Check the visitor-to-widget connection, integrations, administrative access, databases, exports and backups individually.

TLS protects a transport connection; encryption at rest protects stored data. These measures do not by themselves establish end-to-end encryption, in which intermediaries cannot read the content. A service processing message content may need to decrypt it. Avoid describing TLS 1.3 or AES-256 as mandatory GDPR specifications or proof of compliance.

Authentication, access roles and identity integration

Use strong authentication, including MFA where appropriate, for administrative access. Prefer an existing authenticated customer session for account-specific requests over asking someone to type an account identifier into a public chat.

Review authorization separately: a valid login must not expose another customer’s records. Give staff access according to their duties and remove it when no longer needed. Quickchat AI documents its team roles; verify that the available roles meet your requirements.

Evaluate enterprise SSO where relevant, but do not infer SAML support from ordinary Google sign-in. Biometric identification can create additional data-protection obligations and is not a universal safest option.

API security and limited integration permissions

Use scoped credentials and enforce authorization in the connected application. The model’s instruction to access only a particular customer’s data is not an access-control boundary.

Apply suitable rate limits, validate structured parameters and outputs, and review what each Action or integration can read or change. Test cross-customer access and revoked credentials. Record which third parties receive personal data, including error reporting and analytics services.

Monitoring, logs and incident response

Log enough to investigate access and failures without automatically copying every full conversation into every monitoring system. Define access, retention and redaction separately for operational logs.

An incident procedure should cover containment, investigation, recovery, documentation and notification decisions. Under GDPR, a controller notifies a reportable personal-data breach to the competent authority without undue delay and, where feasible, within 72 hours after awareness, unless it is unlikely to create a risk to people’s rights and freedoms. Likely high risk can require informing affected people without undue delay, subject to Article 34 exceptions. A processor informs its controller without undue delay.

These are different duties and thresholds; the Irish DPC’s breach guidance explains the distinction. The proposed GDPR Digital Omnibus changes are not a reason to use a different reporting deadline now.

Security evaluation checklist

Control areaEvidence to check
Transport and storage encryptionActual connections, storage scope, keys and exceptions.
Authentication and authorizationStaff access, visitor identity and cross-customer isolation.
Integration permissionsRequired fields and actions, scoped credentials and revocation.
Security testingRelevant test scope, findings, remediation and retesting.
Input and output handlingStructured validation and safe display; separate AI attack testing.
Least privilegeAccess limited to the people and components that need it.
Software maintenanceDependency ownership, patching and change review.
Data minimisationUnnecessary fields and copies removed from the actual flow.
MonitoringUseful alerts and protected logs with justified retention.
Incident responseNamed owners, reporting assessment and recovery exercises.
Retention and backupsDeletion verification, failure handling and restoration procedures.
Staff trainingRole-specific instructions and a route for escalating mistakes.

Managing AI-specific chatbot risks

AI evaluation should cover the information the model receives and the actions its output can trigger. General software-security controls remain necessary.

Prompt injection and adversarial testing

Prompt injection can arrive through a visitor message or retrieved content that attempts to redirect the model. For example, a document might instruct it to reveal private records or invoke an unrelated Action.

Separate trusted instructions from untrusted content, restrict available permissions, validate action arguments and test unauthorized-access attempts. Filters and instructions can help but do not guarantee prevention. OWASP’s prompt-injection guidance explicitly notes that RAG and fine-tuning do not fully mitigate the vulnerability.

Use synthetic or appropriately prepared test data. Record whether the system refused, disclosed information, invoked a tool or escalated; a reassuring final sentence alone does not establish safe behavior.

Hallucinations and response validation

A model can produce a plausible answer unsupported by the available evidence. Retrieval from a maintained Knowledge Base can help ground answers, but it does not guarantee factual accuracy or enforce permissions by itself.

Test outdated policies, conflicting sources, missing records and requests outside the intended scope. Provide a way to flag errors and route unresolved cases to a person. For account-specific answers, compare outputs against authorized source records rather than relying on the model’s confidence. Our explanation of AI hallucinations discusses the underlying behavior.

Data leakage, training and redaction

Training use, inference, application state and logs are separate processing activities. Do not assume every message trains a model, or that a no-training commitment means no data is transmitted or retained.

Quickchat AI’s Legal FAQ states that customer material is not used to train LLMs and that PII scrubbing is available on request. This is not a promise that every message is scrubbed or that all personal data is detected. Confirm the selected configuration and provider terms.

Input redaction must occur before the processing it is intended to prevent; output redaction occurs after generation. Removing a name can still leave identifying context. The EDPB distinguishes pseudonymisation from anonymisation, and its AI-model opinion requires a case-specific assessment of anonymity.

Evidence for explanations and audit trails

Keep proportionate evidence of retrieved sources, actions, relevant settings and human review. Avoid treating a generated explanation, an internal confidence score or an explanation technique as automatic proof of legal compliance.

Quickchat AI’s Inbox Why AI said that can show retrieved sources and execution evidence. This helps investigate a reply; it is not a complete causal account of model internals or a substitute for assessing explanation obligations in a significant decision workflow.

International processing and server locations

Map storage, model processing, support access, integrations and onward transfers. A database’s region answers only part of the location question.

EEA hosting and processing outside the EEA

GDPR does not impose a universal EU-only hosting rule. Transfers outside the EEA need an applicable Chapter V route, alongside the other GDPR requirements. The EDPB’s transfer guide explains adequacy, appropriate safeguards and limited derogations.

Quickchat AI’s Legal FAQ describes GCP storage in Belgium. Its Privacy Policy separately discusses US transfers and contractual safeguards. Belgium storage therefore does not establish EU-only processing. The FAQ also describes enterprise deployment options, including private cloud, self-hosted LLM and on-premises arrangements; architecture, availability and responsibilities must be agreed for the specific deployment.

Standard Contractual Clauses and the EU-US Data Privacy Framework

The Commission’s current adequacy list includes US commercial organizations participating in the EU-US Data Privacy Framework. Verify the recipient’s active participation and the scope covering the transfer. A US address alone is not enough.

Where using Standard Contractual Clauses or another Article 46 tool, assess whether destination-country laws and practices undermine the safeguards and whether supplementary measures are needed. Covered adequacy transfers do not automatically require the same additional transfer assessment. Neither route removes duties concerning purpose, lawful basis, security or processor contracts.

Do not confuse a cloud provider’s status with the chatbot vendor’s. Quickchat AI’s FAQ describes ongoing DPF alignment, not verified participation.

Provider example: OpenAI API data controls

OpenAI’s API data documentation states that API inputs and outputs are not used for training by default unless the customer opts in. It separately describes abuse-monitoring logs and application state. Standard abuse-monitoring logs may be retained for up to 30 days, with legal or safety exceptions.

Zero Data Retention and Modified Abuse Monitoring require approval and have endpoint limitations. Confirm the actual account, endpoint, contract and processing locations. Consumer ChatGPT history controls do not establish an API integration’s settings. These general provider terms do not prove that a particular Quickchat AI account has zero retention.

Processor agreements and vendor responsibilities

Where a vendor processes personal data on your behalf, Article 28 requires a binding contract or other qualifying legal act. Assess separate uses, such as a provider processing data for its own purposes, rather than assuming every activity has the same role. The EDPB controller/processor guidelines explain the distinction and contract requirements.

Required processor terms and additional AI questions

Check that the agreement covers:

  • The subject matter, duration, nature and purpose of processing, data types, categories of people, and controller rights and obligations.
  • Documented instructions, including transfers, with the applicable EU or member-state legal exceptions.
  • Confidentiality and security measures appropriate under Article 32.
  • Prior specific or general written subprocessor authorization, notice of changes and an opportunity to object where general authorization is used, with required obligations passed down.
  • Assistance with individual rights, security, breach handling and impact assessments.
  • Deletion or return at the controller’s choice after processing services end, and deletion of existing copies unless EU or member-state law requires storage.
  • Information needed to demonstrate compliance and provision for audits and inspections.

Ask separately about model training, feedback, retention and secondary uses. GDPR does not simply require a universal ban on every possible training use; each use needs an appropriate assessment of purpose, role and legal conditions.

Quickchat AI publishes a Data Processing Agreement. Review the applicable signed terms and supporting information. Its availability alone does not establish that a particular contract or deployment meets every requirement above.

Negotiation points for AI providers

Request specific answers about processing locations, subprocessors, operational retention, account controls, breach communication and exit procedures. Distinguish documented product settings from contract-specific commitments.

Ask what happens when a feature is disabled, a channel disconnected, an agent deleted or a contract terminated. Establish the export scope, deletion evidence, remaining legally required data and backup treatment. Liability provisions and service levels are commercial questions as well as part of vendor evaluation; avoid accepting a general security statement as the complete technical schedule.

Personalisation and data minimisation

Start with the least information needed to answer the current question. Persistent profiles require a purpose and assessment of their own.

Differential privacy and processing on a device

Differential privacy can help limit information revealed about individuals in suitable statistical or training applications. Its protection depends on the implementation and parameters; mentioning the technique does not establish anonymisation or lawful processing.

Processing a preference on the visitor’s device can reduce server-side collection. Check what still leaves the device, including identifiers and telemetry. Device storage or access can have ePrivacy implications even when the information is not personal data.

Segment-based answers and individual profiling

Tailoring an answer to a stated product category may require less data than maintaining a long-term behavioral profile. However, assigning a known customer to a segment can still process personal data.

Assess the actual purpose, lawful basis, notice, retention and access controls. Consent is not universally required for every form of personalization, and significant automated decisions need separate Article 22 assessment. Offer a useful basic service where optional profiling is declined.

Chatbots in regulated sectors

Sector rules depend on the entity, activity and jurisdiction. An AI chatbot for a law firm and an AI chatbot for financial services need clearly defined boundaries between general information, account access and professional advice. A disclaimer alone does not settle those boundaries.

Healthcare: sensitive data and applicable HIPAA duties

Health data requires an applicable GDPR special-category condition as well as an Article 6 basis. Booking, administration, symptom assessment and clinical decisions present different risks. An AI chatbot for a dental practice should have a defined clinical escalation route appropriate to its intended role.

In the US, HIPAA applies to covered entities and business associates, not automatically to every piece of US health data. An applicable business-associate relationship needs the required agreement. Verify permissions, safeguards and record-specific retention with the organization responsible. Do not infer HIPAA suitability from a GDPR DPA, an encryption claim or a healthcare landing page.

Finance: recordkeeping and decision controls

Identify the rules applying to the firm and record type before setting retention. FINRA Rule 4511, for example, concerns member firms and uses a six-year period for FINRA records without another specified period. It is not a universal retention rule for every chatbot transcript.

Distinguish public product information, personalized advice and decisions affecting eligibility. Assess authorization, professional obligations, recordkeeping and meaningful review where required. Avoid relying on either a blanket prohibition on automated finance or a generic disclaimer permitting it.

Public-sector services: assessment and accessible information

Public bodies generally need a DPO, subject to the applicable exceptions, while a particular DPIA depends on the processing’s risks. A public FAQ chatbot and a system influencing benefit eligibility need different assessments.

Explain who operates the service, how data is used and how to obtain help or exercise rights. Consider vulnerable users, accessible alternatives and the consequences of inaccurate answers or failed handoffs. Review applicable accessibility and sector requirements rather than assuming the chatbot interface satisfies them.

Evaluating chatbot vendors and technology

Ask for evidence tied to your intended workflow. Our AI chatbot buyer guide provides broader evaluation context; the privacy assessment must still address your actual data flows.

What ISO 27001, SOC 2 and Cyber Essentials establish

ISO/IEC 27001 concerns an information security management system. Review the certificate’s organization, services, locations and validity rather than treating the logo as coverage of every product.

SOC 2 is an attestation report, not a certification. A Type 2 report examines operating effectiveness over its specified period. Check the systems, criteria, exceptions and customer responsibilities in the actual report.

Cyber Essentials is a UK scheme covering baseline technical controls against common internet threats. None of these alone establishes GDPR compliance for your use. Quickchat AI’s Legal FAQ describes SOC 2 as being pursued; do not treat that wording as a completed report.

15 questions to ask prospective vendors

  1. Where are prompts, replies, files, logs and backups stored and processed, and who can access them remotely?
  2. What roles and processing activities does the proposed DPA cover?
  3. How is access to one customer’s data isolated from another’s?
  4. Which connections and stored records are encrypted, and how are keys managed?
  5. What retention and deletion rules apply to each data category?
  6. How are access, correction, erasure and portability requests supported and verified?
  7. Which subprocessors are involved, and how are changes communicated?
  8. Is customer data used for training, evaluation or feedback, and under what terms?
  9. How are incidents investigated and relevant breaches communicated?
  10. What current certificates or assurance reports cover the specific service?
  11. Which authentication, roles and identity integrations are actually available?
  12. What evidence covers prompt injection, unauthorized actions and data leakage?
  13. Which privacy and security choices are defaults, configurable settings or enterprise arrangements?
  14. What logs and source/action evidence can customers access, and what are their limits?
  15. How can we inspect compliance evidence, export data and verify the end-of-service process?

A vendor comparison scorecard

Record evidence and unresolved questions alongside scores. An unknown contractual or operational fact should remain unknown, rather than receiving points for marketing language. A required condition that is unmet should not disappear inside a favorable total.

CategoryVendor AVendor BVendor CPriorityEvidence to record
Roles and processor termsHighActivities, instructions, assistance and audit provisions
Processing locationsHighStorage, inference, support and onward transfers
Notices and consent supportAs applicableActual interface behavior and consent evidence
Rights workflowsHighRequest route, identity checks and response ownership
Export and erasureHighScope, exclusions, verification and backups
Security measuresHighControls appropriate to the intended processing
EncryptionHighTransport, storage, keys and exceptions
Access controlsHighRoles, authentication and isolation evidence
Assurance evidenceAs applicableReport or certificate scope, date and findings
Incident handlingHighContacts, notification and recovery process
AI processing termsHighTraining, inference, logs and application state
AI evaluationHighRelevant tests, limitations and escalation
Workflow suitabilityMediumRequired integrations and task quality
Total costMediumUsage, implementation, review and operation
Support and service levelsMediumActual commitments and response routes
Vendor continuityMediumExit plan and data portability
DecisionRequired conditions met; open issues and owners

Download a deployment data-flow register

Download the editable data-flow register. The shared English pack contains three blank CSVs, a separate fictional example and instructions. Use it to record the components, data movements, evidence and unresolved questions for your proposed deployment. It does not describe a verified Quickchat AI architecture.

  1. In components.csv, list the browser, application, knowledge store, model provider, connected services, logs and backups that actually apply. Record processing and storage locations separately, together with training use, retention, deletion scope and access ownership. Leave unknown facts unresolved.
  2. In data-flows.csv, connect component IDs and describe each flow’s purpose, data categories and access conditions. Record categories and document references, not private transcripts or credentials.
  3. In evidence-register.csv, link each claim to a dated source and its scope. Distinguish vendor statements, contracts and configuration from test plans and observed test receipts. A planned test remains not_run. Assign open questions to an owner.

Import the UTF-8 CSVs as separate sheets and keep their identifiers unchanged. The optional offline checker checks formatting and references; it cannot verify a provider’s claim or determine legal compliance. Use the register alongside the questions and scorecard above, with the review required for your actual deployment.

A practical roadmap for smaller teams

Limit the initial workflow to what the team can operate and verify. Starting with public information can reduce complexity, although free-text input and technical identifiers still need assessment.

Self-hosted software and SaaS trade-offs

Self-hosting can give more direct control over architecture and data handling. It also requires operating, patching, monitoring and securing the system. Licensing and infrastructure costs vary; open-source availability does not guarantee a free deployment or eliminate external processors.

SaaS can provide managed infrastructure and support, but customers still need to establish their purposes, lawful bases, configuration and appropriate terms. Compare the work remaining for your team, not just the subscription price. Verify any private-cloud or self-hosting offer as a specific arrangement rather than assuming it is available on every plan.

Controls that can be implemented with limited resources

Use maintained software, secure transport, appropriate authentication and restricted access. Keep credentials out of prompts and unnecessary records out of the Knowledge Base. Establish a rights-request inbox with an owner and a retention register that reflects actual systems.

Use regulator templates to structure assessment, but write privacy information from your own data flows. A generic policy generator cannot establish what your chatbot does. Test restoration as well as backups, document incidents, and keep a route for human escalation. Where a necessary safeguard or legal assessment is unresolved, reduce the scope before launch.

Three hypothetical implementation examples

These are design examples, not customer case studies, measured outcomes or evidence of regulatory approval.

  • Retail bank information assistant. Limit the bot to approved public product information and direct account transactions to an authenticated service. Assess processing bases, providers and records. Test whether a visitor can induce disclosure of account information. This design still needs review against the bank’s applicable rules.
  • University admissions assistant. Separate general admissions guidance from application status and admissions decisions. A custom rights portal could verify identity and gather relevant records for review and secure delivery. JSON may be useful for applicable portability requests, but producing a file alone does not establish complete access fulfillment or compliance with deadlines.
  • Healthcare administrative assistant. Define the permitted booking and information tasks, minimize requested details and provide an appropriate clinical escalation route. Evaluate redaction on unexpected health information while recognizing missed detections. A disclaimer or redaction layer does not establish that the remaining transcript is anonymous or suitable for unrestricted training.

The EU AI Act alongside GDPR

The AI Act entered into force in August 2024 and applies in stages. It does not replace GDPR. As of this guide’s review date, the Commission’s current implementation timeline reflects adopted changes, not just the original schedule.

Current transparency duties and high-risk application dates

Article 50 applies from 2 August 2026. It requires providers to ensure that people interacting directly with AI are informed of that fact, unless it is obvious in the context. Required information must be clear and accessible at the first interaction. Check the other Article 50 duties where relevant to generated content or the particular system.

The adopted AI Omnibus entered into force on 27 July 2026. The relevant high-risk requirements now apply from 2 December 2027 for Annex III systems and 2 August 2028 for Annex I product-related systems. Classification depends on the intended use and statutory criteria; a chatbot in a regulated industry is not automatically high-risk merely because of its industry.

Assess provider and deployer responsibilities separately, including applicable documentation, oversight, logging and conformity duties. The amended Article 4 still requires measures supporting staff AI literacy, without requiring a guaranteed individual level.

The separate GDPR/ePrivacy Digital Omnibus procedure remained pending when checked on 4 November 2026. Proposed changes to those rules should not be treated as current law.

ISO/IEC 42001 and AI governance

ISO/IEC 42001:2023, published in December 2023, specifies an AI management-system framework. It can help organize responsibilities, risk assessment and ongoing review. Alignment or certification is not an automatic finding that a chatbot meets GDPR or all applicable AI Act obligations.

An implementation timeline and responsibility matrix

Use a staged plan to identify missing evidence before the public launch. The schedule is an example, not a statutory timetable or a promise that every project can finish in 90 days.

A 90-day plan with review points

  • Days 1-30: discovery. Define tasks, data flows, bases, roles and sector requirements. Screen for a DPIA, identify decision owners and gather vendor evidence.
  • Days 31-60: implementation. Agree applicable processor terms; configure notices, access, integrations and retention. Build the necessary rights and incident workflows. Complete assessment work as the design becomes concrete.
  • Days 61-90: verification. Test ordinary tasks, unauthorized requests, incorrect answers, deletion scope and recovery. Train the team, resolve necessary safeguards and review any required DPIA before the relevant processing starts. A limited pilot still needs appropriate protections.

Choose launch timing from readiness, not the calendar alone. The conversational AI platform guide provides additional platform-evaluation context.

RACI example with independent DPO advice

R means responsible for doing the work, A means the organization’s accountable project owner, C means consulted, and I means informed. This operational example does not transfer statutory responsibility away from the controller or processor.

The DPO advises and monitors independently. The DPO guidelines place responsibility for compliance and the DPIA on the controller and warn against conflicting roles that determine processing purposes and means. Not every organization must appoint a DPO.

TaskDPO, where appointedLegal counselSecurity leadIT/operationsController’s project owner
Define purposes and lawful basesCRCCA
Complete required DPIACRRCA
Prepare privacy informationCRCCA
Select vendorCCRRA
Agree processor termsCRCCA
Implement required consent flowsCCCRA
Implement security measuresCCRRA
Operate rights workflowsCRCRA
Define and enforce retentionCRCRA
Test security and remediateICRRA
Handle incidentsCRRRA
Train staffCRRCA
Review deployment and legal changesCRRCA

Before approving the deployment

Review the data map, applicable contracts, retention rules and operational test results together. Confirm who will receive a rights request or incident report and what happens when a provider, integration or purpose changes.

For Quickchat AI, distinguish documented controls from requirements needing a specific agreement. Account or agent deletion, a privacy disclaimer, on-request scrubbing and a stated storage region each have a limited scope. Resolve the requirements for the actual deployment before relying on them.

Frequently asked questions about chatbot privacy

Can a GPT-based chatbot be GDPR compliant?

It can form part of a lawful deployment, depending on the purposes, data, roles, contracts, security, rights handling and transfers. A model name, no-training setting or EU server is insufficient on its own. Pseudonymisation can reduce risk while leaving the data within GDPR’s scope.

How do I delete a user’s data on request?

Verify identity proportionately, identify relevant records, assess erasure grounds and exceptions, coordinate processors, and verify the result. Act without undue delay and normally within one calendar month, with any permitted extension communicated on time. Include logs, exports and backups in the assessment. Deleting a Quickchat AI Agent is not equivalent to erasing its conversations.

Which authentication method should a chatbot use?

Match it to the task. A public FAQ may not need visitor authentication, while account details or transactions need an appropriate authenticated and authorized route. Protect administrative access, consider MFA and verify role restrictions. Neither SSO nor biometrics is a universal answer for every workflow.

How long can I store chat logs under GDPR?

Only as long as justified for the relevant purpose, subject to applicable legal obligations. Define periods or criteria by data category and explain them in the privacy information. A sample 30- or 90-day period is not a GDPR default, and retaining consent evidence also needs justification.

Do I need a DPA if I self-host the model?

Assess whether another entity processes personal data on your behalf. Running software yourself does not automatically create a processor relationship with its publisher, but hosting, support, analytics or other services may do so. Applicable Article 28 terms remain necessary for processors, and self-hosting does not remove your own obligations.

Can a chatbot make fully automated decisions under Article 22?

The Article 22 restriction concerns solely automated decisions with legal or similarly significant effects. Where it applies, assess an applicable exception and the required safeguards, including meaningful human intervention where required. Ordinary support answers are not automatically covered by that restriction; significant eligibility or access decisions need closer review.

What should a chatbot privacy notice include?

Explain the controller and contacts, purposes and bases, relevant recipients and transfers, retention, applicable rights and complaint routes. Include other information required under Articles 13 or 14 for the actual collection, including withdrawal where relying on consent and relevant automated-decision information. Keep it accessible and accurate. Provide required AI-interaction disclosure separately from obtaining consent.

How can I reduce prompt-injection risk?

Treat visitor messages and retrieved content as untrusted. Limit permissions, enforce authorization outside the model, validate action parameters and test attempts to access unauthorized data or perform unrelated actions. Instructions, filters and RAG do not guarantee prevention. Keep a route for investigation and human escalation.

Assess each storage or access operation and its purpose under the applicable ePrivacy implementation. EDPB guidance covers more than cookies. Strictly necessary operations for a service the visitor explicitly requests may be exempt; other operations can require prior consent. Quickchat AI’s widget uses browser local storage for conversation continuity and preferences. Do not assume all widget storage is exempt or that every widget must be blocked in full before a consent choice.

Does the EU AI Act replace GDPR for chatbots?

No. GDPR continues to govern relevant personal-data processing, while the AI Act adds obligations according to the system, role and use. Article 50 transparency duties already apply from 2 August 2026. Check the current amended schedule for high-risk requirements rather than relying on the original 2025/2026 expectations.

To evaluate the Quickchat AI platform, start with a defined workflow and the data it needs, then compare the documented controls and applicable terms against your requirements.

Quickchat AI Quickchat AI Ask Quickchat AI a question