Privacy and Compliance
Hunch includes workspace-level controls for data minimization, retention, export, and destructive delete workflows.
Redaction policy
You can set the overall PII redaction level to:
offstandardstrict
You can also choose which stored areas receive redaction treatment, including:
- chat transcripts
- answer traces
- analytics payloads
- handoff notes
- lead message bodies
Retention windows
Retention can be configured separately for:
- chat transcripts
- analytics events
- lead captures
- human handoffs
- answer traces
- security events
You can leave a bucket unset to keep it indefinitely, or define a retention window in days.
Retention sweeps
Hunch can run retention cleanup manually from Settings, and retention checks also run as part of the broader compliance workflow.
Use a manual sweep when:
- you just changed the policy
- you are responding to a privacy request
- you want to verify the new retention window behaves as expected
Compliance report
The built-in compliance report summarizes:
- workspace member count
- operator security posture
- stored data inventory
- recent compliance activity
- recommendations and warnings
This is useful for internal reviews, customer questionnaires, and operational audits.
Workspace export
Workspace owners can export the full workspace dataset for:
- privacy requests
- internal archive workflows
- compliance review
- migration or backup use cases
Account and workspace deletion
Workspace owners can also permanently delete the owner account and its workspace from Settings.
This is destructive and removes the workspace, including operational history tied to it.
Recommendations
- Turn on at least standard redaction for teams handling sensitive conversations.
- Set explicit retention windows instead of leaving all buckets indefinite.
- Review the compliance report after major workflow changes.
- Pair compliance controls with MFA, IP allowlists, and enterprise session policy.
See also: