[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEKXVG30KMMMDBVC9Y0B7H":3,"skill-same:01M6AEKXVG30KMMMDBVC9Y0B7H":80},{"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":18,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6AEKXVG30KMMMDBVC9Y0B7H","connecticut-ctdpa",null,"Connecticut Data Privacy Act (CTDPA) compliance. Covers consumer rights, controller obligations, dark pattern prohibition, loyalty program exemption, universal opt-out requirement effective January 2025, sensitive data consent, and AG enforcement. Effective July 1, 2023.","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\u002Fprivacy-skills-complete\u002Fskills\u002Fconnecticut-ctdpa\u002FSKILL.md",[],[19,20,21,22,23,24,25],"connecticut ctdpa","state","compliance","data privacy","privacy","data","controller","2026-11-10 10:12:30",false,"---\nname: connecticut-ctdpa\ndescription: >-\n  Connecticut Data Privacy Act (CTDPA) compliance. Covers consumer rights,\n  controller obligations, dark pattern prohibition, loyalty program\n  exemption, universal opt-out requirement effective January 2025,\n  sensitive data consent, and AG enforcement. Effective July 1, 2023.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: us-state-privacy-laws\n  tags: \"ctdpa, connecticut-privacy, dark-patterns, loyalty-program, universal-opt-out\"\n---\n\n# Connecticut Data Privacy Act (CTDPA)\n\n## Overview\n\nThe Connecticut Data Privacy Act (CTDPA), codified as Conn. Gen. Stat. §42-515 through §42-525, was signed into law on May 10, 2022 (SB 6), and became effective July 1, 2023. Connecticut was the fifth state to enact comprehensive consumer privacy legislation. The CTDPA is notable for its explicit prohibition on dark patterns in obtaining consent, its bona fide loyalty program exemption, and its requirement to recognize universal opt-out mechanisms (effective January 1, 2025).\n\n## Applicability (§42-516)\n\nThe CTDPA applies to persons that conduct business in Connecticut or produce products or services targeted to Connecticut residents AND during the preceding calendar year:\n\n1. Controlled or processed personal data of at least 100,000 Connecticut consumers (excluding data processed solely for payment transactions); OR\n2. Controlled or processed personal data of at least 25,000 Connecticut consumers AND derived more than 25% of gross revenue from the sale of personal data.\n\n**Note:** The 25% revenue threshold is lower than Virginia's 50% and mirrors no specific percentage in Colorado.\n\n**Exemptions:** State\u002Flocal government, GLBA institutions (entity-level), HIPAA covered entities\u002FBAs (entity-level), nonprofits, higher education institutions, and data governed by certain federal statutes.\n\n**Liberty Commerce Inc. Assessment:**\nLiberty Commerce Inc. processes personal data of approximately 87,000 Connecticut consumers. With 12% advertising revenue from data sale activities, it does not meet threshold (2). However, excluding payment-only transactions, the consumer count exceeds the threshold under a conservative reading. Liberty Commerce Inc. treats itself as subject to the CTDPA.\n\n## Consumer Rights (§42-520)\n\n### Six Consumer Rights\n\n1. **Right to Access** (§42-520(a)(1)): Confirm processing and access personal data\n2. **Right to Correct** (§42-520(a)(2)): Correct inaccuracies\n3. **Right to Delete** (§42-520(a)(3)): Delete personal data\n4. **Right to Portability** (§42-520(a)(4)): Obtain data in portable, readily usable format\n5. **Right to Opt Out** (§42-520(a)(5)): Opt out of:\n   - Targeted advertising\n   - Sale of personal data\n   - Profiling in furtherance of decisions producing legal or similarly significant effects\n6. **Right to Appeal** (§42-520(f)): Appeal a denial of any rights request\n\n### Response Requirements (§42-520(b)-(e))\n- Respond within 45 days of receipt\n- Extension: up to 45 additional days with notice\n- At least one free response per 12 months per right\n- Appeal: controller must respond within 60 days\n\n## Dark Pattern Prohibition (§42-515(8), §42-518(a)(5))\n\nThe CTDPA explicitly defines and prohibits dark patterns in the context of obtaining consumer consent. A \"dark pattern\" is defined as:\n\n> \"A user interface designed or manipulated with the substantial effect of subverting or impairing user autonomy, decision-making or choice, and includes, but is not limited to, any practice the Federal Trade Commission refers to as a 'dark pattern'.\"\n\n### Implications\n\n- Consent obtained through dark patterns is **not valid consent** under the CTDPA\n- Applies to consent for sensitive data processing (§42-518(a)(5))\n- Applies to consent for processing children's data\n- Any consent mechanism that uses confusing language, hidden options, visual manipulation, or other deceptive practices is invalid\n\n### Dark Pattern Examples (per FTC guidance and CTDPA legislative history)\n\n| Pattern | Description | CTDPA Impact |\n|---------|-------------|-------------|\n| Confirm-shaming | Using guilt-inducing language for the opt-out option | Consent invalid |\n| Hidden options | Making the reject\u002Fdecline option visually less prominent | Consent invalid |\n| Forced action | Requiring consent to access unrelated features | Consent invalid |\n| Trick questions | Using double negatives or confusing language | Consent invalid |\n| Misdirection | Visual design that steers users toward consent | Consent invalid |\n| Nagging | Repeated prompts after consumer declines | Consent invalid |\n\n**Liberty Commerce Inc. Implementation:**\nLiberty Commerce Inc. has conducted a dark pattern audit of all consent interfaces. Consent buttons use equal visual weight (same size, same font, same color prominence). \"Accept\" and \"Decline\" options are presented side by side. Language is affirmative and clear. No confirm-shaming language is used.\n\n## Bona Fide Loyalty Program Exemption (§42-517(c))\n\nThe CTDPA provides an exemption for bona fide loyalty, rewards, premium, discount, or club card programs. Personal data collected as part of such programs is exempt from the sale opt-out right if:\n\n1. The program is a bona fide loyalty program (genuine value provided to the consumer)\n2. The consumer voluntarily participates\n3. The controller clearly discloses the data collection in the loyalty program terms\n4. The data is used solely for the purpose of the loyalty program\n\n**Liberty Commerce Inc. Implementation:**\nLiberty Commerce Inc. operates the \"Liberty Rewards\" program. The program terms clearly state that purchase history and preference data are used exclusively for rewards calculation, personalized offers within the program, and member benefits. This data is not sold or used for cross-context behavioral advertising outside the loyalty program scope.\n\n## Universal Opt-Out Mechanism (§42-520(a)(6))\n\nEffective January 1, 2025, controllers must recognize universal opt-out mechanisms. Requirements parallel Colorado's framework:\n\n- Must recognize and process universal opt-out signals (including GPC)\n- Signal applies to targeted advertising and sale of personal data\n- No additional consumer verification required\n- No pop-up or interstitial questioning the signal\n- Apply at browser\u002Fdevice level for unauthenticated; account level for authenticated\n\n## Sensitive Data (§42-518(a)(5))\n\n### Categories\nSame as Virginia VCDPA:\n1. Racial or ethnic origin\n2. Religious beliefs\n3. Mental or physical health condition or diagnosis\n4. Sexual orientation\n5. Citizenship or immigration status\n6. Genetic or biometric data for identification\n7. Personal data of a known child\n8. Precise geolocation data\n\n### Consent Requirement\nProcessing requires **opt-in consent** that is not obtained through a dark pattern.\n\n## Controller Obligations (§42-518)\n\n1. **Purpose limitation**: Limit processing to what is adequate, relevant, and reasonably necessary\n2. **Data minimization**: Do not collect more than reasonably necessary\n3. **Data security**: Appropriate technical and organizational measures\n4. **Non-discrimination**: No processing in violation of antidiscrimination laws\n5. **Sensitive data consent**: Obtain consent (not via dark pattern) before processing\n6. **Privacy notice**: Reasonably accessible and clear\n7. **DPIAs**: Conduct assessments for targeted advertising, sale, profiling, sensitive data, and high-risk processing\n\n## Enforcement (§42-524, §42-525)\n\n- **Exclusive AG enforcement** — no private right of action\n- **60-day cure period** until December 31, 2024\n- **After January 1, 2025**: AG has discretion on cure period\n- **Penalties**: Treated as unfair trade practices under Conn. Gen. Stat. §42-110b (CUTPA)\n- **Civil penalties**: Up to $5,000 per willful violation under CUTPA\n\n## Key Regulatory References\n\n- Conn. Gen. Stat. §42-515 through §42-525 (CTDPA)\n- Conn. Gen. Stat. §42-110b (Connecticut Unfair Trade Practices Act — enforcement)\n- FTC Dark Patterns Report (September 2022) — referenced in CTDPA definition\n- Global Privacy Control Specification v1.0 — recognized universal opt-out mechanism\n","# Connecticut Data Privacy Act (CTDPA)\n\n## Overview\n\nThe Connecticut Data Privacy Act (CTDPA), codified as Conn. Gen. Stat. §42-515 through §42-525, was signed into law on May 10, 2022 (SB 6), and became effective July 1, 2023. Connecticut was the fifth state to enact comprehensive consumer privacy legislation. The CTDPA is notable for its explicit prohibition on dark patterns in obtaining consent, its bona fide loyalty program exemption, and its requirement to recognize universal opt-out mechanisms (effective January 1, 2025).\n\n## Applicability (§42-516)\n\nThe CTDPA applies to persons that conduct business in Connecticut or produce products or services targeted to Connecticut residents AND during the preceding calendar year:\n\n1. Controlled or processed personal data of at least 100,000 Connecticut consumers (excluding data processed solely for payment transactions); OR\n2. Controlled or processed personal data of at least 25,000 Connecticut consumers AND derived more than 25% of gross revenue from the sale of personal data.\n\n**Note:** The 25% revenue threshold is lower than Virginia's 50% and mirrors no specific percentage in Colorado.\n\n**Exemptions:** State\u002Flocal government, GLBA institutions (entity-level), HIPAA covered entities\u002FBAs (entity-level), nonprofits, higher education institutions, and data governed by certain federal statutes.\n\n**Liberty Commerce Inc. Assessment:**\nLiberty Commerce Inc. processes personal data of approximately 87,000 Connecticut consumers. With 12% advertising revenue from data sale activities, it does not meet threshold (2). However, excluding payment-only transactions, the consumer count exceeds the threshold under a conservative reading. Liberty Commerce Inc. treats itself as subject to the CTDPA.\n\n## Consumer Rights (§42-520)\n\n### Six Consumer Rights\n\n1. **Right to Access** (§42-520(a)(1)): Confirm processing and access personal data\n2. **Right to Correct** (§42-520(a)(2)): Correct inaccuracies\n3. **Right to Delete** (§42-520(a)(3)): Delete personal data\n4. **Right to Portability** (§42-520(a)(4)): Obtain data in portable, readily usable format\n5. **Right to Opt Out** (§42-520(a)(5)): Opt out of:\n   - Targeted advertising\n   - Sale of personal data\n   - Profiling in furtherance of decisions producing legal or similarly significant effects\n6. **Right to Appeal** (§42-520(f)): Appeal a denial of any rights request\n\n### Response Requirements (§42-520(b)-(e))\n- Respond within 45 days of receipt\n- Extension: up to 45 additional days with notice\n- At least one free response per 12 months per right\n- Appeal: controller must respond within 60 days\n\n## Dark Pattern Prohibition (§42-515(8), §42-518(a)(5))\n\nThe CTDPA explicitly defines and prohibits dark patterns in the context of obtaining consumer consent. A \"dark pattern\" is defined as:\n\n> \"A user interface designed or manipulated with the substantial effect of subverting or impairing user autonomy, decision-making or choice, and includes, but is not limited to, any practice the Federal Trade Commission refers to as a 'dark pattern'.\"\n\n### Implications\n\n- Consent obtained through dark patterns is **not valid consent** under the CTDPA\n- Applies to consent for sensitive data processing (§42-518(a)(5))\n- Applies to consent for processing children's data\n- Any consent mechanism that uses confusing language, hidden options, visual manipulation, or other deceptive practices is invalid\n\n### Dark Pattern Examples (per FTC guidance and CTDPA legislative history)\n\n| Pattern | Description | CTDPA Impact |\n|---------|-------------|-------------|\n| Confirm-shaming | Using guilt-inducing language for the opt-out option | Consent invalid |\n| Hidden options | Making the reject\u002Fdecline option visually less prominent | Consent invalid |\n| Forced action | Requiring consent to access unrelated features | Consent invalid |\n| Trick questions | Using double negatives or confusing language | Consent invalid |\n| Misdirection | Visual design that steers users toward consent | Consent invalid |\n| Nagging | Repeated prompts after consumer declines | Consent invalid |\n\n**Liberty Commerce Inc. Implementation:**\nLiberty Commerce Inc. has conducted a dark pattern audit of all consent interfaces. Consent buttons use equal visual weight (same size, same font, same color prominence). \"Accept\" and \"Decline\" options are presented side by side. Language is affirmative and clear. No confirm-shaming language is used.\n\n## Bona Fide Loyalty Program Exemption (§42-517(c))\n\nThe CTDPA provides an exemption for bona fide loyalty, rewards, premium, discount, or club card programs. Personal data collected as part of such programs is exempt from the sale opt-out right if:\n\n1. The program is a bona fide loyalty program (genuine value provided to the consumer)\n2. The consumer voluntarily participates\n3. The controller clearly discloses the data collection in the loyalty program terms\n4. The data is used solely for the purpose of the loyalty program\n\n**Liberty Commerce Inc. Implementation:**\nLiberty Commerce Inc. operates the \"Liberty Rewards\" program. The program terms clearly state that purchase history and preference data are used exclusively for rewards calculation, personalized offers within the program, and member benefits. This data is not sold or used for cross-context behavioral advertising outside the loyalty program scope.\n\n## Universal Opt-Out Mechanism (§42-520(a)(6))\n\nEffective January 1, 2025, controllers must recognize universal opt-out mechanisms. Requirements parallel Colorado's framework:\n\n- Must recognize and process universal opt-out signals (including GPC)\n- Signal applies to targeted advertising and sale of personal data\n- No additional consumer verification required\n- No pop-up or interstitial questioning the signal\n- Apply at browser\u002Fdevice level for unauthenticated; account level for authenticated\n\n## Sensitive Data (§42-518(a)(5))\n\n### Categories\nSame as Virginia VCDPA:\n1. Racial or ethnic origin\n2. Religious beliefs\n3. Mental or physical health condition or diagnosis\n4. Sexual orientation\n5. Citizenship or immigration status\n6. Genetic or biometric data for identification\n7. Personal data of a known child\n8. Precise geolocation data\n\n### Consent Requirement\nProcessing requires **opt-in consent** that is not obtained through a dark pattern.\n\n## Controller Obligations (§42-518)\n\n1. **Purpose limitation**: Limit processing to what is adequate, relevant, and reasonably necessary\n2. **Data minimization**: Do not collect more than reasonably necessary\n3. **Data security**: Appropriate technical and organizational measures\n4. **Non-discrimination**: No processing in violation of antidiscrimination laws\n5. **Sensitive data consent**: Obtain consent (not via dark pattern) before processing\n6. **Privacy notice**: Reasonably accessible and clear\n7. **DPIAs**: Conduct assessments for targeted advertising, sale, profiling, sensitive data, and high-risk processing\n\n## Enforcement (§42-524, §42-525)\n\n- **Exclusive AG enforcement** — no private right of action\n- **60-day cure period** until December 31, 2024\n- **After January 1, 2025**: AG has discretion on cure period\n- **Penalties**: Treated as unfair trade practices under Conn. Gen. Stat. §42-110b (CUTPA)\n- **Civil penalties**: Up to $5,000 per willful violation under CUTPA\n\n## Key Regulatory References\n\n- Conn. Gen. Stat. §42-515 through §42-525 (CTDPA)\n- Conn. Gen. Stat. §42-110b (Connecticut Unfair Trade Practices Act — enforcement)\n- FTC Dark Patterns Report (September 2022) — referenced in CTDPA definition\n- Global Privacy Control Specification v1.0 — recognized universal opt-out mechanism\n",{"name":5,"license":15,"metadata":31,"description":7},{"tags":32,"author":9,"domain":23,"version":33,"subdomain":34},"ctdpa, connecticut-privacy, dark-patterns, loyalty-program, universal-opt-out","1.0","us-state-privacy-laws","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fprivacy-skills-complete\u002Fskills\u002Fconnecticut-ctdpa",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill connecticut-ctdpa",{"tool":50,"command":51},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill connecticut-ctdpa",{"tool":53,"command":54},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill connecticut-ctdpa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fconnecticut-ctdpa\u002FSKILL.md",true,[58,64,70,74],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Ftemplate.md","ASSET","资产文件",1692,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fconnecticut-ctdpa\u002Fassets\u002Ftemplate.md",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fstandards.md","REFERENCE","参考文档",3707,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fconnecticut-ctdpa\u002Freferences\u002Fstandards.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fworkflows.md",4882,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fconnecticut-ctdpa\u002Freferences\u002Fworkflows.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Fprocess.py","SCRIPT","脚本",9941,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fconnecticut-ctdpa\u002Fscripts\u002Fprocess.py",[81,108,125,138,155,168],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":100,"publishedAt":26},"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",[87,92,95],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[101,102,23,21,103,24,104,105,106,107],"email","workplace email privacy","content","policy","testing","monitoring","metadata",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":118,"publishedAt":26},"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",[114,117],{"categoryNo":115,"categoryName":116,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[24,119,120,121,21,122,123,23,124],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":26},"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",[131],{"categoryNo":115,"categoryName":116,"taxonomyType":98,"taxonomyTypeDesc":99},[24,133,134,135,136,123,23,137],"vendor termination data","planning","verification","extraction","certification",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":145,"publishedAt":26},"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",[144],{"categoryNo":115,"categoryName":116,"taxonomyType":98,"taxonomyTypeDesc":99},[146,147,148,149,150,151,152,153,23,24,154],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","assessment","transfer","certifications","processor",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":26},"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",[161],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[23,163,123,164,151,165,166,24,154,147,137,167],"vendor privacy due diligence","review","onboarding","flow","analysis",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":181,"publishedAt":26},"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",[174,177,180],{"categoryNo":175,"categoryName":176,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":178,"categoryName":179,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[182,183,23,184,135,185,21,123,186,154,187,188,189,134],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]