KalaBodha Vault API · Effective September 29, 2026
These terms govern your use of the KalaBodha Vault API (the "Service"), operated by AIMLDS. By using the Service you agree to these terms.
The Service provides zero-knowledge content segregation: namespaced storage of
caller-encrypted envelopes, a tamper-evident audit log, and HMAC proof certificates
verifiable via POST /v1/proofs/verify. The Service is currently
v0.1.0 — functional and tested, but early. Envelope cap: 512 KiB.
kbv_live_… keys confidential; you are responsible for calls made with keys issued to you. Use scoped keys (one namespace per agent) to limit blast radius.Plans carry object and byte quotas per period. Exceeding quota returns HTTP 402
(quota_exceeded). We may rate-limit abusive traffic to protect the Service.
Proof certificates are HMAC-SHA256 signatures over object metadata. If the vault signing key is ever rotated (procedure documented before it happens), previously issued proofs will no longer verify — re-issue after rotation.
The Service is provided "as is", without warranties of any kind. To the maximum extent permitted by law, AIMLDS is not liable for indirect, incidental, or consequential damages, including data-key loss on your side. Direct liability is capped at fees paid in the preceding 12 months.
We may suspend or revoke API keys for abuse, non-payment, or unlawful use. You may stop using the Service at any time; tombstoned data follows the deletion rule in the Privacy Policy.
We may update these terms; material changes will be noted with a new effective date above. Continued use after changes constitutes acceptance. Contact: info@nrupalakolkar.com.