Privacy Policy: Qorus Google Access Projects

Updated: 2025-08-29

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.

Retention and Deletion of Google User Data

Qorus stores and retains access credentials for your Google account in an encrypted form in connection objects. When connection objects containing Google access tokens are deleted, all Google user data is deleted with them. The retention and deletion of Google user data in connections along with the connection objects themselves are exclusively at the discretion of you, the user.

Use of Google User Data

Qorus stores user data (access credentials) only to provide access to your own data through Google APIs, for your own use in integration solutions you create on our platform. This data is neither sold nor shared and is always under your control.

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.

• Google Chat Access (read spaces & memberships; read/write messages; basic profile):

  • https://www.googleapis.com/auth/userinfo.profile
  • https://www.googleapis.com/auth/chat.spaces.readonly
  • https://www.googleapis.com/auth/chat.memberships.readonly
  • https://www.googleapis.com/auth/chat.messages

  These scopes allow Qorus Integration Engine(R) to integrate with Google Chat workspaces by:

  • Discovering available Chat spaces the user has access to (read-only list of spaces).
  • Reading membership information to understand who is in a space (read-only).
  • Reading and sending messages in permitted spaces to power automations, alerts, and workflow updates.
  • Accessing the user’s basic public profile (name, avatar) to attribute actions and display human-readable context in logs and UI.

• Google Tasks Access (full: create, read, update, delete): https://www.googleapis.com/auth/tasks: This scope grants full access to the user’s Google Tasks data, including tasklists and tasks. It enables Qorus Integration Engine(R) to:

  • List tasklists and tasks, including metadata such as titles, notes, due dates, priorities, statuses, and ordering.
  • Create new tasklists and tasks; update existing ones (e.g., title, notes, due/due-time, status, parent/subtask relationships, position); delete tasks or tasklists as configured.
  • Clear completed tasks from a tasklist when instructed.
  • React to task changes (e.g., new tasks created, tasks completed) to power automations, notifications, and workflows.

• YouTube Access (analytics, read-only, full, upload, secure):

  • https://www.googleapis.com/auth/yt-analytics.readonly
  • https://www.googleapis.com/auth/youtube.readonly
  • https://www.googleapis.com/auth/youtube
  • https://www.googleapis.com/auth/youtube.force-ssl
  • https://www.googleapis.com/auth/youtube.upload

  These scopes provide Qorus Integration Engine(R) with the ability to integrate deeply with YouTube for video, playlist, channel, comment, subscription, and analytics management. They enable automations to:

  • Retrieve analytics data (views, watch time, engagement) for reporting and dashboards.
  • Read user channel metadata, playlists, videos, categories, and subscriptions for configuration.
  • Create and manage playlists, update video details, reply to or create comments, and manage subscriptions.
  • Upload videos with metadata (title, description, tags, privacy, category) as explicitly defined by the user.
  • Enforce secure, SSL-only access for operations required by Google (subscriptions, comments).

• Google Contacts Access (profile, create, read, update, delete):

  • https://www.googleapis.com/auth/userinfo.profile
  • https://www.googleapis.com/auth/contacts

  These scopes provide Qorus Integration Engine(R) with the ability to integrate with Google Contacts for contact and group management. They enable automations to:

  • Validate the OAuth2 token and display which Google account is connected.
  • List, search, and fetch contact details including names, emails, phone numbers, organizations, addresses, and birthdays.
  • Create new contacts with comprehensive information, update existing ones, and delete contacts when configured.
  • Manage contact groups, including listing groups, creating new groups, and adding contacts to them.
  • Trigger workflows when a new contact is created.

• Google Drive Access (full: create, read, update, delete): https://www.googleapis.com/auth/drive: This scope grants full access to the user’s Google Drive, including files and folders. It enables Qorus Integration Engine(R) to:

  • List and search files/folders with filters, sorting, and pagination.
  • Upload, download, export Google Docs formats, and replace existing files while preserving IDs.
  • Create folders/shortcuts, copy/move/rename files, and manage locations.
  • Manage sharing and permissions (organization-wide, public, specific users).
  • Monitor events such as new files or folders for automation triggers.
  • Retrieve detailed file/folder metadata for configuration and validation.

• Google Forms Access (forms & Drive: create, read, update; responses; discovery):

  • https://www.googleapis.com/auth/forms
  • https://www.googleapis.com/auth/drive

  These scopes allow Qorus Integration Engine(R) to manage Google Forms and locate form files in Drive. They enable automations to:

  • Create new forms; update titles, descriptions, questions, quiz settings, and other form options.
  • Retrieve full form structure and metadata for configuration and validation.
  • Search for forms stored in Google Drive by name/type with filtering and pagination.
  • Read form responses in bulk or individually with filters and page tokens.
  • Trigger workflows when new responses are submitted to a form.

• Google Docs Access (via Drive; full: create, read, update, delete): https://www.googleapis.com/auth/drive: This scope grants full access to the user’s Google Drive where Google Docs live. It enables Qorus Integration Engine(R) to:

  • List and search Google Docs with filters, sorting, and pagination.
  • Create documents from text or templates; upload files and convert to Google Docs.
  • Append/insert text with formatting; retrieve document content and metadata.
  • Export Google Docs to various formats (PDF, DOCX, etc.).
  • Manage sharing and permissions; move/copy/rename files and organize folders.
  • Monitor new document creation for automation triggers.

• Google Meet Access (spaces read-only/created; recordings locations read-only):

  • https://www.googleapis.com/auth/meetings.space.created
  • https://www.googleapis.com/auth/meetings.space.readonly
  • https://www.googleapis.com/auth/drive.readonly

  These scopes allow Qorus Integration Engine(R) to work with Google Meet spaces and related artifacts. They enable automations to:

  • Discover and read Meet spaces and conferences, including details such as start/end times and space metadata.
  • Access conferences created by the connected account and list participants with attendance metrics where available.
  • Retrieve references to recordings stored in Google Drive (metadata and download/export links) for post-meeting workflows.
  • Retrieve references to generated transcripts and their storage locations for downstream processing.
  • Trigger workflows when conferences end, and when recordings or transcripts are created.

• Google Sheets Access (Sheets & Drive: create, read, update, delete):

  • https://www.googleapis.com/auth/spreadsheets
  • https://www.googleapis.com/auth/drive

  These scopes allow Qorus Integration Engine(R) to manage Google Sheets content and the underlying Drive files. They enable automations to:

  • Create spreadsheets and worksheets; search spreadsheets and tabs; copy sheets between files.
  • Read/write cell ranges; append/update rows; clear or delete rows; apply formatting.
  • Import/upload files and convert to Sheets; export data; retrieve detailed metadata.
  • Organize files and folders; move/copy/rename; create shortcuts.
  • Manage sharing/permissions for collaboration; set org/public/specific-user access.
  • Trigger workflows on new rows, new spreadsheets, and new sheets.

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