Privacy policy

When you register or sign in, we process your name, email address, account identifier and sign-in history. Google sign-in can also provide your profile photo. Supabase handles email/password and Google authentication. Passwords are sent to the authentication service. They are not made available to your bots.

We store account access, trial dates, plan assignments, permissions and team membership to provide the service. Signing in to the desktop app also creates a website session, so you can use either app with the same account.

Sphere Bot processes the messages, instructions, files and other content you provide to your bots, along with their responses and tool results. This can include images, screenshots, browser or computer activity, generated files and skills. When you use transcription or supported media features, audio, transcripts or video may also be processed.

Bot history and workspace data are stored on the bot's computer and in the app's supporting storage. The desktop app also keeps local profile data. A cloud computer processes workspace data on E2B infrastructure. A Docker computer runs on the desktop environment you select. Using Docker does not make model or connector requests local: those requests still reach their configured services.

Only provide content you are allowed to share. A bot that can see a page, file or screenshot may include that information in a model request or a tool result.

Tasks are sent to the model provider configured for your account or team, together with the context needed for that task. This can include conversation history, relevant files, screenshots and tool outputs. OpenRouter, custom inference services and other supported providers apply their own terms, retention practices and privacy policies. Their handling of data can differ, including how they use data to improve models.

When you add a connector, we store its installation and configuration for your account so the web and desktop apps can use it. Connected services receive the requests and content needed to carry out the actions you authorize. API keys and OAuth tokens let the runtime act through those services. The account or team configuration determines which credentials it uses.

We encrypt stored provider credentials and connector secrets in the relevant account or computer storage. Authorized runtime components still need to access them to make requests. Removing a connector stops its use through that installation. You can also revoke its authorization directly with the connected service.

When you authorize an external MCP app, we store its registration, the connection to your Sphere account and the permissions you approved. We store hashes of access and refresh tokens. The connected app can read your bot names, recent user and bot text and task status. If you grant write access, it can also send tasks to existing bots and stop their work.

The app receiving those results applies its own privacy and retention practices. Secret prompts, raw tool calls and shared rooms are excluded from this interface. You can revoke a connection in Connected apps. Revocation stops future access but does not delete information the external app already received.

Team owners manage shared routing, computer settings, member permissions and usage allocations. They can see member usage, including model tokens and computer time. Consider the team's settings before using a team account for personal work.

We manage account access, plans, connector availability and permissions. Operational records can include sign-in and app check-in times, model token usage, computer running time, errors, version and platform details. Diagnostic reports may include error messages and task context. Avoid including passwords or sensitive content in feedback and support reports.

We use these records to enforce access and usage limits, investigate failures, prevent abuse and support the service. If you contact us or submit feedback, we also process your message and contact details to respond.

The website uses cookies for sign-in, account selection, password recovery and the continuation of desktop sign-in. The main website session and sign-in indicator last up to seven days. Temporary sign-in cookies have shorter lifetimes. Signing out clears the website session. The Windows app keeps its own encrypted sign-in on your computer.

We use Vercel Web Analytics to count visitors and page views on public pages and stable app entry pages. It runs without an analytics opt-in popup and uses a temporary request-based hash instead of tracking cookies. Vercel describes these visitor identifiers as expiring after 24 hours. Aggregate statistics can include browser, device, referring site and approximate location information. We remove query strings and URL fragments from analytics page URLs, exclude authentication callbacks, API routes, private dashboard pages and paths containing account or computer identifiers, and do not send custom analytics events or task content. The hosting service also processes technical request information needed to deliver and protect the site. Your browser may store preferences such as your chosen theme. Read more in Vercel’s analytics privacy documentation.

We also count starts of Windows installer downloads from this website. These totals store only the release version, day and number of starts. They do not identify visitors or record account IDs, email addresses, IP addresses or sessions. A start means the website redirected to the installer hosted on GitHub, which handles the file transfer. It does not confirm a completed download or installation.

Our authentication, hosting, database and cloud-computer services process information needed to operate Sphere Bot. Your configured model providers and connected services process data sent through their features. These services may operate in countries outside your own. A custom provider or a team's shared credentials can change which services receive your task data.

We may disclose information when required by applicable law, to respond to valid legal requests or to investigate misuse affecting the service. We do not promise that every external provider uses the same safeguards or retention periods.

Signing out, uninstalling the desktop app or reaching the end of a trial does not automatically delete your account or cloud workspace. A computer may be paused when access ends. Account, connector and usage records can remain so we can manage access, investigate problems and prevent repeated trial abuse.

You can remove connectors in your account, revoke permissions with the connected provider and delete content through the app's available controls. For account deletion, a copy or correction of your personal information, or an objection to its use, use account support. Account support requires sign-in. We will verify your identity and explain any information that must be retained for security, legal obligations or unresolved disputes. Rights depend on the law that applies to you.

Deletion from Sphere Bot does not automatically remove copies already held by an external model or connector provider. Backups and operational records may also take longer to expire than active data. Ask us about the data involved in your request. There is no single retention period for every type of record.

We will update this page when these practices change and show the revision date above. For privacy questions or requests, use account support. Our terms of service explain the rules for using Sphere Bot.