Privacy Policy
Last updated: December 2025
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 by the user via OAuth permissions. 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.
All integrations are optional and can be revoked at any time from the user’s Google Account settings.
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.
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 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
To enable users to discover, list, and retrieve transcripts for Google Meet meetings where transcription was enabled, Internode retrieves transcript information using the Google Meet API. Transcript content is accessed only when a user explicitly requests it.
Internode may request the following scopes depending on enabled features:
Access to meeting spaces created by the app (meetings.space.created)
Used to identify and access Meet sessions initiated or connected through Internode so transcripts can be associated with the correct meeting context.
Read-only access to meeting spaces (meetings.space.readonly)
Used to list and reference conference records and related transcript resources for the authenticated user’s meetings.
Drive file access (drive.file)
Used only to access limited Google Drive file metadata for files created or managed through the app’s integration (for example, metadata associated with a transcript’s destination file). Internode does not use this scope to read arbitrary user documents.
How transcript access works in practice
The transcript list experience is metadata-only (e.g., meeting identifiers/timestamps and human-readable titles where available).
Transcript content (entries, VTT, or Markdown) is retrieved only when the user requests a specific meeting transcript.
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 unrelated Google Drive files or documents
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
Connected integrations can be disabled within Internode
Users may request deletion of stored data at any time
Revoking access immediately stops further data retrieval.
Limited Use Compliance
Internode’s use of Google user data strictly adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not used for advertising, profiling, or training generalized AI models.
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]