Proof workloads stay on customer compute.
TinyZKP.com is designed as a static product site. Guard proving, resume, and verification are local processes and do not send workloads, witnesses, checkpoints, scratch files, or proofs to TinyZKP.
Website delivery
Cloudflare Pages delivers this static site and may process ordinary request metadata such as IP address, user agent, requested URL, timestamp, and security signals under its own infrastructure terms. The site contains no custom contact form, event collector, customer account, proof API, or TinyZKP analytics database.
Merchant checkout
When checkout is eventually enabled, the merchant of record will process purchase identity, billing, tax, payment, receipt, renewal, cancellation, and refund data under the merchant's disclosed privacy terms. TinyZKP must not receive full payment-card data.
License activation
Each exact Guard release will contact the merchant once during activation and send the minimum metadata necessary to validate the subscription and release entitlement. Successful activation is stored locally with owner-only permissions. Proving, resume, verification, and status checks for that activated release are designed to work offline.
Support
Public GitHub issues and private vulnerability reports are processed through GitHub. Do not submit personal data beyond what is necessary, and never submit proof inputs, witnesses, checkpoints, scratch data, proofs, tokens, environment variables, or license keys.
Customer responsibilities
Customers control their workload, scratch, output, diagnostics, host logs, retention, backups, access controls, and deletion. Scratch may contain sensitive intermediate data and should be protected accordingly.
Final notice gate
The production privacy notice must identify the legal controller, contact method, purposes and bases, data categories, processors, transfers, retention, deletion procedures, and applicable rights. Checkout remains disabled until those factual details are supplied and approved.