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 from the diff below (Sol; type: terms change). Check the diff before relying on it.
What changed
Struck in red is what Cursor removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
Changed#1
Before: …5. Security 6. Your rights and choices 7. Privacy policy changes 8. Contacting us Note: For information about how we…
After: …5. Security 6. Your rights and choices 7. Google user data in Grok Bot 8. Privacy policy changes 9. Contacting us Note: For information about how we…
Added#2
Before: …an adequate level of data protection. # 7. nothing here Privacy policy changes We may update this Privacy…
After: …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…
Changed#3
Before: …will constitute your acceptance of such change. # 8. Contacting us We encourage you to contact us…
After: …will constitute your acceptance of such change. # 9. Contacting us We encourage you to contact us…
Changed#4
Before: …5. Security 6. Your rights and choices 7. Privacy policy changes 8. Contacting us Note: For information about how we…
After: …5. Security 6. Your rights and choices 7. Google user data in Grok Bot 8. Privacy policy changes 9. Contacting us Note: For information about how we…
Added#5
Before: …an adequate level of data protection. # 7. nothing here Privacy policy changes We may update this Privacy…
After: …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…
Changed#6
Before: …will constitute your acceptance of such change. # 8. Contacting us We encourage you to contact us…
After: …will constitute your acceptance of such change. # 9. Contacting us We encourage you to contact us…
Compared with the previous archived version (#3632 to #17491). Text is normalized before comparing: dates, counters and tokens show as ‹date›, ‹count›, ‹tok›, and noise-only edits are hidden. Rewindex shows changed passages with a few words of context, not a copy of the page. View the live page (opens in new tab).
Archive proof
Rewindex commits each page capture it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
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.