The Great Discovery — Zoom App Integration Policy

1. Test Plan

To ensure consistent and reliable performance, we employ a structured, two-environment testing model:

• Development Environment: Utilizes local workstations in conjunction with ngrok to facilitate dynamic OAuth redirect testing during initial development cycles.
• Staging Environment: A secured staging server configured with registered OAuth redirect URIs enables quality assurance validation in a controlled, production-like environment.

Testing Workflow:

1. Initiate Zoom OAuth flow via our admin dashboard application.
2. Obtain and securely store access tokens for the authenticated user.
3. Use the Zoom API to create meeting instances tied to the user’s account.
4. Persist meeting metadata within our platform’s database for downstream consumption.
5. Render and launch meetings from the user-facing application interface.

Our testing regimen ensures end-to-end validation of the OAuth exchange, API communication, and user-facing experience prior to any deployment to production.

2. Minimum Scope Policy

In accordance with Zoom’s minimum privilege guidelines, our application explicitly requests only the essential scopes required for the services offered:

• meeting:write — Allows the authenticated user to create and update Zoom meetings directly through our platform.
• meeting:read — Enables retrieval of meeting information for rendering inside our applications.
• meeting:delete — Facilitates removal of Zoom meetings that originated from our system.

All scope usage is limited to meetings initiated from within our ecosystem. No additional user data or external Zoom meeting content is accessed or retained.

3. In-Client Experience and Features

Our Zoom integration is engineered to operate within our own interface without redirecting users to the Zoom web client. Key features include:

• Embedded Meeting Interface: Meetings are launched directly within our user-facing app, offering a unified workflow.
• Interactive Collaboration: Participants and hosts enjoy native Zoom functionality including chat, video conferencing, and screen sharing.
• Session Ownership: Zoom meetings are bound to the authenticated user who initiates the post creation.

4. Support Statement

Users seeking assistance with our Zoom integration may visit our support portal:

https://thegreatdiscovery.com/academy/support

We reiterate that our application accesses only Zoom data generated from within The Great Discovery platform. We do not ingest, store, or manipulate user data or meetings created externally to our application workflow.

5. Documentation and Onboarding Guide

While our Zoom integration documentation is currently being finalized, the core flow for end-users is as follows:

• Step 1: A channel creator initiates a new post within the admin dashboard.
• Step 2: “Zoom Room” is selected as the post type.
• Step 3: The user is redirected to Zoom’s OAuth consent screen to grant access.
• Step 4: Meeting details are configured and submitted.
• Step 5: The Zoom room is embedded and available within the user-facing app.

Upon full release, detailed knowledge base articles and training resources will be made available at the Documentation URL specified within our Zoom App Marketplace submission.

6. User Data Rights

As a data subject, you have the right to request access to, correction of, or deletion of your personal data stored on our platform. You may also request limitations on how your data is processed, object to specific types of processing, or request data portability where applicable.

To exercise your rights, please contact us at support@thegreatdiscovery.com. Requests will be reviewed in accordance with applicable data protection laws, and we may require verification of your identity before fulfilling any request. Response times may vary but are typically handled within 30 days.