A per-feature personal-data inventory with lawful basis, purpose and retention documented for each category, and a gap list covering processor agreements, third-country transfers, data-subject rights mechanisms and deletion code. Where AI calls carry personal data, the anonymize-at-the-call-boundary pattern substitutes opaque identifiers so Chapter V never applies to those calls, permanently, with no re-review when the vendor changes. The result is a privacy notice ready to publish and two audience-split checklists.
What ports as-is
- The seven-principle check against each feature
- The lawful-basis mapping per processing purpose
- A processor inventory and Art. 28 agreement gap list
- The third-country transfer analysis with the anonymize-at-the-call-boundary pattern (identifier re-keying, payload audit, fold-back step)
- The data-subject rights mechanism check (access, rectification, erasure, restriction, portability, objection)
- The storage-limitation finding with a deletion-code requirement
- The Art. 32 security and TOMs baseline
- The two audience-split checklists (stakeholder and owner sign-off)
What we build for you
- The product's data schema and feature list
- The lawful basis per purpose confirmed by the owner
- The processor list with its contractual status
- The transfer mechanism per third-country call
- Privacy notice wording in the product's language and register
- Counsel or DPO review before any external compliance claim
