privacy-compliance-engineer

Design and enforce privacy controls across application, API, and database layers.

2|1|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill privacy-compliance-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: privacy-compliance-engineer
Source: https://github.com/ThiagoGuislotti/copilot-instructions/tree/main/.codex/skills/privacy-compliance-engineer
Command: npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill privacy-compliance-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineering teams identify and remediate personal data risks across applications, APIs, and databases by providing a structured privacy-by-design workflow and validation guidance to prevent PII leakage, enforce retention policies, and produce auditable evidence.

Core Features & Use Cases

  • Data Mapping & Classification: Identify personal data classes, flows, and processing purposes across services and storage.
  • Controls Implementation: Recommend and validate minimization, masking, encryption, and least-privilege access patterns.
  • Retention & Auditability: Define retention and deletion behaviors with auditable evidence and verification steps.
  • Testing & Reporting: Add privacy-focused tests for tenant isolation and sensitive-data leakage and report residual compliance risks with owners and deadlines.
  • Use Case: When updating an API that handles customer profiles, map PII exposure, apply masking and encryption, add retention policies, and produce a compliance remediation plan with validation checks.

Quick Start

Use the privacy-compliance-engineer skill to map personal data flows in the codebase, recommend controls, and produce a prioritized remediation and validation plan.

Frequently Asked Questions about privacy-compliance-engineer

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

FAQPage Schema
How do I implement privacy-by-design controls for PII across my application and database layers?

Privacy-by-design controls for PII are implemented through data mapping, minimization, masking, encryption, and least-privilege access patterns applied systematically across application, API, and database layers to prevent data leakage.

What is the best way to map personal data flows and classify sensitive information in my codebase?

Mapping personal data flows involves identifying personal data classes, tracking processing purposes across services and storage, and classifying sensitive information to expose PII exposure points within your architecture.

How do I set up data retention and deletion policies with auditable evidence?

Data retention and deletion policies require defining specific retention behaviors and deletion workflows, then generating auditable evidence and verification steps to prove compliance with data protection requirements.

Can I add automated privacy tests to check for tenant isolation and sensitive data leakage?

Automated privacy tests validate tenant isolation and detect sensitive data leakage by applying privacy-focused testing workflows that identify residual compliance risks and verify controls are functioning correctly.

When do I need a structured data governance workflow for compliance-oriented architecture changes?

A structured data governance workflow is needed when updating APIs or services handling customer profiles, requiring PII exposure mapping, control validation, and a prioritized compliance remediation plan with owners and deadlines.