This page explains, specifically, what happens to your code and your data as you use CloudeIDE — what stays on your machine, what we send to our AI provider, and what we store on our servers. It's a companion to our Privacy Policy, focused entirely on data flow rather than legal terms.
1. Your workspace stays in your browser
The files and folders you create in the editor are stored in your browser's local storage. They are not uploaded to our servers as a matter of course, and we do not have a copy of your project sitting in a database somewhere. Clearing your browser's site data for CloudeIDE removes your local workspace entirely — we recommend exporting or pushing anything you want to keep.
2. What the AI assistant actually sees
Nothing is sent to the AI assistant until you send a message. When you do, we attach exactly what the interface shows you at that moment — your typed message, plus either the current text selection or the active file's contents, depending on what you've chosen to include. We do not scan, upload, or send your entire project in the background.
That request goes to two places:
- Our backend, which authenticates the request, checks your plan's usage limit, and forwards it to our AI provider.
- Anthropic (the provider of the Claude models), which generates the response you see streamed back into the panel.
3. What we store on our servers
Server-side, we keep only what's needed to make the product work across sessions and to bill accurately:
- Account data — your name, email, and hashed password.
- AI conversation history — the text of your messages to the assistant and its replies, so your conversation is still there next time you sign in.
- Usage metering — a running count of credits spent against your plan's monthly allowance. We store the count, not a log of every request's content beyond the conversation history above.
- Billing records — your plan, subscription status, and transaction identifiers from our payment providers. We never see or store your full card number.
4. Model training
We do not use your code or conversations to train our own models — we don't train any models. On Anthropic's side, code and messages sent through their commercial API are handled under Anthropic's own API terms, which (as of this writing) do not use API customer content to train their models by default. Review Anthropic's privacy policy directly for their current practice, since it governs their side of this independently of CloudeIDE.
5. Sub-processors
Third parties that touch your data, and what they see:
- Anthropic — the content of AI assistant requests (see §2), to generate responses.
- PayPal — your payment details, to process subscription charges. We receive only a transaction status back.
- Our cloud hosting provider — encrypted-at-rest storage for account data, conversation history, and billing records described in §3.
6. How long we keep it
Account data, conversation history, and billing records are kept for as long as your account is active. Deleting your account removes them, except where we're required to retain billing records for tax or accounting purposes. Your local workspace is retained only in your own browser, for as long as you keep it there.
7. Your controls
- Clear a browser tab's local storage to remove your local workspace.
- Start a new conversation in the AI panel at any time — it doesn't carry old context forward once cleared.
- Request export or deletion of your account data by contacting us at support@cloudeide.com.
8. Changes to this policy
If how we handle data changes in a way that affects what's described above, we'll update this page and the "Last updated" date, and where the change is material, we'll say so more prominently.
This page reflects how CloudeIDE is architected today; it is a template and has not been reviewed by a lawyer. Re-verify it against the actual production system (and applicable law, e.g. GDPR/CCPA) before relying on it, and update it if the architecture changes.