LAUNCH VERSION · 19 SEPTEMBER 2026
Security architecture
KYVLT security is based on verifiable limits, non-recoverable secrets, human approval, and immediate revocation.
Authentication
The personal account uses the identity supplied after ChatGPT sign-in. Access decisions are checked on the server.
Secrets
Mandate tokens contain 256 random bits and are hashed before storage. Public proof codes use a separate value and grant no right to act.
Google connection
KYVLT uses OAuth 2.0 with a single-use state value to prevent sign-in redirection attacks. Google tokens are encrypted at rest with AES-GCM, and the requested Gmail permission is limited to sending email.
Budget caps
An authorized amount is deducted using an atomic conditional update. Two concurrent requests cannot exceed the remaining budget.
Requests
Each operation uses an idempotency identifier to prevent duplicate deductions. Prohibited actions and data scopes are checked on the server, and the API applies per-token rate limits.
Passports and delegation
A KYVLT passport is a self-declared technical identity. It grants no authority by itself and is not a legal identity. When an agent chain is supplied, the server checks registered passports, the root agent, and the permitted depth.
Integrity receipts
Each final authorization API decision may produce a receipt binding the action fingerprint, the applied policy fingerprint, and the declared agent chain. The receipt proves consistency of recorded data, not external identity truth or actual execution by a third-party service.
Human confirmation
A mandate may require an explicit decision by its owner. The request then remains pending, and the agent receives no authorization before approval.
Integrated AI assistant
The AI model prepares only a structured proposal. It never receives secret tokens and cannot bypass deterministic server checks, mandate status, or required human confirmation.
My Rights vault
Documents are stored separately from structured records. Every read and deletion checks the owner’s identity on the server. File types and size are restricted, caching is disabled, and files are never made public or sent to the AI model.
Action integrity
An approved action preserves its account, recipients, content, schedule, and attendees. Any material change must create a new authorization request.
Single Gmail send
An atomic update reserves the action before Gmail is called, preventing concurrent duplicate sends. After an ambiguous network error, KYVLT blocks automatic retries and asks the user to check Sent messages.
Revocation
Revocation immediately changes the mandate status. Every new request using that mandate token is then refused.
Pilot scope
The service has not yet received banking certification, an independent security audit, or eIDAS qualification. Those steps are required before regulated use.
Report an issue
Report a vulnerability or suspicious activity to contact@la-cle.app with reproduction steps and without attaching a secret, password, API key, or complete token.
Questions? Contact KYVLT support.