[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADS2SS1P81Q9FCF9VCYD9X":3,"skill-same:01M6ADS2SS1P81Q9FCF9VCYD9X":102},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6ADS2SS1P81Q9FCF9VCYD9X","cookie-consent-ab-audit",null,"Methodology for auditing A\u002FB testing of consent banners to ensure compliance with equal ease of acceptance and rejection. Covers CNIL enforcement patterns including the EUR 150M Google fine, dark pattern detection methodology, manipulative design identification, and regulatory-compliant experimentation boundaries.","mukul975\u002FPrivacy-Data-Protection-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADNKWX1HF4Q5DKEXT5M774",336,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fconsent-management-skills\u002Fskills\u002Fcookie-consent-ab-audit\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[35,36,37,38,39,40,41,42,43],"audit","cookie consent ab audit","testing","design","google","pattern detection","acceptance","compliance","privacy","2026-11-10 10:12:30",false,"---\nname: cookie-consent-ab-audit\ndescription: >-\n  Methodology for auditing A\u002FB testing of consent banners to ensure compliance with\n  equal ease of acceptance and rejection. Covers CNIL enforcement patterns including\n  the EUR 150M Google fine, dark pattern detection methodology, manipulative design\n  identification, and regulatory-compliant experimentation boundaries.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: consent-management\n  tags: \"cookie-consent-ab-testing, dark-patterns, cnil-enforcement, consent-banner, deceptive-design\"\n---\n\n# Auditing Cookie Consent A\u002FB Testing\n\n## Overview\n\nA\u002FB testing consent banners is a common practice to optimize consent rates. However, when these experiments manipulate users into consenting through design asymmetry, deceptive patterns, or unequal ease of acceptance versus rejection, they violate GDPR Article 7 and ePrivacy Directive Article 5(3). The CNIL has been the most active enforcer, issuing a EUR 150 million fine to Google (January 2022) and a EUR 60 million fine to Meta (January 2022) specifically for consent banner design violations.\n\n## Regulatory Framework for Consent Banner Design\n\n### Equal Prominence Requirement\n\nCNIL Deliberation No. 2020-091 (September 17, 2020) and EDPB Guidelines 05\u002F2020 establish:\n\n1. **Equal Visual Weight**: The \"Accept\" and \"Reject\" options must have the same visual prominence — same size, same color treatment, same font, same position hierarchy.\n2. **Equal Interaction Cost**: Rejecting cookies must require the same number of clicks\u002Fsteps as accepting.\n3. **No Pre-Selection**: No purposes or vendors may be pre-selected.\n4. **No Cookie Walls**: Access to content must not be conditioned on cookie acceptance.\n5. **Neutral Language**: Neither option should use encouraging or discouraging language asymmetrically.\n\n### Key Enforcement Actions\n\n| Authority | Target | Fine | Date | Key Finding |\n|-----------|--------|------|------|-------------|\n| CNIL | Google LLC | EUR 150,000,000 | January 6, 2022 | google.fr: accepting cookies required 1 click; rejecting required multiple clicks through secondary menu |\n| CNIL | Meta Platforms Ireland | EUR 60,000,000 | January 6, 2022 | facebook.com: \"Accept Cookies\" button prominently displayed; \"Refuse\" buried in secondary layer |\n| CNIL | Microsoft Ireland | EUR 60,000,000 | December 22, 2022 | bing.com: \"Accept\" button displayed without equally visible \"Refuse\" |\n| CNIL | TikTok | EUR 5,000,000 | December 29, 2022 | tiktok.com: rejecting cookies more complex than accepting; insufficient information |\n| Italian Garante | Clearview AI | EUR 20,000,000 | March 9, 2022 | No valid consent mechanism for biometric data processing |\n\n## Dark Pattern Detection Methodology\n\n### Category 1: Visual Asymmetry\n\n**What to check:**\n- Accept button: color, size, font weight, border, shadow, position\n- Reject button: color, size, font weight, border, shadow, position\n- Are they visually equal? A bright green \"Accept All\" next to a grey text-link \"Manage Preferences\" fails this test.\n\n**Measurement:**\n- Button area (width x height in pixels)\n- Color contrast ratio against background (WCAG calculation)\n- Font size and weight\n- Visual hierarchy position (above vs below the fold, left vs right)\n\n### Category 2: Interaction Asymmetry\n\n**What to check:**\n- Clicks to accept all: typically 1 (click \"Accept All\")\n- Clicks to reject all: should be 1 (click \"Reject All\") — NOT 2+ (click \"Manage\" then toggle then \"Save\")\n- Is a \"Reject All\" button present on the first layer?\n\n**CNIL standard:** A \"Refuse All\" button must be available on the same layer and with the same prominence as the \"Accept All\" button.\n\n### Category 3: Language Manipulation\n\n**What to check:**\n- Accept text: neutral or encouraging? (\"Accept and continue enjoying our site\")\n- Reject text: neutral or discouraging? (\"I don't want a personalized experience\")\n- Is the reject option framed as losing something?\n\n**Examples of non-compliant language:**\n- Accept: \"Accept and enjoy personalized content\" \u002F Reject: \"Continue with limited experience\" — FAIL\n- Accept: \"OK, I agree\" \u002F Reject: \"Reject all cookies\" — PASS (both neutral)\n\n### Category 4: Timing and Delay Manipulation\n\n**What to check:**\n- Does the accept button appear before the reject button?\n- Is there a loading delay on the reject path?\n- Does dismissing the banner (X button) default to accepting?\n\n### Category 5: Repeated Prompting (Nagging)\n\n**What to check:**\n- After rejecting, does the banner reappear on the next page?\n- How frequently is reconsent requested?\n- CNIL recommends no more than every 6 months.\n\n## A\u002FB Test Compliance Boundaries\n\nWhat can be legitimately tested:\n\n| Permitted Tests | Prohibited Tests |\n|----------------|-----------------|\n| Banner position (top vs bottom) | Accept button larger than reject button |\n| Color scheme (both buttons same treatment) | Accept button more prominent than reject |\n| Text wording (both options equally neutral) | Additional clicks required to reject |\n| Layout arrangement (if equal prominence maintained) | Pre-selecting consent purposes in one variant |\n| Icon usage (same for both options) | Cookie wall in any variant |\n| Animation\u002Ftransition style | Accept-only first layer with reject buried |\n| Privacy information presentation format | Discouraging language for reject option |\n\n## Audit Procedure\n\n### Step 1: Capture All A\u002FB Variants\n\nFor each active consent banner experiment:\n- Screenshot all variants across desktop and mobile\n- Record the HTML\u002FCSS for accept and reject elements\n- Document the user flow for accepting and rejecting in each variant\n- Note the traffic split (what percentage of users see each variant)\n\n### Step 2: Apply Dark Pattern Assessment\n\nFor each variant, score against the 5 categories:\n\n| Category | Weight | Score (0-10) | Notes |\n|----------|--------|-------------|-------|\n| Visual Asymmetry | 25% | 0 = equal, 10 = extreme asymmetry | |\n| Interaction Asymmetry | 30% | 0 = equal clicks, 10 = many more clicks to reject | |\n| Language Manipulation | 20% | 0 = neutral, 10 = strongly manipulative | |\n| Timing\u002FDelay | 15% | 0 = no delays, 10 = significant delays on reject | |\n| Repeated Prompting | 10% | 0 = respects choice, 10 = constant nagging | |\n\n**Overall Risk Score:** Weighted sum. Score above 3.0 requires remediation. Score above 5.0 requires immediate removal.\n\n### Step 3: Compare Consent Rates Across Variants\n\nIf a variant achieves significantly higher consent rates through design asymmetry rather than improved information, this is evidence of manipulation:\n\n- **Baseline comparison**: Compare consent rates between fully symmetric designs\n- **Red flag threshold**: If a variant achieves >20% higher consent rate AND has asymmetric design elements, flag for review\n- **Statistical significance**: Use standard A\u002FB testing statistical methods (chi-squared or Bayesian) but apply the regulatory lens — statistical significance of manipulation is evidence of violation\n\n### Step 4: Document and Report\n\nGenerate audit report with:\n- Screenshots of all variants\n- Dark pattern scores per variant\n- Consent rate analysis\n- Recommendations for non-compliant variants\n- Remediation timeline\n\n## Key Regulatory References\n\n- GDPR Article 7 — Conditions for consent (equal ease, freely given)\n- ePrivacy Directive Article 5(3) — Consent for cookies and similar technologies\n- CNIL Deliberation No. 2020-091 — Cookie and tracker guidelines\n- CNIL Deliberation No. 2022-013 — Google fine (EUR 150M)\n- CNIL Deliberation No. 2022-014 — Meta fine (EUR 60M)\n- EDPB Guidelines 05\u002F2020 — Consent under Regulation 2016\u002F679\n- EDPB Guidelines 3\u002F2022 — Dark patterns in social media platform interfaces\n- FTC Report on Dark Patterns (September 2022) — US perspective on manipulative design\n","# Auditing Cookie Consent A\u002FB Testing\n\n## Overview\n\nA\u002FB testing consent banners is a common practice to optimize consent rates. However, when these experiments manipulate users into consenting through design asymmetry, deceptive patterns, or unequal ease of acceptance versus rejection, they violate GDPR Article 7 and ePrivacy Directive Article 5(3). The CNIL has been the most active enforcer, issuing a EUR 150 million fine to Google (January 2022) and a EUR 60 million fine to Meta (January 2022) specifically for consent banner design violations.\n\n## Regulatory Framework for Consent Banner Design\n\n### Equal Prominence Requirement\n\nCNIL Deliberation No. 2020-091 (September 17, 2020) and EDPB Guidelines 05\u002F2020 establish:\n\n1. **Equal Visual Weight**: The \"Accept\" and \"Reject\" options must have the same visual prominence — same size, same color treatment, same font, same position hierarchy.\n2. **Equal Interaction Cost**: Rejecting cookies must require the same number of clicks\u002Fsteps as accepting.\n3. **No Pre-Selection**: No purposes or vendors may be pre-selected.\n4. **No Cookie Walls**: Access to content must not be conditioned on cookie acceptance.\n5. **Neutral Language**: Neither option should use encouraging or discouraging language asymmetrically.\n\n### Key Enforcement Actions\n\n| Authority | Target | Fine | Date | Key Finding |\n|-----------|--------|------|------|-------------|\n| CNIL | Google LLC | EUR 150,000,000 | January 6, 2022 | google.fr: accepting cookies required 1 click; rejecting required multiple clicks through secondary menu |\n| CNIL | Meta Platforms Ireland | EUR 60,000,000 | January 6, 2022 | facebook.com: \"Accept Cookies\" button prominently displayed; \"Refuse\" buried in secondary layer |\n| CNIL | Microsoft Ireland | EUR 60,000,000 | December 22, 2022 | bing.com: \"Accept\" button displayed without equally visible \"Refuse\" |\n| CNIL | TikTok | EUR 5,000,000 | December 29, 2022 | tiktok.com: rejecting cookies more complex than accepting; insufficient information |\n| Italian Garante | Clearview AI | EUR 20,000,000 | March 9, 2022 | No valid consent mechanism for biometric data processing |\n\n## Dark Pattern Detection Methodology\n\n### Category 1: Visual Asymmetry\n\n**What to check:**\n- Accept button: color, size, font weight, border, shadow, position\n- Reject button: color, size, font weight, border, shadow, position\n- Are they visually equal? A bright green \"Accept All\" next to a grey text-link \"Manage Preferences\" fails this test.\n\n**Measurement:**\n- Button area (width x height in pixels)\n- Color contrast ratio against background (WCAG calculation)\n- Font size and weight\n- Visual hierarchy position (above vs below the fold, left vs right)\n\n### Category 2: Interaction Asymmetry\n\n**What to check:**\n- Clicks to accept all: typically 1 (click \"Accept All\")\n- Clicks to reject all: should be 1 (click \"Reject All\") — NOT 2+ (click \"Manage\" then toggle then \"Save\")\n- Is a \"Reject All\" button present on the first layer?\n\n**CNIL standard:** A \"Refuse All\" button must be available on the same layer and with the same prominence as the \"Accept All\" button.\n\n### Category 3: Language Manipulation\n\n**What to check:**\n- Accept text: neutral or encouraging? (\"Accept and continue enjoying our site\")\n- Reject text: neutral or discouraging? (\"I don't want a personalized experience\")\n- Is the reject option framed as losing something?\n\n**Examples of non-compliant language:**\n- Accept: \"Accept and enjoy personalized content\" \u002F Reject: \"Continue with limited experience\" — FAIL\n- Accept: \"OK, I agree\" \u002F Reject: \"Reject all cookies\" — PASS (both neutral)\n\n### Category 4: Timing and Delay Manipulation\n\n**What to check:**\n- Does the accept button appear before the reject button?\n- Is there a loading delay on the reject path?\n- Does dismissing the banner (X button) default to accepting?\n\n### Category 5: Repeated Prompting (Nagging)\n\n**What to check:**\n- After rejecting, does the banner reappear on the next page?\n- How frequently is reconsent requested?\n- CNIL recommends no more than every 6 months.\n\n## A\u002FB Test Compliance Boundaries\n\nWhat can be legitimately tested:\n\n| Permitted Tests | Prohibited Tests |\n|----------------|-----------------|\n| Banner position (top vs bottom) | Accept button larger than reject button |\n| Color scheme (both buttons same treatment) | Accept button more prominent than reject |\n| Text wording (both options equally neutral) | Additional clicks required to reject |\n| Layout arrangement (if equal prominence maintained) | Pre-selecting consent purposes in one variant |\n| Icon usage (same for both options) | Cookie wall in any variant |\n| Animation\u002Ftransition style | Accept-only first layer with reject buried |\n| Privacy information presentation format | Discouraging language for reject option |\n\n## Audit Procedure\n\n### Step 1: Capture All A\u002FB Variants\n\nFor each active consent banner experiment:\n- Screenshot all variants across desktop and mobile\n- Record the HTML\u002FCSS for accept and reject elements\n- Document the user flow for accepting and rejecting in each variant\n- Note the traffic split (what percentage of users see each variant)\n\n### Step 2: Apply Dark Pattern Assessment\n\nFor each variant, score against the 5 categories:\n\n| Category | Weight | Score (0-10) | Notes |\n|----------|--------|-------------|-------|\n| Visual Asymmetry | 25% | 0 = equal, 10 = extreme asymmetry | |\n| Interaction Asymmetry | 30% | 0 = equal clicks, 10 = many more clicks to reject | |\n| Language Manipulation | 20% | 0 = neutral, 10 = strongly manipulative | |\n| Timing\u002FDelay | 15% | 0 = no delays, 10 = significant delays on reject | |\n| Repeated Prompting | 10% | 0 = respects choice, 10 = constant nagging | |\n\n**Overall Risk Score:** Weighted sum. Score above 3.0 requires remediation. Score above 5.0 requires immediate removal.\n\n### Step 3: Compare Consent Rates Across Variants\n\nIf a variant achieves significantly higher consent rates through design asymmetry rather than improved information, this is evidence of manipulation:\n\n- **Baseline comparison**: Compare consent rates between fully symmetric designs\n- **Red flag threshold**: If a variant achieves >20% higher consent rate AND has asymmetric design elements, flag for review\n- **Statistical significance**: Use standard A\u002FB testing statistical methods (chi-squared or Bayesian) but apply the regulatory lens — statistical significance of manipulation is evidence of violation\n\n### Step 4: Document and Report\n\nGenerate audit report with:\n- Screenshots of all variants\n- Dark pattern scores per variant\n- Consent rate analysis\n- Recommendations for non-compliant variants\n- Remediation timeline\n\n## Key Regulatory References\n\n- GDPR Article 7 — Conditions for consent (equal ease, freely given)\n- ePrivacy Directive Article 5(3) — Consent for cookies and similar technologies\n- CNIL Deliberation No. 2020-091 — Cookie and tracker guidelines\n- CNIL Deliberation No. 2022-013 — Google fine (EUR 150M)\n- CNIL Deliberation No. 2022-014 — Meta fine (EUR 60M)\n- EDPB Guidelines 05\u002F2020 — Consent under Regulation 2016\u002F679\n- EDPB Guidelines 3\u002F2022 — Dark patterns in social media platform interfaces\n- FTC Report on Dark Patterns (September 2022) — US perspective on manipulative design\n",{"name":5,"license":15,"metadata":49,"description":7},{"tags":50,"author":9,"domain":43,"version":51,"subdomain":52},"cookie-consent-ab-testing, dark-patterns, cnil-enforcement, consent-banner, deceptive-design","1.0","consent-management","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fconsent-management-skills\u002Fskills\u002Fcookie-consent-ab-audit",67,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-03-17 04:06:52",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill cookie-consent-ab-audit",{"tool":68,"command":69},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill cookie-consent-ab-audit",{"tool":71,"command":72},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill cookie-consent-ab-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fconsent-management-skills\u002Fskills\u002Fcookie-consent-ab-audit\u002FSKILL.md",true,[76,82,88,92,96],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Ftemplate.md","ASSET","资产文件",3695,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fconsent-management-skills\u002Fskills\u002Fcookie-consent-ab-audit\u002Fassets\u002Ftemplate.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"package.json","REFERENCE","参考文档",822,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsandbox-packs\u002Fsandbox-pdflib\u002Fpackage.json",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandards.md",3900,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fconsent-management-skills\u002Fskills\u002Fcookie-consent-ab-audit\u002Freferences\u002Fstandards.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflows.md",6346,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fconsent-management-skills\u002Fskills\u002Fcookie-consent-ab-audit\u002Freferences\u002Fworkflows.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fprocess.py","SCRIPT","脚本",13807,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fconsent-management-skills\u002Fskills\u002Fcookie-consent-ab-audit\u002Fscripts\u002Fprocess.py",[103,122,139,152,169,182],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":114,"publishedAt":44},"01M6AG6K8R3XW10ENWH2FH18RH","workplace-email-privacy","Implements email and internet monitoring compliance in the workplace per Barbulescu v Romania (ECHR Grand Chamber), EDPB guidance, and national labour law. Covers acceptable use policies, legitimate expectation of privacy, proportionality testing, and content vs metadata monitoring. Keywords: email monitoring, Barbulescu, workplace privacy, internet monitoring, acceptable use policy, ECHR, proportionality.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fworkplace-email-privacy\u002FSKILL.md",[109,112,113],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[115,116,43,42,117,118,119,37,120,121],"email","workplace email privacy","content","data","policy","monitoring","metadata",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":132,"publishedAt":44},"01M6AG6FRCBJY7D061BJZMNV49","whistleblower-data","Implements data protection compliance for whistleblowing systems under EU Directive 2019\u002F1937 and GDPR. Covers anonymous reporting channels, identity protection for whistleblowers and accused persons, retention limits, access restrictions, and retaliation prevention. Addresses national transpositions and DPA guidance. Keywords: whistleblower, Directive 2019\u002F1937, anonymous reporting, identity protection, retaliation, retention, reporting channel.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fwhistleblower-data\u002FSKILL.md",[128,131],{"categoryNo":129,"categoryName":130,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[118,133,134,135,42,136,137,43,138],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":44},"01M6AG6CJP0PW3X65HC7VP9SR9","vendor-termination-data","Vendor termination data return and deletion procedures per GDPR Article 28(3)(g). Covers data extraction formats, deletion certification requirements, transition planning, residual data handling, and post-termination verification.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-termination-data\u002FSKILL.md",[145],{"categoryNo":129,"categoryName":130,"taxonomyType":29,"taxonomyTypeDesc":30},[118,147,148,149,150,137,43,151],"vendor termination data","planning","verification","extraction","certification",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":44},"01M6AG69E277DXZB2NF6KV17ZA","vendor-risk-scoring","Vendor privacy risk tiering methodology for processor management. Covers scoring factors including data volume, sensitivity, transfer locations, certifications, breach history, and control maturity with weighted risk calculation and tier assignment.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-risk-scoring\u002FSKILL.md",[158],{"categoryNo":129,"categoryName":130,"taxonomyType":29,"taxonomyTypeDesc":30},[160,161,162,163,164,165,166,167,43,118,168],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","assessment","transfer","certifications","processor",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":44},"01M6AG6655ABFKT2BBWHCP4PAT","vendor-privacy-due-diligence","Pre-contract vendor privacy due diligence per GDPR Article 28(1). Covers risk questionnaires, technical controls assessment, certification review, data flow analysis, and documented sufficiency decisions for processor engagement.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-privacy-due-diligence\u002FSKILL.md",[175],{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[43,177,137,178,165,179,180,118,168,161,151,181],"vendor privacy due diligence","review","onboarding","flow","analysis",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":195,"publishedAt":44},"01M6AG62C3VD8SYNGH4N7RHZTE","vendor-privacy-audit","On-site and remote vendor audit procedures per GDPR Article 28(3)(h). Covers audit planning, evidence collection methodologies, finding classification, remediation tracking, and audit report generation for processor compliance verification.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-privacy-audit\u002FSKILL.md",[188,191,194],{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":192,"categoryName":193,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[196,35,43,197,149,198,42,137,199,168,200,201,202,148],"vendor privacy audit","report","audit report","remediation","collection","remediation-tracking","classification"]