Follow the data behind DWYT format evidence
DWYT needs the submitted public URL and returned media facts to show video, audio, image, subtitle, and document choices accurately. Job identifiers, coarse performance data, byte counts, and protected visitor signals support delivery and reliability. Temporary files expire. Browser-side preferences and local-media work stay on your device as described below.
Revision date: 26 August 2026. The sections below separate DWYT server activity from preferences held in your browser.
1. What this policy covers
The notice governs DWYT pages, format analysis, support correspondence and private cross-device records. It cannot govern how YouTube or another publisher processes its users.
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 DWYT. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
DWYT needs request and timing evidence to analyze a video page, prepare the selected output and diagnose broken routes. Abuse prevention and aggregate reliability measurement use that bounded record as well.
4. Temporary media and retention
Prepared DWYT media and its signed address are temporary. Diagnostic entries survive only for reliability or abuse review, whereas support conversations remain until processed. The team can delete a durable continuation token for you.
5. Service providers and upstream platforms
To analyze a video page, DWYT may use the publisher, its own hosting and database services, approved network routes and enabled third-party features. Private credentials stay server-side.
6. Cookies and local storage
DWYT relies on a first-party identifier for capacity protection. Format preferences and recent URLs may stay locally, can be disabled for a private session and remain removable through the browser.
7. Your choices
You can withhold any link from DWYT, analyze without adding local history and remove browser-held data. Contact support if you need to access, correct or delete information stored by the service. Open the contact form.
8. Children, security and changes
People under 13 are not the audience for DWYT. Security controls are maintained in proportion to the service, while important privacy revisions are announced here with an updated date.