Customer AVV / DPA (Art. 28 GDPR) — Draft
This is a structural draft for agencies that connect shops or upload briefs containing personal data. It is not a finished Auftragsverarbeitungsvertrag. Have counsel issue a binding AVV before processing merchant/end-customer personal data in production.
1. Parties
Controller (Customer): the agency / account holder using ElbeWare AI Studio.
Processor: [Legal name — set LEGAL_OPERATOR_NAME after Gewerbe / UG], [Street / number — set LEGAL_OPERATOR_ADDRESS], [PLZ City — Germany].
2. Subject matter
Processing of personal data that the Customer submits to ElbeWare (briefs, generated artifacts metadata, shop connection identifiers, optional shop smoke / MCP traffic) for the purpose of providing ElbeWare AI Studio.
3. Duration
For the term of the Customer’s ElbeWare account and any legally required retention thereafter.
4. Nature & purpose
- Host account and workspace data
- Run generation / Guard / sandbox pipelines
- Optional shop connectivity and smoke tests as instructed by the Customer
5. Types of data & data subjects
May include Customer employee data (accounts) and, where the Customer chooses to connect shops or include PII in briefs, merchant staff or end-customer data (e.g. order-related fields). Customer decides what to submit.
6. Processor obligations (checklist for counsel)
- Process only on documented instructions (Art. 28)
- Confidentiality of persons authorized to process
- Appropriate TOMs (encryption at rest for secrets, access control, TLS)
- Engage subprocessors only with notice (see Privacy Policy list: Supabase, Stripe, Anthropic, E2B, GitHub, host, email)
- Assist with data subject requests and breach notification
- Delete or return data after end of processing (account deletion flows)
- Make information available for audits as agreed
7. Customer obligations
- Have a lawful basis to submit personal data
- Configure shops / briefs with least privilege
- Sign this AVV (or counsel’s final AVV) before production shop connections that may involve PII
- Remain responsible toward merchants / end customers
8. Acceptance in product
ElbeWare records accepted_avv_at / version when you accept in the Agency area.
Recording acceptance of this draft does not replace a counsel-signed AVV for high-risk processing.