Skip to content

Privacy

How GreenGrid handles your GitHub data.

What we store

When you sign in with GitHub, GreenGrid stores your GitHub user ID, username, display name, avatar URL and — where you have granted the scope — your primary verified email address. We also store the repositories you can access, the schedules you create, and a record of every execution GreenGrid performs.

Access tokens

Your GitHub access token is encrypted with AES-256-GCM before it is written to the database. It is decrypted only inside the server process that calls GitHub on your behalf. Tokens are never sent to the browser, never written to logs, never included in error messages, and never placed in URLs or browser storage.

What we do with GitHub access

GreenGrid reads your repository list and permissions, reads and updates the single maintenance file you configure, and creates commits through GitHub's official REST API. Commits are attributed to your authenticated GitHub account. GreenGrid does not scrape GitHub, does not use browser automation, and does not fabricate author identities.

Sessions

Sessions are opaque random tokens stored as a hash in our database and referenced by an httpOnly, SameSite=Lax cookie. Signing out deletes the session record.

Deleting your data

Disconnecting GitHub from the Settings page revokes GreenGrid's OAuth grant and deletes your account, repository records, schedules and activity history. Commits already created in your repositories are yours and remain untouched.

Contribution graph

GreenGrid does not control GitHub's contribution graph. Whether an activity appears on your profile depends entirely on GitHub's contribution rules.