Receber por email
← Voltar para o catálogo

gdpr-compliance

Ensure GDPR compliance for marketing activities including consent management, data processing, privacy notices, and data subject rights

126estrelas
Atualizado há 7 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add guia-matthieu/clawfu-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/gdpr-compliance-guia-matthieu/svg)](https://www.skillteca.com.br/skills/gdpr-compliance-guia-matthieu)

Skills relacionadas

Ver todas de Dados e Análise →

Alerta por categoria

Receba novas skills de Dados e Análise toda segunda

1 email curto, só com as skills novas de Dados e Análise. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

GDPR Compliance for Marketing

Ensure your marketing activities comply with GDPR requirements for consent, data processing, and privacy rights.

When to Use This Skill

  • Designing consent collection flows
  • Writing privacy notices
  • Auditing marketing data practices
  • Handling data subject requests
  • Documenting lawful basis

Methodology Foundation

Based on GDPR Articles 6, 7, 12-23 and EDPB Guidelines, covering:

  • Lawful basis determination
  • Consent requirements
  • Transparency obligations
  • Data subject rights
  • Documentation requirements

What Claude Does vs What You Decide

| Claude Does | You Decide | |-------------|------------| | Explains GDPR requirements | Business risk tolerance | | Drafts compliant language | Implementation priority | | Identifies gaps | Legal interpretation | | Creates documentation | DPO consultation needs | | Suggests controls | Resource allocation |

Instructions

Step 1: Lawful Basis Assessment

Six Lawful Bases (Article 6):

| Basis | Marketing Use | Documentation Needed | |-------|---------------|----------------------| | Consent | Email marketing, cookies, tracking | Consent records | | Contract | Customer communications | Contract terms | | Legitimate Interest | Soft opt-in, B2B marketing | LIA document | | Legal Obligation | Regulatory comms | Legal reference | | Vital Interest | Rarely applicable | - | | Public Task | Rarely applicable | - |

Marketing Activity Mapping:

| Activity | Typical Basis | Requirements | |----------|---------------|--------------| | Email newsletter | Consent | Double opt-in, easy unsubscribe | | Existing customer upsell | Legitimate Interest | LIA, opt-out available | | Cold B2B outreach | Legitimate Interest | LIA, clear identity | | Website cookies | Consent | Banner, granular choices | | Retargeting ads | Consent | Cookie consent | | Lead magnets | Consent | Clear purpose, separate consent |

Step 2: Consent Requirements

Valid Consent Criteria (Article 7): | Requirement | What It Means | Example | |-------------|---------------|---------| | Freely given | No bundling, no penalty | Separate from T&Cs | | Specific | Clear purpose stated | "Marketing emails about [X]" | | Informed | Who, what, why explained | Privacy notice linked | | Unambiguous | Clear affirmative action | Unchecked checkbox | | Withdrawable | Easy to revoke | One-click unsubscribe |

Consent Record Requirements:

Record for each consent:
- Who consented (identifier)
- When (timestamp)
- What they consented to (purpose)
- How (mechanism)
- What they were told (notice version)

Step 3: Privacy Notice Requirements

Required Elements (Articles 13-14):

| Element | First-Party Data | Third-Party Data | |---------|------------------|------------------| | Controller identity | Required | Required | | DPO contact | If applicable | If applicable | | Purposes | Required | Required | | Lawful basis | Required | Required | | Recipients | Required | Required | | Transfers | If applicable | If applicable | | Retention | Required | Required | | Rights | Required | Required | | Withdrawal | If consent | If consent | | Complaint right | Required | Required | | Source | N/A | Required |

Step 4: Data Subject Rights

Rights Framework:

| Right | Timeline | Marketing Impact | |-------|----------|------------------| | Access (Art. 15) | 1 month | Provide all marketing data | | Rectification (Art. 16) | 1 month | Update preferences | | Erasure (Art. 17) | 1 month | Remove from lists | | Restriction (Art. 18) | 1 month | Pause processing | | Portability (Art. 20) | 1 month | Export in machine format | | Objection (Art. 21) | Immediate for marketing | Stop direct marketing |

Step 5: Documentation & Records

Required Documentation:

  1. Records of Processing Activities (ROPA)
  2. Legitimate Interest Assessments
  3. Consent records and mechanisms
  4. Privacy notices (versioned)
  5. Data Subject Request log
  6. Breach notification procedures

Examples

Example 1: Marketing Email Consent Flow

Input:

Design a GDPR-compliant consent flow for:
- SaaS product newsletter
- Product updates
- Promotional offers
- Third-party partner offers

Output:

## GDPR-Compliant Email Consent Flow

### Consent Collection UI

---

**Signup Form Fields:**

Email: [________________]

[ ] I agree to receive the monthly newsletter with industry insights [ ] I agree to receive product updates and feature announcements [ ] I agree to receive promotional offers and discounts [ ] I agree to receive relevant offers from our trusted partners

[Sign Up]

By signing up, you confirm you've read our [Privacy Notice]. You can withdraw consent anytime via unsubscribe link or contacting us.


**Design Requirements:**
- All checkboxes unchecked by default
- No "select all" option
- Each purpose separate
- Privacy notice linked, not buried
- No dark patterns

---

### Consent Record Structure

{ "email": "user@example.com", "consents": [ { "purpose": "newsletter", "granted": true, "timestamp": "2026-01-31T10:30:00Z", "source": "signup_form_v3", "notice_version": "privacy_v2.1" }, { "purpose": "product_updates", "granted": true, "timestamp": "2026-01-31T10:30:00Z", "source": "signup_form_v3", "notice_version": "privacy_v2.1" }, { "purpose": "promotional", "granted": false, "timestamp": null, "source": null, "notice_version": null }, { "purpose": "third_party", "granted": false, "timestamp": null, "source": null, "notice_version": null } ], "ip_address": "192.168.1.1", "user_agent": "Mozilla/5.0..." }


---

### Email Footer (Required)

You're receiving this because you subscribed to our [newsletter/updates].

Manage preferences: [link] Unsubscribe from this list: [link] Unsubscribe from all: [link]

[Company Name] [Address] [Contact Email]


---

### Preference Center

| Subscription | Status | Action |
|--------------|--------|--------|
| Monthly Newsletter | [ON/OFF] | Industry insights and tips |
| Product Updates | [ON/OFF] | New features and improvements |
| Promotional Offers | [ON/OFF] | Discounts and special deals |
| Partner Offers | [ON/OFF] | Relevant third-party offers |

[Update Preferences] [Unsubscribe from All]

---

### Compliance Checklist

- [ ] All consents granular (separate checkboxes)
- [ ] Checkboxes unchecked by default
- [ ] Clear description of each purpose
- [ ] Privacy notice accessible
- [ ] Withdrawal mechanism clear
- [ ] Consent records stored
- [ ] Double opt-in implemented
- [ ] Unsubscribe in every email
- [ ] Preference center available

Example 2: Legitimate Interest Assessment

Input:

We want to email our existing customers about related products.
Do we need consent or can we use legitimate interest?

Output:

## Legitimate Interest Assessment: Customer Cross-Sell

### Summary

You can likely rely on legitimate interest (not consent) for
emailing existing customers about **similar** products, but must
complete this assessment and offer easy opt-out.

---

### Three-Part LIA Test

#### 1. Purpose Test: Is There a Legitimate Interest?

**Interest:** Promote related products to existing customers
**Legitimacy:** Yes - recognized business interest in customer development
**Benefit:** Revenue growth, customer relationship deepening

✅ **PASS**

---

#### 2. Necessity Test: Is Processing Necessary?

| Question | Answer |
|----------|--------|
| Is email necessary to achieve the interest? | Yes - direct communication channel |
| Is there a less intrusive way? | In-app notifications possible but less effective |
| Is the processing proportionate? | Yes - limited frequency, relevant content |

✅ **PASS** (with conditions)

**Conditions:**
- Limit to genuinely related products
- Reasonable frequency (not daily)
-
Compartilhar X LinkedIn