Verifying receipts without trusting us.
Engineering
Verifying receipts without trusting us.
How ECDSA-P-256 + a public JWKS lets your auditor verify a receipt offline when one was issued, with no CloakAPI account.
Writing on privacy-preserving AI, PII tokenisation, verifiable cryptographic receipts and GDPR — how CloakAPI keeps personal data out of AI providers, and how we build it.
How ECDSA-P-256 + a public JWKS lets your auditor verify a receipt offline when one was issued, with no CloakAPI account.
The sub-tag system lets receipt consumers understand what happened at each layer without a CloakAPI account.
Why no Packagist library solved our byte-compatibility requirement, and how we verified the GF(2^8) arithmetic.
On the gap between "we take privacy seriously" as a marketing claim and privacy as an engineering invariant.
How cross-tenant isolation works, what prompt-pool privacy guarantees, and what the honest residual risk is.