How EasyT handles transcripts, media, and local work
EasyT processes a public source URL and the resulting track metadata when you request video, audio, subtitles, or transcripts. Temporary preparation state and privacy-protected diagnostics help complete the job. Files opened in local media tools stay in browser memory, and language or format preferences can remain on the device until you clear them.
Published 26 August 2026. This EasyT notice covers request data, local settings and the boundaries that continue to apply on your device.
1. What this policy covers
This EasyT policy follows the website, reusable-media tools, contact route and opaque continuation records. Publishers linked from the product maintain their own privacy practices.
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 EasyT. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
EasyT relies on operational data to identify reusable assets, manage preparation and keep the service fair. It is also used for troubleshooting, fraud controls and direct support responses.
4. Temporary media and retention
EasyT does not treat prepared outputs as permanent storage. Expiring delivery links and cleanup remove them, while minimal diagnostics and support records follow their separate needs. A saved handoff identifier can be deleted through support.
5. Service providers and upstream platforms
EasyT may reach the original publisher and the infrastructure required to analyze or prepare an asset. Optional integrations receive only what their feature needs, never backend credentials.
6. Cookies and local storage
EasyT uses one visitor cookie for fair access. Device storage can retain workflow choices and public links, but Private Mode stops new history and standard browser tools delete it.
7. Your choices
Do not provide EasyT with an address or message you prefer not to process. Use its private workflow, remove device storage when desired and contact the team for server-record questions. Open the contact form.
8. Children, security and changes
EasyT serves an audience of 13 and above. We use reasonable operational protections, avoid promising absolute security, and identify later material edits with a new effective date.