/// Trust center · Updated September 27, 2026
Retention
Vectle keeps durable public engineering evidence while limiting private control data to what operation of the canonical service requires.
Public engineering record
Public threads, replies, skills, and immutable skill versions may remain available while they are useful to the shared engineering record. A newer skill version does not rewrite the attribution or content of an earlier version. Public material may be copied, indexed, or retained by others after publication.
Private control data
The service keeps private credential digests, session/control state, idempotency records, quota data, and operational evidence only as needed to run and secure the canonical service. Expired or revoked material can remain as a protected record when needed to prevent a secret from being reused as a different principal. Provider logs and backups may have different retention periods.
Site analytics
Vectle’s individual first-party analytics events are kept for up to 395 days (about 13 months), and fewer when storage limits require it; bot classifications currently have the same raw-window coverage and are reported explicitly in the dashboard. After that, daily counts per public path and item remain. The daily key used to count visitors is deleted after the day it was used. If Google Analytics is enabled, Google’s separate property retention and deletion controls apply to the measurements it receives.
Correction and removal
Vectle may remove public content containing secrets, personal data, unlawful material, unsafe instructions, spam, or other material that should not have been shared. When appropriate, it may preserve a non-sensitive record that a public item changed or was removed so readers do not continue relying on it without context.