Gum reads only the Google data you ask it to read.

Who runs Gum

Gum is maintained by Rasty Turek. For privacy questions, email [email protected].

Google data Gum accesses

Gum asks for this Google OAuth scope:

https://www.googleapis.com/auth/webmasters.readonly

This scope lets Gum read Search Console data for sites you already verified in Google Search Console. Gum cannot edit your sites, change Search Console settings, transfer ownership, or publish content.

How Gum uses Google data

Gum uses Google data to run the command you invoke. For example, Gum can list your verified Search Console sites or read a Search Console report and print the result in your terminal.

Gum does not use Google user data for ads, profiling, or model training.

Gum's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

Where Gum stores data

Gum runs on your machine. Gum stores OAuth tokens in your operating system keychain so it can refresh access without asking you to sign in every time.

Gum does not operate a hosted service for your Google user data. If you pipe command output to another tool, save a file, or configure logging, that output follows the choice you made on your machine.

Sharing

Gum does not sell Google user data. Gum does not share Google user data with third parties unless you choose to send command output somewhere else.

Retention and deletion

OAuth tokens stay in your operating system keychain until you remove them. Run gum logout to remove Gum's local tokens.

You can also revoke Gum from your Google Account permissions page. After you revoke access, Gum cannot refresh tokens for that Google account.