Privacy

GDPR-style subject access export and erasure with consent, cookie, and processing record tracking.

my add privacy
my privacy export --user user-1
my privacy export --user user-1 --output ./exports
my privacy export --user user-1 --dry-run
my privacy delete --user user-1
my privacy delete --user user-1 --dry-run

What gets scaffolded

| Module | Path | |--------|------| | Privacy service | src/privacy/privacy.service.ts | | Consent | src/privacy/consent/ | | Cookies | src/privacy/cookies/ | | Processing registry | src/privacy/processing/ | | Export / deletion | src/privacy/export/, src/privacy/deletion/ | | Register | src/privacy/register-privacy.ts | | Docs | PRIVACY.md |

CLI behavior

When the privacy feature is enabled and src/privacy/register-privacy.ts (or compiled .js) exists, the CLI prefers the generated module's privacyService, dataExporter, and dataDeleter. Otherwise it falls back to the built-in in-memory store seeded from data/privacy-users.json.

Exports include profile data plus consents, cookies, and processing records when those APIs are available on the service.

Related commands

• my compliance check — verifies privacy policy and subject-rights checks
• my add audit — audit trail for data access events