Effective August 30, 2026

gswitch Privacy Policy

gswitch is a local command-line utility created by Simon Corcos. It helps users switch Google Cloud configurations, Application Default Credentials, and optional Google Workspace CLI credentials on their own computers.

Information gswitch accesses

gswitch can start Google OAuth authorization flows at the user's request. Depending on the command and flags a user chooses, the app may request access to Google account identity information, Google Cloud Platform resources, Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, or other custom OAuth scopes supplied by the user.

gswitch only requests these permissions so local developer tools can authenticate to Google services selected by the user. Users decide which account to connect and which optional helper flags or custom scopes to request.

How Google user data is used

gswitch uses Google user data solely to complete local authentication and credential switching workflows requested by the user. The utility does not sell Google user data, use it for advertising, use it to train AI models, or transfer it to unrelated third parties.

Storage and sharing

gswitch does not operate a hosted backend service for collecting Google user data. OAuth tokens and credential files are created by Google Cloud SDK or Google Workspace CLI tooling and stored locally on the user's computer, typically under the user's local configuration directories. gswitch may copy or rename those local credential files so users can switch between accounts.

gswitch does not intentionally transmit credential files to Simon Corcos, SuperCorks, or any hosted service operated for gswitch.

Data protection mechanisms

Authentication and Google API traffic is sent directly between the user's computer and Google over HTTPS/TLS using Google OAuth, Google Cloud SDK, Google Workspace CLI, and Google client libraries. gswitch does not proxy this traffic through a gswitch server and does not receive users' access tokens, refresh tokens, or Google data.

On macOS and Linux, gswitch creates its profile directories with owner-only permissions (mode 700) and stores copied OAuth credential files with owner read/write permissions (mode 600). The shared Application Default Credentials file is a local JSON file that can contain a Google OAuth refresh token; it is not separately encrypted by gswitch. Access is therefore limited by the user's operating-system account, file permissions, and any device encryption the user enables. Legacy Google Workspace CLI credentials remain encrypted when that CLI's encrypted credential format is in use.

gswitch does not log credential contents. It stores only the local account-profile information needed to select the requested credentials. Users should keep their operating system and Google tooling updated, enable device encryption and a screen lock, avoid sharing their local configuration directory, and revoke Google access immediately if a device or credential may be compromised.

Data retention and deletion

Credential files remain on the user's computer until the user deletes them. Users can remove local gswitch, Google Cloud SDK, or Google Workspace CLI credential files from their machine, uninstall the package, or revoke app access from their Google Account security settings.

Security

Users should protect their local computer account and local credential files. gswitch relies on Google OAuth, Google Cloud SDK, Google Workspace CLI, and local operating system protections for the underlying authentication flow and credential storage. Security issues can be reported to simoncorcos.ing@gmail.com.

Contact

Questions about this policy can be sent to simoncorcos.ing@gmail.com.