Asynchronous support

Start with the doctor and the documentation.

TinyZKP is intentionally operated without onboarding calls, an SLA, or a hosted support portal. Ordinary customer support uses a verified private mailbox; private GitHub reporting remains the path for vulnerabilities.

Run the free doctor Open-source issues

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.

Private ordinary support is not yet published. Checkout remains fail-closed until a managed private mailbox, end-to-end delivery, owner access, and retention configuration are verified in signed owner evidence. Public issues are only for non-confidential open-source engine defects. Never post proof data, credentials, or license keys.

Choose the right path

Compatibility question

Run tinyzkp-engine doctor --job job.json, compare the local result with the v1 profile, and do not attach DoctorReportV1 to any message.

Product defect

Use the verified private ordinary-support contact published above. Send only the exact release identity, reason code, a synthetic reproduction, and a manually redacted SupportReportV1. The public issue tracker is limited to non-confidential Community engine defects.

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-engine doctor --job job.json locally; do not share its report.
For Guard, run tinyzkp diagnostics --job job.json or tinyzkp diagnostics --job-dir ./job.
Confirm the artifact signature and exact release identity.
Reproduce with networking disabled after activation.
Inspect SupportReportV1 manually and include only the minimum safe output.

Billing help

When commerce.json states that 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.

Billing portal unavailable