Skip to content

Privacy

How GreenGrid handles your Google, GitHub and Slack data.

What we store

When you sign in with Google, GreenGrid stores your name, email address and profile image. When you connect GitHub it stores your GitHub user ID, username and avatar; when you connect Slack it stores the workspace name and ID and your Slack user ID. We also store the automations and schedules you create and a record of every execution, including the generated standup text and the Slack message identifiers.

Access tokens

GitHub and Slack access tokens are encrypted with AES-256-GCM before they are written to the database and are decrypted only inside the server process that calls those services on your behalf. Google sign-in tokens are not stored at all. Tokens are never sent to the browser, never written to logs, never included in error messages, never placed in URLs or browser storage, and are not visible to administrators.

What we do with GitHub access

For standup automations GreenGrid reads the commits you authored in the repositories and branches you select, for the configured day only. For commit-activity schedules it reads and updates the single maintenance file you configure and creates commits through GitHub's official REST API, attributed to your account.

AI processing

To write a standup, the commit messages (and, if you enable it, changed file names and line counts) from the selected day, plus your optional quick note, are sent to NVIDIA's API and processed by the Nemotron model. Nothing else from your repositories — no source code — is sent. Calls are made from our server; your browser never contacts the AI provider.

What we do with Slack access

GreenGrid lists channels so you can choose one, reads that channel's messages for the current day to find the daily thread and avoid duplicate posts, and posts your update — as the GreenGrid app, or as you if you chose “Post as me”.

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, and a disabled account loses all sessions immediately.

Deleting your data

Disconnecting GitHub or Slack in Settings revokes GreenGrid's access and deletes the stored credential while keeping your automation history. Deleting your account from Settings revokes both integrations and deletes your account, automations, schedules and history. Commits and Slack messages already created 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.