Windows SDK integration

Bundle the Windows executable with your installer payload and run it as a consent-gated child process or managed service.

1. Install

The standalone Windows executable is being rebuilt. The previously published build targets a retired gateway protocol and will not connect. Electron, Node and any JavaScript-based Windows app should integrate the npm package, which is current and supported. For a native (C#/C++) Windows integration, contact [email protected] and we will send the current build.

2. Initialize

// C# — spawn after the user has accepted the consent screen.
var psi = new ProcessStartInfo {
  FileName = "getpassive-sdk.exe",
  Arguments = $"--device-uuid {stableDeviceUuid}",  // key passed via environment, not argv
  UseShellExecute = false,
  CreateNoWindow = true,
  RedirectStandardOutput = true,
  RedirectStandardError = true,
};
psi.Environment["GP_DEV_API_KEY"] = devApiKey;  // argv is readable by any local process
var proc = Process.Start(psi);

// On opt-out / app close:
proc.Kill();

3. Binary downloads

4. Lifecycle notes

Install the executable beside your app or in an application data directory managed by your installer.
Use CreateNoWindow and redirected output for background operation.
If you register a Windows Service, keep the same consent and opt-out controls in your app UI.
Terminate the process during uninstall, opt-out, or application shutdown.

Start the SDK only after your app has shown the required disclosure and the user has accepted it. Use the shared consent guide for the wording and placement expectations.

6. Verify

Use the in-dashboard tester at app.getpassive.io for your app key, or follow the shared quickstart verification steps while the key is in test mode.

Last updated June 14, 2026

Windows SDK integration

1. Install

2. Initialize

3. Binary downloads

4. Lifecycle notes

5. Consent flow

6. Verify