Subprocessors

Last updated: 5 October 2026

Third parties Pure Reason Inc. (“Kylon”) engages to process customer data.

Infrastructure

AI & Voice Models

Task context can include Google email, event, file, document, or spreadsheet content when you authorize an Agent to process it. The selected model and route determine which AI services receive that context; listing a provider here does not mean it receives every task. Google user data and its derivatives are subject to the Limited Use, AI-use, and sharing restrictions in our Privacy Policy. We do not use Google Workspace API data or its derivatives to develop, improve, or train general-purpose or non-personalized AI or machine-learning models, and do not permit recipients processing that data for a Kylon task to do so. Terms and settings for Google-data processing must satisfy those restrictions; this list does not certify a provider’s retention configuration or contractual terms.

An Agent brought by a member can run locally or in a separately hosted environment and use that operator’s configured AI services. These task recipients depend on the Agent configuration and are not necessarily represented by Kylon’s own subprocessor list. Review the relevant disclosure and access grants before enabling that Agent to process Google data.

Operations

Services you connect yourself (e.g. Google, Gmail, Slack, GitHub, Notion) are authorized by you under your own account and are not Kylon subprocessors. Native Google connections use Google OAuth and direct Google APIs, separately from Composio. Connecting a Google account is also distinct from the Google Cloud hosting and Google AI processing services listed above. Likewise, third-party tools Kylon can call on your behalf through its integration proxy (e.g. Apollo and similar data services) act only when you direct them and are not Kylon subprocessors. We update this list as subprocessors change.

© 2026 Pure Reason Inc. All rights reserved.