Know what follows a short-video link through DWTT
When DWTT analyzes a public clip URL, it uses the link, resolver state, timing, format choice, and limited anti-abuse identifiers to complete the request. Recent-link and interface preferences may stay on the device. We do not ask for social-account credentials, and the source network's own privacy rules remain separate from this policy.
Updated on 26 August 2026. Read this page to understand how DWTT handles clip requests and what stays only on your device.
1. What this policy covers
DWTT's clip workflow, service catalog, help messages and private result handoffs are covered here. A social network you visit through a submitted URL keeps its own separate policy.
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 DWTT. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
DWTT processes operational details so a shared clip can be checked, queued and delivered reliably. The same signals support rate limits, incident review and replies from the help team.
4. Temporary media and retention
DWTT expires signed clip deliveries and deletes temporary prepared copies on the cleanup schedule. Operational evidence is short-lived, support correspondence lasts through resolution and a private handoff can be removed on request.
5. Service providers and upstream platforms
DWTT can communicate with the clip host plus infrastructure needed for resolution and delivery. Optional commercial integrations operate separately, and no provider secret is exposed to the visitor.
6. Cookies and local storage
A DWTT cookie supports fair-use limits. Local storage can keep clip preferences and recent public addresses on the device, while Private Mode prevents new history entries and browser settings can erase them.
7. Your choices
Submit only clip links and support details you are comfortable sharing with DWTT. Use a private session for no new local history, clear site data yourself or ask the team about a protected record. Open the contact form.
8. Children, security and changes
DWTT does not target children below 13. Technical and organizational protections reduce risk without eliminating it, and substantive policy revisions will carry a fresh publication date.