Clear about what a record proves.
Verification should make evidence easier to inspect—not overstate what the evidence says.
Private by default
Supporting documents are stored in a private Supabase Storage bucket. Access is scoped to the account that uploaded the file. Public record pages show evidence metadata and SHA-256 fingerprints, not the contents of the uploaded file.
File integrity fingerprints
When an evidence file is uploaded, PROOFLOT calculates its SHA-256 fingerprint. Comparing a candidate file against that fingerprint can indicate whether its bytes match the original upload. The fingerprint does not establish who created a file, when its underlying claims became true, or whether those claims are accurate.
Owner-provided information
Asset descriptions and supporting evidence are supplied by the account holder. A listing does not constitute an inspection, title search, lien search, appraisal, ownership determination, or certification by PROOFLOT.
Access controls
Production deployments should configure Supabase Row Level Security and private storage policies using the included schema. Never expose service-role credentials in a browser bundle. Use HTTPS and configure Supabase authentication redirect URLs for your deployment domain.
On-chain anchoring
The included registry contract supports anchoring a record identifier and evidence digest. Contract deployment and transaction execution require an operator-configured network and wallet. Publishing a digest on-chain does not independently validate the associated asset or document.