Douzy Privacy Policy
Version v4.9.0 | Effective 2026-11-17
Reading note
Douzy is a local desktop UI and local task-management application, and the Renderer itself contains no platform download logic. Douyin, TikTok, and YouTube capabilities are provided by third-party plugins; Telegram runs through an on-device TDLib capability; X runs through a local open-source component shipped with the installation package. Third-party components, account sessions, task inputs, local files, platform Cookies, task history, account content caches, and UI state are stored mainly on your device.
1. Data Stored on Your Device
| Data | Typical location or form | Purpose |
|---|---|---|
| Local files and exports | The local directory you choose | Stores the media, images, audio, subtitles, covers, metadata, or exported files that you produce or choose to save. |
| Configuration and history | config.yml, SQLite database | Stores UI settings, task history, and the follow and "My content" caches. |
| Platform authentication | Douyin/TikTok cookie files; YouTube cookie source setting and the managed copy at userData/; X browser/Profile descriptor or the managed copy at userData/ | Lets you use the corresponding platform account state in your own local environment. X Cookie values are not written to settings or logs. |
| Telegram local account data | The TDLib database key in system secure storage; TDLib sessions; accounts, sources, media catalogs, sync cursors, selection snapshots, and resumable batches in SQLite; local thumbnails | Signs in to the current account, browses the sources it has permission to access, resumes tasks, and cleans up the local cache. The phone number, verification code, and 2FA password are used only for the current authentication step and are discarded after use. |
| Local product state | UI preferences, onboarding, failed items, shortcuts, and similar data in local files or browser storage | Restores local usage state. |
| Third-party plugin packages and panel state | The pinned-version official ZIP and SHA-256 manifest in userData/; the access state in userData/ | Stores the third-party plugins you download or import, records the pinned source, version, and integrity check results, and records your choice to open or close the panel for each platform. The download feature is provided by the third-party plugins you enable. |
| X local component and local state | The local open-source component inside the installation package, together with its license, corresponding source code, and build materials; the X panel and settings in userData/ | Provides local X tasks, records panel confirmation, and restores settings. This component does not need to be downloaded or imported by the user. |
| Local product events | Up to 500 allowlisted events in localStorage | Reviews flows such as parsing, scanning, submission, first file, and zero output on this device; currently not uploaded. |
| Consent state and retry queue | System encrypted storage, or a local file with restricted permissions | Determines whether consent is needed again, and retries after the network recovers. |
| License and purchase state | The signed license credential, the verification credential issued by the server, license timing records, and the most recently read hardware identifier; the random anonymous purchase ID in userData/; the in-app purchase record userData/ | Maintains license state, and recovers the same purchase flow when you actively open the purchase or renewal page. 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/) 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/). 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. |
Local files, platform Cookies, Telegram sessions/catalogs/thumbnails, X scan results, task history, follow/favorite/like caches, other local product events, and local file 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 component 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.
2. 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:
| Scenario | Data scope | Purpose |
|---|---|---|
| Legal consent | Random consent ID, device fingerprint hash, consent type, EULA/privacy/disclaimer versions, accept or decline, client time, app version, operating system version, locale | Proves the legal version the user saw and the choice made. |
| Feature confirmation | Feature identifier, accept or decline, SHA-256 hash of an optional target | Records the user's choice on a specific platform panel or sensitive operation. |
| Basic operation and security records | App version, operating system, device hash, request time, error code, event type, and failure reason | Abuse prevention, security auditing, and troubleshooting. |
| License key activation | The license key, operating system, app version, and the original device fingerprint text: platform, architecture, hardware identifier (IOPlatformUUID on macOS or MachineGuid on Windows), and hostname; after you consent to this version, the hardware hash described in the next row is also attached | Binds the license to the current device. 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, two device hashes are also attached: the fingerprint hash, and 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 | Keeps the license valid, and detects whether the same license has been copied to and used on multiple devices. The server stores the hardware hash and the hash of the verification credential; 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: a fixed web page is opened directly, and no license credential is sent on opening; after you choose to purchase, the server generates a random anonymous purchase ID for this browser purchase. Older versions still send the first-purchase or renewal scenario, the random anonymous purchase ID, and the app version, and attach the existing signed license credential only for renewals | Associates this purchase flow, verifies renewal eligibility, and completes delivery. 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. |
| Promotional campaign events | After you consent to v4.7.0 or a later version, an independent random anonymous client ID, a random event ID, the campaign ID, the result of impression/click/open requests, the event time, the app version, the operating system type, and the interface language are sent | Confirms whether a campaign image entered the visible area and whether a link was clicked, and queries campaign performance per anonymous installation; no campaign URL, image, platform account, license, or device fingerprint is sent. The server stores only the project-scoped hash of the client ID and does not associate it with license or purchase identity; 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. |
| Support requests | The descriptions, attachments, and necessary context you actively submit | Responds to your request. |
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.
3. Data Not Currently Uploaded
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.
4. Third-Party Recipients
When you actively obtain a third-party plugin, check for updates, open a Chrome Web Store extension page, or access a third-party platform through an enabled local component, the corresponding site or platform may process your IP, request time, User-Agent, account identifiers, resource identifiers, and necessary request information under its own policies. Telegram sign-in and media requests are sent directly to Telegram; the X local component requests X directly using the Cookie source you select. Douzy does not control the data-processing rules of these third parties.
When Windows Chrome's App-Bound Encryption causes automatic reading to fail, Douzy may guide you to use the third-party extension Get cookies.txt LOCALLY, independently maintained by kairi003 on the Chrome Web Store, to export a Netscape-format file. This extension is not developed, distributed, or controlled by Douzy. After you select the file, Douzy validates it only in the Main process and saves the managed copy as userData/ on this device, and does not upload the file contents to Douzy servers. Clearing the YouTube sign-in state deletes that managed copy, but does not delete your original exported file or any external Cookie file you configured yourself in earlier versions.
Douzy does not sell personal information and does not use consent, diagnostic, security, or promotional campaign events for personalized advertising profiles.
When you purchase in the app or actively open the purchase page in your system browser, payment is completed on a third-party payment channel. The payment code displayed in the app is generated by the 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. The independent payment service provider receives the random customer identifier, payment product identifier, and return address generated by the license service, and processes the payment account, the order, and necessary network information under its own policies. Douzy does not send the payment service provider the local anonymous purchase ID in plaintext, the device fingerprint, the complete signed license, or the license key; the license service only queries entitlement status and completes license key delivery or extension.
5. 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 must not contain complete Cookies, signed tokens, or sensitive local paths;
- production secrets are not packaged into the client.
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.
6. Your Choices and Rights
You can delete configuration, history, caches, plugin packages, Telegram account data, the managed X Cookie copy, 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. Clearing the X sign-in source deletes only the managed copy and does not delete browser Cookies or the user's original exported file. Signing out of Telegram deletes the local TDLib session, the account catalog cache, and thumbnails on this device; when a resumable batch exists, you must explicitly abandon it, and downloaded files and redacted task records are kept. 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.
7. 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.
8. Policy Changes
Substantive changes involving collected items, purposes, sharing, retention periods, or user rights will update the legal version and require you to consent again in the app. Purely typographical corrections, typo fixes, or corrections that do not change rights or obligations are recorded in legal/. If this policy is inconsistent with the User Agreement and Privacy Policy displayed in the app, the latter prevails.
This policy takes effect from the moment you check "Agree" or continue to use the software.
Supplementary Notice for USD Orders on godouzy.com
Published 2026-11-22
This section supplements how data is processed when you purchase license keys in USD on godouzy.com, and applies together with the above.
- USD orders are collected by third-party services such as Waffo. The email address, country or region, and payment information such as bank cards that you enter on its payment page are collected and processed by that service under its privacy policy; bank card information does not pass through and is not stored on Douzy's servers.
- After payment is completed, Douzy's license service receives from that service the order number, payment status, currency, amount, and the email address you entered, and stores the order record and email address together with the issued license key, for delivering the license key, after-sales support, and handling refunds and chargebacks.
- To access, correct, or delete the above information, email [email protected].