Skip to content

Retention, legal hold and subject requests

Regulations disagree about records: one says keep call logs for years, another says delete personal data as soon as you can. Get it wrong one way and evidence is gone; the other way and you hold data you shouldn't. Vidai sets how long each kind of record is kept from the regulations you follow, never shortens anything behind your back, holds everything when a dispute needs it, and answers a person who asks for a copy of their data or for it to be erased.

How long each record is kept

Proof › Retention & legal hold covers Vidai's own records of AI requests:

Record What it covers
Prompt and reply text What was sent and what came back. The gateway holds it
Call records Who called what, when, the outcome, findings and cost
Tamper-evident records The gateway's sealed records and their seals Enterprise
Audit log Who changed what. Kept for good; erasing someone removes their details, never the record

What Enterprise includes depends on the features your licence includes. Retention, legal hold and subject requests are in every edition.

Each regulation you follow sets a floor: the shortest time some records may be kept ("EU AI Act needs 180 days"). GDPR instead lets you set a ceiling for personal data. A period below a floor is refused, naming the regulation.

Nothing is shortened by itself. Deleting can't be undone, so when a regulation's floor and your GDPR ceiling clash, the longer period applies until an organisation admin decides, with a reason recorded. Stopping following a regulation leaves your periods as they are.

Proof › Retention & legal hold: each kind of record with what's kept, the floor that sets it, and the regulations followed

Hold every record is one switch. While it's on, nothing is deleted, by Vidai or the gateway, and every row reads "Forever". Switching it on or off asks for a reason, recorded in the audit log.

Data subject requests

When someone asks, under GDPR, UK GDPR, CCPA, India's DPDP Act or the Gulf laws, for a copy of their data or for it to be erased, Proof › Data subject requests answers call by call. Choose whose calls: a person, an agent, a key, an application, or an end user your applications name in their requests.

flowchart LR
  Ask[Someone asks] --> Kind{What they asked for}
  Kind -->|A copy of their calls| Copy[A JSON Lines file<br/>content only where you may read it]
  Kind -->|Their content erased| Erase[Content erased here<br/>and on the gateway]
  Erase --> Each[Each call says what happened:<br/>Erased · Waiting for the gateway ·<br/>Held · Kept by a regulation · Nothing kept]
  • A copy includes content only where the person making the request may read it, and every inclusion is recorded.
  • An erasure removes what the calls sent and got back, here and on the gateway. The calls' records stay, without content, and in Request logs their content reads Erased. A call younger than a regulation you follow requires is Kept by a regulation, named, until then. Legal hold stops erasure altogether.

Organisation admins and Compliance officers make requests; nobody else sees the page.

Proof › Data subject requests: an erasure, with what happened to each call