Support: support@tinplate.dev · Zero-Retention Edge Security Support Trust Center DPA GitHub Issues
Cryptographic Audit Trail Ed25519 / ES256 / HMAC-SHA256 · Zero-Logging

Compliance Receipt Verifier

Verify any X-Tinplate-Receipt token issued by ?receipt=true or X-Tinplate-Receipt-Request: true in constant time against our gateway signing keys or public JWKS (/.well-known/jwks.json).

Zero-Trust Offline Verification

How Cryptographic Attestations & body_sha256 Binding Work

  • Asymmetric Signing (EdDSA / ES256): Tokens signed with the gateway Ed25519 key carry header {"alg":"EdDSA","typ":"AAR","kid":"edge-ed-2026-11"} and verify completely offline against GET /.well-known/jwks.json (supporting zero-downtime key rotation across active & retired kid entries).
  • Request-Body Cryptographic Binding: Every receipt commits action_input.body_sha256 over exact request bytes plus prev_hash (linked via X-Tinplate-Prev-Receipt-Hash) without persisting prompts, PII, or responses on Tinplate servers.
  • Zero-Dependency SDK Helper (@tinplate/sdk v1.1.6): Verify locally in Node 18+, Cloudflare Workers, Deno, Bun, or browsers using WebCrypto crypto.subtle:
import { TinplateClient } from "@tinplate/sdk";

const client = new TinplateClient({ apiKey: process.env.TINPLATE_API_KEY! });
const jwks = await client.getJwks(); // caches https://api.tinplate.dev/.well-known/jwks.json
const check = await client.verifyReceiptOffline(receiptToken, { jwks });
console.log(check.valid, check.alg, check.kid, check.payload);

See our Security & Trust Center or inspect Self-Service Portal for key-scoped compliance summaries.