[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF5MJE312XSB7K1DXWNJKQ":3,"skill-same:01M6AF5MJE312XSB7K1DXWNJKQ":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":26,"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},"01M6AF5MJE312XSB7K1DXWNJKQ","texas-tdpsa-compliance",null,"Texas Data Privacy and Security Act (TDPSA) compliance. No revenue threshold applies to all businesses. Covers data broker registration requirements, biometric identifier provisions under CUBI, consumer rights, AG enforcement, and 30-day cure period. Effective July 1, 2024.","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-skills-complete\u002Fskills\u002Ftexas-tdpsa-compliance\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[27,28,29,30,31,32,33],"compliance","texas tdpsa compliance","security","state","data privacy","privacy","data","2026-11-10 10:12:30",false,"---\nname: texas-tdpsa-compliance\ndescription: >-\n  Texas Data Privacy and Security Act (TDPSA) compliance. No revenue\n  threshold applies to all businesses. Covers data broker registration\n  requirements, biometric identifier provisions under CUBI, consumer\n  rights, AG enforcement, and 30-day cure period. Effective July 1, 2024.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: us-state-privacy-laws\n  tags: \"tdpsa, texas-privacy, data-broker, biometric, no-revenue-threshold\"\n---\n\n# Texas Data Privacy and Security Act (TDPSA)\n\n## Overview\n\nThe Texas Data Privacy and Security Act (TDPSA), codified as Tex. Bus. & Com. Code §541.001 through §541.203, was signed into law on June 18, 2023 (HB 4), and became effective July 1, 2024. Texas is the largest state by population to enact comprehensive consumer privacy legislation and is notable for having **no revenue threshold** for applicability — the TDPSA applies to any person that conducts business in Texas or produces products or services consumed by Texas residents, regardless of company size.\n\nThe TDPSA also interacts with the existing Texas Capture or Use of Biometric Identifier Act (CUBI), Tex. Bus. & Com. Code §503.001, which provides separate biometric data protections.\n\n## Applicability (§541.002)\n\nThe TDPSA applies to a person that:\n1. Conducts business in Texas or produces a product or service consumed by Texas residents\n2. Processes or engages in the sale of personal data\n3. Is **not** a small business as defined by the U.S. Small Business Administration (SBA)\n\n**Key feature: No revenue or consumer count threshold.** Unlike California ($25M revenue), Virginia (100,000 consumers), or Colorado (100,000 consumers), the TDPSA applies broadly to any non-small business processing personal data of Texas residents.\n\n**Small business exemption:** Small businesses as defined by SBA size standards are exempt from most provisions but are NOT exempt from the prohibition on selling sensitive data without consent (§541.107(b)).\n\n**Additional exemptions (§541.003):**\n- State agencies and political subdivisions\n- Financial institutions subject to GLBA (entity-level)\n- Covered entities and business associates under HIPAA (entity-level)\n- Nonprofit organizations\n- Institutions of higher education\n- Electric utilities (ERCOT-related)\n\n**Liberty Commerce Inc. Assessment:**\nLiberty Commerce Inc. is not an SBA-defined small business (annual revenue: $48M, 320 employees). It conducts business in Texas and processes personal data of Texas residents. The TDPSA applies.\n\n## Consumer Rights (§541.051)\n\n### Five Consumer Rights\n\n1. **Right to Access** (§541.051(1)): Confirm processing and access personal data\n2. **Right to Correct** (§541.051(2)): Correct inaccuracies\n3. **Right to Delete** (§541.051(3)): Delete personal data\n4. **Right to Portability** (§541.051(4)): Obtain data in portable, readily usable format\n5. **Right to Opt Out** (§541.051(5)): Opt out of:\n   - Targeted advertising\n   - Sale of personal data\n   - Profiling in furtherance of decisions producing legal or similarly significant effects\n\n### Response Requirements (§541.055)\n- Respond within 45 days\n- Extension: up to 45 additional days with notice\n- At least one free response per 12 months per right\n- Appeal process: respond within 60 days\n\n## Sensitive Data (§541.001(29), §541.101(b)(5))\n\n### Categories\n1. Racial or ethnic origin\n2. Religious beliefs\n3. Mental or physical health diagnosis\n4. Sexual orientation\n5. Citizenship or immigration status\n6. Genetic or biometric data processed for identification\n7. Personal data of a known child\n8. Precise geolocation data\n\n### Consent Requirements\nProcessing sensitive data requires **opt-in consent**. For small businesses: selling sensitive data without consent is prohibited regardless of SBA size.\n\n## Data Broker Provisions (§541.201-§541.203)\n\nThe TDPSA includes specific data broker requirements:\n\n### Definition (§541.201)\nA \"data broker\" is a business entity whose principal source of revenue is derived from collecting, processing, or transferring personal data the entity did not directly collect from consumers.\n\n### Registration Requirement (§541.202)\nData brokers must register with the Texas Secretary of State and pay a registration fee. Registration must include:\n- Legal name and primary business address\n- Contact information for privacy inquiries\n- Description of data collection practices\n- Whether the broker has experienced a data breach in the preceding 3 years\n\n### Consumer Rights for Data Brokers (§541.203)\nData brokers must provide:\n- Clear and conspicuous disclosure that they are a data broker\n- A mechanism for consumers to opt out of data collection\n- Instructions for submitting access and deletion requests\n\n**Liberty Commerce Inc. Assessment:**\nLiberty Commerce Inc. is not a data broker — its principal revenue derives from e-commerce, not from collecting\u002Fprocessing\u002Ftransferring personal data. The data broker provisions do not apply.\n\n## Biometric Data: CUBI Interaction\n\n### Texas Capture or Use of Biometric Identifier Act (CUBI) — Tex. Bus. & Com. Code §503.001\n\nCUBI, enacted in 2009, provides additional protections for biometric identifiers:\n- Defines biometric identifier: retina or iris scan, fingerprint, voiceprint, record of hand or face geometry\n- Requires informed consent before capture\n- Prohibits sale, lease, or disclosure without consent\n- Requires reasonable care in storage, transmission, and protection\n- Requires destruction within a reasonable time (when purpose fulfilled or within 3 years of last interaction)\n- No private right of action — AG enforcement only\n- Penalties: Up to $25,000 per violation\n\n**Liberty Commerce Inc. Implementation:**\nLiberty Commerce Inc. does not capture biometric identifiers from Texas consumers. Device-side biometric authentication (Face ID, fingerprint) processes locally and does not transmit biometric data to Liberty Commerce Inc. servers.\n\n## Controller Obligations (§541.101)\n\n1. **Purpose limitation** (§541.101(a)(1)): Limit processing to adequate, relevant, and reasonably necessary purposes\n2. **Data minimization** (§541.101(a)(2)): Do not process beyond what is reasonably necessary\n3. **Data security** (§541.101(a)(3)): Appropriate technical and organizational measures\n4. **Non-discrimination** (§541.101(a)(4)): No processing in violation of antidiscrimination laws\n5. **Sensitive data consent** (§541.101(b)(5)): Obtain consent before processing\n\n### Privacy Notice (§541.101(b))\nMust include:\n- Categories of personal data processed\n- Purposes for processing\n- Consumer rights exercise instructions\n- Categories shared with third parties\n- Categories of third parties\n- Contact information\n\n### Data Protection Assessments (§541.103)\nRequired for:\n- Targeted advertising\n- Sale of personal data\n- Profiling with legal or significant effects\n- Sensitive data processing\n- High-risk processing activities\n\n## Enforcement (§541.151-§541.155)\n\n### Attorney General Authority\n- Exclusive enforcement — no private right of action (except CUBI has AG enforcement only)\n- May investigate and bring action under the Deceptive Trade Practices — Consumer Protection Act (Tex. Bus. & Com. Code §17.41 et seq.)\n\n### 30-Day Cure Period (§541.154)\n- AG must provide 30-day written notice of alleged violation\n- If cured within 30 days and express written statement of cure provided: AG may not bring action\n- **Unlike CPRA:** Cure period is permanent, not sunsetting\n\n### Penalties\n- Civil penalties up to $7,500 per violation\n- Injunctive relief\n- Reasonable attorney fees and investigation costs\n\n## Key Regulatory References\n\n- Tex. Bus. & Com. Code §541.001-§541.203 (TDPSA)\n- Tex. Bus. & Com. Code §503.001 (CUBI — biometric identifiers)\n- Tex. Bus. & Com. Code §17.41 et seq. (DTPA — enforcement framework)\n- SBA Size Standards (13 CFR §121.201) — small business determination\n- Texas Secretary of State — Data broker registration\n","# Texas Data Privacy and Security Act (TDPSA)\n\n## Overview\n\nThe Texas Data Privacy and Security Act (TDPSA), codified as Tex. Bus. & Com. Code §541.001 through §541.203, was signed into law on June 18, 2023 (HB 4), and became effective July 1, 2024. Texas is the largest state by population to enact comprehensive consumer privacy legislation and is notable for having **no revenue threshold** for applicability — the TDPSA applies to any person that conducts business in Texas or produces products or services consumed by Texas residents, regardless of company size.\n\nThe TDPSA also interacts with the existing Texas Capture or Use of Biometric Identifier Act (CUBI), Tex. Bus. & Com. Code §503.001, which provides separate biometric data protections.\n\n## Applicability (§541.002)\n\nThe TDPSA applies to a person that:\n1. Conducts business in Texas or produces a product or service consumed by Texas residents\n2. Processes or engages in the sale of personal data\n3. Is **not** a small business as defined by the U.S. Small Business Administration (SBA)\n\n**Key feature: No revenue or consumer count threshold.** Unlike California ($25M revenue), Virginia (100,000 consumers), or Colorado (100,000 consumers), the TDPSA applies broadly to any non-small business processing personal data of Texas residents.\n\n**Small business exemption:** Small businesses as defined by SBA size standards are exempt from most provisions but are NOT exempt from the prohibition on selling sensitive data without consent (§541.107(b)).\n\n**Additional exemptions (§541.003):**\n- State agencies and political subdivisions\n- Financial institutions subject to GLBA (entity-level)\n- Covered entities and business associates under HIPAA (entity-level)\n- Nonprofit organizations\n- Institutions of higher education\n- Electric utilities (ERCOT-related)\n\n**Liberty Commerce Inc. Assessment:**\nLiberty Commerce Inc. is not an SBA-defined small business (annual revenue: $48M, 320 employees). It conducts business in Texas and processes personal data of Texas residents. The TDPSA applies.\n\n## Consumer Rights (§541.051)\n\n### Five Consumer Rights\n\n1. **Right to Access** (§541.051(1)): Confirm processing and access personal data\n2. **Right to Correct** (§541.051(2)): Correct inaccuracies\n3. **Right to Delete** (§541.051(3)): Delete personal data\n4. **Right to Portability** (§541.051(4)): Obtain data in portable, readily usable format\n5. **Right to Opt Out** (§541.051(5)): Opt out of:\n   - Targeted advertising\n   - Sale of personal data\n   - Profiling in furtherance of decisions producing legal or similarly significant effects\n\n### Response Requirements (§541.055)\n- Respond within 45 days\n- Extension: up to 45 additional days with notice\n- At least one free response per 12 months per right\n- Appeal process: respond within 60 days\n\n## Sensitive Data (§541.001(29), §541.101(b)(5))\n\n### Categories\n1. Racial or ethnic origin\n2. Religious beliefs\n3. Mental or physical health diagnosis\n4. Sexual orientation\n5. Citizenship or immigration status\n6. Genetic or biometric data processed for identification\n7. Personal data of a known child\n8. Precise geolocation data\n\n### Consent Requirements\nProcessing sensitive data requires **opt-in consent**. For small businesses: selling sensitive data without consent is prohibited regardless of SBA size.\n\n## Data Broker Provisions (§541.201-§541.203)\n\nThe TDPSA includes specific data broker requirements:\n\n### Definition (§541.201)\nA \"data broker\" is a business entity whose principal source of revenue is derived from collecting, processing, or transferring personal data the entity did not directly collect from consumers.\n\n### Registration Requirement (§541.202)\nData brokers must register with the Texas Secretary of State and pay a registration fee. Registration must include:\n- Legal name and primary business address\n- Contact information for privacy inquiries\n- Description of data collection practices\n- Whether the broker has experienced a data breach in the preceding 3 years\n\n### Consumer Rights for Data Brokers (§541.203)\nData brokers must provide:\n- Clear and conspicuous disclosure that they are a data broker\n- A mechanism for consumers to opt out of data collection\n- Instructions for submitting access and deletion requests\n\n**Liberty Commerce Inc. Assessment:**\nLiberty Commerce Inc. is not a data broker — its principal revenue derives from e-commerce, not from collecting\u002Fprocessing\u002Ftransferring personal data. The data broker provisions do not apply.\n\n## Biometric Data: CUBI Interaction\n\n### Texas Capture or Use of Biometric Identifier Act (CUBI) — Tex. Bus. & Com. Code §503.001\n\nCUBI, enacted in 2009, provides additional protections for biometric identifiers:\n- Defines biometric identifier: retina or iris scan, fingerprint, voiceprint, record of hand or face geometry\n- Requires informed consent before capture\n- Prohibits sale, lease, or disclosure without consent\n- Requires reasonable care in storage, transmission, and protection\n- Requires destruction within a reasonable time (when purpose fulfilled or within 3 years of last interaction)\n- No private right of action — AG enforcement only\n- Penalties: Up to $25,000 per violation\n\n**Liberty Commerce Inc. Implementation:**\nLiberty Commerce Inc. does not capture biometric identifiers from Texas consumers. Device-side biometric authentication (Face ID, fingerprint) processes locally and does not transmit biometric data to Liberty Commerce Inc. servers.\n\n## Controller Obligations (§541.101)\n\n1. **Purpose limitation** (§541.101(a)(1)): Limit processing to adequate, relevant, and reasonably necessary purposes\n2. **Data minimization** (§541.101(a)(2)): Do not process beyond what is reasonably necessary\n3. **Data security** (§541.101(a)(3)): Appropriate technical and organizational measures\n4. **Non-discrimination** (§541.101(a)(4)): No processing in violation of antidiscrimination laws\n5. **Sensitive data consent** (§541.101(b)(5)): Obtain consent before processing\n\n### Privacy Notice (§541.101(b))\nMust include:\n- Categories of personal data processed\n- Purposes for processing\n- Consumer rights exercise instructions\n- Categories shared with third parties\n- Categories of third parties\n- Contact information\n\n### Data Protection Assessments (§541.103)\nRequired for:\n- Targeted advertising\n- Sale of personal data\n- Profiling with legal or significant effects\n- Sensitive data processing\n- High-risk processing activities\n\n## Enforcement (§541.151-§541.155)\n\n### Attorney General Authority\n- Exclusive enforcement — no private right of action (except CUBI has AG enforcement only)\n- May investigate and bring action under the Deceptive Trade Practices — Consumer Protection Act (Tex. Bus. & Com. Code §17.41 et seq.)\n\n### 30-Day Cure Period (§541.154)\n- AG must provide 30-day written notice of alleged violation\n- If cured within 30 days and express written statement of cure provided: AG may not bring action\n- **Unlike CPRA:** Cure period is permanent, not sunsetting\n\n### Penalties\n- Civil penalties up to $7,500 per violation\n- Injunctive relief\n- Reasonable attorney fees and investigation costs\n\n## Key Regulatory References\n\n- Tex. Bus. & Com. Code §541.001-§541.203 (TDPSA)\n- Tex. Bus. & Com. Code §503.001 (CUBI — biometric identifiers)\n- Tex. Bus. & Com. Code §17.41 et seq. (DTPA — enforcement framework)\n- SBA Size Standards (13 CFR §121.201) — small business determination\n- Texas Secretary of State — Data broker registration\n",{"name":5,"license":15,"metadata":39,"description":7},{"tags":40,"author":9,"domain":32,"version":41,"subdomain":42},"tdpsa, texas-privacy, data-broker, biometric, no-revenue-threshold","1.0","us-state-privacy-laws","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fprivacy-skills-complete\u002Fskills\u002Ftexas-tdpsa-compliance",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 texas-tdpsa-compliance",{"tool":58,"command":59},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill texas-tdpsa-compliance",{"tool":61,"command":62},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill texas-tdpsa-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Ftexas-tdpsa-compliance\u002FSKILL.md",true,[66,72,78,82],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Ftemplate.md","ASSET","资产文件",1384,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Ftexas-tdpsa-compliance\u002Fassets\u002Ftemplate.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fstandards.md","REFERENCE","参考文档",3151,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Ftexas-tdpsa-compliance\u002Freferences\u002Fstandards.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fworkflows.md",3676,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Ftexas-tdpsa-compliance\u002Freferences\u002Fworkflows.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fprocess.py","SCRIPT","脚本",9166,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Ftexas-tdpsa-compliance\u002Fscripts\u002Fprocess.py",[89,112,127,140,157,170],{"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":104,"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,100,103],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[105,106,32,27,107,33,108,109,110,111],"email","workplace email privacy","content","policy","testing","monitoring","metadata",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":120,"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",[118,119],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[33,121,122,123,27,124,125,32,126],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"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",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[33,135,136,137,138,125,32,139],"vendor termination data","planning","verification","extraction","certification",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"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",[146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[148,149,150,151,152,153,154,155,32,33,156],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","assessment","transfer","certifications","processor",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"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",[163],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[32,165,125,166,153,167,168,33,156,149,139,169],"vendor privacy due diligence","review","onboarding","flow","analysis",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":183,"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",[176,179,182],{"categoryNo":177,"categoryName":178,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[184,185,32,186,137,187,27,125,188,156,189,190,191,136],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]