Retention is primarily an organizational policy decision, not a one-click compliance guarantee
The product supports retention metadata and legal hold, but it does not replace the need for a defined internal policy.
Trust Center
Retention, legal hold, and deletion controls
Whispr includes retention-related fields, legal hold controls, and export paths, but retention policy still needs to be defined by the organization. This page shows what the product supports and where internal policy or contract terms still matter.
Retention metadata, legal hold controls, export paths, and manual deletion in some flows
The current product can record retention-related metadata and block certain actions when a legal hold is active.
Confirm your policy with legal, privacy, and signed service terms
Retention obligations vary by jurisdiction, sector, and case type. Your internal policy and contract should define the final rule set.
The codebase supports retention metadata and legal hold, but not universal auto-deletion by default
Compliance cases include retention-related fields such as policy keys and delete-after timestamps, but those fields are not universally populated by default. Legal hold is present and blocks some sensitive compliance actions such as case closure and case export.
Deletion and export exist as operational actions, not as a full retention engine
In the current product, some admin flows support manual report deletion and export. The codebase also contains compliance export behavior and oral-intake defaults that include a retention period field.
- Manual report deletion is implemented through admin endpoints.
- Compliance export exists and is blocked when legal hold is active.
- Handler-created oral intake currently applies a default retention period field.
Retention schedules should come from your governance model, not from assumptions
Because the product does not expose one universal deletion lifecycle across every mode, customers should define retention schedules and approval paths with legal, privacy, HR, or compliance stakeholders before relying on product behavior alone.
Account closure and post-termination handling belong in the contract
Whispr does not publish fixed post-termination timing or deletion commitments on this page. If your team needs offboarding timing, export support, or deletion commitments, confirm them in the service agreement or procurement process.
Legal hold is an operational control, not just a page label
Compliance mode includes a legal-hold flag, and the backend explicitly blocks case close and export actions when a hold is active. That makes the legal-hold feature materially relevant to the operating workflow, not only to UI presentation.