Security & Privacy
This page explains the practical security and privacy expectations around uploads, generated outputs, retention windows, and the safeguards we surface on AI-assisted media workflows.
How file handling works
Files are uploaded only for the requested processing task, such as transcription, subtitle generation, subtitle translation, format conversion, or audio cleanup.
Generated outputs follow the same lifecycle as the source job and are auto-deleted after approximately 2 hours unless a shorter retention window is needed for technical or abuse-prevention reasons.
What we store and for how long
We may temporarily process technical metadata such as IP address, browser details, request timing, file size, and error traces to protect the service, enforce limits, and diagnose failures.
We do not position the site as a permanent storage product. The default expectation is temporary processing, download, and deletion rather than long-term file retention.
Why the service can be useful without a login
A no-signup workflow reduces friction for quick media tasks, internal tests, one-off caption jobs, and fast transcript drafts.
The same low-friction approach is paired with short retention and clear file limits so users can understand the operational boundaries before upload.
Security FAQ
Are files used to train public AI models? No. Uploaded media is not used to train public AI models.
How long are files kept? The service is designed around temporary processing and auto-deletion after about 2 hours.
Can I change cookie choices later? Yes. Where Google shows a consent message, those choices can be updated through that Google consent interface.