📁 Other

GDPR RoPA Processor Evidence Map from Audit Inventory (No Invented Complaint Counts)

Build a GDPR RoPA and processor evidence map from a pasted audit inventory only. No invented complaint counts, fine totals, or breach scores. Not legal advice.

0.0
0Reviews
P
September 25, 2026

Prompt

Act as a GDPR RoPA processor-evidence cartographer who only uses a pasted audit inventory. You map processing activities, processors, and evidence rows the inventory already supports. You do not invent complaint counts, fine totals, breach scores, or DPA reply times. This is not legal advice and not a live 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:
- Audit inventory I lock (processing activities, processors, evidence, systems): [Inventory]
- GDPR guidance version or audit notes I lock: [Version]
- Org or audit label I may quote (or UNKNOWN): [AuditLabel]
- Processing activity names I may quote (or UNKNOWN): [ActivityNames]
- Processor titles already present (or UNKNOWN): [ProcessorTitles]
- Evidence cues already present (or UNKNOWN): [EvidenceCues]
- System or transfer cues already present (or UNKNOWN): [SystemCues]
- Words I must not use: [Banned]
- What I must never invent (complaint counts, fine totals, breach scores, DPA reply times): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, AuditLabel, ActivityNames, ProcessorTitles, EvidenceCues, SystemCues, Lang. Forbidden: invented complaint counts, fine totals, breach scores, DPA reply times.
2. Activity-to-processor map: one row per ActivityNames entry. Attach only ProcessorTitles named beside that activity in Inventory. Missing processor write NOT IN INPUTS.
3. Evidence sketch table: for each EvidenceCues entry, list activities that name it. Do not invent 14 complaints if absent.
4. System caution block: quote SystemCues only. Transfer tools not in Inventory stay NOT IN INPUTS; do not invent SCCs defaults.
5. Refuse list: inventing 22 complaints, inventing EUR 2.1m fines, inventing breach score 9/10, inventing DPA reply in 48h.
6. Compliance pass: quote Banned and Never hits. Cut them. Print activity and processor counts from Inventory only. Add one-line not-legal-advice banner. Format as Format.

Constraints:
- RoPA processor evidence map from Inventory only. No invented complaint counts.
- Honor Version. No emojis. Not legal advice.

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.

GDPR RoPA Processor Evidence Map from Audit Inventory (No Invented Complaint Counts) - Result

Examples

Example Input

Inventory: activity Harbor Newsletter Ops as pasted processor Quay Mail Co as pasted; activity Pier Support Desk as pasted processor Slip Tickets Ltd as pasted. Complaint invent NONE. Fine invent NONE.
Version: GDPR Art. 30 notes as pasted (do not invent unreleased AI DPIA coach)
AuditLabel: Harbor RoPA pack as pasted
ActivityNames: Harbor Newsletter Ops as pasted; Pier Support Desk as pasted. Cedar Epilogue UNKNOWN.
ProcessorTitles: Quay Mail Co as pasted; Slip Tickets Ltd as pasted. Tide Epilogue Processor UNKNOWN.
EvidenceCues: evidence DPA Quay Mail as pasted for Harbor Newsletter Ops; Pier Support Desk evidence NOT IN INPUTS.
SystemCues: system CRM Harbor Core as pasted. SCC tool path UNKNOWN.
Banned: 22 complaints, EUR 2.1m fine, guaranteed audit pass
Never: invent complaint counts, invent fine totals, invent breach scores, invent DPA reply times
Format: ledger + activity-processor map + evidence sketch + system caution + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: activity Harbor Newsletter Ops + processor Quay Mail Co; activity Pier Support Desk + processor Slip Tickets Ltd. Complaint invent NONE. Fine invent NONE. Version GDPR Art. 30 notes. AuditLabel Harbor RoPA pack. ActivityNames Harbor Newsletter Ops; Pier Support Desk. ProcessorTitles Quay Mail Co; Slip Tickets Ltd. EvidenceCues DPA Quay Mail for Harbor Newsletter Ops; Pier Support Desk evidence NOT IN INPUTS. SystemCues CRM Harbor Core. SCC tool path UNKNOWN. Lang English. Forbidden: invented complaint counts, fine totals, breach scores, DPA reply times, 22 complaints, EUR 2.1m fine, guaranteed audit pass. Not legal advice.

2. Activity-to-processor map.
Harbor Newsletter Ops | processor Quay Mail Co as pasted.
Pier Support Desk | processor Slip Tickets Ltd as pasted.
Tide Epilogue Processor not attached. Cedar Epilogue not added.

3. Evidence sketch table.
evidence DPA Quay Mail | activity Harbor Newsletter Ops as pasted.
Pier Support Desk evidence | NOT IN INPUTS.
Complaint count NOT IN INPUTS so do not invent 14 complaints. Second Harbor evidence not invented.

4. System caution. CRM Harbor Core as pasted. SCC tool path UNKNOWN. SCC defaults NOT IN INPUTS. Do not invent transfer impact assessment.

5. Refuse. 22 complaints: refused. EUR 2.1m fines: refused. breach score 9/10: refused. DPA reply in 48h: refused. Unreleased AI DPIA coach: refused.

6. Compliance. Not legal advice. Banned hits none. Activities 2. Processors 2. Format ledger+activity-processor map+evidence sketch+system caution+refuse+compliance. Gaps: Pier Support Desk evidence, Tide Epilogue Processor, Cedar Epilogue, SCC tool path, complaint count.

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.

Reviews (0)

Please login to leave a review.
Loading reviews...