Separate Insts workflow records from your device data
Insts processes each public link, selected format, queue stage, delivery status, and a small set of protected reliability signals. Those server-side records are distinct from recent links and interface settings stored in the browser. Prepared outputs are temporary, continuation tokens are opaque, and local-media tools do not upload the file you open for in-browser conversion.
Updated 26 August 2026. The Insts privacy guide distinguishes workbench evidence, temporary processing and information retained in the browser.
1. What this policy covers
The Insts workbench, rendition directory, contact channel and continuation mechanism fall within this document. Source websites are governed by their respective operators.
2. Information processed
- Submitted links: the public URL is sent to the resolver so it can detect the source and return formats.
- Operational data: request identifiers, coarse timing, status, byte totals and privacy-protected visitor or IP hashes help prevent abuse and diagnose failures.
- Contact messages: name, email, subject, optional public URL and message are stored in the private control center.
- Continuation links: an opaque token maps to the cleaned public media URL in the control database. The URL is not embedded in the token or QR code.
- Device-only preferences: recent-link history, format preference and private-mode choices stay in browser storage unless you clear them.
- Local media tools: a file selected on the local-tools page is read into temporary WebAssembly memory in your browser and is not uploaded to Insts. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
Insts uses workbench evidence for rendition comparison, queued preparation and failure investigation. It also enables fair-use enforcement and informed answers to technical questions.
4. Temporary media and retention
Insts keeps prepared workbench outputs only for the delivery window. Technical observations expire according to operational need, support threads last through handling and an opaque continuation entry can be erased by the team.
5. Service providers and upstream platforms
An Insts job may involve the source host and the workbench's storage, database and network providers. Optional revenue features stay isolated from private routing credentials.
6. Cookies and local storage
Insts stores a quota cookie first-party and can remember workbench settings locally. A private session writes no new recent-link history, and site storage is removable at any time.
7. Your choices
Insts lets you skip any submission, work without adding to recent local items and clear stored settings. Send privacy questions or deletion requests through the help route. Open the contact form.
8. Children, security and changes
Insts is not built for children below 13. Its security practices are reasonable rather than infallible, with any substantial rule revision recorded by date on this page.