GCS is designed to keep the data it stores to a minimum. This page explains what the service accesses, what it stores, and what it does not do.
What GCS does
Lists repositories and contents through the GitHub API.
Uploads files by creating commits in your repositories.
Splits large files into chunks when the upload flow requires it.
Creates folders with a .gitkeep placeholder.
Generates shareable public links for individual files and folders.
What we store
GCS stores minimal server-side records: an encrypted GitHub access token so your session can persist, share-link metadata, user activity, and repository-group mappings for overflow repositories. File content remains in GitHub and is fetched when needed.
What GCS does not do
It does not store your GitHub password.
It does not store your files on GCS servers.
It does not modify repositories beyond file operations you initiate.
It does not access repositories belonging to other users.
It does not sell, share, or use your data for advertising or training.
Access revocation
You can revoke GCS's access at any time from GitHub Settings → Applications. Once revoked, GCS can no longer access your repositories.
