Douzy User Agreement and Privacy Policy

Version v4.9.0 | Effective 2026-11-17


Please read before use

Douzy is a local desktop UI and local task-management application. The Renderer itself contains no platform download logic. Douyin, TikTok, and YouTube capabilities are provided by third-party plugins that you enable; Telegram runs through an on-device TDLib capability; X runs through a local X capability shipped with the installation package. All capabilities are subject to account permissions, content protection, network conditions, third-party platform rules, and applicable law.

Part 1: User Agreement

1. Product Description

1.1 Douzy runs on your device and is used to display and manage local UI workflows, third-party plugins, TDLib, X task status, and local file paths. Douzy is not an official client of Douyin, TikTok, YouTube, Telegram, X, or any third-party platform.

1.2 Words such as "download," "sync," "scan," and "batch" in the interface only mean invoking, submitting, or managing tasks of the third-party plugins you have enabled or of the on-device TDLib; there is no guarantee that content on a third-party platform will be accessible, savable, compatible over the long term, or suitable for your purposes.

1.3 Before first use, Douyin, TikTok, and YouTube require you to prepare and open the third-party plugin panel. Telegram does not appear in the plugin center, and its entry point is determined by the local TDLib capability; you must sign in before use, and Douzy will not join channels automatically. The X capability is shipped with the installation package, but its panel is off by default; before use you must confirm the platform rules and the boundaries of Cookie use.

2. License to Use

Provided that you accept this document, Douzy grants you a personal, non-exclusive, non-transferable, non-sublicensable, revocable software license to run Douzy on your own device, manage third-party plugin, TDLib, or X tasks, and view local file status.

You may share links to the official release pages, but you may not modify, repackage, or impersonate an official version, remove rights notices, or distribute installation packages that contain your personal data, platform Cookies, plugin packages, local configuration, or other sensitive information.

Some features require a valid license key. A license key may be used only by the purchaser, within the agreed number of devices, and may not be transferred, shared, sold, posted publicly, or activated on behalf of others. Features that require a license key may be adjusted, suspended, or withdrawn; this is not a commitment to permanent availability, future pricing, or platform compatibility. When a license key expires, is disabled, or the device is removed, those features stop working, and other features are not affected. When you actively click the entry for obtaining or renewing a license key, Douzy displays in the app the plans provided by the license service and shows a payment code generated by a third-party payment channel, which you scan with a mobile payment app to pay. Payment is completed on the third-party payment channel and handled by an independent payment service provider; Douzy does not access your payment account information.

After a new purchase is credited, if this device has no valid license, Douzy activates automatically; if this device already has a license, Douzy only saves the new license key, and you decide whether to use it. When you replace the current license with a new license key, the remaining term of the original license is not transferred.

Renewal does not issue a new license key; instead, the license service extends the expiration date of the current license key: if it has not expired, the extension runs from the original expiration date, and if it has expired, from the time payment is credited. Devices already bound to that license key update automatically after their next online license check, and the number of devices that can be bound does not change. Upgrading to a lifetime license is priced at the full price of the lifetime plan, and remaining days are not prorated. If the status of the current license key changes during payment so that it cannot be extended, this payment may instead result in a new license key being issued.

When in-app purchase is unavailable, you can still open the purchase page provided by the license service in your system browser; after payment is confirmed, the page provides a new license key, and you need to return to Douzy to enter and activate it manually. The actual plans, prices, availability, after-sales service, and delivery status are as stated in the purchase interface, the purchase page, and the support channels.

3. Boundaries of Use

You are responsible for confirming that the input sources, account permissions, saving behavior, and subsequent uses are lawful and compliant, and you must not use the Douzy UI, enabled third-party plugins, or TDLib to:

  • process content that you have no right to access, save, or use;
  • circumvent a third-party platform's access controls, privacy settings, technical protections, rate limits, or account security mechanisms;
  • publicly distribute, repost, sell, or sublicense locally saved content, or use it for commercial data services;
  • process other people's likeness, privacy, or personal information without authorization;
  • use content for AI training, datasets, public-opinion monitoring, account intelligence, traffic inflation, content spinning, or illicit or gray-market activities;
  • bypass license keys, device binding, signature verification, update verification, or other licensing controls;
  • distribute license keys, license credentials, complete Cookies, signed tokens, sensitive local files, or other secrets;
  • decompile, maliciously capture traffic from, tamper with, sell, or sublicense proprietary parts, except where applicable law cannot exclude this.

If you violate the above rules, Douzy may disable the relevant license keys, stop access to the relevant features, refuse support, or terminate the license in accordance with law.

4. Responsibility for Local Data

Task inputs, local files, SQLite history, follow/favorite/like caches, exports, and logs may contain third-party content or personal information and are saved on your device by default. You are responsible for retention periods, access control, backups, deletion, and subsequent uses, and you must stop processing or delete the data when a rights holder or applicable law requires it.

When using a platform account, you must still comply with the corresponding platform's terms; Douzy will not obtain content authorization on your behalf.

Telegram processing is allowed only for content that the current account already has access to and that the platform marks as savable. Content under content protection, self-destructing content, and paid Stars media that has not been unlocked can never be selected; Stars images/videos that the current account has already unlocked must still pass the content-protection recheck. Douzy does not provide Stars purchase, top-up, balance, or receipt features, and will not unlock content on your behalf.

The X feature must use the Cookies of an account you are entitled to use. You must not use it to circumvent private accounts, access controls, rate limits, or other protective measures; content that X has deleted, restricted, or no longer allows access to must not continue to be processed. This integration is not an official X product, and changes to pages, interfaces, risk controls, or platform rules may cause scanning or downloading to fail.

5. Disclaimer and Limitation of Liability

Douzy is provided on an "as is" and "as available" basis. Third-party plugins, platform pages, interfaces, risk controls, regional restrictions, account status, network conditions, local configuration, user input, and the content itself may each cause identification, scanning, submission, saving, or display to fail. Douzy does not warrant that it is error-free, uninterrupted, permanently compatible, or fit for a particular purpose, nor does it warrant that any content is lawful, accurate, complete, accessible, or savable.

You are responsible for judging the objects you input, the scope of authorization, the saving behavior, and the purpose. To the maximum extent permitted by applicable law, Douzy is not liable for indirect, incidental, special, or punitive damages or third-party claims; where Douzy is required by law to bear liability, its cumulative liability will not exceed the amount you actually paid for license keys in the 12 months before the dispute arose. Liability that cannot be limited by law is not affected by this section.

A license key is a digital product delivered online, and after activation the 7-day no-reason return does not apply (Article 25 of the Law of the People's Republic of China on the Protection of Consumer Rights and Interests); other refund conditions are as stated in the purchase interface, the purchase page, and the support channels, except where applicable law provides otherwise by mandatory provision.

Part 2: Privacy Policy

6. Data Stored Locally

The following data is stored mainly on your device:

  • media, covers, subtitles, metadata, exported files, or other local files that you choose to save;
  • config.yml, SQLite task history, and the follow and "My content" caches;
  • Douyin/TikTok cookies, the YouTube cookie source you select, and the managed copy of YouTube cookies saved at userData/auth/youtube-cookies.txt after manual import;
  • X browser/Profile descriptors, or the managed Netscape Cookie copy saved at userData/auth/x-cookies.txt after manual import; Cookie values are not written to settings or logs;
  • the Telegram TDLib database key, sessions, account/source/media catalogs, sync cursors, thumbnails, selection snapshots, and resumable batches;
  • UI preferences, onboarding, failed items, shortcut state, and recent task state;
  • third-party plugin packages, the SHA-256 manifest, and platform panel state under userData/plugins/yt-dlp/;
  • the X-related local component and build materials inside the installation package, and the separate X panel state and settings under userData/platforms/x/;
  • up to 500 allowlisted product events stored only in localStorage, which are currently not uploaded;
  • consent state and the retry queue.
  • the signed license credential, the verification credential issued by the server, license timing records, and the most recently read hardware identifier, as well as the random anonymous purchase ID used to recover the purchase flow. The hardware identifier is used only to compute the device hashes described below (the fingerprint hash and the hardware hash) when the system temporarily cannot read it; the anonymous purchase ID does not contain an account, device fingerprint, or payment account.
  • the in-app purchase record (userData/purchases.bin), which contains the purchase number, plan, purchase status and time, the license key after payment is credited or the expiration date after renewal, and the purchase credential used to query payment status while waiting for payment to be credited or for manual verification; it is used to continue confirming payment after a restart, recover a purchased license key, and provide the purchase number to the support channels. It is stored encrypted when system encrypted storage is available; when it is not, it is stored in plaintext on this device, like the license file (userData/purchases.json). The purchase credential is removed from the record after payment is credited or the purchase expires; expired records are deleted after 30 days, and this device keeps at most 50 records. The payment code is displayed only in memory and is not written to disk or logs.

These local files, platform Cookies, Telegram authentication secrets and catalogs, X scan results, local history, account caches, other local product events, and local paths are not uploaded to Douzy as diagnostic or product analytics data. The promotional campaign events described separately below are the exception. When you invoke an enabled third-party plugin, TDLib, or X capability on your device through the Douzy UI, the relevant platform processes the necessary requests under its own rules; Douzy's servers do not receive original platform URLs, complete Cookies, Telegram authentication secrets, X scan results, or media files.

Douzy does not receive your:

  • original platform URLs, titles, media files, or local file paths;
  • complete Cookies or account passwords for Douyin, TikTok, YouTube, or X, or your Telegram phone number, verification code, 2FA password, TDLib database key, or sessions;
  • follows, favorites, likes, comments, browsing history, or list of apps on your device;
  • contacts, photo library, precise location, ID number, or other information unrelated to this software.

7. Data That May Be Sent to Douzy Services

To record legal consent, complete license checks, maintain basic service security, and troubleshoot connection failures, the client may send, or the server may generate, the following minimum necessary data:

  • legal consent record: random consent ID, device fingerprint hash, consent type, legal version, accept/decline, time, app version, operating system, and locale;
  • feature confirmation record: feature identifier, accept/decline, and the SHA-256 hash of an optional target;
  • basic operation and security records: app version, operating system, device hash, request time, error code, event type, and failure reason;
  • license key activation: the license key, operating system, app version, and the original device fingerprint text, namely platform, architecture, hardware identifier (IOPlatformUUID on macOS or MachineGuid on Windows), and hostname; after you consent to this version, the hardware hash is also attached. The server stores the fingerprint hash, the device ID derived from it, the hostname, operating system, app version, last activity time, and, at activation and at periodic license checks, the IP address, the country or region determined from it, and the check result;
  • periodic license check: the signed license credential and app version; after you consent to this version, the fingerprint hash is also attached, along with the hardware hash, which is computed only from the platform and hardware identifier and does not include the hostname; if this device holds the one-time verification credential last issued by the server, it is sent back as well. The server stores the hardware hash and the hash of the verification credential, and the verification credential is rotated each time a check passes;
  • obtaining or renewing a license key: in-app purchase: no license credential is sent when plans are read; when a purchase is created, the selected plan identifier and app version are sent; when renewing or upgrading the current license key, this device's signed license credential (which contains authorization information such as the license key ID) is also attached, to verify renewal eligibility and determine which license key to extend; afterwards, the purchase number and purchase credential returned by the server are used to query payment status. In-app purchase does not send the random anonymous purchase ID, device fingerprint, or platform account. Web purchase is made directly in the browser, at which point a random anonymous purchase ID is generated; older versions still send the purchase scenario, the random anonymous purchase ID, the app version, and, for renewals, the existing signed license credential. The server stores the project-scoped hash of the purchase ID, the hash of the purchase credential, the session, the plan, the license key targeted by the renewal, the entitlement verification status, the license key issuance or extension association, and the necessary time records; it does not store the local anonymous purchase ID or the purchase credential in plaintext;
  • the descriptions and attachments you provide when you actively submit a support request.

After you consent to v4.7.0 or a later version, the client also sends the results of impression, click, and open requests for promotional campaigns, with fields limited to an independent random anonymous client ID, a random event ID, the campaign ID, the event time, the app version, the operating system type, and the interface language. The server stores only the project-scoped hash of the client ID, used to reconcile campaign impressions and clicks per anonymous installation; it is not associated with license or purchase identity, and no campaign URL, image, platform account, license, or device fingerprint is sent. Events are deleted after 90 days; this device's pending-send queue holds at most 200 entries, keeps them for 7 days, and retries after failure.

The above data is used only for legal record-keeping, license and purchase delivery, security, abuse prevention, troubleshooting, verification of promotional campaign display, and responding to your requests. Purchase sessions, entitlement verification, license key association, and extension records are stored together with the corresponding license records, to resume delivery, prevent duplicate issuance of license keys or duplicate extensions, and handle after-sales matters or disputes, except where applicable law requires otherwise. Douzy currently does not integrate any product behavior analytics SDK; apart from the promotional campaign events above, it does not upload other local product events, and it has not implemented remote crash reporting.

Device data in activation and periodic license checks is used only for license verification and abuse prevention, for example to detect that the same license has been copied to and used on multiple devices. Abnormal cases are reviewed manually, and your license will not be disabled automatically as a result; if necessary, you may be asked to re-enter the license key on the current device.

The license and consent services are hosted on servers of a third-party cloud provider, and the servers and backups may be located outside the People's Republic of China, so the above data may be processed abroad.

8. Third-Party Recipients

When you actively obtain a third-party plugin, check for updates, open a Chrome Web Store extension page, purchase in the app, open a purchase page, or access a third-party platform through an enabled plugin, TDLib, or X capability, the corresponding plugin source site, extension source site, update distribution site, payment service provider, or third-party platform may process your IP, request time, User-Agent, resource identifiers, payment account, and necessary request information under its own policies. The payment service provider receives only the random customer identifier, payment product identifier, and return address generated by the license service; Douzy does not send it the local anonymous purchase ID in plaintext, the device fingerprint, the complete signed license, or the license key. The payment code displayed in the app is generated by a third-party payment channel, and the payment code image is loaded from that channel's servers; when you choose to open the payment page in a browser, you also access that channel directly. That channel therefore learns necessary network information such as your IP and request time. The payment you make after scanning the code with a mobile payment app is completed within that channel, and Douzy does not access or store your payment account information. Douzy does not control the data-processing rules of these third parties. When you manually import a YouTube or X cookies.txt, Douzy validates it and saves the managed copy only in the Main process on this device and does not upload the file contents to Douzy servers; clearing the corresponding sign-in state deletes the managed copy, but does not delete the original exported file or browser Cookies.

Douzy does not sell personal information and does not use consent, diagnostic, security, or promotional campaign events for personalized advertising profiles.

9. Security

Douzy tries to protect data through local storage, minimized transmission, and system encryption capabilities. The sidecar listens only on 127.0.0.1; except for health checks, the local API uses a random Bearer generated at each startup; logs and public errors should not contain complete Cookies, signed tokens, or sensitive local paths.

No system can guarantee absolute security. When a data incident that may significantly affect your rights occurs, Douzy will handle it as required by applicable law.

10. Your Choices and Rights

You can delete configuration, history, caches, plugin packages, the anonymous purchase ID, in-app purchase records, exported files, and application data on your device, and you can also uninstall Douzy and stop using it. After the anonymous purchase ID is deleted, later purchases will use a new random identifier, and it may not be possible to automatically recover a purchase flow that was not completed earlier. After in-app purchase records are deleted, this device no longer displays purchased license keys and purchase numbers, and purchases whose payment has not yet been credited can no longer be confirmed automatically on this device, so we recommend noting down the purchase number first; deletion does not affect licenses or extensions that have already taken effect on the server. For requests to access, correct, delete, restrict the processing of, or withdraw consent for data where required by law, you can submit them through the customer support channel shown in the app; to prevent others from claiming your data, you may be asked to provide the minimum necessary identity verification materials. Do not submit complete platform Cookies, signed tokens, or other secrets.

Withdrawing legal consent will prevent you from continuing to enter the app; deleting local data may affect settings, history, plugin state, and task recovery.

11. Minors

This software is not directed at children under 14. If a guardian discovers that a child has submitted personal information without consent, the guardian may request deletion through the customer support channel shown in the app.

Part 3: Other Terms

12. Open Source and Rights

Third-party plugin packages, X-related open-source components, and other open-source components are governed by their respective licenses. Except for the parts expressly granted by open-source licenses, the rights in the desktop client, brand, proprietary resources, design, and documentation belong to Douzy or the respective rights holders.

13. Changes, Termination, and Disputes

Substantive changes involving product description, data collection, purposes, sharing, retention periods, liability, or user rights will update the legal version and require you to consent again. If you do not agree to the new version, you may stop using the software and uninstall it.

If this document is inconsistent with the separately published End User License Agreement, Privacy Policy, and Disclaimer, this document prevails.

This document is governed by the laws of the People's Republic of China, without excluding consumer protection rules at your location that cannot be excluded. Disputes shall first be resolved through friendly negotiation; if negotiation fails, except as otherwise provided by mandatory law, they shall be submitted to a people's court with jurisdiction.


This document takes effect from the moment you check "Agree" or continue to use the software.

Supplementary Terms for Purchases on godouzy.com

Published 2026-11-22

This section supplements the price, payment, and refund rules for purchasing license keys on godouzy.com, and applies together with the above.

  • Plans and prices: The purchase page (https://godouzy.com/buy) lists the plans and prices currently available for purchase. USD orders come in two tiers: Yearly pass at 99 USD, with a license key valid for 365 days; Lifetime pass at 199 USD, with a license key that does not expire. The amount actually paid (including applicable taxes and fees) is as shown on the payment page.
  • One-time payment: Each purchase is a one-time payment and does not renew or charge automatically.
  • Collection: USD orders are collected by third-party services such as Waffo. Payment information such as bank cards is handled by that service, and Douzy does not access or store it.
  • Refunds: For USD orders, within 7 days after payment and provided the license key has not yet been activated, you may email [email protected] to request a full refund; no refund is given once the license key has been activated, except where applicable law provides otherwise by mandatory provision. Refunds for CNY orders are handled under "5. Disclaimer and Limitation of Liability" above.