Data & privacy

GitDash is self-hosted: whoever runs an instance holds its data, and nothing is sent to the GitDash project. This page lists what an instance keeps, where, and for how long. The public site, gitdash.info, runs the same code.

What is stored

Data	Where	Kept
Your GitHub token (PAT or OAuth)	Encrypted, HTTP-only session cookie `gitdash_session`. Never sent to the browser's JavaScript or stored in the database.	7 days, or until you sign out
GitHub API responses	In memory, and in the `api_cache` table when organization mode has a database. Keyed per token, so nobody reads another person's cache.	Minutes to hours, per endpoint
Your GitHub id, login and avatar URL	The `users` table (organization mode), so an admin can place you in a group.	Until an admin removes you
Groups, grants and their changes	`user_groups`, `group_flags` and the `permission_audit` log.	Until deleted by an admin
Workflow-run and pull-request history	`workflow_runs`, `pr_facts` and related tables, filled by the nightly sync (which uses the operator's own service token) for Reports and alerts. Admin-made links between GitHub logins live in `identity_links`.	Until deleted by the operator
Connected AI apps and personal MCP keys (only when MCP is on)	`mcp_grants` and `mcp_used_jti` hold ids, the app's name and redirect host or the key's label, and timestamps. No tokens and no keys.	Until you revoke the app or it expires (30 days at most); revoked and expired rows are deleted after 90 days
Alert rules, deliveries and settings	Alert, email, AI and team settings tables. Webhook URLs and keys are visible to admins only.	Until changed or deleted

What leaves the instance

Requests to the GitHub API, made by the server with your own token.
AI insights, only when an admin has configured a provider: the metrics already on screen go to that provider. Run logs and code are never sent.
Email and Slack or webhook alerts, only to destinations an admin set up.
When you connect an AI app, GitDash gives that app an encrypted token for up to 30 days (14 days without use). The token contains your GitHub token, which the app cannot read. Revoking the app in Settings → Connected apps stops GitDash from accepting it. To cut GitHub access too, revoke GitDash in GitHub → Settings → Applications.
When you create a personal MCP key, GitDash shows it to you once and keeps no copy. The key contains an encrypted copy of the token you signed in to GitDash with (your personal access token or your GitHub sign-in), so whoever holds the key can use the read-only MCP tools as you for up to 30 days. Revoke it in Settings → Connected apps. If a key leaks and you signed in with a personal access token, also rotate that token on GitHub. For keys, sign in with a fine-grained, read-only personal access token.

GitDash ships no analytics, tracking pixels or third-party scripts. The hosting platform may keep its own request logs; check your host's policy.

Removing your data

Sign out to delete the session cookie, and revoke the token or OAuth App on GitHub to cut access entirely. On an organization-mode instance, ask its admin to remove your user record. For gitdash.info, open an issue at github.com/dinhdobathi1992/gitdash.

What is stored

Data	Where	Kept
Your GitHub token (PAT or OAuth)	Encrypted, HTTP-only session cookie `gitdash_session`. Never sent to the browser's JavaScript or stored in the database.	7 days, or until you sign out
GitHub API responses	In memory, and in the `api_cache` table when organization mode has a database. Keyed per token, so nobody reads another person's cache.	Minutes to hours, per endpoint
Your GitHub id, login and avatar URL	The `users` table (organization mode), so an admin can place you in a group.	Until an admin removes you
Groups, grants and their changes	`user_groups`, `group_flags` and the `permission_audit` log.	Until deleted by an admin
Workflow-run and pull-request history	`workflow_runs`, `pr_facts` and related tables, filled by the nightly sync (which uses the operator's own service token) for Reports and alerts. Admin-made links between GitHub logins live in `identity_links`.	Until deleted by the operator
Connected AI apps and personal MCP keys (only when MCP is on)	`mcp_grants` and `mcp_used_jti` hold ids, the app's name and redirect host or the key's label, and timestamps. No tokens and no keys.	Until you revoke the app or it expires (30 days at most); revoked and expired rows are deleted after 90 days
Alert rules, deliveries and settings	Alert, email, AI and team settings tables. Webhook URLs and keys are visible to admins only.	Until changed or deleted

What leaves the instance

Requests to the GitHub API, made by the server with your own token.

AI insights, only when an admin has configured a provider: the metrics already on screen go to that provider. Run logs and code are never sent.

Email and Slack or webhook alerts, only to destinations an admin set up.

When you connect an AI app, GitDash gives that app an encrypted token for up to 30 days (14 days without use). The token contains your GitHub token, which the app cannot read. Revoking the app in Settings → Connected apps stops GitDash from accepting it. To cut GitHub access too, revoke GitDash in GitHub → Settings → Applications.

When you create a personal MCP key, GitDash shows it to you once and keeps no copy. The key contains an encrypted copy of the token you signed in to GitDash with (your personal access token or your GitHub sign-in), so whoever holds the key can use the read-only MCP tools as you for up to 30 days. Revoke it in Settings → Connected apps. If a key leaks and you signed in with a personal access token, also rotate that token on GitHub. For keys, sign in with a fine-grained, read-only personal access token.

GitDash ships no analytics, tracking pixels or third-party scripts. The hosting platform may keep its own request logs; check your host's policy.