[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFJWXANEPPY3WJAX92ZXDF":3,"skill-same:01M6AFJWXANEPPY3WJAX92ZXDF":89},{"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":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6AFJWXANEPPY3WJAX92ZXDF","cookie-audit",null,"Comprehensive methodology for auditing website cookies and tracking technologies. Covers automated scanning, cookie categorization, lifecycle documentation, and compliance gap analysis referencing the Planet49 CJEU ruling (C-673\u002F17).","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\u002Fskills\u002Fprivacy\u002Fcookie-audit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34],"audit","cookie audit","documentation","website","compliance","cookies","privacy","methodology","detection","lifecycle","analysis","2026-11-10 10:12:30",false,"---\nname: cookie-audit\ndescription: >-\n  Comprehensive methodology for auditing website cookies and tracking technologies.\n  Covers automated scanning, cookie categorization, lifecycle documentation, and\n  compliance gap analysis referencing the Planet49 CJEU ruling (C-673\u002F17).\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: cookie-consent-compliance\n  tags: \"cookie-audit, cookie-scanning, tracker-detection, planet49, cookie-categorization\"\n---\n\n# Auditing Website Cookies and Trackers\n\n## Overview\n\nA cookie audit is the foundational step in achieving cookie consent compliance. It involves systematically identifying, categorizing, and documenting every cookie and tracking technology deployed on a website. The Court of Justice of the European Union in Planet49 GmbH v. Bundesverband der Verbraucherzentralen (Case C-673\u002F17, 1 October 2019) established that pre-ticked checkboxes do not constitute valid consent under the ePrivacy Directive, and that users must be informed about cookie duration and third-party access before consenting. A thorough audit reveals what consent must be obtained and what disclosures must be made.\n\n## Audit Methodology\n\n### Phase 1: Preparation\n\nBefore scanning, document the audit scope for Pinnacle E-Commerce Ltd:\n\n| Parameter | Value |\n|-----------|-------|\n| Primary domain | www.pinnacle-ecommerce.com |\n| Subdomains in scope | shop.pinnacle-ecommerce.com, account.pinnacle-ecommerce.com, blog.pinnacle-ecommerce.com |\n| Authenticated pages | Yes — customer account, checkout flow |\n| Mobile-specific pages | m.pinnacle-ecommerce.com |\n| Third-party integrations | Google Analytics 4, Meta Pixel, Hotjar, Stripe, Intercom |\n| Scan frequency | Quarterly (next: Q2 2026) |\n\n### Phase 2: Automated Scanning\n\nDeploy scanning tools to capture all cookies and tracking technologies:\n\n**Browser-Based Scanning**\n\nUse a headless Chromium instance to crawl the site and capture:\n- First-party cookies set via `Set-Cookie` headers\n- First-party cookies set via `document.cookie` JavaScript API\n- Third-party cookies from embedded resources\n- LocalStorage and SessionStorage entries\n- IndexedDB databases\n- Pixels and beacons (1x1 image requests, `navigator.sendBeacon()` calls)\n- Browser fingerprinting scripts (canvas, WebGL, AudioContext)\n\n**Network-Level Capture**\n\nMonitor HTTP\u002FHTTPS traffic to identify:\n- Tracking parameters in URL query strings (utm_*, fbclid, gclid)\n- Redirect chains through tracking domains\n- Cookie syncing between third parties\n- Server-to-server data sharing endpoints\n\n### Phase 3: Cookie Categorization\n\nClassify each cookie using the ICC UK Cookie Guide categories, aligned with the ePrivacy Directive Article 5(3):\n\n**Category 1: Strictly Necessary**\nCookies essential for the website to function. No consent required under Article 5(3) exemption.\n\nExamples for Pinnacle E-Commerce Ltd:\n| Cookie Name | Domain | Duration | Purpose |\n|-------------|--------|----------|---------|\n| session_id | .pinnacle-ecommerce.com | Session | Maintains user session state |\n| csrf_token | .pinnacle-ecommerce.com | Session | Cross-site request forgery protection |\n| cart_items | shop.pinnacle-ecommerce.com | 24 hours | Shopping cart contents |\n| auth_token | account.pinnacle-ecommerce.com | 30 minutes | Authentication state |\n| load_balancer | .pinnacle-ecommerce.com | Session | Server load distribution |\n\n**Category 2: Performance\u002FAnalytics**\nCookies that collect aggregate usage data. Consent required.\n\n| Cookie Name | Domain | Duration | Purpose |\n|-------------|--------|----------|---------|\n| _ga | .pinnacle-ecommerce.com | 2 years | Google Analytics client ID |\n| _ga_XXXXXXX | .pinnacle-ecommerce.com | 2 years | GA4 session persistence |\n| _gid | .pinnacle-ecommerce.com | 24 hours | GA4 session distinction |\n| _hjSessionUser_* | .pinnacle-ecommerce.com | 1 year | Hotjar user identification |\n| _hjSession_* | .pinnacle-ecommerce.com | 30 minutes | Hotjar session data |\n\n**Category 3: Functionality**\nCookies that remember user preferences. Consent required unless strictly necessary.\n\n| Cookie Name | Domain | Duration | Purpose |\n|-------------|--------|----------|---------|\n| locale | .pinnacle-ecommerce.com | 1 year | Language preference |\n| currency | shop.pinnacle-ecommerce.com | 1 year | Currency selection |\n| recently_viewed | shop.pinnacle-ecommerce.com | 30 days | Recently viewed products |\n\n**Category 4: Targeting\u002FAdvertising**\nCookies used for ad targeting and cross-site tracking. Consent always required.\n\n| Cookie Name | Domain | Duration | Purpose |\n|-------------|--------|----------|---------|\n| _fbp | .pinnacle-ecommerce.com | 90 days | Meta Pixel browser ID |\n| _fbc | .pinnacle-ecommerce.com | 90 days | Meta click identifier |\n| _gcl_au | .pinnacle-ecommerce.com | 90 days | Google Ads conversion linker |\n| IDE | .doubleclick.net | 13 months | Google ad serving |\n| fr | .facebook.com | 90 days | Meta ad delivery and measurement |\n\n### Phase 4: Gap Analysis\n\nFor each cookie identified, verify against Planet49 requirements:\n\n**Planet49 Compliance Checklist:**\n\n1. **Active consent mechanism**: Is consent collected via affirmative action (click, toggle), not pre-ticked boxes? (Planet49, para. 62)\n2. **Pre-consent information**: Before consent is given, is the user informed of:\n   - Cookie duration? (Planet49, para. 81)\n   - Whether third parties have access? (Planet49, para. 81)\n   - The specific purpose of each cookie category?\n3. **Granularity**: Can users consent to cookie categories individually, not just accept all?\n4. **No cookie walls**: Is site access available without consenting to non-essential cookies?\n5. **Withdrawal mechanism**: Can users withdraw consent as easily as they gave it?\n\n**Gap Analysis Template:**\n\n| Cookie | Category | Consent Collected | Duration Disclosed | Third-Party Disclosed | Gap |\n|--------|----------|-------------------|--------------------|-----------------------|-----|\n| _ga | Analytics | Yes | No — listed as \"persistent\" not \"2 years\" | No — Google not named | Duration + third-party disclosure |\n| _fbp | Targeting | Yes | Yes | Yes | None |\n| locale | Functionality | No | No | N\u002FA | Assess if strictly necessary |\n\n### Phase 5: Reporting\n\nThe audit report for Pinnacle E-Commerce Ltd must include:\n\n1. **Executive summary**: Total cookies found, breakdown by category, critical gaps\n2. **Complete cookie inventory**: Full table with name, domain, duration, purpose, category, legal basis\n3. **Third-party tracker inventory**: All third-party domains receiving data, with data types shared\n4. **Compliance gap register**: Each gap, severity (high\u002Fmedium\u002Flow), remediation recommendation\n5. **Cookie policy update recommendations**: Specific text changes needed\n6. **Consent mechanism assessment**: Whether current banner meets Planet49 requirements\n7. **Recommended scan schedule**: Quarterly for production, on-demand for new feature deployments\n\n## Ongoing Monitoring\n\nSchedule automated scans to detect new cookies introduced by:\n- Developer deployments (new analytics or marketing tags)\n- Third-party script updates (vendor SDK updates adding new cookies)\n- A\u002FB testing platforms adding experiment cookies\n- CDN or infrastructure changes\n\nIntegrate cookie scanning into the CI\u002FCD pipeline: any new cookie detected in staging must be categorized and documented before deployment to production.\n\n## Key Legal References\n\n- **CJEU Case C-673\u002F17 (Planet49)** — Active consent required; pre-ticked boxes invalid; cookie duration and third-party access must be disclosed before consent\n- **ePrivacy Directive 2002\u002F58\u002FEC, Article 5(3)** — Consent required for storing\u002Faccessing information on user devices, with strictly necessary exemption\n- **GDPR Article 4(11)** — Definition of consent: freely given, specific, informed, unambiguous indication\n- **EDPB Guidelines 05\u002F2020 on Consent** — Detailed guidance on valid consent mechanisms\n- **ICC UK Cookie Guide (2012)** — Cookie categorization framework (strictly necessary, performance, functionality, targeting)\n- **CNIL Deliberation No. 2020-091 (17 September 2020)** — Guidelines on cookies and other trackers\n","# Auditing Website Cookies and Trackers\n\n## Overview\n\nA cookie audit is the foundational step in achieving cookie consent compliance. It involves systematically identifying, categorizing, and documenting every cookie and tracking technology deployed on a website. The Court of Justice of the European Union in Planet49 GmbH v. Bundesverband der Verbraucherzentralen (Case C-673\u002F17, 1 October 2019) established that pre-ticked checkboxes do not constitute valid consent under the ePrivacy Directive, and that users must be informed about cookie duration and third-party access before consenting. A thorough audit reveals what consent must be obtained and what disclosures must be made.\n\n## Audit Methodology\n\n### Phase 1: Preparation\n\nBefore scanning, document the audit scope for Pinnacle E-Commerce Ltd:\n\n| Parameter | Value |\n|-----------|-------|\n| Primary domain | www.pinnacle-ecommerce.com |\n| Subdomains in scope | shop.pinnacle-ecommerce.com, account.pinnacle-ecommerce.com, blog.pinnacle-ecommerce.com |\n| Authenticated pages | Yes — customer account, checkout flow |\n| Mobile-specific pages | m.pinnacle-ecommerce.com |\n| Third-party integrations | Google Analytics 4, Meta Pixel, Hotjar, Stripe, Intercom |\n| Scan frequency | Quarterly (next: Q2 2026) |\n\n### Phase 2: Automated Scanning\n\nDeploy scanning tools to capture all cookies and tracking technologies:\n\n**Browser-Based Scanning**\n\nUse a headless Chromium instance to crawl the site and capture:\n- First-party cookies set via `Set-Cookie` headers\n- First-party cookies set via `document.cookie` JavaScript API\n- Third-party cookies from embedded resources\n- LocalStorage and SessionStorage entries\n- IndexedDB databases\n- Pixels and beacons (1x1 image requests, `navigator.sendBeacon()` calls)\n- Browser fingerprinting scripts (canvas, WebGL, AudioContext)\n\n**Network-Level Capture**\n\nMonitor HTTP\u002FHTTPS traffic to identify:\n- Tracking parameters in URL query strings (utm_*, fbclid, gclid)\n- Redirect chains through tracking domains\n- Cookie syncing between third parties\n- Server-to-server data sharing endpoints\n\n### Phase 3: Cookie Categorization\n\nClassify each cookie using the ICC UK Cookie Guide categories, aligned with the ePrivacy Directive Article 5(3):\n\n**Category 1: Strictly Necessary**\nCookies essential for the website to function. No consent required under Article 5(3) exemption.\n\nExamples for Pinnacle E-Commerce Ltd:\n| Cookie Name | Domain | Duration | Purpose |\n|-------------|--------|----------|---------|\n| session_id | .pinnacle-ecommerce.com | Session | Maintains user session state |\n| csrf_token | .pinnacle-ecommerce.com | Session | Cross-site request forgery protection |\n| cart_items | shop.pinnacle-ecommerce.com | 24 hours | Shopping cart contents |\n| auth_token | account.pinnacle-ecommerce.com | 30 minutes | Authentication state |\n| load_balancer | .pinnacle-ecommerce.com | Session | Server load distribution |\n\n**Category 2: Performance\u002FAnalytics**\nCookies that collect aggregate usage data. Consent required.\n\n| Cookie Name | Domain | Duration | Purpose |\n|-------------|--------|----------|---------|\n| _ga | .pinnacle-ecommerce.com | 2 years | Google Analytics client ID |\n| _ga_XXXXXXX | .pinnacle-ecommerce.com | 2 years | GA4 session persistence |\n| _gid | .pinnacle-ecommerce.com | 24 hours | GA4 session distinction |\n| _hjSessionUser_* | .pinnacle-ecommerce.com | 1 year | Hotjar user identification |\n| _hjSession_* | .pinnacle-ecommerce.com | 30 minutes | Hotjar session data |\n\n**Category 3: Functionality**\nCookies that remember user preferences. Consent required unless strictly necessary.\n\n| Cookie Name | Domain | Duration | Purpose |\n|-------------|--------|----------|---------|\n| locale | .pinnacle-ecommerce.com | 1 year | Language preference |\n| currency | shop.pinnacle-ecommerce.com | 1 year | Currency selection |\n| recently_viewed | shop.pinnacle-ecommerce.com | 30 days | Recently viewed products |\n\n**Category 4: Targeting\u002FAdvertising**\nCookies used for ad targeting and cross-site tracking. Consent always required.\n\n| Cookie Name | Domain | Duration | Purpose |\n|-------------|--------|----------|---------|\n| _fbp | .pinnacle-ecommerce.com | 90 days | Meta Pixel browser ID |\n| _fbc | .pinnacle-ecommerce.com | 90 days | Meta click identifier |\n| _gcl_au | .pinnacle-ecommerce.com | 90 days | Google Ads conversion linker |\n| IDE | .doubleclick.net | 13 months | Google ad serving |\n| fr | .facebook.com | 90 days | Meta ad delivery and measurement |\n\n### Phase 4: Gap Analysis\n\nFor each cookie identified, verify against Planet49 requirements:\n\n**Planet49 Compliance Checklist:**\n\n1. **Active consent mechanism**: Is consent collected via affirmative action (click, toggle), not pre-ticked boxes? (Planet49, para. 62)\n2. **Pre-consent information**: Before consent is given, is the user informed of:\n   - Cookie duration? (Planet49, para. 81)\n   - Whether third parties have access? (Planet49, para. 81)\n   - The specific purpose of each cookie category?\n3. **Granularity**: Can users consent to cookie categories individually, not just accept all?\n4. **No cookie walls**: Is site access available without consenting to non-essential cookies?\n5. **Withdrawal mechanism**: Can users withdraw consent as easily as they gave it?\n\n**Gap Analysis Template:**\n\n| Cookie | Category | Consent Collected | Duration Disclosed | Third-Party Disclosed | Gap |\n|--------|----------|-------------------|--------------------|-----------------------|-----|\n| _ga | Analytics | Yes | No — listed as \"persistent\" not \"2 years\" | No — Google not named | Duration + third-party disclosure |\n| _fbp | Targeting | Yes | Yes | Yes | None |\n| locale | Functionality | No | No | N\u002FA | Assess if strictly necessary |\n\n### Phase 5: Reporting\n\nThe audit report for Pinnacle E-Commerce Ltd must include:\n\n1. **Executive summary**: Total cookies found, breakdown by category, critical gaps\n2. **Complete cookie inventory**: Full table with name, domain, duration, purpose, category, legal basis\n3. **Third-party tracker inventory**: All third-party domains receiving data, with data types shared\n4. **Compliance gap register**: Each gap, severity (high\u002Fmedium\u002Flow), remediation recommendation\n5. **Cookie policy update recommendations**: Specific text changes needed\n6. **Consent mechanism assessment**: Whether current banner meets Planet49 requirements\n7. **Recommended scan schedule**: Quarterly for production, on-demand for new feature deployments\n\n## Ongoing Monitoring\n\nSchedule automated scans to detect new cookies introduced by:\n- Developer deployments (new analytics or marketing tags)\n- Third-party script updates (vendor SDK updates adding new cookies)\n- A\u002FB testing platforms adding experiment cookies\n- CDN or infrastructure changes\n\nIntegrate cookie scanning into the CI\u002FCD pipeline: any new cookie detected in staging must be categorized and documented before deployment to production.\n\n## Key Legal References\n\n- **CJEU Case C-673\u002F17 (Planet49)** — Active consent required; pre-ticked boxes invalid; cookie duration and third-party access must be disclosed before consent\n- **ePrivacy Directive 2002\u002F58\u002FEC, Article 5(3)** — Consent required for storing\u002Faccessing information on user devices, with strictly necessary exemption\n- **GDPR Article 4(11)** — Definition of consent: freely given, specific, informed, unambiguous indication\n- **EDPB Guidelines 05\u002F2020 on Consent** — Detailed guidance on valid consent mechanisms\n- **ICC UK Cookie Guide (2012)** — Cookie categorization framework (strictly necessary, performance, functionality, targeting)\n- **CNIL Deliberation No. 2020-091 (17 September 2020)** — Guidelines on cookies and other trackers\n",{"name":5,"license":15,"metadata":40,"description":7},{"tags":41,"author":9,"domain":30,"version":42,"subdomain":43},"cookie-audit, cookie-scanning, tracker-detection, planet49, cookie-categorization","1.0","cookie-consent-compliance","main","9b2ef9eae161c00a17241d42a388571321b33e9f","skills\u002Fprivacy\u002Fcookie-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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill cookie-audit",{"tool":59,"command":60},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill cookie-audit",{"tool":62,"command":63},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill cookie-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fcookie-audit\u002FSKILL.md",true,[67,73,79,83],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Ftemplate.md","ASSET","资产文件",3869,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fcookie-audit\u002Fassets\u002Ftemplate.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fstandards.md","REFERENCE","参考文档",3024,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fcookie-audit\u002Freferences\u002Fstandards.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fworkflows.md",3091,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fcookie-audit\u002Freferences\u002Fworkflows.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fprocess.py","SCRIPT","脚本",20773,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fcookie-audit\u002Fscripts\u002Fprocess.py",[90,114,131,144,160,172],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":105,"publishedAt":35},"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",[96,101,104],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[106,107,30,28,108,109,110,111,112,113],"email","workplace email privacy","content","data","policy","testing","monitoring","metadata",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":124,"publishedAt":35},"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",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,125,126,127,28,128,129,30,130],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":35},"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",[137],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},[109,139,140,141,142,129,30,143],"vendor termination data","planning","verification","extraction","certification",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":35},"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",[150],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},[152,153,154,31,155,156,157,158,30,109,159],"vendor risk scoring","risk","risk scoring","risk-scoring","assessment","transfer","certifications","processor",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":35},"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",[166],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[30,168,129,169,156,170,171,109,159,153,143,34],"vendor privacy due diligence","review","onboarding","flow",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":185,"publishedAt":35},"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",[178,181,184],{"categoryNo":179,"categoryName":180,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[186,24,30,187,141,188,28,129,189,159,190,191,192,140],"vendor privacy audit","report","audit report","remediation","collection","remediation-tracking","classification"]