Privacy
How your account, conversations and files are handled.
Updated October 14, 2026
Data the application handles
Account identifiers and authentication sessions are handled by the configured Supabase project. Saved chats store user and assistant messages in owner-scoped records.
Studio stores generated images and Texel workbooks with your account so you can reopen, edit and download them. Image files are private to their owner.
Temporary chats
Temporary conversation text stays out of saved chat history. Images and workbooks created in temporary chats are stored with your account to support downloads and follow-up edits. Usage, error and security records may still be retained.
Model providers and tools
Your prompts and the conversation context needed to answer them are sent to the selected model provider. The chat adapter requests zero-data-retention routing and disables provider data collection; actual handling also depends on the provider and its account settings.
If you connect an external plugin, requests to that plugin are handled by its server. Only connect services you trust with the information you ask them to process.
kaleidify Code history
kaleidify Code keeps each session on your computer. When you are signed in with a Kaleidify ID, it also keeps a copy of each session with that ID so you can resume it on another machine. The copy holds conversation text, tool inputs and outputs, and the project folder name, never the folder's full path. Known secrets are scrubbed before upload, but other private content in a session may remain. kaleidify Code says this in the terminal before its first upload.
The copy is stored in a separate history database (Convex) that accepts only short-lived tokens issued for your ID. A session stays bound to the ID it started with and is never uploaded under another one. /history off keeps future sessions on your computer only; kaleidify history forget deletes one copy or, with --all, every copy. Signing out everywhere from your account page also ends access to the history copy for every signed-in terminal.
Your account
From your account page you can download an export of your account data, including your kaleidify Code history copy, sign out of every browser and terminal, and delete your Kaleidify ID. Deletion cancels any subscription, removes your cloud history copy, and erases your Studio data and account. Payment records kept by the payment processor are governed by its own retention.
Controls and retention
Users can delete saved sessions from the history interface. Deleting a saved conversation removes its linked messages. Backups, security logs and external provider retention are handled separately.
When error reporting is enabled, diagnostic information is sent to the error reporting service. Do not submit secrets, regulated data, or information you are not authorized to process.