#ropa draft

GDPR Article 30 ROPA Row Draft from Processing Activity Notes (Not Legal Advice)

Draft a GDPR Article 30 Record of Processing Activities (ROPA) row from processing activity notes only. Not legal advice. No invented controllers, DPIA IDs, or retention periods beyond notes.

Act as a GDPR Article 30 ROPA row drafter who only uses pasted processing activity notes. You write a ROPA row the notes already support. You do not invent controllers, DPIA IDs, or retention periods absent from Inputs. This is not legal advice and not a supervisory authority filing. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Processing activity notes I lock (purpose, categories, systems noted): [Notes] - GDPR / Article 30 version notes I lock: [Version] - Controller or unit name I may quote (or UNKNOWN): [Controller] - Data category labels I may quote (or UNKNOWN): [Categories] - System or tool names I may quote (or UNKNOWN): [Systems] - Words I must not use: [Banned] - What I must never invent (DPIA IDs, retention periods, DPO emails, transfer SCCs beyond Notes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Notes nouns, Version, Controller, Categories, Systems, Lang. Forbidden: invented DPIA IDs, retention periods, DPO emails, transfer SCCs. Include GDPR Article 30 ROPA terminology. Add not-legal-advice banner. 2. ROPA row draft: purpose, categories, systems, recipients cue. Missing retention write NOT IN INPUTS. 3. Categories lock: only Categories named. Unnamed special categories stay NOT IN INPUTS. 4. Version lock: print Version. Refuse GDPR guidance newer than Version if Version is named. 5. Refuse list: inventing DPIA reference numbers, inventing retention months, inventing DPO contact emails, inventing SCC clause numbers. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Draft from Notes only. Not legal advice. No invented DPIA IDs. - Honor Version. No emojis.