How Connex handles account and Google authorization data.
Last updated: 9 October 2026
Information Connex uses
Connex uses account information needed to authenticate members, enforce tenant and role access, operate workflows, and provide requested integrations. When a member chooses Google sign-in, Connex receives the Google identity information authorized by the sign-in flow, such as the account identifier, email address, and basic profile information.
Google Workspace authorization
If a member connects a Google Workspace account, Connex requests only the scopes presented on the Google consent screen for the connected features. Those permissions may cover Drive, Calendar, Sheets, Slides, Tasks, and Gmail sending. Member Workspace authorization is stored and used for that member; it is not a global fallback credential for other members.
Members can disconnect the integration in Connex and can also revoke Connex access from their Google Account permissions.
Platform operational email
Connex uses a separate platform Gmail authorization limited to https://www.googleapis.com/auth/gmail.send to send operational messages such as account, invitation, password-reset, and system notification email. This dedicated authorization does not grant Connex permission to read the platform mailbox.
Storage and protection
Connex stores application records needed to operate the service. Google refresh credentials used by member integrations are protected before storage, and short-lived access tokens are treated as transient authorization data. Access to Connex data is constrained by tenant, member, role, and capability checks.
Sharing and retention
Connex uses authorized data to provide the requested service and integrations. Data may be processed by infrastructure or service providers needed to operate Connex, or disclosed when required by law. Authorization data is retained only while it is needed for the connected feature, account operation, security, or legal obligations, and may be revoked or disconnected by the user.
Contact
Questions about this policy or Google authorization can be sent to [email protected].