Asynchronous support

Start with the doctor and the documentation.

TinyZKP is intentionally operated without onboarding calls, an SLA, or a hosted support portal. Use the public issue tracker for ordinary defects and private GitHub reporting for vulnerabilities.

Read documentation Open an issue

Do not send proof data. Never include a witness, input trace, proof bundle, checkpoint, scratch file, environment variable, token, private path, license key, or confidential system detail in an issue or report.

Choose the right path

Compatibility question

Run the free doctor, compare the result with the v1 profile, and use the public issue tracker only with a scrubbed report.

Product defect

Search existing GitHub issues, then open a minimal report with release identity, exit class, and sanitized reproduction.

Security finding

Use private vulnerability reporting. Do not publish exploit detail before coordination.

Support boundary

Support is asynchronous and does not include a response-time guarantee, architecture review, custom AIR work, onboarding, private debugging sessions, security questionnaires, SSO, procurement assistance, hosted operations, or access to customer proof data.

Before opening an issue

Confirm the workload is within the exact released compatibility manifest.
Run tinyzkp doctor with the same job manifest.
Confirm the artifact signature and exact release identity.
Reproduce with networking disabled after activation.
Inspect the doctor JSON manually; it is the only support-safe diagnostic artifact.
Include only the minimum safe output needed to reproduce the defect.

Billing help

Once checkout is live, receipts, invoices, payment updates, renewal, dunning, cancellation, and eligible refunds are handled through the hosted merchant portal linked from the purchase receipt. TinyZKP does not operate a billing account system.