Reference
Privacy and network behavior
Understand the offline-first product boundary and explicit signed catalog request.
Capture Studio has no AI feature, training use, telemetry, analytics, account, API key, customer-media upload, background update check, social publishing, or marketplace publishing.
The only product network action is Check for profile updates, initiated explicitly by the user. It downloads a bounded signed catalog from HTTPS on kiwistudios.co, authenticates it, displays the exact diff, and waits for confirmation. It never uploads project data or media. The product works fully offline with its built-in dated catalog.
Evidence tokenizes paths. Paths inside the project use ${PROJECT}, ${ASSETS}, or ${CACHE}. External paths retain a short hash and filename without the parent directory. Output and source content hashes remain local unless the user intentionally shares evidence.
Customer media, generated proxies, thumbnails, waveforms, caches, outputs, and recovery data stay in the customer’s project or chosen local output location.
Still stuck?
Bring the run receipt with you.
Include the Capture Studio version, Unity version, operating system, render pipeline, Recorder version, output profile, receipt, restoration status, and a minimal reproduction.