Skip to content

Privacy and control

The privacy boundaries of a screen companion

Separate local voice, saved conversations, model requests, and account services. Understand what a screen companion needs to see before using it.

··3 min read

“Runs on your Mac” does not mean every part of an AI conversation stays on the Mac. A useful privacy explanation separates voice processing, screen context, saved history, provider requests, and account services instead of treating them as one system.

Three paths to understandIllustrative diagram
Where each kind of information goesDefault local voice and local history are separate from provider requests and account services. Optional cloud voice has its own data path.On your MacLocal dictation and voiceSaved historyContext and annotationsQuestion + imageAI providerYour selected connectionAccount and subscriptionNo screenshots or chats
  1. 01
    Identify local work

    Default dictation and speech processing happen on the Mac; conversations are saved locally.

  2. 02
    Understand provider context

    Questions and permitted screenshots go through the selected AI provider.

  3. 03
    Separate account data

    Account and billing services handle access data, not screenshots or conversation content.

Default local voice and local history are separate from provider requests and account services. Optional cloud voice has its own data path.

Start with the actual question and screen

A screen companion needs enough visible context to answer the question you asked. That does not make every open window relevant. Before discussing a document, bring the needed portion into view and close or hide unrelated sensitive material. The goal is a clear source, not a full tour of your desktop.

Rayito has capture exclusions, including exclusions for password managers and apps you choose not to show. Treat those as useful controls, not as a reason to ignore what is visible. A sensitive number copied into an ordinary document is still sensitive even if the original app is excluded. Inspect the content you are asking the companion to work with.

Distinguish local voice from the model request

Default dictation and speech run locally. The selected AI provider receives the question and the permitted screen context used for the response. That distinction explains why a local companion can still depend on a network connection and a provider account. “Local app” describes where the interface runs; it is not a promise that model inference is offline.

Optional cloud speech changes the voice path. If you choose a cloud voice provider with your own key, the text to be spoken is sent through that service. Local Spanish voices also require their voice package to be installed; local processing does not mean every voice model arrives in the base download. Check the selected voice and connection rather than assuming all settings behave identically.

Treat saved context as part of the conversation

A useful history can contain more than a text transcript. Rayito preserves conversation context and annotation playback so you can revisit an explanation. This can include the filtered screen content associated with a response. Saving that context helps an old explanation remain understandable, but it also means you should consider what you want to retain on your own Mac.

Replaying a conversation is different from observing the current screen. A replay shows the saved situation, which may no longer match a live document. Continuing a conversation is another step and can involve a new provider request. When the underlying source has changed, show the current version rather than relying on an old capture as evidence of its present state.

Keep account access separate from conversation content

Rayito’s account and billing services are for identity, subscription access, and purchase information. They do not receive screenshots or conversation content as part of that service. This separation is worth understanding alongside the provider connection: a billing system and an AI provider have different jobs. For the current public details, read the site’s privacy policy and review the controls in the app before using private material.