VeilSend

A SMALL FIRST STEP

Try a fake file.
Get a feel for the flow.

You do not need a real customer document to try VeilSend. Start with the built-in text sample, then decide whether this workflow helps you.

Experimental beta, not a stable release. Version 0.2.0-beta.1 is unsigned. Core workflows passed limited checks on one development computer; clean-Windows compatibility, portable image/PDF workflows, uninstall preservation and disconnected operation remain unverified. Keep originals and inspect outputs.

01 / DOWNLOAD & INSTALL

Get the official Windows build.

Target: Windows 10/11 x64. This is not a Mac, Linux or native Windows ARM build. No VeilSend account or subscription is needed.

  1. Open the official v0.2.0-beta.1 release. Read its notes, then expand Assets. Download VeilSend_0.2.0-beta.1_x64-setup-UNSIGNED.exe and SHA256SUMS.txt from that same release. The “Source code” ZIP is not the app.
  2. Check the downloaded file before running it. Compare its SHA-256 with the matching filename in the manifest; use the repository's provenance verifier to also check which GitHub workflow built it. Verification instructions.
  3. Run the installer only if you trust and have verified the download. It installs for your current Windows user. Note the destination shown by the installer. It may need an internet connection to obtain Microsoft's WebView2 runtime if that is missing.
  4. Open VeilSend from the Windows Start menu. If it does not appear, use the install destination you noted. Do not move or delete program files to troubleshoot.
How do I compare the SHA-256?

In File Explorer, open the folder containing the download, right-click an empty area and choose Open in Terminal. In PowerShell, run these read-only commands and compare the hash for the exact installer filename. A matching hash alone does not establish publisher identity. 

Get-FileHash -Algorithm SHA256 .\VeilSend_0.2.0-beta.1_x64-setup-UNSIGNED.exe
Get-Content .\SHA256SUMS.txt
Windows shows an unknown publisher or SmartScreen warning.

This build is unsigned, so a warning is possible. A warning is not proof that the file is authentic or malicious. Do not disable Windows security or blindly bypass a warning. If you cannot establish trust in the download, stop and wait for a future signed release; no delivery date is promised.

Can I use the portable ZIP?

The release also includes a portable ZIP. Extract it fully before opening VeilSend.exe. It still needs a compatible WebView2 runtime. A later portable text trial passed on a Windows 11 development computer, using the built-in fake sample. Portable image/PDF workflows and clean-PC compatibility remain unverified. Save outputs outside either app directory.

02 / FIVE-MINUTE TEXT TRIAL

One sample. A separate copy.

  1. Open text mode and choose Try safe sample. It contains deliberately fake support-log data, not real credentials or customer information.
  2. Choose Scan locally. Review the proposed replacements. The sample also adds a custom sensitive term for this scan. Do not expect the finding count to match a different sample or configuration.
  3. Keep the proposed cleanup selected for this first trial, then choose Clean & verify. Read the cleaned text. Keeping a finding intentionally should be reported as an exception, not silently treated as clean.
  4. Choose Save clean copy. Save to a folder you control outside the app's installation directory. Open the saved text and inspect it. Read the saved-output receipt, not only the earlier in-memory result.
  5. If you see Needs review, an unavailable detector or an error, stop and inspect the issue. “Verified” only describes supported checks; it is never permission to skip your own review.

To try images or PDFs next, use the repository's synthetic fixtures. Use visual-sensitive-sample.png for visual review and pdf-sensitive-sample.pdf for page review. Save to separate files and keep the originals.

PDF trade-off: exported PDFs contain page images, not searchable or selectable text. Forms, signatures, links, bookmarks, attachments and accessibility tags are not preserved. Office files and encrypted PDFs are not supported.

03 / FIND OR REMOVE THE APP

No need to hunt through folders.

  1. Save anything you need, then close VeilSend. Keep source files and exported copies in your own document folder, not inside the program folder. Back up important outputs before removing this experimental build.
  2. Windows 11: open Settings → Apps → Installed apps. Windows 10: open Settings → Apps → Apps & features. Search for VeilSend and choose Uninstall.
  3. If it is absent there, press Win + R, enter appwiz.cpl, and look for VeilSend in the classic program list.
  4. If neither list shows it, find the Start menu shortcut, right-click → Open file location, then inspect the shortcut's Properties → Target to locate the actual installation. Look for uninstall.exe in that same program folder. Do not guess a folder or delete it manually.

The location can differ if you changed it or the installer was launched through a packaged app. A path observed on the development computer is not a universal install path. If you used only the portable ZIP, there is no installed-app uninstaller; keep your outputs separate and close the portable app before removing its extracted folder.

Uninstall preservation is still unverified for this release. A successful uninstall should remove the program and shortcuts while leaving your separately saved files unchanged; please report a failure without attaching those files.

If something gets in the way.

Common first-run problems
What happened What to do
The app will not start Check you downloaded the Windows x64 app, not source code. For portable, extract first. Report whether WebView2 is installed and any short error code. Do not disable antivirus or run as administrator as a workaround.
OCR is unavailable Check the app's local trust center. Windows OCR depends on an installed OCR language supported by the device. An unavailable detector is a reason for review, not a clean result.
PDF rejected or export failed Use an unencrypted PDF, at most 50 pages and 50 MiB. Rendering limits also apply. Try the synthetic PDF first; never post a real failing document.
Nothing was detected Only supported patterns and detectors are checked. Try the built-in sample, confirm the detector states, and manually inspect the content.

04 / TELL US ABOUT THE WORKFLOW

Useful feedback, without the private data.

Tell us what you tried, how often that task comes up, what you normally use, and where VeilSend helped or got in the way. There is no purchase commitment and no need to upload a file.

Share trial feedback ↗Report a bug ↗

GitHub issues are public and require an account. Include only fake examples, the app version, a short error code and detector states. Never include customer names, original files, full local paths, real credentials, copied logs or screenshots containing private data.

For vulnerabilities, use private security reporting instead. Even private reports should use synthetic reproductions, not real secrets.