MH MediaHarvester Web Context API
RETENTION CACHE DELETE

Data Retention Controls

Controls for cache freshness, request logs, generated assets and local cache purging.

Cache

Freshness controls

Most Context endpoints support maxAgeMs so callers can choose cached or fresh results.

maxAgeMs=0
Purge

Local cache purge

Local context/scrape caches can be purged through the compliance API without deleting generated assets.

DELETE /v1/compliance/data-retention/cache
Assets

Generated files

Generated files are kept under generated/ for local access; production should move them to account-level retention policies.

generated/
Retention API Machine-readable controls

Use GET /v1/compliance/data-retention to inspect policy and local counts.

Production retention windows should be tied to plan, organization and legal requirements.

Trust resources