Consent, Privacy & Retention: Policy Designer
Create consent texts, versioning, revocation, and retention schedules that match your intake data.
Prompt Overview
Featured AI Partner
Tips For You
- Keep a short consent inline and link to the full policy. - Show last-updated date and version. - Store consent locale and IP/device fingerprint where allowed.
From Operations TeamNexusAi TechnologyProblem It Solves
Ensures legal clarity and operational handling of consent and retention without ad-hoc policies.
Plain-Language Consent
Readable texts with clear purposes.
Versioned Records
Track every consent update and locale.
Retention Matrix
Purge rules per data/document type.
Revocation Workflow
Operational steps to honor requests.
AI Prompt Instructions
Act as: A privacy counsel and data governance architect for service intake.
Why this task matters: Clients share sensitive info. You must inform, get consent, and manage retention properly.
Important boundaries: Plain-language consent. Versioning. Explicit revocation process. Retention per document type and jurisdiction. Avoid collecting more than necessary.
User inputs:
- Data categories and purposes
- Jurisdictions and minimum/maximum retention
- Contact method for revocation
Objectives:
- Draft consent texts and variants
- Define consent capture/versions in DB
- Map retention rules per data/doc type
- Outline revocation and data subject requests
Analysis workflow:
1) Inventory data categories and purposes
2) Draft consent clauses with references to policies
3) Design DB consent tables with version, timestamp, actor
4) Create retention matrix and purge/archive flows
Required output format:
- Consent text (short/long)
- DB model for consent
- Retention matrix
- Revocation workflow
Quality controls:
- No hidden consents
- Clear contact and timelines for requests
- Logs for revocations and purges
Verification checklist:
- Are consents linked to submissions and files?
- Can we show consent history to auditors?
Final instruction: Output production-ready consent texts and operational handling steps.
Expected Outcome
Consent v1.2: We collect your info to assess eligibility and fulfill services. Retention: ID docs 5y; statements 2y; consent logs 7y.
Implementation Journey
Draft consent in ChatGPT
Provide data categories, purposes, and jurisdictions. Ask ChatGPT to generate short/long consent texts with versioning notes.
20 minModel consent in Supabase
Create consent tables with version, locale, timestamps, and linkage to submissions. Enable audit logging of changes.
25 minImplement retention jobs
Schedule Supabase jobs to purge/archive data by category and retention rules, logging every action.
40 min