📁 Other
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.
0Reviews
Prompt
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.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Notes: purpose Harbor Dock visitor badge logging as pasted; categories name as pasted; email as pasted; systems BadgeDesk as pasted. Retention NONE. DPIA IDs NOT IN INPUTS. Version: GDPR Article 30 ROPA notes as pasted (do not invent EDPB 2026 invent) Controller: Harbor Facilities Unit as pasted Categories: name as pasted; email as pasted. Special category UNKNOWN. Systems: BadgeDesk as pasted. Cloud host UNKNOWN. Banned: guaranteed compliant, DPIA invent, retention invent, DPO email invent Never: invent DPIA IDs, invent retention periods, invent DPO emails, invent SCC clauses Format: ledger + ROPA row + categories + version + refuse + compliance Lang: English
Example Output
1. Ledger. Notes: purpose Harbor Dock visitor badge logging; categories name; email; systems BadgeDesk. Retention NONE. DPIA IDs NOT IN INPUTS. Version GDPR Article 30 ROPA notes. Controller Harbor Facilities Unit. Categories name; email; Special category UNKNOWN. Systems BadgeDesk; Cloud host UNKNOWN. Lang English. Forbidden: invented DPIA IDs, retention periods, DPO emails, SCC clauses, guaranteed compliant, DPIA invent, retention invent, DPO email invent. Banner: Not legal advice. De-identify any personal data beyond Notes. 2. ROPA row draft (GDPR Article 30). Purpose: Harbor Dock visitor badge logging as pasted. Categories: name as pasted; email as pasted. Systems: BadgeDesk as pasted. Recipients: NOT IN INPUTS beyond Notes. Retention: NONE so write NOT IN INPUTS. DPIA IDs: NOT IN INPUTS. 3. Categories lock. name as pasted. email as pasted. Special category UNKNOWN so write NOT IN INPUTS. Do not invent health data category. 4. Version lock. GDPR Article 30 ROPA notes as pasted. EDPB 2026 invent not used. 5. Refuse. DPIA invent: refused. Retention invent: refused. DPO email invent: refused. Guaranteed compliant: refused. SCC invent: refused. 6. Compliance. Banned hits none. Format ledger+ROPA row+categories+version+refuse+compliance. Gaps: retention policy, cloud host, recipients list, transfer basis, DPO contact if any. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.