privacy-agent

Operationalize consent, redaction, retention, and DSAR workflows in camera and IoT pipelines.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/asalhamed/dev-agents --skill privacy-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: privacy-agent
Source: https://github.com/asalhamed/dev-agents/tree/main/privacy-agent
Command: npx skills add https://github.com/asalhamed/dev-agents --skill privacy-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Protect privacy in camera and IoT pipelines by operationalizing consent, redaction, retention, and DSAR workflows.

Core Features & Use Cases

  • Biometric consent management and notices for camera/IoT
  • Redaction pipelines (face/plate/voice) with operator runbooks
  • Retention automation and DSAR tooling with auditable deletion events
  • DPIA templates and cross-jurisdictional compliance guidance
  • Operator runbooks for common privacy requests and signage

Quick Start

Enable biometric consent flows, activate face/plate redaction, and wire retention and DSAR runbooks into your camera network.

Frequently Asked Questions about privacy-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I operationalize privacy and consent for camera and IoT data pipelines?

You operationalize privacy for camera and IoT data by implementing consent capture, redaction pipelines, retention automation, and DSAR routing workflows. This ensures biometric, video, and signage data is processed compliantly across jurisdictions.

What is the best way to automate face and license plate redaction in video pipelines?

Automating face and plate redaction involves activating redaction pipelines paired with operator runbooks. This workflow processes video and voice data to obscure identifiable features while maintaining an auditable privacy compliance record.

How do I handle DSAR requests for biometric and video surveillance data?

Handling DSAR requests for biometric and video data requires routing workflows that manage subject access requests and execute automated deletion. This creates auditable deletion events to verify compliance with privacy regulations.

Do I need a DPIA for deploying IoT cameras with biometric data capture?

Deploying IoT cameras capturing biometric data requires a DPIA to assess cross-jurisdictional privacy risks. Using DPIA templates helps evaluate purpose statements, data classification, and consent mechanisms before activating camera networks.

Can I set automated retention schedules for IoT signage and video data?

Automated retention for IoT signage and video data is supported through retention automation workflows. These schedules enforce purpose-based data classification and trigger auditable deletion events when the retention period expires.

What limitations exist when applying cross-jurisdictional privacy compliance to camera networks?

Cross-jurisdictional compliance for camera networks requires navigating varying consent and biometric regulations. Limitations arise when local signage mandates or biometric restrictions conflict, requiring operator runbooks to manually resolve jurisdiction-specific privacy requests.