Skip to main content
This page documents retention and deletion for data collected by Aletheia Customer Voice (in-product feedback). Retention is a per-org setting, not a plan-tier default — see below for exactly what it does and does not do today.
This document describes the technical retention implementation. It does not constitute legal advice. Consult qualified legal counsel for your specific obligations under GDPR or other applicable data-protection regulations.

​
Retention setting

Every org has a retention_days value for its Customer Voice submissions: an integer from 1 to 3,650, or null. The default is null — retain indefinitely — until an org owner or admin sets a value.
Setting retention_days records the org’s retention policy, but nothing currently reads it to automatically delete aged submissions. There is no scheduled job that enforces this setting yet. The API reports this honestly: the settings response includes "enforcement_active": false. If you need a submission gone, delete it explicitly — see On-request deletion below.

​
Configuring retention

The org-scoped settings endpoint authenticates with a bearer token and is available to the owner/admin (write) or owner/admin/auditor (read) roles. Check the current retention setting for an org:
Set a retention period:
Restore indefinite retention:

​
On-request deletion

Because automatic expiry is not yet enforced, deletion today is always explicit — issued by an org owner or admin. Both endpoints erase the matching rows synchronously (the erasure is complete by the time the response returns) and return 200 OK. Delete all Customer Voice submissions for an org:
Delete a single submission:
A submission ID that doesn’t exist, or belongs to another org, returns 404 either way — the response never discloses which.
Deletion is irreversible. There is no tombstone or recovery window once a submission is erased.

​
Audit trail

Every export, deletion, and settings change is recorded internally in Mnemom’s governance audit log against the acting user and the org. This is a separate log from the general request-level GET /v1/orgs/{org_id}/audit-log endpoint (which covers HTTP-request metadata, not this feedback-specific governance trail) — there is currently no dedicated customer-facing endpoint to query these particular records directly.