Privacy policy

This policy describes Google user data used by the Colab&Drive research workflow.

Data accessed and why

After Google OAuth authorization, the workflow uses the Google Drive API to identify files in the configured research folders, read their contents and metadata, and write generated files to the configured output folder. Google presents a full Drive permission because the authorized client can read and manage Drive files. The public website does not request that permission or receive Drive file contents.

Processing, storage, and sharing

Source files are kept in Google Drive. Data used for a job can be copied to temporary storage in its Google Colab runtime for processing. Output files saved by the job remain in Drive until deleted there. Drive files are transferred to Google Colab to perform the requested job; this public site is outside that data path. The desktop OAuth setup keeps authorization credentials for subsequent API calls.

Use of Google user data is limited to running the research workflow and saving its results. Google user data is not sold or used for advertising. Any sharing you set on a Drive folder or file is managed by Google Drive.

Retention, deletion, and revocation

To remove a runtime copy, delete it in the notebook or terminate the runtime. To remove saved outputs, delete them from your Drive. To stop future access, remove Colab&Drive from your Google Account connections. Revoking access does not delete existing files or copies. Remove locally stored OAuth credentials if you no longer use the desktop client.

Google API Limited Use

Colab&Drive’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Contact

For questions about Google data use or deletion, use the support address shown on the Colab&Drive Google authorization screen.