Written to actually be read. No ad-tech boilerplate — this describes exactly what the extension and its backend touch, in the order you'd hit it using the product.
chrome.storage.local — on your machine, not our servers.| Permission | What it's used for |
|---|---|
tiktok.com / douyin.com access | Read the video data already present on the page you're viewing, so the download buttons work. |
youtube.com access | Detect a video URL to pre-fill the download box; nothing is read from the page beyond the URL. |
downloads | Trigger a save to your Downloads folder — the standard Chrome download flow. |
storage | Keep your download history, device ID, and (if used) license key locally in the browser. |
alarms | Check on a YouTube job's progress in the background if you close the popup mid-download. |
notifications | Tell you when a YouTube download finishes or fails. |
tabs / scripting | Know which site you're on and inject the on-page download button on TikTok/Douyin. |
This half never talks to any server we run. The extension reads data the page already loaded in your browser, and downloads come straight from TikTok's or Douyin's own servers. We have no visibility into which videos you download this way.
To build a downloadable mp4, the extension sends the backend: the video URL, your chosen quality, a random device ID generated on first use (not tied to your name or Google account), and — in metered mode — your license key.
The backend fetches the video, produces the mp4, and briefly relays that file through a private storage channel purely as a place to hold it until you download it; it isn't published, searchable, or shared. The job record (source URL, status, resulting file size) is kept only long enough to serve your download and, if a license is attached, to log the traffic deducted — deductions are recorded as an append-only ledger so balances can be audited, not as a viewing history tied to you.
Traffic packs are paid through PayPal. We receive confirmation that a payment succeeded and for which pack — we never see or store your card or bank details; that's handled entirely by PayPal under their own privacy policy.
Clear local history and the device ID anytime by removing the extension, or by clearing its site data from chrome://extensions. To have a license's server-side ledger data removed, email us the key you used to buy it.
If this policy changes in a way that matters, we'll update the date below. Questions or a data-removal request: [email protected].
Last updated: September 2026.