Privacy Policy: Qorus Google Access Projects

Updated: 2025-02-04

Accessing User Data

These projects allow access to Google resources from a Qorus Integration Engine(R) application instance. The Qorus application instance communicates directly with the Google APIs.

The Qorus Google Access projects never receive your data or the permission to access your data.

When the cloud API is used for the authorization code flow, only anonymous information about the OAuth2 server used is stored; no customer-identifiable information is logged or stored on Qore Technologies' systems.

When the local server is used for the authorization flow, all data related to access to Google resources is stored on the local Qorus application instance.

Qorus Integration Engine(R) includes functionality (APIs and no-code integration objects) that you can execute in order to read or modify your own data. This can only happen after you provide a token, which requires that you authenticate yourself as a specific Google user and authorize these actions.

Qorus Integration Engine(R) can help you get a token by guiding you through the OAuth flow in the browser. There you must consent to allow the Qorus Google Access project to access data on your behalf. The OAuth consent screen will describe the scope of what is being authorized, e.g., it will name the target API(s) and whether you are authorizing “read only” or “read and write” access.

There are two ways to use these packages without authorizing a Qorus Google Access project: bring your own service account token or configure the package to use an OAuth client of your choice.

User Data Collected By This App

No user data is collected or stored by this app. This application only enables you to access your own Google data through Google APIs using Qorus Integration Engine(R).

Sensitive Data Protection

This application does not collect or store any user data of any kind beyond the local storage of access credentials (see Storing User Data below) when accessing Google APIs on the user's behalf.

Sharing User Data

No user data is shared with Qore Technologies or any other party.

Storing User Data

These packages store credentials on the Qorus Integration Engine(R) application instance that you control to enable access to Google APIs on your behalf.

Credentials are access and refresh tokens that are stored against the Qorus connection using strong encryption using the instance-specific private encryption key for your instance generated when your instance is first installed. Qorus uses strong encryption and role-based access control to protect sensitive configuration data from unauthorized access. Credentials are always encrypted at rest and transmitted using a secure modern protocol (HTTPS) only to authorized users. Encrypted data on your instance is specific to your instance.

No Data Used to Train AI / ML Models

Google Workspace APIs are not used to develop, improve, or train generalized AI and/or ML models. No user data is collected and only the access and refresh tokens are stored using strong encryption on the local Qorus instance you control as described in the paragraph above.

How Does Qore Technologies Protect Your Data?

Qore Technologies does not collect or store any data from your Google account beyond the local storage of access credentials (see Storing User Data above). Qore Technologies cloud services are used only for the token exchange, where a secret key is used to communicate with Google servers to acquire access and refresh tokens that allow your Qorus instance to access your own Google data. These tokens are neither logged nor stored on Qore Technologies' servers. Qore Technologies uses encryption for all data transfers and purposefully does not log or store any data related to your Google account (including but not limited to any access or refresh tokens) during this operation.

Scopes

Overview of the scope requested by various Qorus Google Access projects and their rationale:

• Calendar Access (full: create, read, update, delete): https://www.googleapis.com/auth/calendar: This scope provides full access to all calendars and calendarLists associated with the user. This will allow Qorus Integration Engine(R) to create, read, update, and delete any and all information related to Google calendars and calendarLists, including calendars, events, and associated information.
• Gmail Access (full: create, read, update, delete): https://mail.google.com/: This scope provides full access to the email address and all data associated with it. This will allow Qorus Integration Engine(R) to create, read, update, and delete any and all information related to Gmail data, including emails, folders, and other information.

Policies for authors of packages or other applications

Do not use client IDs or client secrets from Qorus Google Access projects in any external package or tool. Per the Google User Data Policy, your application must accurately represent itself when authenticating to Google API services.

Qorus Google Access projects are designed to work only with Qorus Integration Engine(R) and should never be used for any other purpose or in any other context.

See also

• Acceptable Use Policy (the "AUP"), which outlines prohibited uses of our Services
• Terms of Service (the "ToS"), which describes the terms under which our Services can be used