Blaze Google integrations and data handling
This page supplements the Igness Privacy Policy with details about data access, use, AI processing, storage and deletion for Blaze’s Google integrations. It covers integrations that operate Google services, separately from signing in to Blaze with a Google account.
Google integrations are under review by Google. Availability depends on the app version and release status.
Before connecting
Review Blaze’s explanation of the data and its uses for the Google service you are connecting before continuing to Google’s authorization screen. On Google’s screen, check the account and requested permissions, then choose whether to allow access.
Blaze operates within the connected account’s Google permissions. Connecting does not grant the account access to data it could not otherwise access.
Data and permissions
Blaze uses Google APIs to carry out the work you request and return the results in your conversation. Each integration provides these functions:
| Integration | Data handled and current functions | Requested scope |
|---|---|---|
| Gmail | Send email using the recipients, CC, BCC, subject and body you specify; receive the send result. Reading or searching incoming mail is not available | gmail.send |
| Google Calendar | Read events in a specified calendar, including titles, times, descriptions, locations and attendees; create events and send invitations when specified | calendar.events |
| Google Drive | List metadata such as names, types, modification times and links for files available to this integration; create folders and upload local files | drive.file |
| Google Sheets | Read a specified spreadsheet’s title, sheet information and cell values; create spreadsheets and update or append cell values | spreadsheets |
| Google Docs | Read a specified document’s title and text; create documents and append text | documents |
| Google Slides | Read a specified presentation’s title and text from slides, shapes and tables; create presentations and edit slides | presentations |
The full scope names begin with https://www.googleapis.com/auth/, followed by the value in the table. Google’s authorization screen describes the full permission. The operations Blaze performs are limited to the functions in the table above.
Why Calendar event access is requested
Blaze reads existing events and creates new events in the calendar you specify. This includes calendars you own and shared calendars, identified by calendar ID, where the connected account has the necessary access.
- Read-only access cannot create events.
- Free/busy access does not provide event details such as titles or allow event creation.
- Owner-only access does not support the same work in shared calendars owned by someone else.
- App-created-calendar access does not cover existing calendars.
Blaze therefore requests calendar.events. Blaze retrieves and creates events. It does not create calendars or change calendar sharing settings.
AI processing and sharing
Content and operation results obtained from Google become part of the Blaze conversation used for AI responses and decisions about subsequent actions. The necessary conversation content is sent through Igness servers to the AI service in use.
Blaze uses only AI services that do not use submitted data for training.
Limited Use statement
Blaze’s use of information obtained through Google APIs, including its transfer to other apps, complies with the Limited Use requirements in the Google API Services User Data Policy. The Google Workspace API User Data and Developer Policy also applies to Google Workspace data.
Google-derived data is used only to provide the Blaze features disclosed to users. It is not used for advertising, data sales or credit assessment. Google-derived data, including raw, aggregated, anonymized and derived data, is not used or transferred to create, train or improve generalized AI or machine learning models. These restrictions also apply to transfers to AI services. Human access is limited to the circumstances permitted by Google’s policy, such as explicit consent to view specific data, security needs or legal requirements.
Data storage
- Connection credentials: Credentials needed to maintain Google connections are stored on the device using OS encryption.
- Conversation history: Google content, operation results and responses derived from them may remain in local conversation history.
- Files: Large operation results may be saved in separate local files. Files created, downloaded or exported during use may also remain separately from the conversation.
- Igness servers: Content obtained from Google is not stored on Igness servers.
Disconnecting and deleting data
- Remove the connection in Blaze: Removing the relevant Google integration from the connections list in Settings deletes that connection’s configuration and local credentials. Check each connection if you have connected multiple Google services.
- Revoke access at Google: In your Google account’s connections, select Access to your Google Account, choose Blaze, open See details, and select Remove access. This is separate from removing a Sign in with Google connection. See Google’s instructions. Removing a connection in Blaze does not itself revoke the grant at Google.
- Delete conversation history: Follow Deleting a thread for conversations containing Google data. Archiving is not deletion. Separately saved files and exports need to be checked and deleted separately.
- Review data in Google services: Removing Blaze connections or conversations does not undo sent email, created events, or uploaded, created or edited Google files. Make any necessary changes within the relevant Google service.
Requests to review, correct, delete or stop use of personal information held by Igness follow the procedures in the Privacy Policy. Contact hello@igness.ai with questions or requests.