# Manage consent records and suppressions

Consent evidence and withdrawal events can become inconsistent across marketing tools. This skill records pseudonymous consent facts and applies immediate suppression through a controlled registry.

## Install

```bash
npx skillstore add aaron-he-zhu/consent-registry
```

## Metadata

- Status: approved
- Slug: aaron-he-zhu-consent-registry
- Version: 19.0.0
- Author version: 19.0.0
- Skillstore revision: r2
- Version status: valid
- Tree hash: c38d6f26963a2aa3e973c26ccbb9363d3f32418199203289219dfd2032f5c248
- Author: aaron-he-zhu
- GitHub username: aaron-he-zhu
- License: Apache-2.0
- Repository: https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/protocol/consent-registry
- Ref: adcb3549b15782055d0beb6d29f113d20de08f92
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 80
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/aaron-he-zhu-consent-registry
- Manifest: https://skillstore.pages.dev/api/skills/aaron-he-zhu-consent-registry/manifest

## Capabilities

- Records opt-in evidence with source, timestamp, lawful basis, and proof references.
- Checks the live suppression result for a pseudonymous subject ID.
- Applies unsubscribe, complaint, and hard-bounce suppression immediately.
- Requires fresh authorized evidence before restoring contact permission.
- Prepares verified erasure actions while retaining a suppression tombstone.
- Reports event identifiers, revisions, and missing evidence without raw contact data.

## Use Cases

- Record a verified opt-in: Add timestamped opt-in evidence with lawful basis and proof references.
- Process an urgent unsubscribe: Immediately create a suppression record from a validated unsubscribe event.
- Review consent before outreach: Check live suppression status and identify missing consent evidence.

## Prompt Templates

### Check suppression status

```
Check whether pseudonymous subject ID sha256-7d9f is currently suppressed.
```

### Record an opt-in

```
Record opt-in for subject sha256-7d9f with source reference, timestamp, lawful basis, and proof reference.
```

### Process an unsubscribe

```
Immediately suppress subject sha256-7d9f using unsubscribe event evt-882 and report the required confirmation steps.
```

### Review a restore request

```
Review whether this restore request has fresh authorized opt-in evidence later than the previous withdrawal. List missing requirements.
```

## Limitations

- Does not send email, change ESP state, or approve a list for sending.
- Requires a verified runtime, schema, and host capabilities for canonical mutations.
- Cannot infer lawful basis when supporting evidence is missing.
- Works with pseudonymous identifiers and proof references, not raw contact data.

## Best Practices

- Use a pseudonymous subject ID and never include raw contact information.
- Provide source, timestamp, lawful basis, and proof references for every opt-in.
- Recheck live suppression status before any downstream email action.

## Anti Patterns

- Do not treat cached segments or exported rows as authoritative consent evidence.
- Do not restore permission using older or proxy evidence.
- Do not manually edit the consent stream or suppression cache.

## Security Audit

- Audited at: 2026-07-26T10:02:56.218\+00:00
- Summary: Most detections are Markdown formatting, fixed documentation links, or fixed local path resolution. One documented shell invocation accepts a supplied subject ID without showing quoting or argument-array handling, which can create command-injection risk if copied into a shell. No prompt-injection or data-exfiltration intent was found.

## Stats

- Views: 0
- Downloads: 7
- Favorites: 0
- Popularity score: 0