Control the trail left by a QuickT clip check
QuickT processes the public clip link and the technical result needed to show downloadable media. Limited job state, coarse timing, byte counts, and protected anti-abuse signals support the service. Mobile recent-link history remains in browser storage unless Private Mode prevents a new entry or you clear it, and temporary prepared files expire from the media node.
Notice updated 26 August 2026. QuickT explains mobile-link processing, on-device preferences and the limits of its server records.
1. What this policy covers
This notice covers QuickT's mobile workflow, network catalog, assistance form and device-handoff tokens. It does not replace a creator platform's own privacy statement.
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 QuickT. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
QuickT handles link and device context to resolve a mobile share, maintain queue state and present the result. Limited operational signals also support rate controls and incident analysis.
4. Temporary media and retention
QuickT deletes temporary mobile-ready outputs after their availability window closes. Operational traces and support messages follow limited purposes, while a durable device handoff may be removed by contacting support.
5. Service providers and upstream platforms
QuickT may use a creator network, hosting systems, databases and approved outbound routes for a mobile request. Optional ads or donations do not receive hidden service credentials.
6. Cookies and local storage
QuickT uses a first-party cookie for mobile quotas and abuse defense. Recent share links and interface preferences can stay on the phone, unless Private Mode is used, and may be erased through browser settings.
7. Your choices
QuickT visitors control whether a mobile link or message is sent. They can pause local history, erase site storage and use the help form for access, correction or deletion enquiries. Open the contact form.
8. Children, security and changes
QuickT is not a service for children under 13. Practical safeguards apply to the mobile workflow, while material policy adjustments appear here with a replacement date.