[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEV2CJXFWMH62C796CQJSJ":3,"skill-same:01M6AEV2CJXFWMH62C796CQJSJ":117},{"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":31,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6AEV2CJXFWMH62C796CQJSJ","global-privacy-control",null,"Implementation guide for Global Privacy Control (GPC) automated opt-out signal per CPRA Section 1798.135(e). Covers Sec-GPC HTTP header detection, JavaScript navigator.globalPrivacyControl API, and state-specific requirements for CA, CO, CT, MT, TX, and OR. Includes server-side detection code and compliance mapping.","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\u002Fglobal-privacy-control\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[32,33,34,35,36,37,38,39,40,41,42],"privacy","global privacy control","javascript","http","code","state","browser","server","compliance","navigator","detection","2026-11-10 10:12:30",false,"---\nname: global-privacy-control\ndescription: >-\n  Implementation guide for Global Privacy Control (GPC) automated opt-out signal\n  per CPRA Section 1798.135(e). Covers Sec-GPC HTTP header detection, JavaScript\n  navigator.globalPrivacyControl API, and state-specific requirements for CA, CO,\n  CT, MT, TX, and OR. Includes server-side detection code and compliance mapping.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: consent-management\n  tags: \"global-privacy-control, gpc, cpra, opt-out-signal, browser-privacy\"\n---\n\n# Implementing Global Privacy Control (GPC)\n\n## Overview\n\nGlobal Privacy Control (GPC) is a browser-level signal that communicates a user's privacy preference to opt out of the sale or sharing of their personal information. The GPC specification defines both an HTTP header (`Sec-GPC: 1`) and a JavaScript API (`navigator.globalPrivacyControl`) for transmitting this signal.\n\nUnder California Privacy Rights Act (CPRA) Section 1798.135(e), businesses must treat GPC signals as valid opt-out requests. The California Attorney General confirmed this enforcement position in the Sephora settlement (August 2022, $1.2 million fine), which was the first enforcement action involving GPC signals.\n\n## Legal Requirements by State\n\n### California — CPRA (effective January 1, 2023)\n\n- **Section 1798.135(e)**: A business that collects consumers' personal information shall treat the consumer's use of an opt-out preference signal as a valid request to opt out of sale\u002Fsharing under Section 1798.120.\n- **AG Regulation 11 CCR 7025(b)**: If a business collects personal information from consumers online, the business shall treat an opt-out preference signal as a valid request to opt-out of sale\u002Fsharing for that browser or device and any consumer profile associated with that browser or device.\n- **Sephora Settlement (August 2022)**: California AG fined Sephora $1.2 million for failing to honor GPC signals, among other violations.\n\n### Colorado — Colorado Privacy Act (CPA, effective July 1, 2024)\n\n- **Section 6-1-1306(1)(a)(IV)(A)**: Consumers may exercise the right to opt out through an opt-out preference signal sent by a platform, technology, or mechanism on behalf of the consumer, to the extent technically feasible.\n- **CPA Rules 4.6**: Controllers must recognize universal opt-out mechanisms by July 1, 2024.\n\n### Connecticut — Connecticut Data Privacy Act (CTDPA, effective July 1, 2023)\n\n- **Section 42-520(b)(5)**: Beginning January 1, 2025, controllers must recognize universal opt-out mechanisms for the sale of personal data and targeted advertising.\n\n### Montana — Montana Consumer Data Privacy Act (effective October 1, 2024)\n\n- **Section 30-14-2807**: Controllers must recognize opt-out preference signals as valid opt-out requests for the sale of personal data and targeted advertising.\n\n### Texas — Texas Data Privacy and Security Act (TDPSA, effective July 1, 2024)\n\n- **Section 541.055**: Controllers must allow consumers to opt out of the sale of personal data and targeted advertising. Universal opt-out mechanisms must be honored beginning January 1, 2025.\n\n### Oregon — Oregon Consumer Privacy Act (effective July 1, 2024)\n\n- **Section 646A.578**: Controllers shall provide a method by which consumers can opt out that includes recognition of opt-out preference signals.\n\n## GPC Technical Specification\n\n### HTTP Header Detection\n\nThe GPC signal is transmitted as an HTTP request header:\n\n```\nSec-GPC: 1\n```\n\nThis header is set by the browser (or browser extension) on every HTTP request when the user has enabled GPC. The header is absent (not set to 0) when GPC is not enabled.\n\n### JavaScript API Detection\n\nThe GPC signal is also available via the JavaScript DOM API:\n\n```javascript\n\u002F\u002F Check if GPC is supported and enabled\nif (navigator.globalPrivacyControl === true) {\n    \u002F\u002F User has opted out — do not sell\u002Fshare personal information\n    \u002F\u002F Do not load non-essential tracking scripts\n    \u002F\u002F Set internal opt-out flag for this user\n}\n```\n\nKey considerations:\n- `navigator.globalPrivacyControl` returns `true` when GPC is enabled\n- `navigator.globalPrivacyControl` returns `false` or `undefined` when GPC is not enabled or not supported\n- Check should occur before loading any tracking or advertising scripts\n\n### Server-Side Detection (HTTP Header)\n\nOn the server side, check for the `Sec-GPC` header in incoming requests:\n\n```\nIf Sec-GPC header is present AND equals \"1\":\n    → Set opt-out flag for this session\u002Fuser\n    → Do not initiate sale or sharing of personal information\n    → Do not load third-party tracking pixels\n    → Log GPC signal receipt for compliance records\n```\n\n## Implementation Architecture at CloudVault SaaS Inc.\n\n### Client-Side Detection\n\nCloudVault SaaS Inc. checks GPC at two points:\n\n1. **Page Load**: Before initializing any analytics or advertising SDKs, check `navigator.globalPrivacyControl`. If `true`, suppress non-essential tracking.\n\n2. **Consent Banner Interaction**: If GPC is detected, pre-select the \"Opt Out of Sale\u002FSharing\" option in the cookie consent banner and display a notice: \"We detected your Global Privacy Control signal. Your opt-out preference has been applied.\"\n\n### Server-Side Processing\n\nThe CloudVault SaaS Inc. backend middleware:\n\n1. Inspects every incoming HTTP request for the `Sec-GPC: 1` header.\n2. If detected, sets a session-level flag `gpc_opt_out = true`.\n3. If the request is associated with an authenticated user, propagates the opt-out to the user's consent record for applicable purposes (sale\u002Fsharing).\n4. Returns a `Sec-GPC` response header echoing the signal (transparency).\n5. Logs the GPC signal receipt with timestamp, user agent, and associated user ID (if authenticated).\n\n### Mapping GPC to Internal Consent System\n\nGPC is a binary signal (opt out of sale\u002Fsharing). CloudVault SaaS Inc. maps it to specific consent purposes:\n\n| GPC Signal | Internal Purpose | Action |\n|-----------|-----------------|--------|\n| Sec-GPC: 1 | pur_benchmarking_003 (Third-party data sharing) | Withdraw consent \u002F opt out |\n| Sec-GPC: 1 | pur_advertising_004 (Targeted advertising) | Withdraw consent \u002F opt out |\n| Sec-GPC: 1 | pur_analytics_001 (Service improvement) | No change (internal use, not sale\u002Fsharing) |\n| Sec-GPC: 1 | pur_marketing_002 (Product emails) | No change (direct marketing, not sale\u002Fsharing) |\n\n### Conflict Resolution\n\nWhen a user has manually opted in via the preference center but their browser sends GPC:\n\n- **CPRA approach**: GPC takes precedence. Per AG regulation 11 CCR 7025(c), if a conflict exists between the opt-out preference signal and the consumer's participation in a financial incentive program, the business shall respect the opt-out preference signal but may notify the consumer of the conflict and give the consumer the choice to confirm their participation.\n- **CloudVault SaaS Inc. policy**: Display a notification: \"Your browser is sending a Global Privacy Control signal to opt out of data sharing. This overrides your previous opt-in. To continue sharing data for industry benchmarking, you can confirm your preference in Settings > Privacy.\"\n\n## Compliance Verification\n\nTo verify GPC implementation:\n\n1. Install a GPC-enabled browser or extension (Firefox with Enhanced Tracking Protection, DuckDuckGo browser, Brave browser, or the OptMeowt extension for Chrome)\n2. Navigate to CloudVault SaaS Inc. application\n3. Verify that `Sec-GPC: 1` header is sent in network requests\n4. Confirm that tracking scripts are not loaded\n5. Confirm that the consent banner reflects the opt-out preference\n6. Verify server-side logs record the GPC signal\n7. Confirm that authenticated users have their consent record updated\n\n## Key Regulatory References\n\n- CPRA Section 1798.135(e) — Opt-out preference signal requirement\n- California AG Regulation 11 CCR 7025 — GPC implementation details\n- GPC Specification (globalprivacycontrol.org) — Technical standard\n- Colorado Privacy Act Section 6-1-1306(1)(a)(IV)(A) — Universal opt-out\n- Connecticut CTDPA Section 42-520(b)(5) — Universal opt-out mechanism\n- Montana MCDPA Section 30-14-2807 — Opt-out preference signals\n- Texas TDPSA Section 541.055 — Opt-out methods\n- Oregon OCPA Section 646A.578 — Opt-out preference signals\n- Sephora Settlement (California AG, August 2022) — First GPC enforcement\n","# Implementing Global Privacy Control (GPC)\n\n## Overview\n\nGlobal Privacy Control (GPC) is a browser-level signal that communicates a user's privacy preference to opt out of the sale or sharing of their personal information. The GPC specification defines both an HTTP header (`Sec-GPC: 1`) and a JavaScript API (`navigator.globalPrivacyControl`) for transmitting this signal.\n\nUnder California Privacy Rights Act (CPRA) Section 1798.135(e), businesses must treat GPC signals as valid opt-out requests. The California Attorney General confirmed this enforcement position in the Sephora settlement (August 2022, $1.2 million fine), which was the first enforcement action involving GPC signals.\n\n## Legal Requirements by State\n\n### California — CPRA (effective January 1, 2023)\n\n- **Section 1798.135(e)**: A business that collects consumers' personal information shall treat the consumer's use of an opt-out preference signal as a valid request to opt out of sale\u002Fsharing under Section 1798.120.\n- **AG Regulation 11 CCR 7025(b)**: If a business collects personal information from consumers online, the business shall treat an opt-out preference signal as a valid request to opt-out of sale\u002Fsharing for that browser or device and any consumer profile associated with that browser or device.\n- **Sephora Settlement (August 2022)**: California AG fined Sephora $1.2 million for failing to honor GPC signals, among other violations.\n\n### Colorado — Colorado Privacy Act (CPA, effective July 1, 2024)\n\n- **Section 6-1-1306(1)(a)(IV)(A)**: Consumers may exercise the right to opt out through an opt-out preference signal sent by a platform, technology, or mechanism on behalf of the consumer, to the extent technically feasible.\n- **CPA Rules 4.6**: Controllers must recognize universal opt-out mechanisms by July 1, 2024.\n\n### Connecticut — Connecticut Data Privacy Act (CTDPA, effective July 1, 2023)\n\n- **Section 42-520(b)(5)**: Beginning January 1, 2025, controllers must recognize universal opt-out mechanisms for the sale of personal data and targeted advertising.\n\n### Montana — Montana Consumer Data Privacy Act (effective October 1, 2024)\n\n- **Section 30-14-2807**: Controllers must recognize opt-out preference signals as valid opt-out requests for the sale of personal data and targeted advertising.\n\n### Texas — Texas Data Privacy and Security Act (TDPSA, effective July 1, 2024)\n\n- **Section 541.055**: Controllers must allow consumers to opt out of the sale of personal data and targeted advertising. Universal opt-out mechanisms must be honored beginning January 1, 2025.\n\n### Oregon — Oregon Consumer Privacy Act (effective July 1, 2024)\n\n- **Section 646A.578**: Controllers shall provide a method by which consumers can opt out that includes recognition of opt-out preference signals.\n\n## GPC Technical Specification\n\n### HTTP Header Detection\n\nThe GPC signal is transmitted as an HTTP request header:\n\n```\nSec-GPC: 1\n```\n\nThis header is set by the browser (or browser extension) on every HTTP request when the user has enabled GPC. The header is absent (not set to 0) when GPC is not enabled.\n\n### JavaScript API Detection\n\nThe GPC signal is also available via the JavaScript DOM API:\n\n```javascript\n\u002F\u002F Check if GPC is supported and enabled\nif (navigator.globalPrivacyControl === true) {\n    \u002F\u002F User has opted out — do not sell\u002Fshare personal information\n    \u002F\u002F Do not load non-essential tracking scripts\n    \u002F\u002F Set internal opt-out flag for this user\n}\n```\n\nKey considerations:\n- `navigator.globalPrivacyControl` returns `true` when GPC is enabled\n- `navigator.globalPrivacyControl` returns `false` or `undefined` when GPC is not enabled or not supported\n- Check should occur before loading any tracking or advertising scripts\n\n### Server-Side Detection (HTTP Header)\n\nOn the server side, check for the `Sec-GPC` header in incoming requests:\n\n```\nIf Sec-GPC header is present AND equals \"1\":\n    → Set opt-out flag for this session\u002Fuser\n    → Do not initiate sale or sharing of personal information\n    → Do not load third-party tracking pixels\n    → Log GPC signal receipt for compliance records\n```\n\n## Implementation Architecture at CloudVault SaaS Inc.\n\n### Client-Side Detection\n\nCloudVault SaaS Inc. checks GPC at two points:\n\n1. **Page Load**: Before initializing any analytics or advertising SDKs, check `navigator.globalPrivacyControl`. If `true`, suppress non-essential tracking.\n\n2. **Consent Banner Interaction**: If GPC is detected, pre-select the \"Opt Out of Sale\u002FSharing\" option in the cookie consent banner and display a notice: \"We detected your Global Privacy Control signal. Your opt-out preference has been applied.\"\n\n### Server-Side Processing\n\nThe CloudVault SaaS Inc. backend middleware:\n\n1. Inspects every incoming HTTP request for the `Sec-GPC: 1` header.\n2. If detected, sets a session-level flag `gpc_opt_out = true`.\n3. If the request is associated with an authenticated user, propagates the opt-out to the user's consent record for applicable purposes (sale\u002Fsharing).\n4. Returns a `Sec-GPC` response header echoing the signal (transparency).\n5. Logs the GPC signal receipt with timestamp, user agent, and associated user ID (if authenticated).\n\n### Mapping GPC to Internal Consent System\n\nGPC is a binary signal (opt out of sale\u002Fsharing). CloudVault SaaS Inc. maps it to specific consent purposes:\n\n| GPC Signal | Internal Purpose | Action |\n|-----------|-----------------|--------|\n| Sec-GPC: 1 | pur_benchmarking_003 (Third-party data sharing) | Withdraw consent \u002F opt out |\n| Sec-GPC: 1 | pur_advertising_004 (Targeted advertising) | Withdraw consent \u002F opt out |\n| Sec-GPC: 1 | pur_analytics_001 (Service improvement) | No change (internal use, not sale\u002Fsharing) |\n| Sec-GPC: 1 | pur_marketing_002 (Product emails) | No change (direct marketing, not sale\u002Fsharing) |\n\n### Conflict Resolution\n\nWhen a user has manually opted in via the preference center but their browser sends GPC:\n\n- **CPRA approach**: GPC takes precedence. Per AG regulation 11 CCR 7025(c), if a conflict exists between the opt-out preference signal and the consumer's participation in a financial incentive program, the business shall respect the opt-out preference signal but may notify the consumer of the conflict and give the consumer the choice to confirm their participation.\n- **CloudVault SaaS Inc. policy**: Display a notification: \"Your browser is sending a Global Privacy Control signal to opt out of data sharing. This overrides your previous opt-in. To continue sharing data for industry benchmarking, you can confirm your preference in Settings > Privacy.\"\n\n## Compliance Verification\n\nTo verify GPC implementation:\n\n1. Install a GPC-enabled browser or extension (Firefox with Enhanced Tracking Protection, DuckDuckGo browser, Brave browser, or the OptMeowt extension for Chrome)\n2. Navigate to CloudVault SaaS Inc. application\n3. Verify that `Sec-GPC: 1` header is sent in network requests\n4. Confirm that tracking scripts are not loaded\n5. Confirm that the consent banner reflects the opt-out preference\n6. Verify server-side logs record the GPC signal\n7. Confirm that authenticated users have their consent record updated\n\n## Key Regulatory References\n\n- CPRA Section 1798.135(e) — Opt-out preference signal requirement\n- California AG Regulation 11 CCR 7025 — GPC implementation details\n- GPC Specification (globalprivacycontrol.org) — Technical standard\n- Colorado Privacy Act Section 6-1-1306(1)(a)(IV)(A) — Universal opt-out\n- Connecticut CTDPA Section 42-520(b)(5) — Universal opt-out mechanism\n- Montana MCDPA Section 30-14-2807 — Opt-out preference signals\n- Texas TDPSA Section 541.055 — Opt-out methods\n- Oregon OCPA Section 646A.578 — Opt-out preference signals\n- Sephora Settlement (California AG, August 2022) — First GPC enforcement\n",{"name":5,"license":15,"metadata":48,"description":7},{"tags":49,"author":9,"domain":32,"version":50,"subdomain":51},"global-privacy-control, gpc, cpra, opt-out-signal, browser-privacy","1.0","consent-management","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fprivacy-skills-complete\u002Fskills\u002Fglobal-privacy-control",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill global-privacy-control",{"tool":67,"command":68},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill global-privacy-control",{"tool":70,"command":71},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill global-privacy-control","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fglobal-privacy-control\u002FSKILL.md",true,[75,81,87,91,97,101,105,109,113],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Ftemplate.md","ASSET","资产文件",4060,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fglobal-privacy-control\u002Fassets\u002Ftemplate.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fstandards.md","REFERENCE","参考文档",3691,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fglobal-privacy-control\u002Freferences\u002Fstandards.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fworkflows.md",5376,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fglobal-privacy-control\u002Freferences\u002Fworkflows.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fbeads_sync_canonical.sh","SCRIPT","脚本",16281,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbeads-issue-tracking\u002Fscripts\u002Fbeads_sync_canonical.sh",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fcheck_beads_jsonl_drift.sh",16413,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbeads-issue-tracking\u002Fscripts\u002Fcheck_beads_jsonl_drift.sh",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fcompare_beads_jsonl_semantic.py",7554,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbeads-issue-tracking\u002Fscripts\u002Fcompare_beads_jsonl_semantic.py",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fprocess.py",11899,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fglobal-privacy-control\u002Fscripts\u002Fprocess.py",{"path":110,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fsort_beads_jsonl.py",717,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbeads-issue-tracking\u002Fscripts\u002Fsort_beads_jsonl.py",{"path":114,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fvalidate_beads_issues_jsonl.py",1222,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbeads-issue-tracking\u002Fscripts\u002Fvalidate_beads_issues_jsonl.py",[118,140,157,170,187,200],{"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":131,"publishedAt":43},"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",[124,127,130],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[132,133,32,40,134,135,136,137,138,139],"email","workplace email privacy","content","data","policy","testing","monitoring","metadata",{"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":150,"publishedAt":43},"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",[146,149],{"categoryNo":147,"categoryName":148,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[135,151,152,153,40,154,155,32,156],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"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":43},"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",[163],{"categoryNo":147,"categoryName":148,"taxonomyType":26,"taxonomyTypeDesc":27},[135,165,166,167,168,155,32,169],"vendor termination data","planning","verification","extraction","certification",{"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":177,"publishedAt":43},"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",[176],{"categoryNo":147,"categoryName":148,"taxonomyType":26,"taxonomyTypeDesc":27},[178,179,180,181,182,183,184,185,32,135,186],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","assessment","transfer","certifications","processor",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":43},"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",[193],{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[32,195,155,196,183,197,198,135,186,179,169,199],"vendor privacy due diligence","review","onboarding","flow","analysis",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":213,"publishedAt":43},"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",[206,209,212],{"categoryNo":207,"categoryName":208,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":210,"categoryName":211,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[214,215,32,216,167,217,40,155,218,186,219,220,221,166],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]