[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE9DDYRBAYD55MNF99PR30":3,"skill-same:01M6AE9DDYRBAYD55MNF99PR30":88},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6AE9DDYRBAYD55MNF99PR30","nist-pf-communicate",null,"Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW awareness raising and CM.PO communication policies. Provides transparency mechanisms, stakeholder engagement frameworks, privacy notice templates, and communication workflow guidance.","mukul975\u002FPrivacy-Data-Protection-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADNKWX1HF4Q5DKEXT5M774",337,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-engineering-skills\u002Fskills\u002Fnist-pf-communicate\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33],"NIST","nist pf communicate","implement","workflow","communication","framework","engineering","privacy","awareness","templates","2026-11-10 10:12:30",false,"---\nname: nist-pf-communicate\ndescription: >-\n  Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW\n  awareness raising and CM.PO communication policies. Provides transparency\n  mechanisms, stakeholder engagement frameworks, privacy notice templates,\n  and communication workflow guidance.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: privacy-engineering\n  tags: \"nist-privacy-framework, communicate-function, privacy-transparency, stakeholder-engagement, privacy-notices\"\n---\n\n# NIST Privacy Framework — COMMUNICATE Function\n\n## Overview\n\nThe COMMUNICATE function develops and implements appropriate activities to enable organizations and individuals to have a reliable understanding and engage in a dialogue about how data are processed and associated privacy risks. This function is essential for building trust and ensuring transparency with data subjects, regulators, and business partners.\n\n## COMMUNICATE Function Subcategories\n\n### CM.AW — Awareness\n\nRaising awareness of data processing practices and privacy risks among stakeholders.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| CM.AW-P1 | Mechanisms (e.g., notices, internal policies) for communicating data processing purposes, practices, and associated privacy risks are established and in service | Publish layered privacy notices. Maintain internal data processing documentation. Establish communication channels for privacy inquiries. |\n| CM.AW-P2 | Mechanisms for obtaining feedback from individuals about data processing and associated privacy risks are established and in service | Deploy feedback forms on privacy pages. Monitor privacy-related inquiries through support channels. Conduct periodic privacy perception surveys. |\n| CM.AW-P3 | System\u002Fproduct\u002Fservice design enables data processing visibility | Implement privacy dashboards for data subjects. Provide real-time data processing status. Enable granular consent visibility. |\n| CM.AW-P4 | Records of data disclosures and sharing are maintained and can be accessed for review or transmission | Maintain disclosure registers. Enable data subjects to view sharing history. Automate disclosure logging. |\n| CM.AW-P5 | Data corrections or deletions can be communicated to individuals or organizations that have received the data | Implement downstream notification workflows. Track data recipients for correction propagation. Automate deletion verification across partners. |\n| CM.AW-P6 | Data provenance and lineage are maintained and can be accessed for review or transmission | Document data origins and transformation history. Provide lineage visualization. Enable audit trail access for authorized parties. |\n| CM.AW-P7 | Impacted individuals and organizations are notified about a privacy breach or event | Develop breach notification templates. Establish notification timelines per jurisdiction. Maintain contact information for notification delivery. |\n| CM.AW-P8 | Individuals are provided with mitigation mechanisms for observed privacy risks | Offer identity protection services post-breach. Provide self-service privacy controls. Communicate available remediation options. |\n\n### CM.PO — Communication Policies\n\nPolicies governing how privacy-related information is communicated.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| CM.PO-P1 | Transparency policies, processes, and procedures for communicating data processing purposes, practices, associated privacy risks, and options for enabling data subjects' data processing preferences are established and in service | Develop layered transparency framework. Define communication standards for each audience. |\n| CM.PO-P2 | Roles and responsibilities for communicating privacy-related information are established | Assign communications ownership. Define approval workflows for external privacy communications. |\n\n## Transparency Framework\n\n### Layered Privacy Notice Architecture\n\n```\nLayer 1: Short Notice (Banner\u002FSummary)\n├── Who we are\n├── What data we collect\n├── Key purposes\n├── Core rights\n└── Link to full notice\n\nLayer 2: Full Privacy Notice\n├── Detailed purposes and legal bases\n├── Data categories and sources\n├── Recipients and transfers\n├── Retention periods\n├── Complete rights information\n├── Contact information\n└── Links to supplementary notices\n\nLayer 3: Supplementary Notices\n├── Cookie Policy\n├── Children's Privacy Notice\n├── Employee Privacy Notice\n├── Specific Service Notices\n└── Jurisdiction-Specific Addenda\n\nLayer 4: Just-in-Time Notices\n├── Collection-point notifications\n├── Consent requests with context\n├── Purpose-specific explanations\n└── Processing change notifications\n```\n\n### Communication Channel Matrix\n\n| Audience | Channel | Frequency | Content Type | Owner |\n|----------|---------|-----------|-------------|-------|\n| Data subjects (general) | Website privacy center | Continuous | Notices, policies, FAQs | Privacy Team |\n| Data subjects (customers) | Email, in-app notifications | Event-driven | Consent changes, updates | Marketing + Privacy |\n| Data subjects (employees) | Intranet, HR portal | Semi-annual + event | Employee privacy info | HR + Privacy |\n| Regulators | Formal correspondence | As required | Compliance reports, notifications | Legal + DPO |\n| Business partners | Contract addenda, portal | Annual + event | Processing terms, audit rights | Legal + Procurement |\n| Board\u002Fexecutives | Dashboards, presentations | Quarterly | Risk reports, KPIs | CPO |\n| Internal teams | Confluence, training | Monthly | Guidelines, best practices | Privacy Champions |\n\n## Privacy Notice Content Requirements\n\n### Mandatory Elements by Regulation\n\n| Element | GDPR Art. 13\u002F14 | CCPA\u002FCPRA | LGPD | PIPEDA |\n|---------|-----------------|-----------|------|--------|\n| Controller identity | Required | Required | Required | Required |\n| DPO contact | Required | N\u002FA | Required (DPO equivalent) | N\u002FA |\n| Processing purposes | Required | Required | Required | Required |\n| Legal basis | Required | N\u002FA | Required | N\u002FA |\n| Data categories | Required | Required | Required | Required |\n| Recipients | Required | Required | Required | Required |\n| International transfers | Required | N\u002FA | Required | Required |\n| Retention periods | Required | Disclosed on request | Required | Required |\n| Data subject rights | Required | Required | Required | Required |\n| Right to complain | Required | N\u002FA | Required | Required |\n| Automated decision-making | Required | CPRA: Required | Required | N\u002FA |\n| Data source (indirect collection) | Required | Required | Required | Required |\n| Sale\u002Fsharing opt-out | N\u002FA | Required | N\u002FA | N\u002FA |\n| Financial incentive terms | N\u002FA | Required | N\u002FA | N\u002FA |\n\n## Stakeholder Engagement Workflows\n\n### Data Subject Inquiry Handling\n\n```\nInquiry Received\n    |\n    v\nClassify Inquiry Type\n├── General Privacy Question → FAQ\u002FKnowledge Base → Respond within 5 business days\n├── Data Subject Request → Route to DSR Workflow → Respond within regulatory deadline\n├── Complaint → Escalate to DPO → Investigate → Respond within 15 business days\n├── Breach Inquiry → Route to Incident Team → Coordinate response\n└── Consent Change → Process immediately → Confirm within 24 hours\n```\n\n### Privacy Communication Approval Workflow\n\n| Communication Type | Drafting | Review | Approval | Distribution |\n|-------------------|----------|--------|----------|-------------|\n| Privacy policy update | Privacy Team | Legal | CPO + General Counsel | Web team |\n| Breach notification | Incident Lead | Legal + DPO | CEO + General Counsel | Communications |\n| Regulatory response | DPO | Legal | General Counsel | DPO |\n| Marketing consent request | Marketing | Privacy Team | CPO | Marketing |\n| Internal policy update | Privacy Team | Stakeholders | CPO | Internal comms |\n\n## Feedback Mechanisms\n\n### Privacy Perception Survey Template (Annual)\n\n1. How aware are you of our privacy practices? (1-5 scale)\n2. How easy is it to find information about how we use your data? (1-5 scale)\n3. How confident are you that we protect your personal data? (1-5 scale)\n4. Have you exercised any privacy rights in the past 12 months? (Yes\u002FNo, which ones)\n5. How satisfied were you with the response? (1-5 scale, if applicable)\n6. What privacy improvements would you like to see? (Open text)\n7. How likely are you to recommend us based on our privacy practices? (0-10 NPS)\n\n## Control Mapping\n\n| NIST PF COMMUNICATE | ISO 27701 | GDPR Article | APEC CBPR |\n|---------------------|-----------|--------------|-----------|\n| CM.AW-P1 | A.7.3.2 | Art. 12, 13, 14 | Principle 5 |\n| CM.AW-P2 | A.7.3.8 | Art. 77 | Principle 9 |\n| CM.AW-P3 | A.7.2.5 | Art. 12(1) | Principle 5 |\n| CM.AW-P4 | A.7.5.3 | Art. 19 | Principle 7 |\n| CM.AW-P7 | A.7.3.9 | Art. 34 | Principle 8 |\n| CM.PO-P1 | A.7.3.2 | Art. 12 | Principle 5 |\n| CM.PO-P2 | 5.3 | Art. 37-39 | Principle 9 |\n\n## References\n\n- NIST Privacy Framework Version 1.0 (January 16, 2020)\n- Article 29 Working Party WP260 — Guidelines on Transparency\n- EDPB Guidelines 04\u002F2022 on Calculation of Administrative Fines\n- ISO\u002FIEC 29100:2011 — Privacy Framework (Privacy Principles)\n","# NIST Privacy Framework — COMMUNICATE Function\n\n## Overview\n\nThe COMMUNICATE function develops and implements appropriate activities to enable organizations and individuals to have a reliable understanding and engage in a dialogue about how data are processed and associated privacy risks. This function is essential for building trust and ensuring transparency with data subjects, regulators, and business partners.\n\n## COMMUNICATE Function Subcategories\n\n### CM.AW — Awareness\n\nRaising awareness of data processing practices and privacy risks among stakeholders.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| CM.AW-P1 | Mechanisms (e.g., notices, internal policies) for communicating data processing purposes, practices, and associated privacy risks are established and in service | Publish layered privacy notices. Maintain internal data processing documentation. Establish communication channels for privacy inquiries. |\n| CM.AW-P2 | Mechanisms for obtaining feedback from individuals about data processing and associated privacy risks are established and in service | Deploy feedback forms on privacy pages. Monitor privacy-related inquiries through support channels. Conduct periodic privacy perception surveys. |\n| CM.AW-P3 | System\u002Fproduct\u002Fservice design enables data processing visibility | Implement privacy dashboards for data subjects. Provide real-time data processing status. Enable granular consent visibility. |\n| CM.AW-P4 | Records of data disclosures and sharing are maintained and can be accessed for review or transmission | Maintain disclosure registers. Enable data subjects to view sharing history. Automate disclosure logging. |\n| CM.AW-P5 | Data corrections or deletions can be communicated to individuals or organizations that have received the data | Implement downstream notification workflows. Track data recipients for correction propagation. Automate deletion verification across partners. |\n| CM.AW-P6 | Data provenance and lineage are maintained and can be accessed for review or transmission | Document data origins and transformation history. Provide lineage visualization. Enable audit trail access for authorized parties. |\n| CM.AW-P7 | Impacted individuals and organizations are notified about a privacy breach or event | Develop breach notification templates. Establish notification timelines per jurisdiction. Maintain contact information for notification delivery. |\n| CM.AW-P8 | Individuals are provided with mitigation mechanisms for observed privacy risks | Offer identity protection services post-breach. Provide self-service privacy controls. Communicate available remediation options. |\n\n### CM.PO — Communication Policies\n\nPolicies governing how privacy-related information is communicated.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| CM.PO-P1 | Transparency policies, processes, and procedures for communicating data processing purposes, practices, associated privacy risks, and options for enabling data subjects' data processing preferences are established and in service | Develop layered transparency framework. Define communication standards for each audience. |\n| CM.PO-P2 | Roles and responsibilities for communicating privacy-related information are established | Assign communications ownership. Define approval workflows for external privacy communications. |\n\n## Transparency Framework\n\n### Layered Privacy Notice Architecture\n\n```\nLayer 1: Short Notice (Banner\u002FSummary)\n├── Who we are\n├── What data we collect\n├── Key purposes\n├── Core rights\n└── Link to full notice\n\nLayer 2: Full Privacy Notice\n├── Detailed purposes and legal bases\n├── Data categories and sources\n├── Recipients and transfers\n├── Retention periods\n├── Complete rights information\n├── Contact information\n└── Links to supplementary notices\n\nLayer 3: Supplementary Notices\n├── Cookie Policy\n├── Children's Privacy Notice\n├── Employee Privacy Notice\n├── Specific Service Notices\n└── Jurisdiction-Specific Addenda\n\nLayer 4: Just-in-Time Notices\n├── Collection-point notifications\n├── Consent requests with context\n├── Purpose-specific explanations\n└── Processing change notifications\n```\n\n### Communication Channel Matrix\n\n| Audience | Channel | Frequency | Content Type | Owner |\n|----------|---------|-----------|-------------|-------|\n| Data subjects (general) | Website privacy center | Continuous | Notices, policies, FAQs | Privacy Team |\n| Data subjects (customers) | Email, in-app notifications | Event-driven | Consent changes, updates | Marketing + Privacy |\n| Data subjects (employees) | Intranet, HR portal | Semi-annual + event | Employee privacy info | HR + Privacy |\n| Regulators | Formal correspondence | As required | Compliance reports, notifications | Legal + DPO |\n| Business partners | Contract addenda, portal | Annual + event | Processing terms, audit rights | Legal + Procurement |\n| Board\u002Fexecutives | Dashboards, presentations | Quarterly | Risk reports, KPIs | CPO |\n| Internal teams | Confluence, training | Monthly | Guidelines, best practices | Privacy Champions |\n\n## Privacy Notice Content Requirements\n\n### Mandatory Elements by Regulation\n\n| Element | GDPR Art. 13\u002F14 | CCPA\u002FCPRA | LGPD | PIPEDA |\n|---------|-----------------|-----------|------|--------|\n| Controller identity | Required | Required | Required | Required |\n| DPO contact | Required | N\u002FA | Required (DPO equivalent) | N\u002FA |\n| Processing purposes | Required | Required | Required | Required |\n| Legal basis | Required | N\u002FA | Required | N\u002FA |\n| Data categories | Required | Required | Required | Required |\n| Recipients | Required | Required | Required | Required |\n| International transfers | Required | N\u002FA | Required | Required |\n| Retention periods | Required | Disclosed on request | Required | Required |\n| Data subject rights | Required | Required | Required | Required |\n| Right to complain | Required | N\u002FA | Required | Required |\n| Automated decision-making | Required | CPRA: Required | Required | N\u002FA |\n| Data source (indirect collection) | Required | Required | Required | Required |\n| Sale\u002Fsharing opt-out | N\u002FA | Required | N\u002FA | N\u002FA |\n| Financial incentive terms | N\u002FA | Required | N\u002FA | N\u002FA |\n\n## Stakeholder Engagement Workflows\n\n### Data Subject Inquiry Handling\n\n```\nInquiry Received\n    |\n    v\nClassify Inquiry Type\n├── General Privacy Question → FAQ\u002FKnowledge Base → Respond within 5 business days\n├── Data Subject Request → Route to DSR Workflow → Respond within regulatory deadline\n├── Complaint → Escalate to DPO → Investigate → Respond within 15 business days\n├── Breach Inquiry → Route to Incident Team → Coordinate response\n└── Consent Change → Process immediately → Confirm within 24 hours\n```\n\n### Privacy Communication Approval Workflow\n\n| Communication Type | Drafting | Review | Approval | Distribution |\n|-------------------|----------|--------|----------|-------------|\n| Privacy policy update | Privacy Team | Legal | CPO + General Counsel | Web team |\n| Breach notification | Incident Lead | Legal + DPO | CEO + General Counsel | Communications |\n| Regulatory response | DPO | Legal | General Counsel | DPO |\n| Marketing consent request | Marketing | Privacy Team | CPO | Marketing |\n| Internal policy update | Privacy Team | Stakeholders | CPO | Internal comms |\n\n## Feedback Mechanisms\n\n### Privacy Perception Survey Template (Annual)\n\n1. How aware are you of our privacy practices? (1-5 scale)\n2. How easy is it to find information about how we use your data? (1-5 scale)\n3. How confident are you that we protect your personal data? (1-5 scale)\n4. Have you exercised any privacy rights in the past 12 months? (Yes\u002FNo, which ones)\n5. How satisfied were you with the response? (1-5 scale, if applicable)\n6. What privacy improvements would you like to see? (Open text)\n7. How likely are you to recommend us based on our privacy practices? (0-10 NPS)\n\n## Control Mapping\n\n| NIST PF COMMUNICATE | ISO 27701 | GDPR Article | APEC CBPR |\n|---------------------|-----------|--------------|-----------|\n| CM.AW-P1 | A.7.3.2 | Art. 12, 13, 14 | Principle 5 |\n| CM.AW-P2 | A.7.3.8 | Art. 77 | Principle 9 |\n| CM.AW-P3 | A.7.2.5 | Art. 12(1) | Principle 5 |\n| CM.AW-P4 | A.7.5.3 | Art. 19 | Principle 7 |\n| CM.AW-P7 | A.7.3.9 | Art. 34 | Principle 8 |\n| CM.PO-P1 | A.7.3.2 | Art. 12 | Principle 5 |\n| CM.PO-P2 | 5.3 | Art. 37-39 | Principle 9 |\n\n## References\n\n- NIST Privacy Framework Version 1.0 (January 16, 2020)\n- Article 29 Working Party WP260 — Guidelines on Transparency\n- EDPB Guidelines 04\u002F2022 on Calculation of Administrative Fines\n- ISO\u002FIEC 29100:2011 — Privacy Framework (Privacy Principles)\n",{"name":5,"license":15,"metadata":39,"description":7},{"tags":40,"author":9,"domain":31,"version":41,"subdomain":42},"nist-privacy-framework, communicate-function, privacy-transparency, stakeholder-engagement, privacy-notices","1.0","privacy-engineering","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fprivacy-engineering-skills\u002Fskills\u002Fnist-pf-communicate",68,"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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill nist-pf-communicate",{"tool":58,"command":59},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill nist-pf-communicate",{"tool":61,"command":62},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill nist-pf-communicate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-engineering-skills\u002Fskills\u002Fnist-pf-communicate\u002FSKILL.md",true,[66,72,78,82],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Ftemplate.md","ASSET","资产文件",1578,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-engineering-skills\u002Fskills\u002Fnist-pf-communicate\u002Fassets\u002Ftemplate.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fstandards.md","REFERENCE","参考文档",1334,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-engineering-skills\u002Fskills\u002Fnist-pf-communicate\u002Freferences\u002Fstandards.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fworkflows.md",1805,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-engineering-skills\u002Fskills\u002Fnist-pf-communicate\u002Freferences\u002Fworkflows.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fprocess.py","SCRIPT","脚本",6590,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-engineering-skills\u002Fskills\u002Fnist-pf-communicate\u002Fscripts\u002Fprocess.py",[89,116,133,146,163,176],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":106,"publishedAt":34},"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",[95,98,101],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[107,108,31,109,110,111,112,113,114,115],"email","workplace email privacy","compliance","content","data","policy","testing","monitoring","metadata",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":126,"publishedAt":34},"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",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[111,127,128,129,109,130,131,31,132],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":34},"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",[139],{"categoryNo":123,"categoryName":124,"taxonomyType":104,"taxonomyTypeDesc":105},[111,141,142,143,144,131,31,145],"vendor termination data","planning","verification","extraction","certification",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":34},"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",[152],{"categoryNo":123,"categoryName":124,"taxonomyType":104,"taxonomyTypeDesc":105},[154,155,156,157,158,159,160,161,31,111,162],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","assessment","transfer","certifications","processor",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":170,"publishedAt":34},"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",[169],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[31,171,131,172,159,173,174,111,162,155,145,175],"vendor privacy due diligence","review","onboarding","flow","analysis",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":189,"publishedAt":34},"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",[182,185,188],{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":186,"categoryName":187,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[190,191,31,192,143,193,109,131,194,162,195,196,197,142],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]