Information we collect
How we use information
Google user data
If you connect a Google account to export reports into Google Sheets, Books AI requests only the access that feature needs: See, edit, create, and delete your spreadsheets (spreadsheets) to write a report into the sheet you choose; See, edit, create, and delete only the files you use with this app (drive.file) to create a new spreadsheet when you ask for one; and your email address and Google account identifier (openid, email) so we can show you which account is connected. The Books AI add-on inside Google Sheets uses only spreadsheets.currentonly and script.container.ui, which reach the spreadsheet you have open and nothing else.
We use that access to write the report you asked for into the tab you named, and to read that destination tab beforehand only so we can warn you when it already contains data that a refresh would replace. We do not scan, index, or otherwise read the rest of your Drive or your spreadsheets.
Of the credentials Google issues, we store only the refresh token, encrypted at rest with an envelope key held in AWS KMS. Access tokens are requested when a refresh runs and are never written to storage or logs, and we do not keep copies of the spreadsheet contents we write. Google user data is never sold, never used to train AI models, and never shared with third parties except the infrastructure providers needed to run the export.
You can end this access at any time — disconnect Google in Books AI under Reports → Export to Google Sheets, or remove Books AI at myaccount.google.com/permissions. Revoking it stops scheduled refreshes; sheets already written stay in your Drive, under your control.
Books AI'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.