mukul975/privacy-data-protection-skills

nist-pf-communicate

- Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW awareness raising and CM.PO communication policies.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill nist-pf-communicate

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

NIST Privacy Framework — COMMUNICATE Function

Overview

The 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.

COMMUNICATE Function Subcategories

CM.AW — Awareness

Raising awareness of data processing practices and privacy risks among stakeholders.

SubcategoryDescriptionImplementation Guidance
CM.AW-P1Mechanisms (e.g., notices, internal policies) for communicating data processing purposes, practices, and associated privacy risks are established and in servicePublish layered privacy notices. Maintain internal data processing documentation. Establish communication channels for privacy inquiries.
CM.AW-P2Mechanisms for obtaining feedback from individuals about data processing and associated privacy risks are established and in serviceDeploy feedback forms on privacy pages. Monitor privacy-related inquiries through support channels. Conduct periodic privacy perception surveys.
CM.AW-P3System/product/service design enables data processing visibilityImplement privacy dashboards for data subjects. Provide real-time data processing status. Enable granular consent visibility.
CM.AW-P4Records of data disclosures and sharing are maintained and can be accessed for review or transmissionMaintain disclosure registers. Enable data subjects to view sharing history. Automate disclosure logging.
CM.AW-P5Data corrections or deletions can be communicated to individuals or organizations that have received the dataImplement downstream notification workflows. Track data recipients for correction propagation. Automate deletion verification across partners.
CM.AW-P6Data provenance and lineage are maintained and can be accessed for review or transmissionDocument data origins and transformation history. Provide lineage visualization. Enable audit trail access for authorized parties.
CM.AW-P7Impacted individuals and organizations are notified about a privacy breach or eventDevelop breach notification templates. Establish notification timelines per jurisdiction. Maintain contact information for notification delivery.
CM.AW-P8Individuals are provided with mitigation mechanisms for observed privacy risksOffer identity protection services post-breach. Provide self-service privacy controls. Communicate available remediation options.

CM.PO — Communication Policies

Policies governing how privacy-related information is communicated.

SubcategoryDescriptionImplementation Guidance
CM.PO-P1Transparency 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 serviceDevelop layered transparency framework. Define communication standards for each audience.
CM.PO-P2Roles and responsibilities for communicating privacy-related information are establishedAssign communications ownership. Define approval workflows for external privacy communications.

Transparency Framework

Layered Privacy Notice Architecture

Layer 1: Short Notice (Banner/Summary)
├── Who we are
├── What data we collect
├── Key purposes
├── Core rights
└── Link to full notice

Layer 2: Full Privacy Notice
├── Detailed purposes and legal bases
├── Data categories and sources
├── Recipients and transfers
├── Retention periods
├── Complete rights information
├── Contact information
└── Links to supplementary notices

Layer 3: Supplementary Notices
├── Cookie Policy
├── Children's Privacy Notice
├── Employee Privacy Notice
├── Specific Service Notices
└── Jurisdiction-Specific Addenda

Layer 4: Just-in-Time Notices
├── Collection-point notifications
├── Consent requests with context
├── Purpose-specific explanations
└── Processing change notifications

Communication Channel Matrix

AudienceChannelFrequencyContent TypeOwner
Data subjects (general)Website privacy centerContinuousNotices, policies, FAQsPrivacy Team
Data subjects (customers)Email, in-app notificationsEvent-drivenConsent changes, updatesMarketing + Privacy
Data subjects (employees)Intranet, HR portalSemi-annual + eventEmployee privacy infoHR + Privacy
RegulatorsFormal correspondenceAs requiredCompliance reports, notificationsLegal + DPO
Business partnersContract addenda, portalAnnual + eventProcessing terms, audit rightsLegal + Procurement
Board/executivesDashboards, presentationsQuarterlyRisk reports, KPIsCPO
Internal teamsConfluence, trainingMonthlyGuidelines, best practicesPrivacy Champions

Privacy Notice Content Requirements

Mandatory Elements by Regulation

ElementGDPR Art. 13/14CCPA/CPRALGPDPIPEDA
Controller identityRequiredRequiredRequiredRequired
DPO contactRequiredN/ARequired (DPO equivalent)N/A
Processing purposesRequiredRequiredRequiredRequired
Legal basisRequiredN/ARequiredN/A
Data categoriesRequiredRequiredRequiredRequired
RecipientsRequiredRequiredRequiredRequired
International transfersRequiredN/ARequiredRequired
Retention periodsRequiredDisclosed on requestRequiredRequired
Data subject rightsRequiredRequiredRequiredRequired
Right to complainRequiredN/ARequiredRequired
Automated decision-makingRequiredCPRA: RequiredRequiredN/A
Data source (indirect collection)RequiredRequiredRequiredRequired
Sale/sharing opt-outN/ARequiredN/AN/A
Financial incentive termsN/ARequiredN/AN/A

Stakeholder Engagement Workflows

Data Subject Inquiry Handling

Inquiry Received
    |
    v
Classify Inquiry Type
├── General Privacy Question → FAQ/Knowledge Base → Respond within 5 business days
├── Data Subject Request → Route to DSR Workflow → Respond within regulatory deadline
├── Complaint → Escalate to DPO → Investigate → Respond within 15 business days
├── Breach Inquiry → Route to Incident Team → Coordinate response
└── Consent Change → Process immediately → Confirm within 24 hours

Privacy Communication Approval Workflow

Communication TypeDraftingReviewApprovalDistribution
Privacy policy updatePrivacy TeamLegalCPO + General CounselWeb team
Breach notificationIncident LeadLegal + DPOCEO + General CounselCommunications
Regulatory responseDPOLegalGeneral CounselDPO
Marketing consent requestMarketingPrivacy TeamCPOMarketing
Internal policy updatePrivacy TeamStakeholdersCPOInternal comms

Feedback Mechanisms

Privacy Perception Survey Template (Annual)

  1. How aware are you of our privacy practices? (1-5 scale)
  2. How easy is it to find information about how we use your data? (1-5 scale)
  3. How confident are you that we protect your personal data? (1-5 scale)
  4. Have you exercised any privacy rights in the past 12 months? (Yes/No, which ones)
  5. How satisfied were you with the response? (1-5 scale, if applicable)
  6. What privacy improvements would you like to see? (Open text)
  7. How likely are you to recommend us based on our privacy practices? (0-10 NPS)

Control Mapping

NIST PF COMMUNICATEISO 27701GDPR ArticleAPEC CBPR
CM.AW-P1A.7.3.2Art. 12, 13, 14Principle 5
CM.AW-P2A.7.3.8Art. 77Principle 9
CM.AW-P3A.7.2.5Art. 12(1)Principle 5
CM.AW-P4A.7.5.3Art. 19Principle 7
CM.AW-P7A.7.3.9Art. 34Principle 8
CM.PO-P1A.7.3.2Art. 12Principle 5
CM.PO-P25.3Art. 37-39Principle 9

References

  • NIST Privacy Framework Version 1.0 (January 16, 2020)
  • Article 29 Working Party WP260 — Guidelines on Transparency
  • EDPB Guidelines 04/2022 on Calculation of Administrative Fines
  • ISO/IEC 29100:2011 — Privacy Framework (Privacy Principles)

Related by task

from this repository

More skills

All skills
mukul975
Community

applying-privacy-design-patterns

- Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate. Covers pattern selection methodology per processing activity, mapping to GDPR principles, and practical implementation guidance for privacy-by-design system architecture.

installs
1
GitHub stars
315
Updated
Mar 16
mukul975
Community

brazil-lgpd

- Guides compliance with Brazil's Lei Geral de Proteção de Dados (LGPD, Lei 13.709/2018). Covers the 10 lawful bases under Art. 7, DPO appointment, ANPD enforcement, data subject rights under Arts. 17-22, and international transfer mechanisms. Keywords: LGPD, Brazil data protection, ANPD, lawful bases, data subject rights, international transfers.

installs
1
GitHub stars
315
Updated
Mar 16
mukul975
Community

adequacy-assessment

- Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

installs
1
GitHub stars
295
Updated
Mar 16
mukul975
Community

age-gating-services

- Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

installs
1
GitHub stars
295
Updated
Mar 16