Dingdok is built to keep your activity local. There is no analytics dashboard, no media stored on our servers, and no browsing history collected. This article lists exactly what leaves your machine and when.
What is never uploaded
- Downloaded media. Files are written straight to the folder you choose and never transmitted to us.
- Your queue and library. The download list, history, and file names stay on your device.
- Browsing history. We do not track which links you parse or when.
- Page contents. Dingdok reads pages to find formats; it does not upload their content anywhere.
What is sent, and only when needed
- Activation. The license key and a device fingerprint are sent to the license server once, when you activate or move a seat.
- Update checks. The app requests a small version manifest to see whether a newer build exists. This contains the app version and platform.
- Optional diagnostics. If you explicitly submit a bug report, the attached log includes error text and your app version — never media or URLs unless you add them.
Where data is stored locally
- Queue database and settings: the app support folder for your operating system.
- Logs: the same folder, rotated and capped in size.
- Cache: temporary fragments, cleared automatically after a completed download.
You can delete all of it by removing the support folder; see your platform’s install article for the exact path.
Network destinations
Dingdok connects to:
- The source site you are downloading from, exactly as a browser would.
- The license server, for activation and reactivation.
- The update endpoint, for version checks.
There are no other outbound connections, and no third-party analytics SDKs are bundled.
Your controls
- Disable update checks under Settings → General.
- Run fully offline after activation.
- Clear logs and cache at any time.
Related
Read the full Privacy Policy in the Legal Center for retention periods and contact details.