BEFORE IT LEAVES YOUR COMPUTER

Share the context.
Keep the private bits.

A second look at the logs, screenshots and PDFs you send. Find likely sensitive details, make a separate redacted copy, and check the saved result.

Try the Windows beta See the workflow

Free & open source · Windows x64
v0.2.0-beta.1 · Unsigned experimental build

SUPPORT HANDOFF / EXAMPLESynthetic data

support-handoff.log

              status=connection_timeout
            
              customer=[EMAIL]
            
              api_key=[SECRET]
            
              host=[PRIVATE_IP]
            
              retry_in=30s

Useful context stays.Selected details become replacements.

Workflow illustration, not a live scan or an app screenshot.

01 / Process on your device02 / Keep the original03 / Check the saved copy

ONE LAST CHECK

For the everyday
“can you send that over?”

Built for support handoffs, bug reports and client updates. One file at a time, with you in control.

01 / TEXT & LOGS

The bug report.
Not the API key.

Review likely credentials, email addresses, private IPs and local paths in text, logs, JSON and .env files.

02 / SCREENSHOTS

The screen.
Not every detail.

Review detected text, faces, QR codes and barcodes. Cover selected regions and remove supported image metadata.

03 / PDF DOCUMENTS

The document.
A separate copy.

Review pages and add manual covers. Export a rebuilt, image-only PDF without the original text layer or active objects.

PDF output loses text search, selection, forms and signatures.

INSPECT → CLEAN → CHECK

A pause.
Not a whole process.

Review what gets removed. Then inspect the result before you share it.

Explore a fixed synthetic example below. This website does not scan, accept or upload your files.

STEP 1 / INSPECT

Find the details you did not mean to send.

customer=alex@example.com
host=192.168.12.44
status=connection_timeout

In the desktop app, review suggested replacements before cleaning. This example contains an email address and a private IP.

Illustration only. “Verified” means supported checks completed, not that every sensitive detail was found.

The app lets you review matches, create a separate copy, and check its saved output. The interactive illustration needs JavaScript; downloads and guides do not.

FROM THE WINDOWS APP

The actual app.
A deliberately fake log.

Captured from the published v0.2.0-beta.1 portable app on a Windows 11 development computer. These are screenshots, not a video or a browser simulation.

01 / Load the built-in synthetic sample

VeilSend desktop app showing its built-in fake support log and Scan locally button. — All names, addresses, credentials and paths in this sample are synthetic. Open the image to inspect it at full size.

02 / Review the proposed replacements

VeilSend desktop review showing six findings selected for cleanup and zero intentional exceptions. — This sample produced six findings, including its custom sensitive term. Counts depend on input and enabled rules.

03 / Inspect the cleaned text

VeilSend desktop cleaned-text preview with replacement labels, zero remaining rule matches and a Save clean copy button. — This frame is the cleaned preview, before saving. In the subsequent test, a separate file was saved and reread; seven predefined source markers were absent. That is a bounded sample check, not a guarantee.

No personal files were used. This additional portable text test does not establish clean-PC compatibility, image/PDF portable behavior, offline operation or uninstall preservation.

CLEAR BOUNDARIES

Local processing.
Human judgment.

No account in the desktop app. No analytics or crash uploads. No automatic sharing.

What stays on my computer?

The desktop app processes source content locally. It does not upload files or use cloud inference. The installer may need internet access to obtain Microsoft WebView2. Disconnected operation has not yet been verified for this beta.

What does “Verified” actually mean?

Supported checks completed for that output with no remaining supported findings or intentional exceptions. Detectors can miss information. Keep originals and manually inspect every output; this is not a safety guarantee or a compliance certification.

What can this beta handle?

UTF-8 text up to 10 MiB; JPEG/PNG up to 25 MiB; unencrypted PDFs up to 50 MiB and 50 pages, subject to render limits. One file at a time. No Office files, batch processing or Mac/Linux desktop builds.

Is it ready for critical work?

No. This is an unsigned experimental beta, not a stable release. Core workflows were smoke-tested on one Windows 11 development computer with synthetic data. A portable text trial also passed on that development computer. Clean-system compatibility, portable image/PDF workflows and uninstall preservation remain unverified. Start with fake data.

Read the recorded validation scope ↗

What does it cost?

This beta is free and open source under the MIT license. There is no paid plan or checkout today. We are learning which workflows need improvement before deciding whether to offer optional paid features.

HELP SHAPE THE NEXT VERSION

Try one handoff.
Tell us what got in the way.

Did it save a step? Did you have to switch to another tool? Practical feedback matters more than a star.

Start the five-minute trial Share trial feedback ↗

GitHub account required. Feedback issues are public. Use descriptions and fake examples only—never customer files, secrets, private paths or screenshots of real data.

Report a security issue privately ↗

Share the context.Keep the private bits.

For the everyday“can you send that over?”

The bug report.Not the API key.

The screen.Not every detail.

The document.A separate copy.

A pause.Not a whole process.