Private-data presales proof

Prove fit on real data.
Never ask for the data.

Turn one narrow fit question into an inert evaluator. Your prospect runs it locally, chooses the aggregate evidence to return, and keeps every row on their device.

  • No prospect upload
  • No vendor-supplied code
  • No hidden receipt fields

The TrialVeil boundary

One question crosses in. Only chosen proof crosses back.

  1. 01Vendor rulesInert, inspectable evaluator pack
  2. 02Prospect-local runFiles and exact results stay here
  3. 03Chosen aggregatesBound to the exact pack version

A matching hash confirms content consistency only. It does not authenticate a person, file, device, or execution.

Built for the stalled presales moment

Replace “send us a sample” with an inspectable local test.

For technical B2B vendors whose qualified prospect cannot upload production-like data or grant environment access before a POC.

AUTHOR

Freeze one narrow fit question

Define logical fields, deterministic thresholds, and the maximum receipt menu. Rehearse the complete mechanism on authorized or synthetic data.

RUN

Let the prospect keep every row

A private, purchase-backed Runner link shows every exact operand before enabling files, then evaluates CSV or flat NDJSON in a bounded browser Worker with connections denied.

DECIDE

Return only chosen coarse evidence

The prospect previews zero to eight allowed fields. The vendor verifies exact pack and engine consistency without receiving raw rows, mappings, or exact rates.

A deliberately narrow trust claim

Privacy boundary, not remote attestation.

STAYS WITH THE PROSPECT
  • Source files and filenames
  • Local source keys and mappings
  • Exact counts, rates, and row-level values
  • Unselected result fields
MAY CROSS BACK
  • Buyer-selected PASS or FAIL statuses
  • Buyer-selected 5% bands for cohorts of 100+
  • Buyer-selected coarse count bands
  • Pack, engine, and receipt consistency hashes
NEVER CLAIMED
  • Vendor or prospect identity
  • Which file was evaluated
  • Proof that execution happened
  • Certification that source data was truthful

Pay only after the full rehearsal

A complete Free decision, then the right one-time export.

No subscription and no per-prospect fee. Starter unlocks a reusable single-input pack; Pro adds relationship-aware checks across up to three inputs. Prospects need no account.

FREE

$0

Prove the mechanism first
  • Complete synthetic worked example
  • Local draft for up to 3 inputs and 30 rules
  • Exact local rehearsal
  • Draft download and reopen
Build and rehearse

PRO · ONE TIME

$20

Relationship-aware fit proof
  • Up to 3 inputs and 30 rules
  • Up to 2 cross-input join checks
  • Unlimited prospect runs and revisions
  • Server-verified entitlement recovery
Rehearse Pro first

A browser-held recovery capability is checked against TrialVeil's server before each export. It cannot restore a local draft you did not save.

Before you send a pack

What security teams will ask.

Does TrialVeil upload or store prospect data?

The versioned Runner is a single HTML response with no analytics or external assets. It checks that its connection policy is active before file controls unlock. Files, mappings, and exact results remain in that page and are cleared when the private session ends.

Can a vendor put code or a tracking URL in a pack?

No. A pack is strict JSON with a closed set of fields and deterministic opcodes. Unknown keys, URLs, executable instructions, unsupported references, duplicate keys, and a changed content hash are rejected before prospect data can be chosen.

Does a matching receipt prove the prospect ran the test?

No. It proves only that the receipt is internally consistent and bound to the exact loaded pack and Runner engine. TrialVeil does not authenticate identity, input, execution, or truth.

What if the evaluator needs proprietary code, an API, or a database?

TrialVeil is not the right boundary. It deliberately supports structural, coverage, range, timestamp, uniqueness, and bounded relationship-fit questions only.