Home Privacy and Data
🔒

Privacy and Data

Privacy, permissions, and data handling for SoLo Support.
By Jeremy Smith
• 3 articles

Personal computers and private AI access

Private computer ownership A personal account keeps its own isolated workspace internally. You do not need to configure a business organization. Your signed-in owner account controls enrollment and device management. Keep downloaded installers and enrollment tokens private, and only enroll computers you own or have permission to access. Optional AI test access Allow AI access is off by default and requires an account owner or administrator. It enables a separately configured private desktop integration on eligible Windows, Linux or macOS computers, subject to local capture/input permissions and organization policies. It does not install an OpenAI store plugin or automatically connect an agent. Public store approval has not been announced. Enabling AI access on a computer and approving an agent connection are separate decisions. Start the connection from your AI service, sign in with the account that owns the computer, and choose the computers that connection may access. No computer is selected automatically. Installing another Host Agent does not add that computer to an existing connection's approved list. Screenshots and control Only authorize a test computer with sensitive windows closed. Passwords, authentication secrets, payment-card information, government IDs and private health information are outside this connection's intended use. An authorized agent can receive screenshots and send keyboard and mouse input through the separately configured gateway. Screenshots go to the connected AI service that requested them. SoLoSupport's gateway decodes the live stream in memory and sends requested screenshots to the connected AI service. The AI service has its own data-handling settings. When the workspace enables or requires AI recording, SoLoSupport stores desktop video until its recording retention period expires. Audio is not captured. A visible session banner is still required. After a recorded AI session ends, open Sessions → Recording or the agent's end-session link for playback and Download recording (WebM). Sign in to the same workspace: the session's technician and workspace owners/admins can retrieve it. Other technicians, customers and unauthenticated visitors cannot. Failed or interrupted recordings are marked failed. New single-monitor recordings use the full canvas with centered letterboxing; existing recordings keep their original layout. Zero recording retention prevents recording-enabled AI sessions from starting. Downloaded copies are outside server retention. macOS needs Screen Recording and Accessibility permissions. Linux Wayland needs local desktop-portal sharing/input approval and a supported portal. The OS running the AI service does not determine the remote computer's eligibility. Physical capture/input acceptance remains platform-specific; do not assume every desktop or locked-screen state is supported. Stop or revoke access End the current session through the agent or the Host Agent's local stop control. Revoke AI access blocks the next agent screenshot or action; also choose End open sessions to disconnect immediately. Revoke an individual agent connection from Connected agents. Consent changes are recorded in Activity. Authorization for a computer does not replace authorization for the agent's current task.

Last updated on Oct 10, 2026

Organizations: optional recording and AI access

Recording is optional for new organizations New business workspaces start with Require session recording off. An owner or administrator can change it under Settings → Session guardrails. Existing workspaces keep their current settings; upgrading does not disable a recording requirement. Activity logs and screen recordings Session records and activity logs remain available without screen recording. They identify the actor, computer, session times and state, and AI access changes. They are not a video of the desktop. Audit-log and recording retention are separate settings. AI desktop access An organization can authorize the private AI integration on supported Windows, Linux or macOS computers. Allow AI access requires an owner or administrator; each connected AI service also needs approval for its selected computers. Visible session banners, disconnect and revocation still apply. Under Settings → Session guardrails, Record AI sessions stores private AI desktop video without requiring recording for every support session. Require session recording takes precedence. AI sessions honor both settings and the recording retention period; they stop control if recording fails. After a recorded session ends, its technician and workspace owners/admins can open Sessions → Recording to play or download the WebM. Audio is not captured. Zero recording retention prevents recording-enabled AI sessions from starting. Recording is an administrator choice; the gateway never overrides it. Public OpenAI approval has not been announced.

Last updated on Oct 10, 2026