Verity stores information for processed request URLs in the Verity database. Data stored includes:
...
JSON response data is maintained by Verity for a time-to-live (TTL) period. The default TTL varies depending on the type of content analyzed.
There are different TTL periods for Video, Image, and Text data. Page data is further analysed to differentiate between website home pages and all other pages on the site (as website home pages are likely to update frequently).
For example https://www.latimes.com/, the home page of the Los Angeles Times, will be updated frequently and will therefore have a TTL of 30 minutes. The page https://www.latimes.com/travel/list/la-best-dog-friendly-hikes-trails-beaches-parks is unlikely to be updated frequently and will have a TTL of 30 days.
Verity considers a home page to be a web page accessed at either:
<website URL>/<website URL>/index.htmlPage –
...
360 days | ||
...
4 days | ||
...
30 days | ||
Every Verity response includes processedAt and expiresAt fields, indicating the date and time that classification data was generated and will expire from Verity storage:
| Code Block |
|---|
"processedAt": "2021-05-25T17:57:03.690Z" |
...
"expiresAt": "2021-06-24T17:57:03.690Z" |
GumGum backs up Verity page and video analysis classification data for 11 months. The page, image, and video metadata is backed up for 180 days.
...