Overview
This page describes how long data persists in Seeq and what Seeq treats as authoritative.
Seeq has two storage models. The first is content created in Seeq, specifically, analyses, topics, projects, Vantage rooms, and anything else a user builds. Seeq stores this content and does not expire or purge it on a schedule. The second is data pulled from connected datasources. Seeq is a calculation and visualization layer rather than a replacement historian, so this data is retrieved and cached rather than stored, and the source system remains authoritative.
Content Created in Seeq
Seeq does not apply an automatic expiration period, time-to-live, or scheduled purge to customer-created content in an active Seeq tenant. This includes Workbench Analyses, Organizer Topics, Data Lab Projects, Vantage Rooms, and the configurations and metadata associated with that content.
This content remains available until it is deleted by an authorized user, or until deletion is required by the applicable customer agreement, a customer request, applicable law, privacy requirements, or service-termination procedures. Seeq’s access controls and, provided that audit trail is enabled, audit capabilities apply to content changes and deletion activity.
Data That Originates in Seeq
Unlike data retrieved and cached from connected datasources, some data originates in Seeq itself. This includes Vantage event and context records persisted as part of a Vantage Room, uploaded CSV content, and manually created signals, conditions, and scalars. For this data, Seeq is the system of record, and the retention behavior above applies in full.
Connected Datasource Data and Caching
Seeq does not replace the connected datasource as the authoritative system of record. Seeq may retain portions of data retrieved from connected datasources in the customer’s isolated Seeq tenant to improve performance. This cached data is not the authoritative copy of the source data. Cached data may be invalidated automatically, evicted as part of cache management, or cleared by a user or administrator. Cache behavior is separate from the lifecycle of Seeq application content.
For details on cache behavior and cache invalidation, see Understanding Data Caching.