Legal Document
Privacy Policy
How Prizm collects, uses, and protects your personal information.
01
Introduction
Prizm. ("Prizm", "we", "our", or "us") operates the getprizm.ai website and the Prizmconnector platform (collectively, the "Service"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service. Please read this policy carefully. If you disagree with its terms, please discontinue use of the Service.
02
Information We Collect
We collect information in the following ways:
- Account Information: When you register, we collect your name, email address, company name, and password.
- Usage Data: We automatically collect information about how you interact with the Service, including API call logs, feature usage, and performance metrics.
- Third-Party OAuth Credentials: When you connect a connector (e.g., Slack, Salesforce), we receive and securely store OAuth tokens on your behalf. We never store plaintext passwords for third-party services.
- Payment Information: If you subscribe to a paid plan, payment details are processed by our payment provider (Stripe). Prizm does not store full card numbers or CVV codes.
- Communications: If you contact us via email or support channels, we keep a record of that correspondence.
- Cookies and Tracking: We use cookies and similar technologies to maintain sessions, remember preferences, and analyse usage. See Section 7 for more detail.
03
How We Use Your Information
We use the information we collect to:
- Provide, operate, and improve the Service.
- Authenticate your identity and maintain the security of your account.
- Execute API requests on your behalf to connected third-party services using your stored OAuth tokens.
- Send transactional emails (billing receipts, password resets, security alerts).
- Send product updates and marketing communications where you have opted in — you may unsubscribe at any time.
- Comply with applicable laws, regulations, and legal processes.
- Detect, investigate, and prevent fraudulent or unauthorised activity.
04
How We Share Your Information
Prizm does not sell your personal data. We may share information in limited circumstances:
- Service Providers: We share data with trusted vendors who help us operate the Service (cloud hosting, analytics, email delivery, payment processing). These providers are contractually bound to use data only as directed by Prizm.
- Third-Party Connectors: Data is transmitted to third-party services only when you explicitly initiate an API action through our platform.
- Business Transfers: If Prizm is acquired or merges with another company, your information may be transferred as part of that transaction. We will notify you before this occurs.
- Legal Requirements: We may disclose information if required by law or if we believe disclosure is necessary to protect our rights or the safety of others.
05
Data Security
We implement industry-standard technical and organisational measures to protect your data, including:
- TLS 1.2+ encryption for data in transit.
- KMS encryption for sensitive credentials at rest.
- Role-based access controls.
- Security monitoring and periodic assessments.
Despite our safeguards, no method of transmission over the Internet is 100% secure. We encourage you to use a strong password and enable two-factor authentication.
06
Data Retention
We retain your personal data for as long as your account is active or as needed to provide the Service. If you delete your account, we will delete or anonymise your personal data within 30 days, except where we are required to retain it for legal or compliance purposes. OAuth tokens for connected connectors are revoked and deleted immediately upon account deletion.
The following specific retention periods apply:
- Execution logs — retained for 90 days, then automatically purged.
- Webhook delivery logs — retained for 90 days, then automatically purged.
- User activity logs — retained for 1 year, then automatically purged.
- Admin audit logs — retained for 7 years for legal and compliance purposes (SOC 2 / GDPR Article 5(2)).
- Data export files — download links expire after 7 days and the underlying files are deleted automatically.
- Financial records — retained for 7 years as required by applicable tax law.
07
Cookies and Tracking Technologies
We use the following categories of cookies:
- Essential Cookies: Required for authentication, security, and core functionality. Cannot be disabled.
- Analytics Cookies: Help us understand how users interact with the Service (e.g., PostHog, Amplitude). You may opt out via your browser settings or our cookie consent manager.
- Marketing Cookies: Used to deliver relevant advertisements. Only placed with your consent.
You can manage cookie preferences in your browser settings. Disabling non-essential cookies will not affect core functionality.
08
Your Rights
Depending on your location, you may have the following rights regarding your personal data:
- Access: Request a copy of the personal data we hold about you.
- Correction: Request correction of inaccurate or incomplete data.
- Deletion:Request deletion of your personal data ("right to be forgotten").
- Portability: Request your data in a machine-readable format.
- Objection: Object to processing based on legitimate interests or for direct marketing purposes.
- Withdraw Consent: Where processing is based on consent, withdraw it at any time without affecting prior processing.
To exercise these rights, email us at privacy@getprizm.ai. We will respond within 30 days. We may ask you to verify your identity before processing your request.
09
International Data Transfers
Prizm is based in the United States. If you are accessing the Service from outside the US, your information may be transferred to and processed in the US or other countries. Where required, we rely on Standard Contractual Clauses (SCCs) approved by the European Commission to ensure adequate data protection for transfers from the EEA, UK, and Switzerland.
10
Children's Privacy
The Service is not directed to individuals under the age of 16. We do not knowingly collect personal data from children. If you become aware that a child has provided us with personal data, please contact us at privacy@getprizm.ai and we will take steps to delete that information.
11
Google API Integrations, OAuth Scopes & Use of Google User Data
Prizm is an AI connectivity platform that enables users and organizations to securely connect applications, data sources, and services to AI agents, automation workflows, and MCP-compatible clients.
Users may connect Google services such as Gmail, Google Drive, Google Docs, Google Sheets, Google Slides, Google Calendar, Google Chat, Google Forms, Google Contacts, Google Tasks, Google Meet, Google Photos, Google Classroom, Google Analytics, Google Ads, Google Search Console, YouTube, Google Admin SDK, BigQuery, and other supported Google services.
Google integrations are optional. Users explicitly choose which Google services to connect and which permissions to grant. Prizm requests Google OAuth scopes only when a user connects and authorizes a corresponding Google service.
Prizm does not request access to Gmail, Google Drive, Google Calendar, Google Docs, Google Sheets, Google Chat, Google Forms, Google Classroom, Google Analytics, Google Ads, YouTube, Google Photos, Google Meet, Search Console, BigQuery, or Google Admin data during account login.
During authentication, Prizm may request only basic profile and account identification information necessary to authenticate users and manage accounts.
How Prizm Uses Google User Data
Google user data is accessed, processed, and transferred only to provide functionality explicitly requested and authorized by the user.
Examples include:
- Reading, drafting, sending, organizing, and managing Gmail messages
- Creating, updating, and managing Google Calendar events
- Checking calendar availability and scheduling meetings
- Creating, editing, organizing, and managing Google Drive files
- Creating and updating Google Docs, Sheets, Slides, and Forms
- Reading and updating Google Contacts
- Managing Google Tasks
- Creating and managing Google Meet conferences
- Sending and reading Google Chat messages
- Managing Google Classroom resources
- Reading Google Analytics reports
- Managing Google Ads data
- Reading Search Console data
- Managing YouTube content
- Performing Google Workspace administration tasks
- Querying and analyzing BigQuery datasets
- Executing user-authorized AI workflows and MCP tool operations
Google user data is never accessed unless explicitly authorized by the user through the applicable Google OAuth consent flow.
Only the scopes required for the specific integration you enable will be requested. Prizm applies the principle of least privilege — we request only the minimum permissions necessary for the functionality you have chosen to use.
Google Account
| Scope | What it allows & how Prizm uses it |
|---|---|
| userinfo.email | Access to your primary Google Account email address. Used to identify your account when connecting Google services and to associate integrations with your user identity. |
| userinfo.profile | Access to your basic Google Account profile information that you have made publicly available, such as your name and profile photo. Used to display your identity within Prizm when managing connected integrations. |
| user.emails.read | Access to read all email addresses associated with your Google Account. Used alongside Google Contacts to identify all addresses linked to your account, enabling accurate contact lookups, email routing, and identity matching across connected workflows. |
Gmail
| Scope | What it allows & how Prizm uses it |
|---|---|
| gmail.readonly | Read-only access to all email messages, threads, and labels. Used to search your inbox, retrieve email content for summaries or analysis, and read thread history in user-initiated workflows. |
| gmail.metadata | Access to email headers (sender, recipient, subject, date) without reading email body content. Used to list emails, filter by sender or date, and display inbox overviews without accessing private message body text. |
| gmail.compose | Ability to create and manage email drafts. Used to draft emails on your behalf based on your instructions, without sending them until you explicitly approve. |
| gmail.modify | Ability to read, modify, and delete emails and labels, but not permanently delete threads. Used to archive messages, apply or remove labels, mark messages as read/unread, and organize inbox folders per your instructions. |
| gmail.send | Ability to send email messages on your behalf. Used only when you explicitly instruct Prizm to send an email or reply to a thread as part of a user-authorized automation workflow. |
| gmail.labels | Access to create, read, update, and delete Gmail labels. Used to create custom labels for organizing emails and apply label-based routing in automation workflows. |
| gmail.addons.current.action.compose | Access to the message being composed in a Gmail add-on context. Used to insert content or suggestions into a message you are actively writing. |
| gmail.addons.current.message.action | Access to the full content of the currently selected message in a Gmail add-on context. Used to take actions on an open email such as replying, forwarding, or extracting data. |
| gmail.addons.current.message.metadata | Access to the headers (sender, subject, date) of the currently selected message in a Gmail add-on context, without reading the body. Used to display contextual information about an email without accessing its content. |
| gmail.addons.current.message.readonly | Read-only access to the full content of the currently selected message in a Gmail add-on context. Used to analyze or summarize the open email without making any changes. |
| mail.google.com | Full access to your Gmail account including reading, composing, sending, and permanently deleting messages. Requested only for advanced workflows that require complete mailbox management capabilities as explicitly authorized by you. |
Google Drive
| Scope | What it allows & how Prizm uses it |
|---|---|
| drive.file | Access only to files that Prizm has created or that you explicitly open or share with the app. Used to create, read, and update specific files as part of user-authorized workflows, without accessing your entire Drive. |
| drive.readonly | Read-only access to all files in your Google Drive. Used to search for files, retrieve file content, list folder structures, and display file information in user-initiated queries without modifying any data. |
| drive | Full access to all files in your Google Drive including creating, reading, updating, moving, and deleting files and folders. Requested only for advanced file management workflows explicitly authorized by you, such as bulk organization, file uploads, or folder restructuring. |
Google Docs
| Scope | What it allows & how Prizm uses it |
|---|---|
| documents | Full read and write access to your Google Docs documents. Used to create new documents, read existing document content, insert or update text, generate structured reports and meeting summaries, and modify document content as directed by your instructions. |
Google Sheets
| Scope | What it allows & how Prizm uses it |
|---|---|
| spreadsheets | Full read and write access to your Google Sheets spreadsheets. Used to create new spreadsheets, insert rows, update cell values, format sheets, and manage structured data as directed by your instructions. |
| spreadsheets.readonly | Read-only access to your Google Sheets spreadsheets. Used to retrieve and analyze spreadsheet data, generate reports or summaries, and display cell values in user-initiated queries without making any changes to your data. |
Google Slides
| Scope | What it allows & how Prizm uses it |
|---|---|
| presentations | Full read and write access to your Google Slides presentations. Used to create new presentations, add or update slides, insert text and images, and generate presentation content as directed by your instructions. |
| presentations.readonly | Read-only access to your Google Slides presentations. Used to read slide content, extract text, and analyze presentation structure in user-initiated queries without modifying any slides. |
Google Forms
| Scope | What it allows & how Prizm uses it |
|---|---|
| forms.body | Full read and write access to your Google Forms. Used to create new forms, add or update questions, configure settings, and manage form structure as directed by your instructions. |
| forms.body.readonly | Read-only access to your Google Forms structure and questions. Used to read form configurations, extract question lists, and display form details without making any changes to the form. |
| forms.responses.readonly | Read-only access to responses submitted to your Google Forms. Used to retrieve and analyze form submissions, generate response summaries, and display response data in user-initiated queries without modifying any submission data. |
Google Calendar
| Scope | What it allows & how Prizm uses it |
|---|---|
| calendar.app.created | Access only to calendars and events that Prizm has created. Used to manage events created by Prizm on your behalf, such as scheduling meetings or reminders, without accessing your personal or pre-existing calendar data. |
| calendar.calendarlist.readonly | Read-only access to the list of calendars in your Google account. Used to discover which calendars you have (e.g., personal, work, shared) so that events can be scheduled to the correct calendar. |
| calendar.events.public.readonly | Read-only access to public events on your calendars. Used to read publicly visible calendar events to display schedules or check for scheduling conflicts, without accessing private event details. |
| calendar.freebusy | Access to free/busy time information from your calendar without revealing event titles or details. Used to check your availability for scheduling meetings and suggest open time slots without reading the content of your calendar events. |
Google Meet
| Scope | What it allows & how Prizm uses it |
|---|---|
| meetings.space.created | Access only to Google Meet spaces (conference rooms) created by Prizm. Used to create new Meet video conference links on your behalf and retrieve join information for scheduled meetings. |
| meetings.space.settings | Access to read and update settings for Meet spaces created by Prizm. Used to configure meeting options such as access controls, co-host permissions, and recording preferences for meetings created through Prizm. |
Google Chat
| Scope | What it allows & how Prizm uses it |
|---|---|
| chat.messages | Full read and write access to messages in Google Chat spaces and direct messages. Used to send messages, update message content, and delete messages as directed by your instructions. |
| chat.messages.readonly | Read-only access to messages in Google Chat. Used to read message history, search conversations, and retrieve message content in user-initiated queries without sending or modifying any messages. |
| chat.messages.create | Ability to send new messages in Google Chat spaces and direct messages. Used to post messages, notifications, and updates to Chat conversations as explicitly instructed by you. |
| chat.messages.reactions | Ability to add and remove emoji reactions on messages in Google Chat. Used to react to messages as part of user-authorized automation workflows. |
| chat.messages.reactions.readonly | Read-only access to emoji reactions on messages. Used to read reaction data for analytics or display purposes without adding or removing reactions. |
| chat.spaces | Full read and write access to Google Chat spaces (group conversations). Used to create new spaces, update space settings, and manage space details as directed by your instructions. |
| chat.spaces.readonly | Read-only access to the list and details of Google Chat spaces you belong to. Used to discover available spaces and retrieve space information in user-initiated queries without creating or modifying any spaces. |
| chat.memberships | Full access to manage memberships in Google Chat spaces. Used to add or remove members from spaces and update membership roles as directed by your instructions. |
| chat.memberships.readonly | Read-only access to membership information in Google Chat spaces. Used to list space members and read membership details in user-initiated queries without modifying any memberships. |
| chat.users.availability | Ability to read and set availability status for users in Google Chat. Used to update your availability status and check the presence status of other users when coordinating collaboration workflows. |
| chat.users.availability.readonly | Read-only access to user availability status in Google Chat. Used to check whether users are active or away when scheduling messages or coordinating team workflows, without changing anyone's status. |
Google Contacts
| Scope | What it allows & how Prizm uses it |
|---|---|
| contacts | Full read and write access to your Google Contacts. Used to search for contacts by name or email, create new contacts, update existing contact details (such as phone numbers or addresses), and support contact-based communication workflows as directed by your instructions. |
| contacts.readonly | Read-only access to your Google Contacts. Used to look up contact information, autocomplete names and email addresses, and retrieve contact details in user-initiated queries without creating or modifying any contact records. |
Google Tasks
| Scope | What it allows & how Prizm uses it |
|---|---|
| tasks | Full read and write access to your Google Tasks. Used to create new tasks, update task titles and due dates, mark tasks as complete, organize tasks into lists, and manage task-based workflows as directed by your instructions. |
| tasks.readonly | Read-only access to your Google Tasks. Used to list and read task details, display pending tasks, and retrieve task information in user-initiated queries without creating or modifying any tasks. |
Google Photos
| Scope | What it allows & how Prizm uses it |
|---|---|
| photoslibrary.appendonly | Ability to upload new photos and videos to your Google Photos library. Used to add images to your library as part of user-authorized workflows without accessing or modifying any of your existing photos. |
| photoslibrary.edit.appcreateddata | Ability to edit metadata (such as descriptions and titles) of media items and albums created by Prizm. Used to update captions or album names for content that Prizm has previously uploaded on your behalf, without accessing your personal photos. |
| photoslibrary.readonly.appcreateddata | Read-only access to photos, videos, and albums created by Prizm. Used to retrieve and display media that Prizm has uploaded on your behalf, without accessing any of your personal or pre-existing photo library content. |
Google Classroom
| Scope | What it allows & how Prizm uses it |
|---|---|
| classroom.courses.readonly | Read-only access to the list of courses you are enrolled in or teach. Used to display your courses and retrieve course details without modifying any course data. |
| classroom.coursework.students | Access to manage coursework (assignments and quizzes) for students in your courses. Used by teachers to create, update, and delete coursework items as directed by user instructions. |
| classroom.coursework.students.readonly | Read-only access to coursework assignments visible to students. Used to retrieve assignment details, due dates, and descriptions for display in user-initiated queries. |
| classroom.coursework.me | Access to manage your own coursework submissions as a student. Used to submit assignments, update submission content, and track your own coursework progress. |
| classroom.courseworkmaterials | Access to manage course materials (non-graded resources) in your courses. Used by teachers to post, update, and organize learning materials such as documents, videos, and links. |
| classroom.courseworkmaterials.readonly | Read-only access to course materials in your courses. Used to retrieve posted resources and materials for display in user-initiated queries without modifying any content. |
| classroom.topics | Access to create, update, and delete topics within your Classroom courses. Used to organize course content under topic headings as directed by teacher instructions. |
| classroom.topics.readonly | Read-only access to topic listings in your Classroom courses. Used to list and display course topics in user-initiated queries without creating or modifying any topics. |
| classroom.rosters.readonly | Read-only access to the list of students and teachers enrolled in your courses. Used to retrieve roster information for course management workflows without modifying enrollment data. |
| classroom.announcements | Access to create, update, and delete announcements in your Classroom courses. Used by teachers to post course-wide notices, updates, and reminders as directed by user instructions. |
| classroom.announcements.readonly | Read-only access to announcements in your Classroom courses. Used to retrieve and display posted announcements in user-initiated queries without publishing or modifying any announcements. |
| classroom.course-work.readonly | Read-only access to all coursework items across your courses. Used to retrieve comprehensive assignment listings for scheduling and planning workflows without modifying any coursework. |
| classroom.student-submissions.students.readonly | Read-only access to student submission data for coursework in your courses. Used by teachers to retrieve and review student submissions for grading assistance workflows without modifying submission records. |
| classroom.student-submissions.me.readonly | Read-only access to your own assignment submission history. Used by students to check the status and grades of their own submitted work without accessing other students' data. |
| classroom.guardianlinks.students.readonly | Read-only access to guardian invitation links for students in your courses. Used by teachers in guardian communication workflows to retrieve guardian connection status without modifying any guardian links. |
| classroom.guardianlinks.me.readonly | Read-only access to your own guardian invitation links. Used by students to check their guardian connection status without modifying any guardian relationships. |
| classroom.push-notifications | Ability to receive push notifications for Classroom events such as new assignments or announcements. Used to trigger automated responses to Classroom activity in real-time notification workflows. |
Google Analytics
| Scope | What it allows & how Prizm uses it |
|---|---|
| analytics.readonly | Read-only access to your Google Analytics account data including traffic reports, audience metrics, conversion data, and website performance statistics. Used to retrieve analytics reports, generate traffic summaries, and produce business performance insights in user-initiated queries without modifying any analytics configuration or data. |
Google Ads
| Scope | What it allows & how Prizm uses it |
|---|---|
| adwords | Access to your Google Ads account data including campaigns, ad groups, keywords, budgets, and performance metrics. Used to read campaign performance data, generate advertising reports, retrieve budget and bidding information, and analyze advertising effectiveness in user-authorized workflows. |
Google Search Console
| Scope | What it allows & how Prizm uses it |
|---|---|
| webmasters | Full access to your Google Search Console properties including search performance data, index coverage, sitemap management, and URL inspection. Used to retrieve search analytics, submit sitemaps, and manage Search Console data as directed by your instructions. |
| webmasters.readonly | Read-only access to your Google Search Console properties. Used to retrieve search performance reports, click and impression data, index coverage status, and keyword ranking information for SEO analysis in user-initiated queries without modifying any Search Console settings. |
YouTube
| Scope | What it allows & how Prizm uses it |
|---|---|
| youtube.readonly | Read-only access to your YouTube account including channel information, video details, playlists, and subscriptions. Used to retrieve channel statistics, list videos, and analyze content performance in user-initiated queries without modifying any YouTube data. |
| youtube | Full access to your YouTube account including managing videos, playlists, comments, and channel settings. Used to update video metadata, manage playlists, and perform channel management actions as directed by your instructions. |
| youtube.force-ssl | Full YouTube account access requiring SSL-encrypted connections for all API calls. Used when managing sensitive channel operations that require enforced secure transport, such as handling comments and community posts. |
| youtube.upload | Ability to upload videos to your YouTube channel. Used exclusively when you instruct Prizm to publish or upload video content to your channel as part of a content publishing workflow. |
| youtubepartner | Access to YouTube Partner Program features including content ID, asset management, and monetization data. Used to retrieve monetization status, manage content claims, and access partner-level channel data in user-authorized workflows. |
| youtubepartner-channel-audit | Read-only access to channel audit information for YouTube Partner Program compliance. Used to retrieve channel policy status and compliance data required for partner program eligibility verification. |
| youtube.channel-memberships.creator | Access to your YouTube channel membership data including member lists and membership levels. Used to retrieve membership information and manage member interactions as part of creator community workflows. |
| youtube.third-party-link.creator | Ability to manage third-party links associated with your YouTube channel, such as merchandise or external website links. Used to create or update channel link associations in user-authorized creator workflows. |
Google Admin SDK
| Scope | What it allows & how Prizm uses it |
|---|---|
| admin.directory.user | Full access to manage user accounts in your Google Workspace directory. Used by Workspace administrators to create, update, suspend, and delete user accounts as directed by admin instructions. |
| admin.directory.user.readonly | Read-only access to user account information in your Google Workspace directory. Used to list users, retrieve user profiles, and search the directory in admin queries without modifying any user accounts. |
| admin.directory.user.alias | Access to manage email aliases for user accounts in your Workspace. Used to add or remove email aliases as part of user account management workflows. |
| admin.directory.user.alias.readonly | Read-only access to email aliases for user accounts in your Workspace. Used to list and retrieve alias configurations without creating or deleting any aliases. |
| admin.directory.domain | Access to manage domains registered in your Google Workspace account. Used by administrators to add, verify, or remove domains from the Workspace organization as directed by admin instructions. |
| admin.directory.domain.readonly | Read-only access to domain information in your Workspace account. Used to list registered domains and retrieve domain verification status in admin queries without modifying domain settings. |
| admin.directory.group | Full access to manage Google Groups in your Workspace including creating, updating, and deleting groups and their settings. Used by administrators to manage mailing lists and security groups as directed by admin instructions. |
| admin.directory.group.readonly | Read-only access to Google Groups in your Workspace. Used to list groups, retrieve group details, and search the groups directory in admin queries without creating or modifying any groups. |
| admin.directory.group.member | Access to manage membership in Google Groups within your Workspace. Used to add or remove members from groups as part of user provisioning and access management workflows. |
| admin.directory.group.member.readonly | Read-only access to membership lists for Google Groups in your Workspace. Used to retrieve group membership information and check whether a user belongs to a specific group without modifying any memberships. |
| admin.directory.orgunit | Access to manage organizational units (OUs) in your Google Workspace hierarchy. Used by administrators to create, update, move, and delete OUs as part of organizational structure management workflows. |
| admin.directory.orgunit.readonly | Read-only access to organizational unit information in your Workspace hierarchy. Used to list OUs, retrieve OU details, and understand the organizational structure in admin queries without modifying any OU settings. |
BigQuery
| Scope | What it allows & how Prizm uses it |
|---|---|
| bigquery | Full access to your Google BigQuery resources including datasets, tables, and query execution. Used to run SQL queries against your datasets, retrieve query results, list available tables and schemas, and generate data analysis reports as directed by your instructions. Prizm does not store raw BigQuery data beyond the scope of the immediate query execution. |
Data Storage & Retention
Prizm may process and retain execution-related information for operational functionality, auditability, debugging, security monitoring, abuse prevention, compliance, and service reliability.
Execution records may include:
- Tool name
- Connector name
- Execution status
- Request parameters
- Response outputs
- User-requested content involved in execution
Execution logs are retained for up to 90 days and are automatically deleted after the retention period expires.
Security
OAuth access tokens and refresh tokens are encrypted at rest using Key Management Service (KMS) encryption.
All communication with Google APIs occurs over encrypted TLS-secured connections.
OAuth credentials are never exposed through:
- Application logs
- Execution history
- Analytics systems
- Monitoring systems
- User-facing interfaces
Access to stored credentials is restricted to systems required to provide authorized functionality.
Limited Use Compliance
Prizm's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Prizm does not operate, own, or develop any internal artificial intelligence, large language (LLM), or machine learning models.
Google Workspace and Google API-derived user data is never:
- Sold to third-party entities or advertising brokers.
- Used for targeted advertising displays or behavioral profiling.
- Used to train any artificial intelligence, large language, or machine learning models.
- Handled by human personnel or system contractors unless explicit consent has been provided to troubleshoot an isolated error, to comply with legal/statutory investigations, or when data is thoroughly scrubbed of personal identifiers for structural safety checks.
Revoking Access
Users may revoke Google access at any time through:
- Google Account Permissions
- Prizm Integration Settings
Revoking access immediately prevents future access to Google-connected functionality.
Stored OAuth credentials associated with revoked integrations become invalid and can no longer be used for future requests.
Contact
Questions regarding Google API access, privacy, data retention, deletion requests, or security practices may be directed to: vault@getprizm.ai
12
Third-Party Links
The Service may contain links to third-party websites or services. Prizm is not responsible for the privacy practices of those third parties. We encourage you to review their privacy policies before providing any personal information.
13
Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by email or by posting a prominent notice on the Service at least 30 days before the changes take effect. Your continued use of the Service after the effective date constitutes acceptance of the updated policy.
Questions?
If you have any questions about this document, please contact us at legal@getprizm.ai or write to us at Prizm., getprizm.ai.