privacy-by-design
Privacy-by-design workflow for embedding data minimization, lawful basis, retention, and user-rights readiness into product decisions. Use when a feature touches personal data and privacy controls must be defined before implementation; do not use for narrow infrastructure tuning that does not affect personal-data handling.
Works with
--- name: privacy-by-design description: Privacy-by-design workflow for embedding data minimization, lawful basis, retention, and user-rights readiness into product decisions. Use when a feature touches personal data and privacy controls must be defined before implementation; do not use for narrow infrastructure tuning that does not affect personal-data handling. license: Apache-2.0 --- # Privacy By Design ## Overview Use this skill to make privacy requirements explicit, enforceable, and testable before implementation. ## Scope Boundaries - Use this skill when the task matches the trigger condition described in `description`. - Do not use this skill when the primary task falls outside this skill's domain. ## Shared References - Lawful basis and minimization rules: - `references/lawful-basis-and-minimization-rules.md` ## Templates And Assets - Privacy control matrix template: - `assets/privacy-control-matrix-template.csv` - Data lifecycle map template: - `assets/data-lifecycle-map-template.md` ## Inputs To Gather - Feature scope and personal-data touchpoints. - Applicable legal/policy obligations for target markets. - Data flow boundaries and third-party transfers. - Retention and user-rights operational capabilities. ## Deliverables - Privacy control matrix with ownership. - Data lifecycle map from collection to deletion. - Consent/notice and user-rights requirements. - Residual privacy risk and approval record. ## Workflow 1. Map lifecycle with `assets/data-lifecycle-map-template.md`. 2. Define controls in `assets/privacy-control-matrix-template.csv`. 3. Validate decisions against `references/lawful-basis-and-minimization-rules.md`. 4. Confirm operational feasibility for retention/deletion/rights handling. 5. Publish controls and unresolved risks. ## Quality Standard - Every data element has explicit purpose and legal basis/authorization. - Data collection is minimized and retention is bounded. - User-rights handling is operationally executable. ## Failure Conditions - Stop when lawful basis or purpose limitation is undefined. - Stop when retention/deletion controls cannot be enforced. - Escalate when transfer safeguards or approvals are missing.
More DevOps & Infrastructure skills
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
appinsights-instrumentation
microsoft/azure-skills
Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices.
azure-storage
microsoft/azure-skills
Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Answers questions about storage access tiers (hot, cool, cold, archive), when to use each tier, and tier comparison. Provides object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics. Includes lifecycle management. USE FOR: blob storage, file shares, queue storage, table storage, data lake, upload files, download blobs, storage accounts, access tiers, storage tiers, hot cool cold archive, storage tier comparison, when to use storage tiers, lifecycle management, Azure Storage concepts. DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging).

