XOS1 / Documentation

How Connectors Work

Your accounts, connected with your permission. A guide to what you allow, what the assistant can read and the controls that keep the choice yours.

Last updated

Connectors are an optional part of XOS1, XiteAI’s Windows personal assistant. They are designed to bring information from accounts you choose into your conversations. Enabling a setting and granting access to an external account are separate choices.

01Permission comes first

Open Connectors in XOS1 Settings to review its permission page. Closing the page does not grant permission. Allowing Connectors reveals the provider controls; it does not sign you into Gmail or authorise a mailbox.

You choose which provider to enable. Connecting an account requires a successful sign-in and consent through that provider. A local preference or an account label alone does not authorise access.

02Connecting an account

A Gmail connection has three permission steps:

  1. Choose Gmail.Enable Gmail and select Sign in with Google. Choose your account in the browser; no email or account-name entry is needed in XOS1 before sign-in.
  2. Choose your Google account.Sign in on Google’s page in your browser and review the requested access. XOS1 does not need your Google password.
  3. Review the connection.The account’s name, photo and email identify which account you are authorising. A cancelled or unsuccessful sign-in does not authorise a connection.

The connector permission page inside XOS1 and Google’s account-authorisation page serve different purposes. Neither is a substitute for the other.

03What Gmail access is for

Gmail access lets you read recent messages from the accounts you authorise. Read recent mail shows the latest messages from today and yesterday. Select a message to read its text in the temporary mail view.

Account identity
Google sign-in (openid) identifies the account you authorised. Your email address, name and photo (userinfo.email and userinfo.profile) identify and display it in Connectors.
Read-only mail
gmail.readonly permits reading message headers, labels and content. Message content can be needed to understand a request, deadline or change that the subject line alone does not explain.

The requested Gmail permission is read-only. It does not grant permission to send, edit or delete email, change Gmail settings, or access Google Drive or Google Calendar. Additional permissions require their own explanation and authorisation.

04Your different accounts

The account controls are designed for up to five Gmail accounts, with optional names such as Personal or Work. You can choose one main account or leave that choice unset. The main-account label does not grant additional permissions.

Account names and preferences help distinguish accounts; they do not create a Google session. Each account requires its own successful authorisation.

05Where information goes

Connector preferences and account identity are saved locally. Account credentials are stored separately, protected by Windows for your user account on this device. Credentials are excluded from Ecosystem sync and portable exports.

The mail reader fetches messages directly from Google into a temporary view. It makes no AI requests and does not save a mailbox archive. Account access and any additional AI processing are separate decisions, each requiring an appropriate explanation and permission.

Google account data will be used for the disclosed connector features. It will not be sold, used for advertising or credit decisions, or used to train general-purpose AI models. Its use and transfer must follow Google’s User Data Policy, including Limited Use, and the Workspace user data policy.

Permission to read email does not authorise unrelated uses of its contents. Review the Privacy Policy’s Google accounts section for storage, processing and deletion information.

06Pausing and disconnecting

Pausing suspends account activity while retaining the protected connection. Disconnecting removes the account’s credentials and preferences from the device and requests Google revocation. If Google cannot be reached, XOS1 tells you to review access in your Google Account connections.

Once a Google connection exists, you can also revoke its access from your Google Account connections. Revocation stops future authorised access; it does not itself erase information already processed or exported.

07Policies and questions

Read our Privacy Policy’s Google accounts section for the data disclosures, the Terms of Service for using XOS1 and the Acceptable Use Policy for prohibited uses.

For questions about account data, consent or deletion, contact [email protected].