Verify Windows Download
Installer Signature
Every installer is signed with Authenticode. The current publisher thumbprint is A07D419B4DC93D7E3F36BC62AF409216A92897A5. The certificate is self signed, so Windows may show a SmartScreen warning even when the file is genuine.
The signature is tamper evidence. It proves the bytes you received are the bytes we built. It does not by itself prove a trusted publisher to Windows.
Published Hash
The signed update manifest carries the SHA-256 of the signed installer. Compare it with Get-FileHash -Algorithm SHA256 -Path "Flookup Data Wrangler Setup.exe" in PowerShell.
If the hash differs, delete the file. Do not run an installer whose hash does not match the published value.
Signed Updates
Update manifests are signed with Ed25519. The app verifies the signature before it offers a release. It also checks the download host against an allowlist that contains our own domains.
Electron fuses prevent the packaged app from being relaunched as a plain Node process or opened with an inspector switch. Embedded asar integrity validation detects a repacked application folder.
Local Data
Cleaning, matching, profiling and deduplication run on your machine. The workbook is stored in your user data folder. Results stay there until you export them.
The engine and scoring kernel are hashed against a local integrity manifest at startup. The Check integrity button in Account shows which file changed if a check fails.
Network Calls
The app contacts the activation service for leases and the update host for signed manifests. Connector actions contact the remote service you choose. Nothing else uploads spreadsheet content.
Licence requests carry a device fingerprint, the app version, the licence id and the signed lease used to renew it. They do not carry file paths, workbook values or stack traces. Errors are sanitised before they reach the interface.