verifold

PRIVACY & BOUNDARIES

Public information.
Private evidence.

This website explains Verifold. It does not connect to your data pipeline.

What this site does

It serves static pages, local fonts and a small navigation script. It includes curated descriptions of synthetic local experiments. There are no report uploads, account forms, intake forms, analytics scripts, external font requests or application APIs in this website.

The site saves only your selected light or dark appearance in local storage. It does not use cookies or session storage, and does not store reports or personal information. When hosted, the hosting provider necessarily receives ordinary web requests and may retain access or security logs under its own policies. These site-level statements are not a promise of anonymous browsing or a description of every hosting setting.

Your reports stay in the local product

The separate developer-alpha explorer displays imported reports in browser memory. That explorer, its optional local fixture runner and its server endpoints are not part of this public website.

Reports can contain sensitive identifiers, versions, digests and query configuration. Do not publish private reports, pipeline payloads or credentials as website assets.

Read access is still sensitive access

Verifold’s verifier uses read access to inspect supported sources and indexes. Adoption requires scoped permissions, an explicit source inventory and metadata contracts. The current prototype has not established production readiness for arbitrary shared collections, multiple replicas or missing deletion history.

Evidence has limits

Verifold does not synchronize systems, automatically repair data, certify complete physical erasure or prove AI answer correctness. Online observations retain global UNKNOWN. The local experiments are not security certifications or production service guarantees.

Read the verification boundaries