[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF9DAWV6BGHFX89JC1EG5V":3,"skill-same:01M6AF9DAWV6BGHFX89JC1EG5V":93},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6AF9DAWV6BGHFX89JC1EG5V","state-law-applicability",null,"US state privacy law applicability assessment tool. Evaluates revenue thresholds, data volume thresholds, business exemptions (GLBA, HIPAA, nonprofits), employee data carve-outs, and SBA small business determinations across all enacted state privacy laws.","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\u002Fus-state-privacy-skills\u002Fskills\u002Fstate-law-applicability\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30],"state","state law applicability","assessment","assessment tool","hipaa","privacy","data","2026-11-10 10:12:30",false,"---\nname: state-law-applicability\ndescription: >-\n  US state privacy law applicability assessment tool. Evaluates revenue\n  thresholds, data volume thresholds, business exemptions (GLBA, HIPAA,\n  nonprofits), employee data carve-outs, and SBA small business\n  determinations across all enacted state privacy laws.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: us-state-privacy-laws\n  tags: \"applicability, thresholds, exemptions, glba, hipaa, small-business\"\n---\n\n# State Privacy Law Applicability Assessment\n\n## Overview\n\nDetermining which US state privacy laws apply to an organization requires evaluating multiple criteria: revenue thresholds, consumer\u002Fdata volume thresholds, industry-specific exemptions, entity-type exemptions, and data-type exemptions. This skill provides a systematic assessment framework and Python automation tool for evaluating applicability across all major enacted state privacy laws.\n\n## Assessment Framework\n\n### Step 1: Geographic Nexus\n\nFor each state, determine if the organization has nexus through:\n- **Conducting business** in the state (physical presence, employees, registered entity)\n- **Targeting residents** of the state (marketing, advertising, or providing products\u002Fservices specifically to state residents)\n- **Producing products\u002Fservices** consumed by state residents\n\nMost state laws use \"conducts business in [state] OR produces products or services targeted to [state] residents\" as the nexus requirement.\n\n### Step 2: Threshold Assessment\n\n| State | Threshold 1 | Threshold 2 | Revenue Alternative |\n|-------|------------|-------------|---------------------|\n| California | 100,000 consumers\u002Fhouseholds | 50% revenue from sale\u002Fsharing | $25,000,000 annual gross revenue |\n| Virginia | 100,000 consumers | 25,000 consumers + 50% revenue from sale | None |\n| Colorado | 100,000 consumers | 25,000 consumers + revenue\u002Fdiscount from sale | None |\n| Connecticut | 100,000 consumers (excl. payment) | 25,000 consumers + 25% revenue from sale | None |\n| Texas | Non-SBA small business | N\u002FA | None (no threshold) |\n| Oregon | 100,000 consumers (excl. payment) | 25,000 consumers + 25% revenue from sale | None |\n| Montana | 50,000 consumers (excl. payment) | 25,000 consumers + 25% revenue from sale | None |\n| Kentucky | 100,000 consumers | 25,000 consumers + 50% revenue from sale | None |\n\n### Step 3: Entity-Level Exemptions\n\n| Exemption | CA | VA | CO | CT | TX | OR | MT | KY |\n|-----------|----|----|----|----|----|----|----|----|\n| Government | N\u002FA (for-profit only) | Exempt | Exempt | Exempt | Exempt | Exempt | Exempt | Exempt |\n| GLBA financial institutions | Data-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level |\n| HIPAA covered entities | Data-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level |\n| Nonprofits | Not exempt | Exempt | Exempt | Exempt | Exempt | **Not exempt** | Exempt | Exempt |\n| Higher education | Not exempt | Exempt | Exempt | Exempt | Exempt | Not exempt | Exempt | Exempt |\n| Air carriers | Not exempt | Not exempt | Not exempt | Not exempt | Not exempt | Not exempt | **Exempt** | Not exempt |\n\n### Step 4: Data-Level Exemptions\n\nData that is already governed by certain federal laws may be exempt even if the organization itself is not:\n\n| Federal Law | Full Name | Data Type |\n|-------------|-----------|-----------|\n| GLBA | Gramm-Leach-Bliley Act (15 U.S.C. §6801) | Financial data under GLBA privacy rules |\n| HIPAA | Health Insurance Portability and Accountability Act (42 U.S.C. §1320d) | Protected health information (PHI) |\n| FERPA | Family Educational Rights and Privacy Act (20 U.S.C. §1232g) | Education records |\n| FCRA | Fair Credit Reporting Act (15 U.S.C. §1681) | Consumer credit reports |\n| DPPA | Driver's Privacy Protection Act (18 U.S.C. §2721) | Motor vehicle records |\n| COPPA | Children's Online Privacy Protection Act (15 U.S.C. §6501) | Children's data under COPPA |\n| Farm Credit Act | Farm Credit Act of 1971 (12 U.S.C. §2001) | Farm credit data |\n\n**California distinction:** CCPA\u002FCPRA exempts the **data** governed by these federal laws, not the **entity**. A GLBA-covered bank is still subject to CCPA for personal data that falls outside GLBA's scope (e.g., marketing data not related to financial products).\n\n### Step 5: Employee Data Assessment\n\n| State | Employee Data Status |\n|-------|---------------------|\n| California | Fully covered (CPRA removed prior partial exemption) |\n| Virginia | Exempt from consumer rights; controller duties apply |\n| Colorado | Exempt from consumer rights; controller duties apply |\n| Connecticut | Exempt from consumer rights; controller duties apply |\n| Texas | Exempt from consumer rights; controller duties apply |\n| Oregon | **Partial exemption**: Rights exempt; controller duties, DPIAs, sensitive consent apply |\n| Montana | Exempt from consumer rights; controller duties apply |\n| Kentucky | Exempt from consumer rights; controller duties apply |\n\n### Step 6: SBA Small Business Determination (Texas TDPSA)\n\nThe TDPSA is the only state law that uses the SBA small business definition. Key steps:\n\n1. Identify the organization's primary NAICS code\n2. Look up the SBA size standard for that NAICS code in 13 CFR §121.201\n3. Compare the organization's annual receipts or employee count to the threshold\n4. If the organization qualifies as a small business:\n   - Most TDPSA provisions are **exempt**\n   - Prohibition on selling sensitive data without consent **still applies** (§541.107(b))\n\nCommon SBA thresholds for technology\u002Fretail companies:\n\n| NAICS | Industry | Revenue Threshold |\n|-------|----------|-------------------|\n| 454110 | Electronic shopping | $40,000,000 |\n| 519130 | Internet publishing and web search portals | $47,000,000 |\n| 518210 | Data processing and hosting | $35,000,000 |\n| 511210 | Software publishers | $47,000,000 |\n| 541511 | Custom computer programming | $34,000,000 |\n\n## Liberty Commerce Inc. Assessment Summary\n\n| State | Consumers | Revenue from Sale | Applicable | Basis |\n|-------|-----------|-------------------|------------|-------|\n| California | 320,000 | 12% | **YES** | Revenue >$25M + 100K consumers |\n| Virginia | 145,000 | 12% | **YES** | 100K+ consumers |\n| Colorado | 98,000 | 12% | **YES** | 25K+ with revenue from sale |\n| Connecticut | 87,000 | 12% | **Borderline** | Below 100K; below 25% revenue |\n| Texas | 410,000 | 12% | **YES** | Non-SBA small business |\n| Oregon | 72,000 | 12% | **NO** | Below both thresholds |\n| Montana | 28,000 | 12% | **NO** | Below both thresholds |\n| Kentucky | 68,000 | 12% | **NO** | Below both thresholds |\n\n## Key Regulatory References\n\n- SBA Size Standards: 13 CFR §121.201\n- GLBA: 15 U.S.C. §6801-6809\n- HIPAA: 42 U.S.C. §1320d et seq.; 45 CFR Parts 160, 164\n- FERPA: 20 U.S.C. §1232g\n- FCRA: 15 U.S.C. §1681 et seq.\n- COPPA: 15 U.S.C. §6501-6506\n- DPPA: 18 U.S.C. §2721-2725\n","# State Privacy Law Applicability Assessment\n\n## Overview\n\nDetermining which US state privacy laws apply to an organization requires evaluating multiple criteria: revenue thresholds, consumer\u002Fdata volume thresholds, industry-specific exemptions, entity-type exemptions, and data-type exemptions. This skill provides a systematic assessment framework and Python automation tool for evaluating applicability across all major enacted state privacy laws.\n\n## Assessment Framework\n\n### Step 1: Geographic Nexus\n\nFor each state, determine if the organization has nexus through:\n- **Conducting business** in the state (physical presence, employees, registered entity)\n- **Targeting residents** of the state (marketing, advertising, or providing products\u002Fservices specifically to state residents)\n- **Producing products\u002Fservices** consumed by state residents\n\nMost state laws use \"conducts business in [state] OR produces products or services targeted to [state] residents\" as the nexus requirement.\n\n### Step 2: Threshold Assessment\n\n| State | Threshold 1 | Threshold 2 | Revenue Alternative |\n|-------|------------|-------------|---------------------|\n| California | 100,000 consumers\u002Fhouseholds | 50% revenue from sale\u002Fsharing | $25,000,000 annual gross revenue |\n| Virginia | 100,000 consumers | 25,000 consumers + 50% revenue from sale | None |\n| Colorado | 100,000 consumers | 25,000 consumers + revenue\u002Fdiscount from sale | None |\n| Connecticut | 100,000 consumers (excl. payment) | 25,000 consumers + 25% revenue from sale | None |\n| Texas | Non-SBA small business | N\u002FA | None (no threshold) |\n| Oregon | 100,000 consumers (excl. payment) | 25,000 consumers + 25% revenue from sale | None |\n| Montana | 50,000 consumers (excl. payment) | 25,000 consumers + 25% revenue from sale | None |\n| Kentucky | 100,000 consumers | 25,000 consumers + 50% revenue from sale | None |\n\n### Step 3: Entity-Level Exemptions\n\n| Exemption | CA | VA | CO | CT | TX | OR | MT | KY |\n|-----------|----|----|----|----|----|----|----|----|\n| Government | N\u002FA (for-profit only) | Exempt | Exempt | Exempt | Exempt | Exempt | Exempt | Exempt |\n| GLBA financial institutions | Data-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level |\n| HIPAA covered entities | Data-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level | Entity-level |\n| Nonprofits | Not exempt | Exempt | Exempt | Exempt | Exempt | **Not exempt** | Exempt | Exempt |\n| Higher education | Not exempt | Exempt | Exempt | Exempt | Exempt | Not exempt | Exempt | Exempt |\n| Air carriers | Not exempt | Not exempt | Not exempt | Not exempt | Not exempt | Not exempt | **Exempt** | Not exempt |\n\n### Step 4: Data-Level Exemptions\n\nData that is already governed by certain federal laws may be exempt even if the organization itself is not:\n\n| Federal Law | Full Name | Data Type |\n|-------------|-----------|-----------|\n| GLBA | Gramm-Leach-Bliley Act (15 U.S.C. §6801) | Financial data under GLBA privacy rules |\n| HIPAA | Health Insurance Portability and Accountability Act (42 U.S.C. §1320d) | Protected health information (PHI) |\n| FERPA | Family Educational Rights and Privacy Act (20 U.S.C. §1232g) | Education records |\n| FCRA | Fair Credit Reporting Act (15 U.S.C. §1681) | Consumer credit reports |\n| DPPA | Driver's Privacy Protection Act (18 U.S.C. §2721) | Motor vehicle records |\n| COPPA | Children's Online Privacy Protection Act (15 U.S.C. §6501) | Children's data under COPPA |\n| Farm Credit Act | Farm Credit Act of 1971 (12 U.S.C. §2001) | Farm credit data |\n\n**California distinction:** CCPA\u002FCPRA exempts the **data** governed by these federal laws, not the **entity**. A GLBA-covered bank is still subject to CCPA for personal data that falls outside GLBA's scope (e.g., marketing data not related to financial products).\n\n### Step 5: Employee Data Assessment\n\n| State | Employee Data Status |\n|-------|---------------------|\n| California | Fully covered (CPRA removed prior partial exemption) |\n| Virginia | Exempt from consumer rights; controller duties apply |\n| Colorado | Exempt from consumer rights; controller duties apply |\n| Connecticut | Exempt from consumer rights; controller duties apply |\n| Texas | Exempt from consumer rights; controller duties apply |\n| Oregon | **Partial exemption**: Rights exempt; controller duties, DPIAs, sensitive consent apply |\n| Montana | Exempt from consumer rights; controller duties apply |\n| Kentucky | Exempt from consumer rights; controller duties apply |\n\n### Step 6: SBA Small Business Determination (Texas TDPSA)\n\nThe TDPSA is the only state law that uses the SBA small business definition. Key steps:\n\n1. Identify the organization's primary NAICS code\n2. Look up the SBA size standard for that NAICS code in 13 CFR §121.201\n3. Compare the organization's annual receipts or employee count to the threshold\n4. If the organization qualifies as a small business:\n   - Most TDPSA provisions are **exempt**\n   - Prohibition on selling sensitive data without consent **still applies** (§541.107(b))\n\nCommon SBA thresholds for technology\u002Fretail companies:\n\n| NAICS | Industry | Revenue Threshold |\n|-------|----------|-------------------|\n| 454110 | Electronic shopping | $40,000,000 |\n| 519130 | Internet publishing and web search portals | $47,000,000 |\n| 518210 | Data processing and hosting | $35,000,000 |\n| 511210 | Software publishers | $47,000,000 |\n| 541511 | Custom computer programming | $34,000,000 |\n\n## Liberty Commerce Inc. Assessment Summary\n\n| State | Consumers | Revenue from Sale | Applicable | Basis |\n|-------|-----------|-------------------|------------|-------|\n| California | 320,000 | 12% | **YES** | Revenue >$25M + 100K consumers |\n| Virginia | 145,000 | 12% | **YES** | 100K+ consumers |\n| Colorado | 98,000 | 12% | **YES** | 25K+ with revenue from sale |\n| Connecticut | 87,000 | 12% | **Borderline** | Below 100K; below 25% revenue |\n| Texas | 410,000 | 12% | **YES** | Non-SBA small business |\n| Oregon | 72,000 | 12% | **NO** | Below both thresholds |\n| Montana | 28,000 | 12% | **NO** | Below both thresholds |\n| Kentucky | 68,000 | 12% | **NO** | Below both thresholds |\n\n## Key Regulatory References\n\n- SBA Size Standards: 13 CFR §121.201\n- GLBA: 15 U.S.C. §6801-6809\n- HIPAA: 42 U.S.C. §1320d et seq.; 45 CFR Parts 160, 164\n- FERPA: 20 U.S.C. §1232g\n- FCRA: 15 U.S.C. §1681 et seq.\n- COPPA: 15 U.S.C. §6501-6506\n- DPPA: 18 U.S.C. §2721-2725\n",{"name":5,"license":15,"metadata":36,"description":7},{"tags":37,"author":9,"domain":29,"version":38,"subdomain":39},"applicability, thresholds, exemptions, glba, hipaa, small-business","1.0","us-state-privacy-laws","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fus-state-privacy-skills\u002Fskills\u002Fstate-law-applicability",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill state-law-applicability",{"tool":55,"command":56},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill state-law-applicability",{"tool":58,"command":59},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill state-law-applicability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fus-state-privacy-skills\u002Fskills\u002Fstate-law-applicability\u002FSKILL.md",true,[63,69,75,79,83,87],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Ftemplate.md","ASSET","资产文件",3395,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fus-state-privacy-skills\u002Fskills\u002Fstate-law-applicability\u002Fassets\u002Ftemplate.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"DEEPENING.md","REFERENCE","参考文档",2559,"https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fengineering\u002Fcodebase-design\u002FDEEPENING.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"DESIGN-IT-TWICE.md",2777,"https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fengineering\u002Fcodebase-design\u002FDESIGN-IT-TWICE.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fstandards.md",3456,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fus-state-privacy-skills\u002Fskills\u002Fstate-law-applicability\u002Freferences\u002Fstandards.md",{"path":84,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fworkflows.md",4432,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fus-state-privacy-skills\u002Fskills\u002Fstate-law-applicability\u002Freferences\u002Fworkflows.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fprocess.py","SCRIPT","脚本",17365,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fus-state-privacy-skills\u002Fskills\u002Fstate-law-applicability\u002Fscripts\u002Fprocess.py",[94,118,135,148,164,177],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":109,"publishedAt":31},"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",[100,105,108],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":106,"categoryName":107,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[110,111,29,112,113,30,114,115,116,117],"email","workplace email privacy","compliance","content","policy","testing","monitoring","metadata",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":128,"publishedAt":31},"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",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[30,129,130,131,112,132,133,29,134],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":31},"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",[141],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[30,143,144,145,146,133,29,147],"vendor termination data","planning","verification","extraction","certification",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":31},"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",[154],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[156,157,158,159,160,26,161,162,29,30,163],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","transfer","certifications","processor",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"publishedAt":31},"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",[170],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[29,172,133,173,26,174,175,30,163,157,147,176],"vendor privacy due diligence","review","onboarding","flow","analysis",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":190,"publishedAt":31},"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",[183,186,189],{"categoryNo":184,"categoryName":185,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[191,192,29,193,145,194,112,133,195,163,196,197,198,144],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]