A record’s life
Raw content is kept only as long as a stated purpose needs it. A post moves to the archive at 90 days, is de-identified at 365 days and is deleted at 1,095 days.

How long each thing is kept
One schedule covers every class of data, and one job applies it, every hour by default. This table is read from the product’s settings when this site is built.
| What it is | How long it is kept | What happens then |
|---|---|---|
| The answer a source returns, exactly as it arrived | 7 days | The answer is deleted; its header (the call, the service that answered, the cost and the status) is kept for 365 days |
| Original images, videos and audio | 72 hours after the verdict | Deleted, unless it is cited; its fingerprints and 6 of its key frames stay |
| Further key frames, the audio track and working copies of media | 72 hours | Deleted, unless it is cited |
| The detailed time series behind each topic’s lane on the Timeline | 48 hours | Rolled into hourly figures |
| Forecasts, with how each turned out | 35 days | Deleted |
| Counts by the minute | 90 days | Rolled up: five-minute counts are kept to 365 days and hourly counts are kept to 730 days |
| Items that failed processing, held for an audited replay | 14 days | Deleted |
| Posts, accounts, the replies, reposts, quotes, mentions and follows between them, and media records | 90 days in the live store, then in the archive | De-identified at 365 days: text, handles, links and ids are removed, and the topic, group of copies, state, language, stance, reach, authenticity band of the account and time are kept. Deleted 730 days later |
| The numbers computed from each post to compare it with others | 30 days in the live store, then in the archive to 90 days | Deleted |
| Transcripts of speech in media | 90 days | Deleted |
| The full answers of the media checks | 90 days | The full answer is deleted; the scores stay with the verdict |
| Service logs, which hold no post text, handles, links or user ids | 30 days in the live store, then in cold storage to 365 days | Deleted |
| Traces that follow one item through the services | 7 days | Deleted |
| Verdicts, groups of copies, coordinated groups and their reports, flags, labels, written explanations, response actions, daily reports, usage records and versions of the settings | 730 days | Exported to the archive in India, then deleted from the database |
| The audit log | Permanently | Never deleted |
| The reference set of media the checks are tested on | Permanently, under legal hold | Never deleted |
| Evidence packs: copies of everything a verdict, label, report or action cites | For as long as the record that cites it exists | Sealed and checksummed; deleted with the record that cites it |
| Reports | 730 days | Deleted |
Legal hold
A legal hold names a topic, a group of copies, a group of accounts or a single object. The retention job skips anything under a hold at every stage, so nothing it covers is moved, de-identified or deleted until the hold is lifted.
Anything cited by a verdict of likely or high certainty, a label, a report or a response action is copied into a sealed evidence pack when it is cited. The pack is kept for as long as the record that cites it exists, and later deletions cannot break it.
Closing a case seals its evidence pack and freezes the retention of the objects linked to it.
A hold is a change to the retention settings. In production it needs an approver and a second person’s acknowledgement, and every batch the job deletes is written to the audit log. Take-down requests, from a platform or from a person the data is about, run through the same job with their reason recorded.
When you leave
For a client of the shared system, leaving has three parts.
What you take
Your organisation’s data, as CSV files and a PDF summary.
When the rest goes
After the export, the rest is deleted within 30 days, without touching any other client’s data.
Public posts you shared with others
A collected copy that another client still watches stays for that client. A copy no client watches any more goes with the rest.
Compare this schedule with your own records policy, class by class.
Request a demo/trust/retention · Retention and deletion