Skip to content
cloudroom

Privacy policy

What Cloudroom collects, why, and how to turn it off. Updated November 13, 2026.

This policy explains how Cloudroom Inc., a Delaware corporation (“Cloudroom”, “we”, “us”), handles your data. We are responsible for it. See also our terms and security pages.

The short version

  • Your code, prompts, and files are yours. We never sell them, rent them, or use them to train AI models.
  • We never give your data to advertisers or data brokers. Only the service providers that run Cloudroom handle it, and only to run it.
  • Local threads stay on your computer. Only six features send us any of their content, and you control each one.
  • Cloud threads run in your own isolated sandbox. No other user can see them.
  • Your agents talk to your model providers, such as Anthropic or OpenAI, directly. Cloudroom never sits in between.
  • Usage stats never include your prompts, code, or files. You can turn them off.

Your account

  • When you sign in, we store your email and login provider.
  • If you joined our waitlist before it closed on October 13, 2026, we store your answers, including your email and, if you shared it, your phone number. We used them to review your application and contact you about access.
  • An AI model scored waitlist answers. The score decided the order in which we invited people.
  • Every waitlist email has an unsubscribe link. Once you use it, we stop emailing you.
  • When you use an invite code, we record who invited you.
  • When you buy a plan, Polar handles the payment. We never see your card details. We store your plan and subscription status, and Polar shares your email, billing name, and country with us.
  • When you buy Ultra, we ask for your name and role, company and team size, why you bought Cloudroom, your Slack email, and your phone number. We email your answers to our team to set up your onboarding call.

Desktop app usage

  • The app sends usage events, such as app starts, threads and messages started, plugin installs, which plugins are on and how often each is used, how many tokens Local threads use each day by agent and model, share links you make or copy, and settings searches that find nothing.
  • A settings search is sent only if it has 4 words or fewer, 40 characters or fewer, and only letters. Searches with digits, @, dots, or other symbols are never sent.
  • Each event includes the app version, your operating system and chip type, which agent you used, your Cloudroom plan, and your country and time zone.
  • When a thread fails, we send the type of error, such as a rate limit or a lost connection, never the error text. We also count when upgrade offers are shown and clicked.
  • Usage events never include your prompts, messages, code, files, or file names. Plugins you add from outside Cloudroom’s catalogs are counted without their names.
  • Events carry a random ID created on your computer. When you sign in, we link it to your account so we can help you when something breaks.
  • If connecting or installing Claude Code or Codex fails, we save the error and a summary of your setup with your account, such as app and agent versions, plan type, free disk space, and whether a proxy is on. Never file paths, emails, or tokens.

To turn it off, open Settings and switch off “Share usage data and setup errors”, or run room-cli settings general telemetryEnabled false.

Local threads

  • Local threads run on your computer. Their messages and files stay there, with six exceptions below.
  • Thread names: to give threads clear names, the app may send a thread’s first message and first reply to us for AI processing. We do not keep that text. To turn it off, set Settings → “Rename vague titles” to Off.
  • Agent feedback: your agents can send us short reports about Cloudroom bugs and ideas. To turn it off, switch off Settings → “Send agent feedback”.
  • Share links: when you share a thread, we store a copy of its messages so anyone with the link can read it. Stop sharing deletes the copy. We count views and button clicks on the shared page on our own servers, never with an outside service, and never with the link itself.
  • Voice input: if the app’s own transcription fails, it may send your recording to us to turn it into text. We do not keep the recording.
  • Smart search: on paid plans, Cmd+K search sends what you type and a short card for each open thread (its title, project, one-line summary, and a matching snippet) to us for AI processing, to rank the results. We do not keep that text. To turn it off, switch off Settings → “Smart search”.
  • Wrong-project hint: on paid plans, while you type a new thread’s prompt, the app sends the prompt and a short summary of each project to us for AI processing, to suggest the right project. We do not keep that text. To turn it off, switch off Settings → “Wrong-project hint”.

Cloud threads

  • Cloud threads run on cloud computers. To run them, we copy the project you choose, along with your Cloud environment settings, skills, and instructions.
  • Logins and API keys you copy to the cloud are stored encrypted and used only to run your cloud threads.
  • Cloud computers count the tokens each thread uses, by agent and model, so we can see how Cloudroom is used. Never the text.
  • We save each cloud thread’s chat history, and may keep a saved copy of archived cloud threads, until you delete them. Unused cloud threads are deleted automatically after your plan’s limit, or sooner if you pick a shorter time in Settings → Auto-delete.
  • Mac access: when a cloud agent runs a command on your Mac, an AI model checks the command for security risks, after we remove common secrets. If it looks risky, the model also reads up to 2,000 characters of your latest messages in that thread to see if you asked for it, and we keep the command, with common secrets removed, so our team can review it. We never keep your messages.

Phone access

  • When you open Cloudroom from your phone, its traffic passes through a relay to reach your Mac.
  • Today that relay is BB Connect at getbb.app, run by BB, the open-source project Cloudroom’s desktop app is built on. BB’s privacy policy applies to it.
  • We are moving phone access to cloudroom.run, which we run. See our domains on the security page.

Website

  • We count page views. We record the page path, not query strings.
  • Our servers keep request logs for 14 days.
  • We use only the cookies needed to sign you in, one that remembers an affiliate’s link you arrived through, and one that remembers a shared thread you viewed, for 30 days.

How we use your data

  • To run Cloudroom and the features you use.
  • To keep it secure and enforce usage limits.
  • To fix bugs, support you, and improve the product.
  • To email you about your account and access.
  • We do not sell your data, and we do not use your content to train AI models.

Who can see it

  • Our developers look at account data, cloud chat history, and diagnostics only when needed to fix problems or support you. They never see your saved logins or keys.
  • Your agents talk to your model providers, such as Anthropic or OpenAI, directly, with your own accounts. Their privacy policies apply.
  • We use these service providers. They handle data only to provide their service to us:
  • Supabase: database and sign-in. Vercel: website hosting, page-view counts, cloud computers, and AI processing. TypeSafe: the AI model that names threads, checks Mac access commands, and scored waitlist answers. Upstash: cloud computers. Cloudflare: file storage for cloud history and saved thread copies, and phone access relay.
  • Resend and SendGrid: email. Google Workspace: our inbox and onboarding calls. Cal.com: booking calls. Hostinger: desktop app usage and cloud diagnostics. OpenRouter: voice transcription and Mac access command checks. Discord: team alerts. Polar: payments and billing. Dub: our affiliate program. It gets account IDs and, for customers an affiliate brought, payment amounts. Never names or emails.
  • Most of them are in the US. Where data leaves the EU, we rely on our providers’ safeguards, such as Standard Contractual Clauses.
  • We share data with authorities only when the law requires it.

How long we keep it

  • Account data, cloud history, and saved thread copies: until you delete them or close your account. Unused cloud threads are deleted after your plan’s limit, or sooner if you pick a shorter time in Settings → Auto-delete.
  • Saved logins and keys: until you remove them or close your account.
  • Website request logs: 14 days.
  • Billing records: as long as tax law requires.
  • After you close your account, we delete your data within 30 days.

Your rights

  • You can ask to see, correct, export, or delete your data, or object to how we use it. Email us and we will reply within 30 days.
  • You can also complain to your local data protection authority.
  • Cloudroom is not for anyone under 18.

Changes and contact

We change the date above when we update this policy, and tell you about important changes. For questions or requests, email support@cloudroom.dev, or write to Cloudroom Inc., 2810 N Church St STE 90007, Wilmington, DE 19802, USA.