Your account stays yours.
grr is a local command-line tool. This policy describes what the software does with credentials and requests, and what this static site does not do.
The grr project does not operate a backend, collect telemetry, or build an advertising profile. The CLI runs on your machine and uses your own Google OAuth credentials to call the Google services you choose.
What the CLI does
When you run a grr command, the binary sends the request to the relevant Google API using the access and refresh tokens issued to your Google account. grr sends only the requests needed for the command you selected. Google processes those requests under Google’s own applicable terms and privacy policies.
grr includes no analytics SDK, usage telemetry, or project-operated data collection endpoint. Your shell history, command output, and any files you create remain under your control.
Credentials and token storage
The OAuth client ID is stored in your local ~/.grr/config.toml file (or %USERPROFILE%\.grr\config.toml on Windows). A client secret is optional and, when configured, is used at the token endpoint.
OAuth tokens are stored first in the operating system keyring: Windows Credential Manager, macOS Keychain, or the Linux Secret Service through D-Bus. On headless systems where a keyring is unavailable, grr falls back to <cache dir>/grr/token.json. A token found in that fallback file is automatically imported into the keyring when possible.
Anyone with access to your user account or local files may be able to access those credentials. Protect your machine, your config file, and your Google account as you would any other credential.
This website
This site is static and has no analytics cookies or tracking scripts. The stats panel is rendered with build-time values. If its optional browser refresh runs, the browser makes direct requests to crates.io and GitHub’s public API; those services receive the ordinary network information required to serve their APIs.
No project data, OAuth token, or CLI command is sent to the grr website or to the project maintainers by the website.
Sharing and retention
grr does not sell personal information, share it with data brokers, or share it with third parties on behalf of the project. Data returned by Google APIs remains in the place your command and output handling put it. You are responsible for choosing where to save files, logs, and command output.
Contact
For privacy questions or to report a concern, open an issue in the project tracker: github.com/debanjanbasu/grr-cli/issues ↗. Please do not include OAuth tokens, client secrets, or other private credentials in an issue.