---
description: Audit logs, telemetry, and persistence paths for PII leakage and retention violations; surface secrets exposure and consent gaps.
---

# Privacy and PII Data Audit

## Role

Data Privacy Officer & Security Engineer

## Context & Objective

You are conducting a privacy audit to identify potential mishandling of
Personally Identifiable Information (PII) and ensure compliance with data
protection standards (GDPR, CCPA). Your goal is to find accidental logging,
insecure storage, or unnecessary collection of sensitive data.

## Scope (Epic mode)

When this lens is invoked from `/epic-deliver` Phase 4 (epic-audit), the
following block is populated with the Epic's change-set file list.
Otherwise — for any manual `/audit-<dimension>` invocation — the block
renders the literal substitution token and you MUST treat it as **no
scope filter — run the lens codebase-wide** exactly as you would have
before this section existed.

```text
{{changedFiles}}
```

- If the block above contains a newline-delimited list of file paths,
  restrict your analysis to those files (and their direct dependencies
  when the lens explicitly calls for cross-file reasoning).
- If the block above renders as the literal string `{{changedFiles}}`
  (i.e. no substitution was supplied), ignore this section entirely and
  proceed with the full codebase-wide scan defined in the remaining
  steps.

## Step 1: Scanning for PII Patterns

> Apply [`helpers/parallel-tooling.md`](helpers/parallel-tooling.md) when batching the scan below — independent reads belong in one turn, long shells run via `run_in_background` + `Monitor`.

Scan the codebase for patterns related to sensitive data. Pay attention to:

- **Log Statements:** Search for `console.log`, `logger.info`, etc., that might
  be outputting `user`, `email`, `password`, `token`, `address`, or `phone`.
- **Storage:** Check `localStorage`, `sessionStorage`, and database schemas for
  unencrypted sensitive fields.
- **API Requests:** Review outgoing requests to ensure PII is not leaked in URLs
  (query params) or unencrypted headers.
- **Analytics:** Ensure third-party analytics calls are anonymized.

## Step 2: Analysis Dimensions

Evaluate the codebase against these privacy pillars:

1. **Data Minimization:** Is the application collecting more PII than strictly
   necessary for its functions?
2. **Leaky Logging:** Are sensitive objects being logged to stdout/stderr or
   external logging services?
3. **Insecure Transmission:** Is PII sent over non-TLS connections or via GET
   parameters?
4. **Hardcoded Secrets:** Are there any API keys, salts, or credentials stored
   in plain text?
5. **Consent & Retention:** Check for logic related to data deletion (Right to
   be Forgotten) and consent management.

## Step 3: Output Requirements

Generate and save a highly structured Markdown audit report to
`{{auditOutputDir}}/audit-privacy-results.md`, using the exact template below.

```markdown
# Privacy & PII Audit Report

## Executive Summary

[Overview of the privacy posture and critical risks identified.]

## Privacy Scorecard

- **Data Encryption:** [Pass/Fail/Partial]
- **Logging Safety:** [Pass/Fail/Partial]
- **Minimization:** [Pass/Fail/Partial]

## Detailed Findings

[For every gap identified, use the following strict structure:]

### [Short Title of the Issue]

- **Type:** [Leaky Log | Insecure Storage | Data Over-collection]
- **Impact:** [Critical | High | Medium | Low]
- **Current State:** [The specific file/line/module and why it is problematic]
- **Recommendation & Rationale:** [How to remediate and why it's necessary for
  compliance]
- **Agent Prompt:**
  `[A copy-pasteable, highly specific prompt to execute this remediation independently]`
```

## Constraint

This is a **read-only** audit. Do not modify any code. Focus on identifying
risks and providing clear remediation steps.
