LocalProof Trust Center
Operator, security, privacy, source, payment, and evidence-boundary information for LocalProof.
Operator and service identity
LocalProof is operated by Davisville Labs LLC. The canonical machine-readable service identity is published at /.well-known/localproof.json.
Security
LocalProof uses HTTPS, server-owned source manifests, allowlisted official public hosts, bounded requests, and strict credential separation. Caller authorization headers, cookies, payment credentials, arbitrary headers, and caller request bodies are not forwarded to public source systems. Security contact and disclosure metadata are published in security.txt.
Privacy and regulated-use boundary
Customer-facing property intelligence is privacy-minimized and excludes restricted personal fields where the released source contract requires it. Commerce analytics is designed not to contain raw addresses, prompts, request bodies, buyer IP addresses, credentials, payment proofs, or paid result bodies. LocalProof is not a consumer-reporting or background-screening service and must not be used for regulated individual eligibility decisions.
Source and evidence boundary
LocalProof prioritizes official public sources, preserves provenance and uncertainty, and treats missing or unavailable records as bounded evidence rather than proof of absence. Current source reachability is not a claim of completeness. Zoning context is research evidence, not a legal opinion or proposed-use determination.
Payments and recovery
Paid work must pass eligibility checks before a machine-payment challenge is issued. Settlement and delivery are separate states. An identical authorized retry can recover a settled result during the configured recovery window without another charge when the rail supports it.