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.

Media Verdict console

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 isHow long it is keptWhat happens then
The answer a source returns, exactly as it arrived7 daysThe 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 audio72 hours after the verdictDeleted, unless it is cited; its fingerprints and 6 of its key frames stay
Further key frames, the audio track and working copies of media72 hoursDeleted, unless it is cited
The detailed time series behind each topic’s lane on the Timeline48 hoursRolled into hourly figures
Forecasts, with how each turned out35 daysDeleted
Counts by the minute90 daysRolled 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 replay14 daysDeleted
Posts, accounts, the replies, reposts, quotes, mentions and follows between them, and media records90 days in the live store, then in the archiveDe-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 others30 days in the live store, then in the archive to 90 daysDeleted
Transcripts of speech in media90 daysDeleted
The full answers of the media checks90 daysThe full answer is deleted; the scores stay with the verdict
Service logs, which hold no post text, handles, links or user ids30 days in the live store, then in cold storage to 365 daysDeleted
Traces that follow one item through the services7 daysDeleted
Verdicts, groups of copies, coordinated groups and their reports, flags, labels, written explanations, response actions, daily reports, usage records and versions of the settings730 daysExported to the archive in India, then deleted from the database
The audit logPermanentlyNever deleted
The reference set of media the checks are tested onPermanently, under legal holdNever deleted
Evidence packs: copies of everything a verdict, label, report or action citesFor as long as the record that cites it existsSealed and checksummed; deleted with the record that cites it
Reports730 daysDeleted

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.

  1. What you take

    Your organisation’s data, as CSV files and a PDF summary.

  2. When the rest goes

    After the export, the rest is deleted within 30 days, without touching any other client’s data.

  3. 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