Ecommerce: a chat assistant for online shops (Ireland and EU): a worked example map
A worked example of a Boundsmap map. It shows the five layers of the system and the four boundaries between them, what UK and EU law asks at each boundary, and whose obligation each one is. Self-assessed, and not legal advice. The map above is the one you can open and answer.
Boundary 1: Source Materials ↔ Capability Builders
No obligation is settled here yet. 2 questions need your answer.
Boundary 2: Capability Builders ↔ Integrators
No obligation at this boundary in this example.
Boundary 3: Integrators ↔ Operators
1 obligation. 1 question needs your answer.
- EU GDPR Art. 28: Quaybell and the online shops (their customer service staff) are different parties, and personal data passes between them. Whoever processes it on the other's behalf needs that set down in writing: purpose, duration, categories of people, security, sub-processors, and what happens at the end. Which of you is controller and which is processor depends on who decides why the data is used, and you can both be controllers; that is a question about your contract, not one this map can answer for you.
Boundary 4: Operators ↔ Affected Parties
3 obligations. 2 questions need your answer.
- EU GDPR Art. 6: A lawful basis is needed for the personal data this system handles while it is running. That is a separate question from the basis for anything it was built from, and has to be settled even where it was built from nothing. Contract and legitimate interests are the usual candidates; legitimate interests needs a documented balancing test. Record it per purpose, not once for the product: routing, monitoring and telling someone what to expect are different purposes even inside one system.
- EU GDPR Art. 13: The people whose information this system processes have to be told, at the point it is collected, that it will be handled this way, including that an AI system is involved and what that means for them. This is the privacy notice they actually see, not the one filed with your policies.
- Art. 50(2): Synthetic text, image, audio or video output must be marked in a machine-readable way as artificially generated.