> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mnemom.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Aletheia Customer Voice — Privacy & Data Use

> What Aletheia Customer Voice collects, how it is used, retention periods, and your rights under GDPR

Aletheia Customer Voice is Mnemom's in-product feedback feature. A signed-in user in the Mnemom dashboard, or an agent authenticated with an API key, can send a compliment, problem report, or suggestion about the Mnemom platform itself. This page explains what data is collected, how it is used, how long it is retained, and how to exercise your rights.

<Note>
  This page does not constitute legal advice. It describes how Mnemom processes Customer Voice data. Consult qualified legal counsel for your specific GDPR obligations as a data controller or processor.
</Note>

## Consent block disclosure

This section contains the copy shown in the product's Customer Voice consent prompt, and this page is the "full details" destination that prompt links to.

<Info>
  **Mnemom Aletheia — Customer Voice**

  When you submit feedback, Mnemom records the feedback text, your reporter identity (your account, or your agent's identity if submitted via API key), and — only if you opt in — recent prompt context and diagnostic information. Sensitive content (emails, API keys, tokens, phone numbers) is redacted before storage. Feedback is retained until you or your org delete it, or until your org sets a retention period. [Full details and your rights →](/guides/customer-voice-privacy)
</Info>

## What we collect

| Data category | Examples | Collection trigger |
| - | - | - |
| **Feedback content** | Title (up to 500 characters), body (up to 20,000 characters), category (`compliment`, `problem`, or `suggestion`) | You submit feedback via the dashboard or `POST /v1/feedback` |
| **Reporter identity** | Your signed-in user ID, or your agent's ID if submitted via an API key | Always recorded — feedback is not anonymous |
| **Recent prompts** (optional) | Recent AI prompt context | Only if you check "include recent prompts" — gated on your explicit consent |
| **Diagnostics** (optional) | Diagnostic/debug context | Only if you check "include diagnostics" — gated on your explicit consent |
| **Contact preference** | Whether you agreed to be contacted about this submission | Always recorded |
| **Submission metadata** | Org ID (if applicable), submission surface (dashboard or API), timestamps | Captured on submission |

**What we do not collect:** Nothing beyond what you submit in the fields above. Before a submission is stored, its text is scanned and any credential- or PII-shaped content (email addresses, API keys, JWTs, long hex strings, tokens, phone numbers) is redacted.

## How it is used

Feedback is reviewed internally to improve the Mnemom product and prioritize fixes. It is not sold, rented, or transferred to third parties for their own purposes, and it is not used for advertising.

## Retention

By default, Customer Voice submissions are retained **indefinitely** — there is no automatic expiry. An org owner or admin can set a retention period (1–3,650 days) on the org's Customer Voice settings; see the [retention policy](/guides/customer-voice-retention) for how, and for the current state of automatic enforcement of that setting.

Regardless of any configured retention period, you can delete submissions at any time (see **Your rights** below) — that delete is immediate.

## Your rights

As the reporter (or the org owner/admin acting on your organization's submissions) you have the following rights:

| Right | How to exercise |
| - | - |
| **Access** | Export your org's Customer Voice submissions via `GET /v1/orgs/{org_id}/customer-voice/export` (owner, admin, or auditor role) |
| **Deletion (GDPR Article 17)** | `DELETE /v1/orgs/{org_id}/customer-voice/{submission_id}` for one submission, or `DELETE /v1/orgs/{org_id}/customer-voice` for every submission in the org (owner or admin role) |
| **Correction** | Submissions are point-in-time records; correction is handled by deleting the original submission and re-submitting |
| **Portability** | Submissions export as structured JSON via the export endpoint |

Both delete endpoints erase the matching rows synchronously and return `200 OK` with the number of rows deleted — there is no waiting period.

<Warning>
  Deletion is irreversible. Once a Customer Voice delete call returns, the submitted content cannot be recovered.
</Warning>

## Legal basis for processing

Mnemom processes Customer Voice data on the basis of:

* **Legitimate interests (GDPR Article 6(1)(f)):** Operating a feedback channel for the product customers depend on.
* **Consent (GDPR Article 6(1)(a)):** Expressed through the Customer Voice consent prompt, and separately through the explicit opt-in checkboxes for including recent prompts or diagnostics in a submission.

## Related

* [Customer Voice Retention Policy](/guides/customer-voice-retention) — Full retention schedule, deletion phases, and audit trail
* [GDPR Right to Erasure](/guides/gdpr-data-subject-rights) — Right to erasure and deletion cascade architecture
* [EU AI Act Compliance](/guides/eu-compliance) — Article 50 transparency obligations
* [Compliance Posture](/guides/compliance) — Mnemom's full regulatory compliance status


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.