Desktop AI Companion Privacy: Microphone, Screen, and Control

Desktop AI companion privacy has two parts: what an application can access on your computer, and what happens to information you send to the service. A familiar character on screen should not make either part harder to understand.

Begin with the features you intend to use. Typed conversation, voice, screen-aware features, and file sharing can involve different inputs. You should be able to connect each requested permission to a specific feature instead of accepting a broad request because the character seems friendly.

Warmth makes a desktop companion. This is a general evaluation guide, including questions to ask of our own product. It is not a statement that Warmth implements every optional feature or control described below. For its data practices, read the current Privacy Policy and Terms.

A character on screen does not prove screen access

Seeing an animated character beside a browser does not establish that the character can read the browser. Displaying a window and obtaining content from other windows are separate capabilities.

If a companion offers a feature that discusses your screen, ask what is captured: a selected window, a screenshot you choose, or an ongoing stream. Ask what starts the capture, how you stop it, and whether the captured content is uploaded or retained.

On Mac, Apple provides separate controls for screen and system audio recording. Their existence is a reminder to evaluate the permission actually requested; a voice conversation and screen recording are not the same input.

Know when the microphone is available and when it is active

Permission to use a microphone does not describe the app's listening mode. It might receive audio during an explicit session, while a button is held, or through another interaction. Look for a clear explanation and visible session controls.

Find out what happens when you mute, close the conversation, hide the character, and quit the app. Those actions may have different meanings. Muting speaker output, for example, should not be assumed to stop microphone input.

Apple's microphone guide explains the Mac control. Microsoft's camera and microphone privacy guide explains Windows controls and their exceptions, including limits around desktop applications. Use these as device controls, alongside the app's explanation of what it does with audio.

Read a permission in the context of the package

Do not expect every operating system or installer format to provide an identical set of prompts. A Windows desktop application may have capabilities that are not governed by the same per-app settings as other apps; Microsoft explains this distinction in its app permissions documentation.

On Linux, packaging also matters. Flatpak documents its sandbox permissions and portals, including how access can be added. That documentation applies to Flatpak applications, not automatically to every Linux download.

If a companion requests filesystem or accessibility access, look for the specific purpose. A selected file is different from broad access to a folder. If the feature is optional, find out whether the rest of the app works without enabling it. Avoid treating a missing prompt as proof of no access.

Ask what travels beyond the computer

Installing an app does not by itself make the AI local or the conversation offline. A desktop interface may use remote systems to generate replies, transcribe speech, or produce audio.

Before sharing something sensitive, look for an explanation of these separate items:

• The text or audio sent to generate a response.
• Any transcript created from your speech.
• Conversation history saved in your account.
• Memories derived from earlier conversations.
• Diagnostics or support records that might contain content.

Then ask how long each is retained, which providers process it, and what deletion affects. Our AI companion privacy checklist covers account and service questions in more detail. The desktop guide adds device access to that existing checklist.

Keep personal conversation out of shared spaces

Privacy also involves the people physically or virtually near your computer. A spoken reply can be heard across a room. A conversation window can appear during screen sharing. A notification preview can reveal context without anyone opening the app.

Try the setup you actually use: headphones, a shared desk, a work call, or a family computer. Choose text when you do not want spoken replies, and inspect your screen-sharing preview before presenting. Decide when the companion should appear automatically and when you prefer to open it yourself.

These habits do not replace the service's data controls. They address another part of privacy: who can see or hear the conversation from your side of the interaction.

Make leaving understandable

Before making a companion part of your routine, find the separate paths for ending a voice session, quitting the app, changing a subscription, and deleting data. Removing a desktop application does not establish that its service account or stored conversations have also been removed.

Our guide to deleting AI chats and accounts explains the distinction between history, memory, and account records. If a policy does not answer your question, ask the publisher about the exact data or permission you mean rather than accepting a general assurance that the product is private.

For Warmth, the desktop overview describes the conversation experience and the current setup shows how to begin. A comfortable first conversation starts with understanding what you are choosing to share.