This service needs to process the link you submit and temporary task files to handle a download request. Download history is not publicly listed, but that does not mean links are never processed or that no logs exist.
What data do tasks and sessions involve?
- Task input: the public media URL, selected format, and title, duration, status and error information obtained by the server. Permission confirmation is validated at submission, not added as a persistent consent record.
- An anonymous session: a first-party HttpOnly cookie identifies the task owner; a CSRF token protects submissions. These are not credentials for the source platform.
- Temporary media: processing requires downloading, converting and temporarily storing files. This is not long-term storage.
- Rate-limit data: the application stores identifiers derived from the anonymous session or client and request times for abuse prevention, not a public download history.
Retention and cleanup
- Media: a ready file is available to download for up to 1 hour(s). Downloads stop at expiry. Temporary and expired files are deleted by cleanup; disk deletion is not guaranteed at the exact expiry instant.
- Feedback: the private review queue uses a 30 days retention period, separate from the short media limit.
- Task records: expired task metadata becomes eligible for deletion 24 hours after expiry. The source URL is cleared at terminal states such as completion or cancellation and on expiry processing; expiry cleanup also clears the title and duration.
- Sessions: an anonymous session is valid for 24 hours after issue. Clearing cookies may remove access to previous tasks but does not immediately delete server-side data.
- Rate-limit records: records older than 24 hours become eligible for deletion.
The worker triggers cleanup on each loop; accessing an expired, non-running task also triggers cleanup. Records beyond their retention period are deleted on the next cleanup. If the worker is stopped or unavailable, physical deletion may be delayed. These periods are not an unconditional promise of instant erasure. Cancellation still requires executors to stop; clicking cancel does not prove files have been cleaned up.
Where does the data go?
The page sends your input link only to this site's API, not to third-party analytics, font or advertising services embedded in the page. The server must contact the source platform to obtain media; that platform may record the server's requests.
These pages do not directly load external source-platform thumbnails or provide a public task history. Production Nginx / Cloudflare log fields and retention periods are currently unknown and require deployment-side confirmation. Application retention periods do not apply to those logs and are not a claim of no logging.
How is feedback handled?
Consent is validated at submission; no separate consent record is stored. The stored fields are the feedback ID, creation time, message and optional email address. They enter the site's private review queue for technical, content or copyright issues. A successful submission means it was received and saved, not that an email was sent, the issue was resolved or a response time is guaranteed.
Include only what is needed to review the issue, not passwords, verification codes, identity documents or private media. The maintenance entity, review responsibility and receiving arrangements still require operator confirmation; no organization, email address or credentials are invented here.
Correction and private deletion requests
Use the feedback form for a specific deletion or correction request, including an approximate submission time and only the details needed to locate it. Do not publish private information. Maintainers can verify and delete feedback through private administration. Receipt does not mean deletion is complete, and the form does not send email. If the queue is full, try later rather than sending duplicates.
You can read the site without submitting a task. Review the terms of use for usage boundaries.