Last updated: August 3, 2026
Internode (“we”, “our”, “us”) provides an AI‑assisted workspace that helps individuals and teams organize work artifacts, meetings, and decisions. This Privacy Policy explains what data we access, how it is used, and the controls users have - specifically in relation to Google OAuth permissions and transcription features.
Overview of Data Access
Internode only accesses data explicitly authorized through ordinary user OAuth permissions or, where applicable, Google Workspace domain-wide delegation. Access is limited to the minimum scopes required to provide clearly defined features. We do not sell user data, use it for advertising, or access data without user initiation.
Ordinary OAuth integrations are optional and can be revoked at any time from the user’s Google Account settings. Domain-wide delegation is authorized and revoked by a Google Workspace administrator through the Google Admin console.
Sharing, Transfer, and Disclosure of Data
We do not sell Google user data. We may share, transfer, or disclose Google user data only in the following circumstances:
With service providers (processors): We use trusted vendors to operate our service (e.g., cloud hosting, databases, logging/monitoring, customer support tools). These vendors process data only on our instructions and are contractually required to protect it.
With other users at your direction: If you use Internode in a shared workspace, information you choose to share (such as summaries, extracted action items, or linked artifacts) may be visible to workspace members you invite.
For legal reasons: We may disclose information if required to comply with applicable law, lawful requests, or to protect the rights, safety, and security of Internode and our users.
Business transfers: If Internode is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred as part of that transaction, subject to this policy.
With your explicit consent: We may share data when you explicitly request or authorize us to do so.
Google OAuth Permissions
When a user connects a Google account, Internode requests only the OAuth scopes necessary for the specific features the user enables.
Google Workspace Domain-Wide Delegation
A Google Workspace administrator may authorize Internode’s service account for specific scopes through Google Admin domain-wide delegation. Internode’s UI accesses Google data only by impersonating the logged-in user’s email address, not other users’ mailboxes or data.
Users can disconnect the integration in Internode. Google Workspace administrators can revoke domain-wide delegation in the Google Admin console.
Basic Identity Scopes
Email address (userinfo.email)
Used solely to identify the authenticated user and associate data with the correct Internode account.Basic profile information (userinfo.profile)
Used to display the user’s name and avatar within the application UI.These scopes are required for authentication and account management only.
Google Gmail Permissions
Gmail access is requested only when a user connects Gmail and enables email-based features.
Gmail read-only (gmail.readonly)
Used when the user connects Gmail so Internode can show their mailbox inside the product and import a specific email thread the user selects into their workspace. Internode does not bulk-scan or continuously sync the mailbox in the background.
Gmail compose (gmail.compose)
Used only to create and update a follow-up draft in the user’s own Gmail account, and to send that draft only after the user explicitly confirms that specific message. Internode does not send email automatically, on a schedule, or in bulk. Internode does not use this access to change labels, trash, read/unread state, or other mailbox settings.
Google Contacts Permissions
Contacts access is requested only when a user connects Google Contacts.
Contacts (contacts.readonly) and Other contacts (contacts.other.readonly)
Used to read names and email addresses from the signed-in user’s saved Contacts and Other contacts so Internode can match people already present in the user’s workspace. This access is read-only. Internode does not create, edit, or delete contacts.
Google Drive Permissions
Internode may request the following Google Drive scopes depending on the features a user enables.
Drive file access (drive.file)
Used for files created or managed through Internode’s integration, including files associated with transcript destinations.
Drive read-only access (drive.readonly)
Used to access documents a user connects for knowledge, wiki, and other explicitly enabled Internode features. When enabled, Internode uses this access so the signed-in user can browse and search their own Drive by file name and import a file they select. Internode does not write, rename, move, share, or delete Drive files with this permission. Internode does not access unrelated Drive documents.
Google Calendar Permissions
Calendar access is feature‑gated and requested only when a user enables calendar‑based workflows.
View calendar events (calendar.readonly)
Used to display upcoming meetings so the user can:
Select meetings for summaries or automation
Associate transcripts and notes with calendar events
Generate overviews and reports related to meetings
Create or update calendar events (calendar.events)
Used only when the user explicitly takes an action such as:
Adding a generated report or link back into a calendar event
Creating a follow‑up event derived from an existing meeting
Internode does not modify calendar data automatically or without direct user interaction.
Google Meet & Transcription Permissions
How Transcripts Are Used
When a user grants Google Meet transcription access, Internode can retrieve and display meeting transcript content associated with the user’s meetings (only for meetings where transcription was enabled). Transcripts are processed to:
Generate summaries and overviews
Extract action items or tickets
Enable automation workflows defined by the user
Internode does not:
Modify original transcript resources
Access Google Drive files or documents beyond those a user explicitly connects for enabled features
Continuously scan user content
Perform general-purpose document indexing unrelated to user-requested meeting workflows
Transcript access is limited to the minimum necessary to perform user‑requested actions. Transcript content is accessed only in response to explicit user actions (such as viewing, exporting, searching, or importing transcripts) and is not accessed in the background without user initiation.
Data Processing & Storage
Data retrieved via Google APIs is processed only to deliver user‑initiated features
Stored data is encrypted at rest and in transit
Transcripts and derived artifacts remain private to the user or their explicitly shared workspace
Internode retains data only as long as needed to provide the service or until the user deletes it.
User Control & Revocation
Users maintain full control over their data:
OAuth permissions can be revoked at any time from Google Account security settings; Google Workspace administrators can revoke domain-wide delegation in the Google Admin console
Connected integrations can be disabled within Internode
Users may request deletion of stored data at any time
Revoking ordinary OAuth access or domain-wide delegation immediately stops further data retrieval.
Limited Use Compliance
Internode’s use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data, use Google user data for advertising, or use Google user data to develop, improve, or train generalized AI or machine-learning models. Human access to Google user data is limited to the user’s affirmative consent to view specific content; security purposes such as investigating abuse or bugs; compliance with applicable law; or aggregated and anonymized data used for internal operations.
When a user uses a feature that generates text — for example, rewriting a follow-up in their writing style or summarizing content they asked Internode to process — Internode may send the text needed for that request to our AI service providers solely to produce the result and return it to the user. This happens only when the user takes that action.
Account Deletion
Users may permanently delete their account at any time through the app. To do so, navigate to Settings → Advanced Settings and select the account deletion option. This applies to both the mobile and web applications. Disconnecting a Google permission in Internode removes Internode’s stored authorization for that permission. Deleting an Internode account removes Google authorizations and records derived from that Google data; routine encrypted backups expire according to our backup schedule rather than being erased instantly.
Sign in with Apple & Data Privacy
Users who sign in with Apple may opt to use Apple's private email relay service, which obscures their real email address and limits personal identification. However, if a user chooses to connect a data source - such as email, Slack, or calendar - their authentic credentials and email address are required to facilitate data extraction and correctly attribute that data to the relevant assignee. At this point, a link between the user's identity and their connected data is established.
Contact
This policy is designed to reflect exactly how permissions are used in practice and is updated as new features are added. If you have any questions about this Privacy Policy, please contact us at: Internode Inc.
Gust Delaware, Inc., 16192 Coastal Highway, Lewes, Delaware 19958
Email: [email protected] or [email protected]