Privacy
Repository work stays in your control.
GitDash uses provider-authorized access to do the work you request, and optional analytics to improve the public site.
Last updated: 10 August 2026.
Account and repository data
GitDash uses GitHub or GitLab authorization to access only the information needed for the actions you start, such as listing, editing, archiving, or restoring repositories. Provider tokens are runtime credentials and are not sent to analytics services.
Optional analytics
With your permission, GitDash uses PostHog, hosted in the EU, for page views, selected product events, feedback surveys, and browser errors. Automatic interaction capture and console-error capture are disabled. Events do not include repository names, provider tokens, account identifiers, or form contents.
Session replay is disabled until you choose analytics. When enabled, it is limited to public marketing and blog pages, masks all text and inputs, and removes query strings from captured network requests. GitDash never records replay on repository, canvas, studio, authentication, admin, or API routes.
Your choices
You can change your analytics choice at any time. Browser privacy controls can also block analytics requests.
Questions
For privacy questions or requests, contact the GitDash project through its public GitHub repository.