Understand the connection.

Effective October 20, 2026

Plixy Executor is a personal, self-hosted Executor deployment operated by Arman Khan. This notice describes the integration and this separate informational website. It is not a public sign-up service.

Information used

When an account is connected, the integration receives the OAuth credentials and account information needed to maintain that connection. When authorized tools run, it may retrieve service content, such as messages, calendar events, documents, issue details, or analytics, within the permissions granted by the account holder. The actual consent screen identifies the permissions requested.

Purpose and access

Connected information is used to carry out authorized queries, actions, and AI-assisted workflows. Account connections and client tool permissions are configured separately. A shared OAuth client identifies the application; it does not itself separate tenants or grant access to every connected account.

Storage and retention

Connection credentials and application state are stored on the operator’s self-hosted Executor instance. Application state, operational records, and backups may persist until removed or rotated by the operator. Content may also remain in the histories or logs of an authorized client. No fixed automatic deletion period is promised.

AI clients and other providers

If a connected tool is exposed to an authorized AI client, its results may be sent to that client and its selected model provider. Their processing and retention are governed by their own settings and policies. Connecting an account should not be treated as a guarantee that all processing remains on the self-hosted machine.

Google user data

Google account access is limited to the scopes approved during authorization and is used to provide the authorized integration features. Google user data is not sold, used for advertising, or used by this integration to develop or train generalized AI models. Any transfer to an authorized AI client must support the requested user-facing feature and comply with Google’s Limited Use requirements.

Plixy Executor’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Revoking access and deletion

You can revoke the integration in your service provider’s account settings and disconnect saved accounts in Executor. Revocation stops future authorized access but does not necessarily erase previously saved application records, client histories, or backups. Contact the operator through your existing communication channel, or through the operator website, to request removal of retained connection information.

This public website

This is a static information site. Its pages contain no OAuth secrets, connected account content, analytics scripts, sign-in form, or application data store. The hosting provider may process ordinary request information, including IP addresses and browser headers, to deliver and protect the website.

Changes and contact

This notice may be updated when the integration’s data handling changes. The effective date above identifies the current notice. For questions about a work account, also consult the relevant workspace administrator before granting access.