How SaveTK treats public clip links and temporary files
SaveTK sends a public clip URL to the matching resolver and processes the returned media options you choose. Bounded job records, transfer facts, coarse timing, and privacy-protected identifiers support delivery and abuse prevention. Publisher download controls are not bypassed, prepared files are temporary, and your browser decides how long local preferences or recent links remain.
Dated 26 August 2026. SaveTK sets out how creator-post requests, local history and support messages are treated.
1. What this policy covers
SaveTK includes post checks, source listings, support communication and opaque continuation URLs. The original social service keeps authority over its account and audience data.
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 SaveTK. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
SaveTK uses post-level evidence to find creator-visible assets, prepare the chosen copy and keep requests within fair limits. Diagnostics are retained only for reliability and abuse response.
4. Temporary media and retention
SaveTK prepares creator-post copies temporarily and removes them with scheduled cleanup. Diagnostics are bounded, assistance messages remain until resolved and support can delete an opaque result-continuation record.
5. Service providers and upstream platforms
SaveTK can contact the post publisher and the operational providers needed to prepare an authorized copy. Backend tokens and routing details remain private even when a result is shared.
6. Cookies and local storage
SaveTK protects capacity with a first-party visitor cookie. Creator-post history and preferences can be held locally, are not added during Private Mode and can be removed with the browser's site-data controls.
7. Your choices
Only share creator-post links with SaveTK when you accept their processing. Private Mode and browser deletion control local history, while support handles questions about retained service records. Open the contact form.
8. Children, security and changes
SaveTK is intended for people aged 13 and over. Technical precautions cannot make the internet perfectly safe, and future substantive policy changes will be clearly dated.