Privacy

There is no account, no telemetry, and no server. This page says exactly what that means.

What leaves your machine

Google, by way of gcloud

Every ten minutes GCloud Dot runs gcloud auth print-access-token. That command talks to Google exactly as it does when you run it yourself, the app adds no traffic of its own and sees no credential material beyond whether the command succeeded. Nothing about that request is reported anywhere else.

GitHub, once a day, if you leave it on

The update check requests the public releases endpoint for this repository. It sends nothing but the request itself and a user agent naming the version, and GitHub sees what any web request shows: an IP address and a timestamp. Turn it off in Settings and no request is ever made.

That is the complete list

There is no analytics service, no crash reporter, no license check, and no server belonging to this project for anything to be sent to.

What is stored, and where

One JSON file, written by you and readable by you:

macOS, ~/Library/Application Support/GCloudDot/state.json
Windows, %LOCALAPPDATA%\GCloudDot\state.json
Linux, ~/.local/share/gcloud-dot/state.json

It holds the times of your recent gcloud auth login runs, the session lengths that have been observed, which warnings have already been shown for the current session, and your settings. Run gcloud-dot paths to see the exact location on your machine.

It contains no credentials. No tokens, no refresh tokens, no key material. The app never copies anything out of gcloud's credential store; it only asks gcloud whether a credential still works.

Your account address and project id are read from gcloud's own configuration each time they are displayed, and are not written into this file.

What it reads

gcloud's configuration directory, for the active configuration, account, and project.
gcloud's own command logs, to find when you last completed a login.
The application default credentials file, for its type and modification time.

All read-only. GCloud Dot never writes into gcloud's directories.

Removing it

Uninstalling leaves the state file in place, because the session lengths inside it took days of real time to observe and a reinstall should not start from nothing. To remove that too:

sh uninstall.sh --purge

Or delete the directory above by hand. Nothing survives elsewhere.

This page describes GCloud Dot 1.1.11.