# Cursor: Privacy (legal) page changed > Cursor’s privacy policy adds “Google user data in Grok Bot,” describing access to Gmail, Google Calendar and Google Drive when users connect a Google account. It says access is limited to enabled features, including reading and labeling email, sending email on request, managing calendar events, and Canonical: https://rewindex.com/change/p17491 Last updated: 2026-11-08T08:44:49Z **Summary:** Cursor’s privacy policy adds “Google user data in Grok Bot,” describing access to Gmail, Google Calendar and Google Drive when users connect a Google account. It says access is limited to enabled features, including reading and labeling email, sending email on request, managing calendar events, and finding, reading, creating or editing requested files. _(machine-written, sol)_ - Kind: Privacy policy · Label: Changed (not classified) (rule) - Changed: 2026-11-08 08:44 UTC · Detected: 2026-11-08 08:44 UTC - [Source: https://cursor.com/privacy](https://cursor.com/privacy) - [Company: Cursor](https://rewindex.com/company/cursor.md) - Versions: before page\_version:3632 → after page\_version:17491 - Change 2 of 2 for this page ## What changed **1. Changed** ```diff …5. Security 6. Your rights and choices 7. - Privacy policy changes 8. + Google user data in Grok Bot 8. Privacy policy changes 9. Contacting us Note: For information about how we… ``` **2. Added** ```diff …an adequate level of data protection. # 7. + Google user data in Grok Bot When you connect a Google account to Grok Bot, it accesses only the Google data needed for the features you turn on: Gmail: to read, search and label your email, and to draft or send email when you ask. Google Calendar: to read your calendars and availability, and to create or update events when you ask. Google Drive: to find, read, create and edit the files you ask Grok Bot to work with. Google Docs, Sheets and Slides: to read and edit the documents, spreadsheets and presentations you ask Grok Bot to work with. Your Google account email: to identify the connected account. How we use it. Grok Bot uses Google user data only to provide the features you request. We don't use it for advertising and we don't sell it. We share it only as needed to provide those features, for security, or to comply with the law. AI training. For users who opt to connect to Google Apps via Google OAuth, we shall not use any Google Apps content for any of our internal AI or other training purposes (such as training our machine learning models), including developing new products or services based on such content. People. Our staff don't read your Google data unless you ask us to … Privacy policy changes We may update this Privacy… ``` **3. Changed** ```diff …will constitute your acceptance of such change. # - 8. + 9. Contacting us We encourage you to contact us… ``` **4. Changed** ```diff …5. Security 6. Your rights and choices 7. - Privacy policy changes 8. + Google user data in Grok Bot 8. Privacy policy changes 9. Contacting us Note: For information about how we… ``` **5. Added** ```diff …an adequate level of data protection. # 7. + Google user data in Grok Bot When you connect a Google account to Grok Bot, it accesses only the Google data needed for the features you turn on: Gmail: to read, search and label your email, and to draft or send email when you ask. Google Calendar: to read your calendars and availability, and to create or update events when you ask. Google Drive: to find, read, create and edit the files you ask Grok Bot to work with. Google Docs, Sheets and Slides: to read and edit the documents, spreadsheets and presentations you ask Grok Bot to work with. Your Google account email: to identify the connected account. How we use it. Grok Bot uses Google user data only to provide the features you request. We don't use it for advertising and we don't sell it. We share it only as needed to provide those features, for security, or to comply with the law. AI training. For users who opt to connect to Google Apps via Google OAuth, we shall not use any Google Apps content for any of our internal AI or other training purposes (such as training our machine learning models), including developing new products or services based on such content. People. Our staff don't read your Google data unless you ask us to … Privacy policy changes We may update this Privacy… ``` **6. Changed** ```diff …will constitute your acceptance of such change. # - 8. + 9. Contacting us We encourage you to contact us… ``` ## History of this page | When (UTC) | Change | Label | | --- | --- | --- | | 2026-10-20 12:06 UTC | [Privacy (legal) page changed](https://rewindex.com/change/p3632.md) | Changed (not classified) | | 2026-11-08 08:44 UTC | Privacy (legal) page changed (this change) | Changed (not classified) | Previous: [change](https://rewindex.com/change/p3632.md) · All Cursor changes: [timeline](https://rewindex.com/company/cursor/changes.md) _Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._ ## Cite this Privacy (legal) page changed on Cursor’s Privacy (legal) page, changed 2026-11-08 08:44 UTC (change 2 of 2). - Canonical URL: https://rewindex.com/change/p17491 - Citation: Cursor, “Privacy (legal) page changed” (2026-11-08 08:44 UTC). Archived by Rewindex: https://rewindex.com/change/p17491 (CC BY 4.0). - Markdown link: `[Cursor: Privacy (legal) page changed (2026-11-08)](https://rewindex.com/change/p17491)` --- Canonical: https://rewindex.com/change/p17491 · Markdown: https://rewindex.com/change/p17491.md · JSON: https://rewindex.com/api/v1/changes/p17491 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-11T04:57:55.610Z