B1Xagi Privacy Policy

Effective date: 2026-09-27

Who we are

B1Xagi is an AI workspace for conversation, research, coding, media creation and assisted tasks. The service is owned by Advance Technology Training, LLC and developed by Bolosoft Computers Limited

Privacy contact: privacy@bolosoft.tech

This policy covers b1xagi.com and the B1Xagi local application and companion where they link to this policy. Third-party websites and services have their own policies.

Information we process

Account information. If you choose Google sign-in, we receive your Google account identifier, verified email address and profile information needed to identify your account. Sign-in requests identity permissions (openid, email and profile). We do not receive your Google password. Signing in alone does not authorize access to Gmail, Drive or Calendar.

Messages and context. We process prompts, conversation context, selected file contents, instructions, tool inputs and generated responses to perform your requests. Context-editor notes and text files are held in browser memory before submission. When you submit, the applicable context is included in the request. Conversation history and saved workspace files can also be stored on your device. A local history feature does not mean that submitted requests are processed only on your device.

Voice and media. When you enable voice, microphone access and speech recognition depend on your browser and its permissions. Your browser's speech service may process audio remotely. Recognized text is used as a task or conversation input. Text for spoken replies is sent to a speech-generation service; generated audio is delivered to your device. Image and video requests send prompts and any supported references to the relevant generation service. Voice labels such as Richard SB1X and Richelle NB1X identify AI companions, not human operators.

Connected services. Optional integrations process the data and permissions shown when you connect or invoke them. The current Google integration code supports read-only Gmail, Drive metadata and Calendar events; these connections are separate from account sign-in and are not automatically enabled by it. Availability depends on deployment and authorization. If offered, we will explain the requested access before connection. Integration tokens must be protected and are used to make authorized service requests.

Assisted browser and desktop tasks. Cloud-browser tasks may process requested URLs, task instructions, page contents, screenshots and action results, including through an AI provider for planning. After pairing and native approval, the optional desktop companion can list visible application titles and approved folders, read selected text files and capture the screen. Reviewed computer control is separately enabled and off by default. An approved exact plan can edit selected files, run PowerShell commands under your Windows account, open websites and use the pointer or keyboard in a specified window. Commands may affect data beyond the selected working folder. Action results, including command output and screenshots, return to the paired browser; text results are added to a cloud conversation only when you explicitly choose to add them. File edits may create local undo copies. Separately approved camera or screen frames can be processed by the local offline model. Screen captures and command output may contain sensitive information.

Operational information. We process information needed for security, troubleshooting and service operation, such as network requests, IP addresses in infrastructure logs, errors, model usage, timing, generation-job identifiers and usage counts. Some features use local or server databases. Optional response caching can retain generated content if enabled by the operator.

Purposes and legal bases

We use information to authenticate users, perform requested AI and integration tasks, maintain sessions, enforce usage limits, provide support, detect abuse and keep the service reliable. Where applicable data-protection law requires a legal basis, these purposes may rely on providing the requested service, legitimate interests in security and operation, legal obligations, or consent for optional permissions. Where we rely on consent, you may withdraw it; this does not affect processing already lawfully performed.

Service providers and disclosure

Operating the service can require sharing request data with hosting, AI routing/model, media, speech and selected integration providers. Current deployment dependencies include Kamatera for hosting, OpenRouter and its selected model providers for AI processing, and ElevenLabs for generated speech. Google supports Google sign-in and any separately authorized Google integrations. Browser speech recognition may use a service chosen by your browser. Only the providers required for the feature and configuration in use should receive the relevant data.

We may also disclose information when legally required, to address fraud or security incidents, or as part of a lawful business transfer subject to appropriate safeguards.

Google user data commitments

B1Xagi's handling and transfer of data obtained through Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements. Google user data will be used only for the user-facing features that you request and authorize. It will not be sold, used for advertising or used to train generalized AI models. Transfers and human access will be limited to circumstances permitted by that policy, including service delivery, your affirmative consent where required, security and applicable legal obligations. Google Workspace data will not be routed to AI services unless the processing is permitted, disclosed and protected by suitable provider terms.

Storage, retention and security

Browser history and saved files remain on that device until removed through applicable app controls or browser site-data controls. In-memory context is lost when its browser session is cleared or closed. Downloads you save separately remain until you remove them.

The current web sign-in session has an eight-hour lifetime; the temporary login-state cookie lasts ten minutes. Clearing cookies or signing out removes the browser session, but does not erase every operational record. The offline cache stores application assets, not API responses or credentials. Other local workspace storage is separate from that offline cache.

Server records, support records, integration credentials, optional caches, provider-held data and backups have different retention needs. Retention depends on whether a record is still needed to deliver an active request or connection, resolve a support or security issue, meet a legal obligation, or maintain a recoverable backup. There is no single automatic deletion period for all categories. Contact support for the applicable retention and deletion options; deleting local history does not automatically delete server, backup or provider records.

We use safeguards appropriate to the service, including HTTPS, access controls and scoped approvals. No system is completely secure. Processing may occur outside your country through infrastructure and providers.

Your choices and rights

You can stop voice, revoke microphone permissions, sign out, remove local workspace data and disconnect the desktop companion. You can review or revoke Google access through your Google Account's third-party connections settings. Revoking access stops future authorized access but does not itself delete data already received.

Contact the privacy address to request access, correction, deletion or other rights available under applicable law. We may need to verify your identity and explain any lawful retention exceptions. Local device copies and separately downloaded files may require action on your device.

Children, changes and contact

B1Xagi is intended for adults aged 18 or over. If you believe a child has provided personal information, contact us.

We will update this policy when our practices change, revise its effective date and provide additional notice or seek consent where required. Questions and privacy requests may be sent to the privacy contact above.