Effective date: 2026-11-08
This privacy policy describes how colab-controller ("the application") handles information when the account owner authorizes it to use Google Colab.
The application requests the following Google OAuth scopes:
openid — identify the signed-in Google account.https://www.googleapis.com/auth/userinfo.email — read the account email address.https://www.googleapis.com/auth/cloud-platform — required by the Google Cloud SDK's Application Default Credentials login flow.https://www.googleapis.com/auth/colaboratory — allocate, inspect, and release Colab runtimes.The application does not request access to Google Drive, Gmail, Contacts, Calendar, or other Google account data.
OAuth credentials (client ID, client secret, and refresh token) are stored only on the account owner's self-hosted system or in the owner's private secret store, with restricted file permissions. They are not published to this website and are not sent to third parties.
Operational metadata is retained only as long as needed for recovery, auditing, and the owner's configured retention period. Runtime proxy tokens are short-lived and are not stored in the controller database.
The application does not sell, rent, or share personal information with third parties. Data is sent to Google only as required to use the Google APIs described above.
Access is limited to the account owner. Credentials are protected with file permissions and secret-store controls. The application does not log OAuth tokens or client secrets.
You can revoke the application's access at any time from your Google Account's third-party access settings: https://myaccount.google.com/permissions. Revoking access invalidates the refresh token. You can also delete the locally stored credentials and operational data.
For privacy questions or deletion requests, contact ryokuryukaiax@gmail.com.