Skip to content
Legal

Privacy Policy

Last updated: October 28, 2026

Consoles is made by MTB Media LLC ("Consoles", "we", "us"). This policy covers the Consoles desktop app, the consoles.ai website and the cloud services behind them. It describes what we actually store and why.

The short version
  • Local-workspace chats, files and saved credentials stay on your computer. If you choose a cloud workspace, they live on your Agent Computer instead.
  • AI requests go from the computer running your workspace to the provider you sign in to. Cloud chat messages pass through our authenticated connection to your Agent Computer.
  • We store your Consoles account and the cloud features you choose to use: Messages, live streams, Compute, your organization's shared library and session reports you send us.
  • We do not sell personal data, use it for advertising, or use it to train AI models.

1. The desktop app: what stays on your computer

For local workspaces, the Consoles desktop app keeps your chats, session history, project files, settings and agent output on your computer. API keys, sign-in tokens and other credentials for those workspaces are encrypted and stored locally. We do not receive copies of local-workspace credentials. A cloud workspace is different: its data and encrypted provider credentials are stored on your Agent Computer so it can keep working without your laptop.

You can use the desktop app without a Consoles account. Some features (Messages, live streaming, organizations) need one.

2. AI providers

Consoles works with AI providers you choose and sign in to, such as Anthropic, OpenAI, GitHub Copilot, Google, xAI, Meta and Cursor. When you send a message, the app sends your prompt, the relevant context (for example file contents and tool output) and your credentials for that provider directly from the computer running your workspace to the provider. For local workspaces, these requests do not pass through Consoles servers. For cloud workspaces, your messages and agent responses pass through our authenticated relay and the agent runs on your hosted computer using your provider account.

Each provider handles that data under its own terms and privacy policy. Please review them, especially before working with sensitive data.

3. Your Consoles account

If you create a Consoles account, we store:

  • Profile: name, email address, profile picture and your username (screen name).
  • Sign-in data: a hashed password if you use one, two-factor settings, and the sign-in sessions on your devices, including the IP address and browser or device type for each session.
  • Linked sign-in accounts: if you sign in with GitHub, Google or Microsoft, the account identifier and the access tokens that provider issues to Consoles. For GitHub we also store your GitHub username.
  • Organizations: organizations you create or join, your role, invitations, join requests, and verified email domains and single sign-on settings an organization admin sets up.

When you sign in with Google, we receive your name, email address and profile picture. We use them only to create and run your Consoles account. Consoles' use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4. Messages

Messages lets you chat with other Consoles users and receive email at your @mail.consoles.ai address. To deliver them we store your contacts list, your presence (online, away message, and the project name you are working on, which your contacts can see) and the messages themselves.

  • Instant messages wait in a delivery queue until each of your devices has received them, and are removed from the queue after at most 30 days. Files sent in Messages are stored in our cloud storage.
  • Email you receive at mail.consoles.ai is stored in our cloud storage (the original message and its attachments) so you can open it from any device. Thread details used for replies (subject, sender and participants) are kept for 180 days. Email you send from Consoles is delivered through Cloudflare.

5. Live streaming

If you go live, what you choose to share (your screen, camera, audio, chat activity and terminal output) is relayed to viewers at consoles.ai/live in real time and is public. Most of the stream passes through in memory only. We keep a small amount: your channel settings and schedule, the last 100 stream chat lines, chat clips you create, follows, poll votes and a history of past streams (title, time and counts).

6. Cloud computers, Compute and video

If you use cloud computers or Compute, we store the workspace, code you run, job records and output files. Agent Computers run on boat by ASCII; Compute jobs can run on Cloudflare (CPU) and Modal (CPU and GPU). Cloud chats, project files and encrypted model credentials live on your Agent Computer. Access tokens used to connect to that computer are encrypted in our database and are not sent to your browser. Tool credentials are encrypted before we store them.

When you choose managed Video (Rend), we create a linked, separate Rend identity using your Consoles account identifier, name and email. Your video projects, uploaded media and editing requests are processed by Rend. We store the linked account identifier and encrypted short-lived access tokens. We record computer hours, render runtime, estimated AI cost and storage usage to show and enforce free-alpha limits. No charges are collected by this alpha integration.

7. Organization library

Organizations can share skills, sources, agents and settings with their members. These bundles are stored in our cloud storage and visible to members of that organization. Credentials, tokens and other secrets are stripped before a bundle is uploaded, so each member signs in to shared sources with their own account.

8. Session reports, feedback and applications

  • Session reports. When you choose "Report to Consoles…", the app uploads a zip of that session's full trace: messages, subagent transcripts, tool calls and output (which can include code and file contents) and a slice of the app log. Consoles administrators can read it to debug the problem. Reports are only sent when you ask.
  • Feedback you or an agent sends through the app's feedback tool is stored with the session identifier it came from.
  • Job applications sent through our careers page are stored so we can review them.

9. Student data protection

For schools, the desktop app can replace personal details with placeholders before they reach the AI model: student and guardian names, student IDs, dates of birth, and emails, phone numbers and similar identifiers. The real values are kept in an encrypted vault on the computer running that workspace (your own computer for local work, or your Agent Computer for cloud work) and are restored there when the agent’s answer comes back. Text detected and masked by this protection is sent to the AI provider as placeholders.

Detection is rule-based and can miss things, especially names that are not on a roster you have loaded. It works on text only: images and screenshots are not masked. While protection is on, the app's browser blocks screenshots on sites you mark as sensitive.

10. Other connections the desktop app makes

  • Updates: the app checks updates.consoles.ai for new versions.
  • Approximate location: unless you set a location, the Home screen asks our server once a day for your approximate city (from your IP address, via Cloudflare) to show local time of day. We do not store it.
  • Crash reports: the app can send error and crash reports to Sentry. Authorization headers, tokens, keys and passwords are removed before they are sent.
  • Connecting Google, Microsoft or Slack as a source: the sign-in redirect passes through a callback page at agents.craft.do, operated by Craft Docs, which hands the result back to the app on your computer. The resulting tokens are stored on the computer running the workspace.

11. Cookies

consoles.ai uses a cookie to keep you signed in, and your browser's local storage for preferences such as light or dark mode. We do not use advertising or analytics cookies. Sign-up and sign-in forms use Cloudflare Turnstile to block bots.

12. Service providers

We use these providers to run Consoles. They process data only on our behalf.

ProviderWhat for
CloudflareHosting, database, file storage, email sending and receiving, real-time audio and video relay, CPU compute, bot protection
ModalCloud CPU and GPU machines for Compute jobs
boat by ASCIIAgent Computers, cloud chats, files and encrypted provider credentials
RendManaged video identities, projects, media, editing and supported renders
SentryDesktop app error and crash reports
GitHub, Google, MicrosoftSign-in, when you choose that option

AI providers you sign in to handle model requests under their own terms (see section 2), including when those requests originate from your Agent Computer.

13. How we use data

We use the data above to provide and secure Consoles, deliver your messages and streams, fix problems you report and contact you about your account. We do not sell personal data, share it for advertising, or use your content to train AI models. We disclose data only to the service providers above, to the people you choose to share with (contacts, viewers, your organization), or when the law requires it.

14. Schools and districts

Consoles is built for teachers, staff and other adults. Student information a school handles in the desktop app stays on the school's computers, except for what is sent to the AI provider the school chooses. We do not sell student data or use it for advertising or model training. Districts can request a data privacy agreement (DPA) by emailing support@consoles.ai. Districts may also request our supplemental information for New York Education Law 2-d and the Parents' Bill of Rights for Data Privacy and Security.

15. How long we keep data

We keep account data while your account is open. Messages are kept as described in section 4. Session reports, feedback, workbooks and stored email are kept until you or we delete them, or until your account is deleted. When you delete your account we delete your account data and the content tied to it, except where we must keep something to meet a legal obligation.

16. Security

Data is encrypted in transit. Stored tool credentials are encrypted, and passwords are hashed. Access to stored data is limited to the systems that need it and to Consoles administrators. No system is perfectly secure; if we learn of a breach affecting your data we will notify you as the law requires.

The invite-only cloud alpha is not end-to-end encrypted. Its authorized services and agent runtime process the plaintext needed to provide the features you use; your chosen AI provider also receives the model context described above.

17. Your choices and rights

  • You can update your name, username and profile picture in your account settings.
  • You can ask for a copy of your data, a correction, or deletion of your account and its data by emailing support@consoles.ai from the address on your account. We will respond within 30 days.
  • Data on your computer is under your control: deleting a workspace or uninstalling the app removes it.

18. Children

Consoles is not directed to children and is not meant for direct use by students under 13. We do not knowingly collect personal information from children under 13. If you believe a child has created an account, contact us and we will delete it.

19. Changes

We will post changes to this policy on this page and update the date above. If a change materially affects how we use your data, we will tell you by email or in the app before it takes effect.

20. Contact

MTB Media LLC (Consoles). Questions or requests: support@consoles.ai.