Coralflavor

Chat with an uncensored LLM

Chat now

An independent explainer of Coralflavor's dual-mode architecture: ephemeral burn mode using browser session storage and encrypted save mode with client-side keys.

Published 2026-11-15

How Coralflavor Works: Burn Mode vs Save Mode Explained

Coralflavor offers two distinct chat storage modes—burn mode and save mode—that represent fundamentally different privacy trade-offs. Burn mode keeps conversations entirely ephemeral, stored only in the browser’s session storage and never written to the backend. Save mode encrypts chat history with AES-256-GCM before sending it to the cloud, but stores decryption keys exclusively in the user’s browser. This architecture gives users granular control over their data, but also introduces specific risks and dependencies that are worth understanding before relying on either mode.

Burn Mode: Ephemeral by Default

Burn mode is the default setting for all new users and free accounts. According to Coralflavor’s privacy policy, burn-mode chats are “never written to our database” and “kept only in your browser (in session storage for the current tab).” The browser sends the conversation with each message so the model can maintain context, but closing the tab discards the chat entirely.

This design prioritizes zero data retention. Coralflavor states that burn-mode prompts are sent to model providers using “zero data retention (ZDR) endpoints, which claim not to retain prompts or outputs after processing.” The privacy policy includes a caveat that the limits of this assurance are detailed in Section 6, though independent verification of these ZDR claims has not been publicly documented.

One nuance: if a free user starts upgrading to Pro, the current burn-mode chat is copied to the browser’s local storage for up to 24 hours, allowing the user to save it after completing the upgrade. This is the only exception to the ephemeral rule.

The homepage reinforces that burn mode is the default, stating “Chats stay in your browser and are not saved to your history.” A blog post comparing Coralflavor to Notrack.ai further confirms that “no IP addresses are logged for chat interactions.”

However, there are open questions. The privacy policy does not specify how long session storage persists before browser garbage collection, or whether any metadata (such as timestamps or session IDs) is logged despite the ZDR claims. The policy also acknowledges that session storage could theoretically be accessed by browser extensions or malware, though this risk is not explicitly discussed in Coralflavor’s documentation.

Save Mode: Encrypted Cloud Storage with Client-Side Keys

Save mode is available only to Pro subscribers. When enabled, chat content—including prompts, AI responses, extracted text from uploads, and chat titles—is encrypted in the browser with AES-256-GCM before being sent to Coralflavor’s database. The database stores only ciphertext.

The encryption keys are stored in the user’s browser local storage, not on Coralflavor’s servers. According to the privacy policy, “Our servers only assign key numbers (such as 001, 002) and never receive the keys themselves. As a result, not even CoralFlavor can read your saved chats directly from the database.”

This design means that if a user loses their encryption key—by clearing browser site data, switching devices without exporting the key, or accidentally deleting local storage—Coralflavor cannot recover the saved chats. The privacy policy explicitly warns: “Back up your key from the encryption keys option in the chat sidebar.”

Save mode protects chats at rest, but not during transmission. To generate a reply, the current conversation is still sent to Coralflavor’s servers and on to model providers in readable form, just as in burn mode. This is a necessary architectural limitation: the model needs the plaintext to respond.

Pro users can switch between save and burn mode at any time, and can delete individual saved chats. The preference is stored in the browser and applied to later chats.

Understanding the technical mechanisms is essential for making informed decisions about data privacy in an unfiltered AI environment.

FAQ

What happens to my chat history if I close the tab in burn mode?

Burn-mode chats are stored only in your browser’s session storage for the current tab. Closing the tab discards the chat entirely; it is never written to the backend database.

Can Coralflavor recover my saved chats if I lose my encryption key?

No. Encryption keys for save mode are stored only in your browser’s local storage, not on servers. If you clear site data or switch devices without exporting your key, Coralflavor cannot recover the chats.

Is save mode available to free users?

No. Save mode is available only to Pro subscribers. Free users and new users default to burn mode, where chats remain ephemeral.

Does burn mode guarantee that no one else can access my chats?

Burn mode uses zero data retention (ZDR) endpoints with model providers.

Are saved chats encrypted while being sent to the model for a reply?

No. To generate a reply, the current conversation is sent to Coralflavor’s servers and on to model providers in readable form, just as in burn mode. Save mode only protects chats at rest in the database.