Skip to content

Add ellmer to Google privacy policy #798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
thisisnic wants to merge 2 commits into from
Closed

Add ellmer to Google privacy policy #798

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
57d410c
Add ellmer to Google privacy policy doc
thisisnic Sep 21, 2026
720ebed
Add pedantic Claude feedback
thisisnic Sep 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions content/google_privacy_policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ The tidyverse team maintains several packages that make it easier to work with G

* [gargle](https://gargle.r-lib.org) provides general R infrastructure for Google APIs, such as auth
* [bigrquery](https://bigrquery.r-dbi.org) wraps the [BigQuery API](https://developers.google.com/bigquery/)
* [ellmer](https://ellmer.tidyverse.org) wraps the [Gemini API](https://ai.google.dev/gemini-api/docs), among other LLM providers
* [googledrive](https://googledrive.tidyverse.org) wraps the [Drive API](https://developers.google.com/drive/)
* [gmailr](https://gmailr.r-lib.org) wraps the [Gmail API](https://developers.google.com/gmail/api/)
* [googlesheets4](https://googlesheets4.tidyverse.org) wraps the [Sheets API](https://developers.google.com/sheets/api/)
Expand Down Expand Up @@ -42,22 +43,25 @@ There are two ways to use these packages without authorizing the Tidyverse API P

Overview of the scopes requested by various Tidyverse API Packages and their rationale:

* `userinfo.email` (read only): All OAuth tokens obtained with the Tidyverse API Packages request this scope so that cached tokens can be labelled with the associated Google user, allowing you to more easily access Google APIs with more than one identity. The Tidyverse API Packages do NOT have access to and do NOT store your Google password.
* `userinfo.email` (read only): All OAuth tokens obtained through gargle request this scope so that cached tokens can be labelled with the associated Google user, allowing you to more easily access Google APIs with more than one identity. The Tidyverse API Packages do NOT have access to and do NOT store your Google password.
* BigQuery and Google Cloud Platform (read/write): The bigrquery package lets you upload, query, and modify data stored in Google BigQuery, as well as retrieve metadata about projects, datasets, tables, and jobs.
* Drive (read/write): The googledrive package allows you to manage your Drive files and therefore the default scopes include read/write access. The googledrive package makes it possible for you to get a token with more limited scope, e.g. read only.
* Gemini (`generative-language.retriever`): The ellmer package uses this scope to send your prompts to the Gemini API and receive responses, when you sign in through the browser with `chat_google_gemini()`.
* Gmail (read/write): The gmailr package allows you to fully manage your Gmail account and therefore the default scope grants that ability. The gmailr package makes it possible for you to get a token with more limited scope, e.g. read or compose only.
* Sheets (read/write): The googlesheets4 package allows you to manage your spreadsheets and therefore the default scopes include read/write access. The googlesheets4 package makes it possible for you to get a token with more limited scope, e.g. read only.

### Sharing user data

The packages only communicate with Google APIs. No user data is shared with the owners of the Tidyverse API Packages, RStudio, or any other servers.
When working with Google APIs, the packages only communicate with Google. No user data is shared with the owners of the Tidyverse API Packages, RStudio, or any other servers.

### Storing user data

These packages may store your credentials on your local machine, for later reuse by you. **Use caution when using these packages on a shared machine**.

By default, an OAuth token is cached in a local file, such as `~/.R/gargle/gargle-oauth`. See the documentation for [`gargle::gargle_options()`](https://gargle.r-lib.org/reference/gargle_options.html) and [`gargle::credentials_user_oauth2()`](https://gargle.r-lib.org/reference/credentials_user_oauth2.html) for information on how to control the location of the token cache or suppress token caching, globally or at the individual token level.

ellmer's browser-based OAuth flow does not write its token to disk; the token is held in memory for the current R session only.

# Data protection policy

We do not collect any data about you and we do not have any access to data that you retrieve by using this package. Security procedures are in place to protect the confidentiality of any that we might come across, and we use best practices, such as encryption and mandatory usage of 2FA, as a matter of course.
Expand Down
Loading