- What information we collect
- How we use the information we collect
- Choices you can make about the way your information is collected and used
- How we protect personal information electronically and physically
- Gmail: With your authorization, we access email message metadata (sender, recipient, subject, date), email body content, and attachment information. We also use this access to create drafts and send emails on your behalf when you direct us to do so.
- Google Drive: With your authorization, we access file metadata (name, type, size, modification date) and file content. We also use this access to create files, create folders, and update existing files in your Google Drive when you direct us to do so.
-
Gmail (
gmail.compose,gmail.readonly): Email metadata (sender, recipient, subject, date, labels), email body content, and the ability to create drafts and send emails on your behalf. -
Google Drive (
drive): File and folder metadata (name, type, size, dates, sharing status), the ability to read and download file content, and the ability to create files, create folders, and update existing files on your behalf.
- To display your email messages, labels, and threads within the Airstore interface
- To create email drafts and send emails when you explicitly instruct us to do so
- To display your Google Drive files and folders within the Airstore interface
- To read and download Google Drive file content when you request it
- To create files, create folders, and update files in your Google Drive when you explicitly instruct us to do so
- OAuth credentials: We store your Google OAuth access tokens and refresh tokens in our database to maintain your authorized connection. These credentials are used solely to authenticate API requests on your behalf.
- Email and file content: We do not persistently store your Google email content or Google Drive file content on our servers. All data from Google APIs is accessed in real time and held only in memory for the duration of your active session.
- Task outputs: When you use Airstore to perform tasks that involve Google data (for example, summarizing an email or analyzing a document), the resulting task output may be stored. These outputs contain derived content, not raw copies of your Google data.
- OAuth credentials are retained only for as long as your integration connection remains active. There is no separate retention period beyond the active connection.
- Google API data (emails, files, metadata) is not persistently stored and therefore has no retention period. Data is fetched on demand and discarded after your session.
- Task outputs that may reference or derive from Google data are retained in accordance with the general data retention practices described in this Privacy Policy and your workspace settings.
- Your stored OAuth credentials (access token and refresh token) are immediately and permanently deleted from our database.
- Because we do not persistently store your Google email content or Google Drive file content, there is no cached Google data to delete.
- Task outputs that were generated using Google data will remain unless you separately request their deletion.