SAVACLIP / PRIVACY
Privacy and data handling
How SavaClip handles source URLs, download jobs, temporary files, logs, and platform sessions.
Scope of this notice
This notice describes the current SavaClip implementation and may be updated when the service changes. SavaClip does not require a visitor account. Do not submit confidential source links or sensitive personal content. Privacy questions can be sent to [email protected].
Source links and job records
A download job stores the submitted source URL, selected options and supplied title, status and progress, retry information, timestamps, a hashed access token, and file details such as name, size, path, and expiry. The service uses these records to process, retry, cancel, and serve downloads. URLs can themselves contain identifiers or personal information. Preview requests retrieve source metadata; Douyin metadata can also enter the cache described below.
Files and retention limits
Completed-file links expire 24 hours after completion. Save your file before expiry; availability during that window is not guaranteed. Files are physically deleted only while the cleanup worker is running, and deletion can fail, so a file may remain on the server after its link expires. This service is not permanent storage. The completed-job cleanup attempts to remove expired files and their job records. It does not provide a comprehensive deletion schedule for failed or cancelled jobs, partial files, or operational logs; these have no fixed retention period enforced by the current code. A failed file deletion can leave a file behind even after its job record is removed. Cancellation stops work where possible but is not a request to erase all related data.
Douyin metadata cache
The service can cache Douyin source URLs, media identifiers, source metadata, and temporary media delivery URLs to avoid repeated source requests. Cache reuse is time-limited (five minutes by default, configurable up to thirty minutes). Expired database entries are removed when a later cache write runs, not necessarily at the moment they expire.
Cookies and browser storage
The downloader interface keeps active job state in page memory; it does not implement visitor account cookies or persistent download history in browser storage. The server can use operator-managed platform sessions, encrypted cookie records, temporary cookie files, and a persistent browser profile when retrieving media. These are not your browser’s login session. Never send your own passwords or cookies to obtain support. Operator session storage has no visitor-facing automatic deletion schedule. Infrastructure providers such as Cloudflare may set their own technical cookies.
Logs and network providers
Operational logs record events such as queued jobs, source URLs, error codes, and processing outcomes. The application logger removes URL query strings and redacts sensitive field names, but that is not a promise that every infrastructure log is anonymous. The site is served through Cloudflare; Cloudflare and hosting or network providers may process connection information such as IP addresses and request metadata under their own practices. The project does not specify a fixed log retention period.
Requests to third parties
Source platforms and media delivery services receive requests needed to retrieve metadata and files. Video thumbnails displayed in the downloader can load directly from third-party hosts in your browser, exposing connection information such as your IP address to those hosts. Following external help links also sends you to a third party. Those services have their own policies.
Protect access links and ask questions
Treat job and file links as sensitive: someone with the access token may access job status or the completed file while it is available. Do not post those links publicly. Email [email protected] for privacy questions or a data request; there is no guaranteed response deadline or automated erasure process.
Provider reference: Cloudflare Privacy Policy.