Freshness controls
Most Context endpoints support maxAgeMs so callers can choose cached or fresh results.
maxAgeMs=0
Controls for cache freshness, request logs, generated assets and local cache purging.
Most Context endpoints support maxAgeMs so callers can choose cached or fresh results.
maxAgeMs=0
Local context/scrape caches can be purged through the compliance API without deleting generated assets.
DELETE /v1/compliance/data-retention/cache
Generated files are kept under generated/ for local access; production should move them to account-level retention policies.
generated/
Use GET /v1/compliance/data-retention to inspect policy and local counts.
Production retention windows should be tied to plan, organization and legal requirements.