Cybersecurity

Privacy

Privacy: Map personal-data handling and minimize unnecessary collection. Review authorized scope, assets, trust boundaries, identities, logs, and threat model and produce a data-flow and privacy risk review.

Download SKILL.md

---
name: cybersecurity-privacy
description: Use for privacy when asked to map personal-data handling and minimize unnecessary collection; produce a data-flow and privacy risk review.
license: MIT
metadata:
author: Thrive
category: cybersecurity
---

# Privacy

## When to use

Use this skill for privacy when you need to map personal-data handling and minimize unnecessary collection. The expected result is a data-flow and privacy risk review.

## Boundaries

Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it.

## Inputs

Inspect authorized scope, assets, trust boundaries, identities, logs, and threat model. Resolve missing information that would change the method; state lesser assumptions in the result.

## Method

1. **Diagnose.** Set written authorization, assets, trust boundaries, identities, sensitive data, and available telemetry.
2. **Decide.** Prioritize findings by realistic exploit path and business impact.
3. **Produce.** Build a data-flow and privacy risk review from the inspected material; keep assumptions distinguishable from observed facts.

## Decision rules

- Prioritize an exploit path with realistic preconditions; distinguish confirmed exposure from a theoretical weakness.
- When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact.

## Domain rules

- Keep testing within the stated authorization and minimize sensitive data exposure.
- State residual risk, detection coverage, and the accountable owner.

## Verification

Verify retention, access, and current obligations. Compare the result with the user's acceptance criteria and record any unverified boundary.

Record safe reproduction, affected assets, impact, mitigation, retest result, residual risk, and owner.

## Evidence and stop conditions

- Verify current authoritative sources for rules, prices, clinical claims, or obligations that can change. Distinguish fact, interpretation, and assumption.
- Stop before an external action or regulated judgment without the required authorization or qualified reviewer.
- When evidence is materially missing or conflicting, state the uncertainty and the exact source or decision needed to proceed.

## Stop conditions

If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed.

## Output

Provide a data-flow and privacy risk review. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use.

<!--
MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
-->