Your data in Kameleo.

Accounts and practice data

When authentication is enabled, Clerk handles sign-in. Kameleo associates your Clerk user ID with your attempts, edited challenge files, chat messages, unlocked hints, test results, and scores. These records let you resume practice and review submissions.

AI and code execution

Using the assistant sends your prompt, relevant conversation history, and challenge code context to Google’s Gemini API. Running or submitting a challenge sends a snapshot of your code and its tests to an E2B sandbox. Application records are stored in MongoDB.

Do not paste passwords, API keys, confidential work code, or personal information into challenges or chat. Provider processing and retention also depend on their policies and the account settings used by Kameleo.

Cookies and operational logs

Authentication uses session technology, including cookies. Hosting providers process requests to deliver the service. Application logs record request IDs, routes, response status and timing; the application does not deliberately include chat text or authentication tokens in these logs. Optional error monitoring may be enabled by the operator.

Retention and requests

The prototype does not yet have an automatic deletion schedule or a self-service data export or deletion tool. Before submitting personal data, ask the person who invited you to the prototype about retention or to arrange access, export or deletion. A public privacy contact must be established before open registration.

Provider information

Learn more from Clerk, Google Gemini, E2B, and MongoDB. Which services are active depends on the prototype’s deployment configuration.