DupeRadar — Duplicate Download Detector Privacy
Download metadata and selected file hashes remain local. Only license fields are sent to CodingFrontend when the user activates or validates Pro.
Only the extension identifier, license key, pseudonymous installation name, server-issued instance ID, and validation timestamps are used for centralized licensing. License keys are sent only in POST JSON bodies.
CodingFrontend owns checkout and payment-provider integration. DupeRadar never handles card data or calls checkout directly.
No analytics, advertising identifiers, tracking pixels, hosted AI, download URLs, full local paths, or downloaded file contents are collected.
Preferences
Capped duplicate-alert metadata using basenames rather than full paths
User-selected SHA-256 hashes
License key, activation instance ID, and validation timestamps
Canonical extension identifier
License key
Activation instance ID where applicable
Pseudonymous installation label during activation
DupeRadar never automatically or manually deletes downloaded files. Clearing DupeRadar history affects only extension-local alert and hash records.
Licensing
For Pro activation, the license key and a user-readable browser instance name are sent over HTTPS to CodingFrontend and Dodo Payments. The CodingFrontend database stores a keyed hash of the license key, the Dodo instance ID, product association, and validation timestamps—not the raw key.
Payments
Checkout is hosted by Dodo Payments. CodingFrontend never embeds payment credentials in the extension and does not treat the checkout return page as proof of purchase.
Contact
Questions can be sent through the CodingFrontend contact page.