Introduction
We believe a simple tool needs simple data practices. This page explains precisely what happens to information that reaches us when you use the site: what we process, what we don’t, and why.
[The site operator’s operational details — legal name, contact email, and jurisdiction — will be added here before launch.]
The link you paste: transient processing, no storage
When you submit a video link, we process it in the server’s memory for the moment it takes to request the video’s public page from TikTok and extract the media options. We do not save the link to a database, we keep no history of your links or downloads, and we don’t tie requests to your identity. Once the request ends, the servers discard the data.
While a video file is being delivered to you, the data streams through our servers with caching disabled and no storage; the raw media URL never reaches your browser — it stays inside a signed ticket that expires automatically.
Infrastructure logs from Cloudflare
The site is hosted on Cloudflare (Pages and Pages Functions). As part of delivering the service, Cloudflare logs incoming requests according to its standard practices — these logs typically include your IP address, user agent (browser and operating system), timestamps, and data volume. Those logs belong to Cloudflare and are governed by its own policy; we add no databases of our own on top.
At our application level, when an error occurs we may log its general category and status code for debugging purposes only — never full links and never identifiers that point back to you.
The consent cookie
On your first visit, a banner asks for your consent regarding analytics and advertising. Your choice is stored in a first-party cookie named tt_consent containing the consent state and its timestamp, lasting about six months. This cookie is essential to fair operation: it guarantees tracking tools load only after you consent, and that a later change of heart is honored.