Skip to content

Installation

Jump to bottom
Max Ivankovsky edited this page Aug 12, 2026 · 1 revision

Installation

CloakDLP has two parts, and both matter: the desktop installer (which covers clipboard, print, and local HTTP network traffic) and a browser extension (which covers typed card entry on real checkout pages, almost all of which are HTTPS today). Installing only one gives you partial coverage.

Desktop install (MSI)

  1. Download CloakDLP-Setup.msi from the latest release.
  2. Run it. It needs admin elevation, like any installer that registers a Windows Service.
  3. That's the whole setup. On finish:
    • Two Windows Services start automatically: CloakDLP Console (the web console, http://127.0.0.1:8123) and CloakDLP Agent (the endpoint monitor).
    • A per-user tray notifier launches immediately (not just at next logon) and shows a Windows notification whenever a match is caught.
    • The console opens in your default browser on its own, already signed in. There's no account to create and no password: the console only trusts requests from the local machine (loopback), so it logs you in automatically.
    • The agent self-registers with the console and picks up an auto-provisioned "Credit Card Entry" policy. Nothing to copy-paste, no API key to configure by hand.

Uninstalling is just as simple: Settings → Apps or appwiz.cpl, uninstall "CloakDLP." Both services, the startup shortcut, and all installed files are removed, and the running tray notifier is stopped first so nothing is left orphaned.

See installer/README.md for exactly what lands where on disk.

Browser extension

The extension isn't force-installed by the MSI, and isn't yet published to the Chrome Web Store or Edge Add-ons, so today it needs to be loaded manually:

  1. Open the CloakDLP console (http://127.0.0.1:8123). The Overview page has an "Install extension" prompt that detects your actual browser (Chrome, Edge, and Brave are all supported) and walks through the exact steps for it.
  2. In short: download the extension zip from the console, extract it to a folder, open your browser's extensions page, turn on Developer mode, and "Load unpacked" pointing at that extracted folder.
  3. The extension self-registers with the console the same way the desktop agent does, no configuration needed.

Once it's published to a store, this collapses to a single "Add to Chrome"-style click; see browser-extension/README.md for the publishing plan.

What each piece actually catches

Channel Covered by Notes
Typed into a checkout form Browser extension The primary path for real-world card entry; works over HTTPS since it reads the field directly, before the browser encrypts anything
Clipboard Desktop tray app Runs in your logged-in session specifically, not the background service; see Troubleshooting for why
Printing Desktop agent service Scans the print job's document title only, not the actual page content
Plain HTTP network traffic Desktop agent service A local forward proxy; HTTPS/CONNECT requests are rejected outright rather than silently passed through unscanned

Clone this wiki locally