Skip to content

    Forward Deployed Engineer

    Compliance Questions in Customer AI Reviews

    Answer EU AI Act, GDPR, SOC 2, HIPAA and ISO 42001 questions in a customer review: what the engineer supplies and what only the customer's legal team decides.

    By Published 8 min read

    • fde
    • compliance
    • governance
    • security-review
    • customer-delivery
    Share

    This lesson is part of AI Solution Architect: Discovery, Scope and Security. Enroll for free, then sign in, to read it in full.

    What you'll learn: how to sort compliance questions in a customer review into facts you evidence, readings of the law that legal decides, and honest unknowns.

    WARNING

    Not legal advice. It explains what an engineer typically supplies in a review. It does not say which law applies to any system or that any product complies. The customer's legal and compliance team decides. Law dates are as of 2026-11-03: open the linked source before you rely on one.

    At a glance

    Figure 1. Where each review question goes

    flowchart TD accTitle: Routing a compliance question in a customer review accDescr: A review question is first checked for whether it asks about a fact of the system. If yes and evidence exists, the engineer answers with evidence; if there is no evidence yet, it is recorded as unknown with an owner and a date. If it asks how a law or standard applies, it goes to the customer's legal or compliance team, and the engineer supplies the facts they ask for. Q["Review question"] --> F{"Is it a fact about the system?"} F -- yes --> K{"Do you have evidence now?"} K -- yes --> E["Answer with evidence"] K -- no --> U["Unknown, owner, date"] F -- "no: how does a law apply?" --> L["Route to customer legal"] L --> S["Supply the facts they ask for"]

    How to read this: you answer facts, the customer's lawyers answer readings of the law, the rest is a named unknown.

    • Facts you can show (data flow, subprocessors, retention, logs) are yours.
    • Which law applies, which risk category and whose role: not yours.
    • Never write "compliant" about your own system.

    Scenario

    Composite scenario, not a real company. Lumen Industrial Supply, a fictional distributor, is piloting the read-only Order and Policy Assistant for 24 customer-service agents. Its legal team sent a review sheet naming the EU AI Act, GDPR, SOC 2, HIPAA and ISO/IEC 42001, asking "Is the system compliant?"

    What you will be able to do

    • Say what you supply for five regimes.
    • Sort questions into answer, route or unknown.
    • Write a date-safe sentence about a law.

    Prerequisites

    Customer security and platform reviews: its field table is your evidence. Theory: Governance and responsible AI.

    Core ideas

    Five regimes, one split

    Regime What it is (per its source) Covers You supply Legal decides
    EU AI Act, Regulation (EU) 2024/1689 Rules for AI systems by risk Providers, deployers, others (Art. 2) Purpose, oversight description, log fields Role, risk category, articles
    GDPR, Regulation (EU) 2016/679 Rules for processing personal data Controllers and processors Data flow, fields, subprocessors, retention, deletion path Personal data or not, lawful basis, roles
    SOC 2 (AICPA) A CPA examination of a service organisation's controls Service organisations Providers you use; their reports Whether a report is enough
    HIPAA (US regulations, 45 CFR 160.103) US rules that define protected health information Covered entities and business associates Data classes: any health information? Whether it applies, any associate contract
    ISO/IEC 42001 A standard for an AI management system Any organisation providing or using AI Records: decisions, changes, evaluations Whether to adopt it

    How to read this: the last two columns are the split.

    What the texts say

    The Commission's page describes four AI Act levels: banned practices, high-risk, transparency duties, and minimal risk. Article 6 and Annex III make listed areas high-risk (such as biometrics and employment), with a conditional exception in Article 6(3). Article 50(1) requires providers to design AI systems that interact directly with people so that they are told it is an AI system, unless obvious.

    GDPR defines personal data as information relating to an identifiable person (Art. 4(1)). Articles 15 to 22 give rights including access, erasure and not being subject to a solely automated decision with significant effects. Article 28(2) bars a processor from engaging another processor without the controller's written authorisation.

    Figure 2. The assistant's data flow as a reviewer will draw it

    flowchart LR accTitle: Data flow of the Order and Policy Assistant for a compliance review accDescr: The client app sends a question through the API gateway to the orchestrator. The orchestrator reads order fields from the order management system and policy passages from the document store, sends the question, needed fields and passages through the model gateway to the LLM provider, and writes log entries to the trace store. The LLM provider is listed as a possible subprocessor for legal to classify. C["Client app"] --> G["API gateway"] G --> O["Orchestrator"] O --> S["OMS: order fields"] O --> D["Document store: policy passages"] O --> M["Model gateway"] M --> P["LLM provider: possible subprocessor"] O --> T["Trace store: ids and versions"]

    How to read this: each arrow is a hop a reviewer will ask about; mark where data leaves.

    The questions the review will ask

    Question Evidence you hand over Owner
    What data leaves our network, to whom? Figure 2, field table, provider list with terms link and date You
    Is personal data sent to the model? Field list of what it receives You list; legal classifies
    What do logs hold, for how long? Log field list; retention setting You; customer sets period
    Can one person's data be found and deleted? Map of every store (OMS, logs, provider), draft deletion path You map; legal answers requests
    Who can check or override an answer? Read-only scope, cited sources, the agent decides You
    Do users know it is AI? Screenshot of the label You; legal decides if Art. 50 applies
    Is it high-risk? Purpose statement Legal

    Decision exercise. A reviewer writes: "Confirm the assistant is not high-risk." Choose: (A) "Confirmed, it is read-only." (B) "Yes, high-risk, to be safe." (C) Send the purpose statement and oversight description; route the classification to legal.

    Model answer

    C. Classification under Article 6 is a legal reading, and A and B both decide it. Read-only is a fact, not an answer.

    Explain it back. Tell the customer's legal lead in three sentences why you will not write "compliant", what you supply and what is legal's.

    Worked example

    Assumptions: illustrative.

    A reviewer writes: "High-risk rules start 2 August 2026." Check the sources, not memory:

    • As published in 2024, Article 113 applied the Act from 2 August 2026.
    • Regulation (EU) 2026/1744 (the Digital Omnibus on AI, signed 8 July 2026, published 24 July 2026, in force 27 July 2026) replaced Article 113's date for Chapter III sections 1 to 3, except Article 6(5): 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems. It amends other provisions too: read its text.
    • Recomputed in Python: 16 months later for Annex III; 12 months after the original 2 August 2027 for Article 6(1).
    • Of the 7 table rows, you own 2, 4 are shared, 1 is legal's.

    Reply: "As of 2026-11-03 the Commission page shows these dates [link]. Whether it is high-risk is for your legal team."

    At the customer: asked "Are you compliant with the AI Act?", say: "We make no compliance claim. Here is what the system does and its records; your legal team decides how the Act applies."

    Practice task

    Build the review evidence pack: copy the question table, add one evidence link per row, and mark each row Answer, Route or Unknown (owner and date).

    Answer, route or unknown? (interactive when JavaScript is on)

    The sheet asks, "Are you a processor under GDPR?"

    • Answer yes: it handles order data
    • Supply the data flow; route the role question to legal
    • Answer no: logs hold no personal data
    Answer

    Supply the data flow; route the role question to legal. Roles are a legal reading, and a "no" ignores data sent to the model.

    A reviewer asks for the provider's SOC 2 report. You have not requested it.

    • Say the provider is SOC 2 compliant
    • Say your own system holds a SOC 2 report
    • Record it as unknown with an owner and date; request the report
    Answer

    Record it as unknown with an owner and date; request the report. A visible unknown can be accepted; a memory claim cannot.

    A reviewer says high-risk AI Act rules start 2 August 2026.

    • Agree: that is the date in the law
    • Give today's dates with the link, say an amending regulation moved them
    • Say the rules never apply to internal tools
    Answer

    Give today's dates with the link, say an amending regulation moved them. The 2024 text and Regulation (EU) 2026/1744 give different dates, so a dated, linked answer is safe. "Never apply" is a legal reading.

    Exercise

    Sort eight items into Answer, Route or Unknown: (1) the subprocessor list; (2) whether a data protection impact assessment is needed; (3) the log retention period; (4) whether a business associate contract is needed; (5) a screenshot of the AI label; (6) the provider's retention terms; (7) whether Annex III covers customer service; (8) the deletion path for one agent's data.

    Acceptance criteria:

    • Each item has one pile and an evidence item or owner.
    • No item says "compliant" or "fully".
    • One Unknown has an owner and a date.

    Done when a reviewer can check each choice alone.

    Hint 1: ask who could be wrong

    If a file proves it, it is yours. If a lawyer could read it differently, route it.

    Hint 2: split mixed items

    Items 2 and 4 mix both: supply facts, route the decision.

    Common mistakes

    • Writing "compliant". You describe; only legal concludes.
    • Quoting a date from memory. The 2026 amendment changed dates; cite source and day.
    • Answering a legal question to look helpful. A wrong "no" is worse than "routed".
    • Claiming a provider's report as yours.

    Knowledge check

    1. What is the split between you and the customer's legal team?

    You supply evidenced facts such as data flow and logs. Legal decides how a law applies, such as roles and risk.

    2. Why does a law date need "as of" and a link?

    Regulation (EU) 2026/1744 changed Article 113 dates after the 2024 text. A dated, linked sentence lets readers re-check.

    3. Why is "is it high-risk?" not yours to answer?

    It reads intended purpose against Annex III and Article 6(3).

    4. Why list the model provider as a "possible subprocessor"?

    GDPR Article 28(2) bars a processor from engaging another processor without the controller's written authorisation, so the customer needs the provider list. Whether it is a processor is legal's call.

    5. What do you say when asked whether you hold SOC 2 or ISO 42001?

    State what you hold (possibly nothing) and what you requested from providers. Both cover organisations, not products.

    You can now

    • Add the evidence pack to your design pack.
    • Say, for five regimes, what you supply and what legal decides.
    • Route a question without answering it.
    • Reply to "are you compliant?" without a claim.

    Further reading

    Last verified: 2026-11-03

    Next

    Optional page. Back to the core path: Rollout plan and solution proposal

    Enroll to keep reading

    Lesson 8 of 8 · AI Solution Architect: Discovery, Scope and Security

    Answer EU AI Act, GDPR, SOC 2, HIPAA and ISO 42001 questions in a customer review: what the engineer supplies and what only the customer's legal team decides.

    In the rest of this lesson

    • Worked example
    • Practice task
    • Exercise
    • Common mistakes
    • Knowledge check
    • You can now

    Enrolling is free. It unlocks every lesson in AI Solution Architect: Discovery, Scope and Security, tracks your progress across devices and keeps your quiz scores. The newsletter is optional.

    Ask about this article

    Get answers grounded in this post. AI-generated — based on this article, and may be imperfect.

    Scaled AI Weekly

    Enjoyed this? Get more like it every Monday.

    Real architecture decisions, LLMOps patterns that survive production, and engineering leadership advice — from 12+ years of building at enterprise scale. Free. No spam. Unsubscribe anytime.

    Get new articles by email

    Free. We email a confirmation link first, and you can unsubscribe from any email.

    Join engineers building production AI systems

    Comments