Separate connection for each service
Drive, Gmail, Calendar, and YouTube are authorized separately so one feature does not silently unlock another.
Google integrations · Reviewed July 18, 2026
Google access, explained clearly.
Google connections are optional. LumenQube asks for a permission only when you connect the matching feature, uses it to complete actions you request, and lets you disconnect at any time.
Permissions map to visible features
Read and write permissions are limited to the operations described below; LumenQube does not request delete access.
Approval before consequential actions
Sending mail, creating events or documents, RSVPing, and uploading videos require an explicit user action or approval.
Disconnect whenever you choose
Disconnecting deletes LumenQube's stored authorization for that service. Access can also be revoked in your Google Account.
You start from the relevant LumenQube feature.
Google shows the account and requested permissions.
LumenQube calls Google only for the action you request.
The encrypted server-side authorization record is deleted.
Permissions and why they are necessary
| Google service and OAuth scope | User-facing use in LumenQube | Why a narrower permission is not enough |
|---|---|---|
| Google identity openid profile | Sign in to LumenQube with Google and show which Google account is connected to an optional service. | LumenQube receives only the account identifier, name, email address, and profile image needed for sign-in and account transparency. |
| Google Drive https://www.googleapis.com/auth/drive.readonly | Search the user's Drive, read a file the user selects from results, import Google Sheets or CSV data, and refresh an explicitly connected spreadsheet. | The feature searches files the user already has across Drive. drive.file alone cannot discover or read those existing files unless each is first opened with LumenQube. |
| Google Drive https://www.googleapis.com/auth/drive.file | Create a new Google Doc only when the user approves a “create Drive document” action, and access files created or opened through LumenQube. | The read-only scope cannot create a document. drive.file is the narrow write permission and does not grant general write or delete access across Drive. |
| Gmail https://www.googleapis.com/auth/gmail.readonly | Search the user's mailbox and read a message the user asks LumenAgent to summarize or use in a task. | Metadata-only access does not provide the message body required for the user-requested reading and summarization feature. LumenQube does not request modify or delete access. |
| Gmail https://www.googleapis.com/auth/gmail.send | Send a new email or reply after LumenQube shows the action and the user approves it. | This is Google's send-only permission. It does not allow LumenQube to edit mailbox state or delete messages. |
| Google Calendar https://www.googleapis.com/auth/calendar.events | List and search events, create an event the user approves, and RSVP to an event at the user's direction. | The feature needs both event reading and event changes. LumenQube does not request access to Calendar settings or unrelated Google account data. |
| YouTube https://www.googleapis.com/auth/youtube.upload | Upload only the finished video the user chooses from LumenDesign, with the title, description, tags, audience, and visibility the user reviews. | This is Google's upload-only scope. It does not grant permission to read, edit, or delete the user's existing videos. |
How Google user data is handled
- Access and use. LumenQube accesses Google data only after the user connects that service and only to provide the visible feature described above.
- Storage. OAuth access and refresh tokens are encrypted at rest in LumenQube's server-side vault. Google file, email, and calendar responses are not routinely retained as a separate server-side dataset. Content can remain in a local LumenQube document or task history when the user chooses to use or save the result.
- AI-assisted tasks. When a user explicitly asks LumenAgent to summarize or transform connected content, the content needed for that request may be sent through LumenQube's managed backend to the AI processor identified in our Privacy Policy. It is used only to return that user-facing result, not for advertising or to train generalized AI models.
- Sharing. LumenQube does not sell Google user data, use it for targeted advertising, or disclose it to data brokers. A service provider receives data only when needed to deliver the user-requested feature, protect the service, or comply with law.
- Human access. LumenQube personnel do not read Google user data unless the user gives explicit permission for specific support, access is necessary to investigate abuse or a security incident, or access is required by law.
- Retention and deletion. The connector authorization remains until the user disconnects, revokes access at Google, or deletes the LumenQube account. Disconnecting deletes the stored connector token record. Locally saved results remain under the user's control.
Limited Use. LumenQube's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Your controls
- Connect only the Google service you want from its feature in LumenQube.
- Review Google's consent screen before granting access.
- Review consequential actions in LumenQube before they are sent to Google.
- Use Disconnect in LumenQube to delete the stored connector authorization, or revoke LumenQube from your Google Account's third-party access controls.
- Request account and associated cloud-data deletion by emailing privacy@lumenqube.com.
For the complete legal disclosure, including subprocessors, security, retention, international transfers, and privacy rights, read our Privacy Policy. For help connecting or disconnecting a service, contact support@lumenqube.com.
Connect only what helps your workflow.
Explore the broader privacy model or get help with connecting and disconnecting a Google service.