---
name: gdpr-data-processing-record
description: "Drafts a GDPR Article 30 record of processing entry for one activity, covering purposes, data categories, recipients, transfers, retention and security. Use when a data controller or DPO must document one processing activity in a GDPR Article 30 register entry. Do not use for drafting a privacy policy or running a full data protection impact assessment. Related topics: legal, compliance, gdpr."
---

# GDPR Data Processing Record

Drafts a GDPR Article 30 record of processing entry for one activity, covering purposes, data categories, recipients, transfers, retention and security.

## When to use

Use this skill when a data controller or DPO must document one processing activity in a GDPR Article 30 register entry. Do not use it for drafting a privacy policy or running a full data protection impact assessment.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Map each input to the Article 30(1) field it belongs in.
3. Flag extra conditions for special category data, children and transfers outside the EEA.
4. Mark each required field that the inputs do not answer as a gap.
5. List open questions and add a note that the entry should be confirmed by a qualified person.

## Inputs

- **Activity name** (free text, e.g. "Customer email marketing")
- **Data controller name** (free text, e.g. "your organisation name")
- **Controller contact or DPO** (free text, e.g. "name and email")
- **Processing purpose** (longer free text)
- **Categories of data subjects** (choose any: Customers, Employees, Website visitors, Job applicants, Suppliers, Children, Other)
- **Categories of personal data** (choose any: Name and contact details, Financial data, Health data, Location data, Online identifiers, Biometric data, Special category data)
- **Data retention period** (free text, e.g. "3 years from last interaction")
- **Legal basis** (choose one: Consent, Contract performance, Legal obligation, Vital interests, Public task, Legitimate interests)
- **Data transferred outside the EEA** (choose one: Yes, No)
- **Security measures** (choose any: Encryption, Access controls, Pseudonymisation, Regular audits, Staff training)

## Output

A table-form ROPA entry with the Article 30(1) fields completed, flagged gaps, and a closing list of open questions.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### GDPR Article 30 Record Entry

Draft a Record of Processing Activities entry for one processing activity.

- Activity name: {{Activity name}}
- Data controller name: {{Data controller name}}
- Controller contact or DPO: {{Controller contact or DPO}}
- Processing purpose: {{Processing purpose}}
- Categories of data subjects: {{Categories of data subjects}}
- Categories of personal data: {{Categories of personal data}}
- Data retention period: {{Data retention period}}
- Legal basis: {{Legal basis}}
- Data transferred outside the EEA: {{Data transferred outside the EEA}}
- Security measures: {{Security measures}}

Write the entry as a table with the Article 30(1) fields: controller details, purposes, categories of subjects and data, recipients, third-country transfers with safeguards, retention periods and a general description of security measures. If special category data or children are selected, flag the extra Article 9 condition or parental consent needed. If a transfer is outside the EEA, name a mechanism to check, such as an adequacy decision or standard contractual clauses. Mark every field you could not complete from the inputs as a gap.

End with a list of open questions and a note that a qualified person should confirm the entry.

## Pitfalls

- Naming a legal basis that does not fit the purpose, such as consent for payroll.
- Leaving transfers and safeguards blank when data goes outside the EEA.
- Describing security measures vaguely instead of naming those in use.
