EU GDPR Article 33/34 Data Breach Regulatory Notice
30 Production Challenge Scenarios • Real-Time Automated Quality Scoring
Interactive Prompt Engineering Lab
Test and score your prompts against real-world enterprise scenarios. Get immediate 4-axis quality telemetry, negative guardrail verification, and golden reference prompts.
1. Authoritative Persona
Expert role + zero fluff
2. Deterministic Schema
XML tags + JSON / keys
3. Negative Guardrails
NEVER / fallback rules
4. Token Efficiency
150–1,800 chars concise
Enterprise OperationsStaff
EU GDPR Article 33/34 Data Breach Regulatory Notice
A misconfigured S3 bucket exposed 14,200 customer email addresses and hashed passwords for 4 hours before remediation. Draft the formal notification to the Data Protection Authority (DPA) under GDPR Article 33.
Target Input Context / Untrusted Data:
Records Exposed: 14,200 EU user profiles (Name, Email, bcrypt salted password hashes, last login IP) Exposure Duration: 4 hours 12 minutes Remediation: Bucket policy revoked, API keys rotated, CloudTrail forensic audit confirmed 3 IP downloads DPA Deadline: 72 hours from detection.
Quality Requirements & Guardrails:
Define a Chief Privacy & Data Protection Officer (DPO) persona.
Follow the mandatory 4-part GDPR Article 33 structure (Nature of breach, DPO contact, Consequences, Measures taken).
Confirm passwords were encrypted with bcrypt cost factor 12.
Enforce formal legal regulatory terminology.
Your System Prompt Draft
67 chars~17 tokens
Golden Reference Architecture (100% Quality Benchmark)
<system_instructions>
You are the certified Data Protection Officer (DPO) of an enterprise SaaS platform.
Draft the formal Data Breach Notification to the Lead Supervisory Authority in compliance with GDPR Article 33.
STATUTORY REPORTING REQUIREMENTS:
1. NATURE OF BREACH: Describe the unintended exposure of 14,200 records via Amazon S3 bucket policy misconfiguration.
2. CATEGORIES OF DATA: Explicitly clarify that financial data was NOT exposed; data consisted of usernames, emails, and bcrypt salted password hashes (work factor 12).
3. LIKELY CONSEQUENCES: Assess risk to data subjects as low-to-medium due to cryptographic strength of hashes.
4. REMEDIAL ACTIONS TAKEN: Bucket containment within 4 hours, forced session token revocation, and mandatory zero-trust IAM scanning.
5. Output structured report inside <gdpr_article_33_report> tags.
</system_instructions>