Privacy notice
How TeamLedger handles the personal data in the repositories it analyses and of the people who use it.
Whose data
People who appear in analysed repositories. Git commits and GitHub activity contain names, GitHub logins, avatars and e-mail addresses of the people who wrote, reviewed or discussed the code. TeamLedger reads them to attribute contributions. E-mail addresses are never stored as such: only a salted hash is kept, to recognise the same person across their identities.
People who use TeamLedger. When you sign in with GitHub, TeamLedger stores your GitHub account id, login, display name and avatar, the workspaces you belong to and when you last signed in. It also keeps the list of public repositories you own or have contributed to (names and public details only), so you can pick one to analyse; the list is replaced each time you sign in. Your GitHub access token is used once, during sign-in, to confirm who you are and read that list, and is not stored.
People who join the waiting list. The e-mail address (and company, if given) is stored with the date of your consent, only to tell you when TeamLedger opens to more teams.
What is measured, and what is not
TeamLedger measures observable contributions to code: commits, pull requests, reviews and the lines of today’s code each person wrote. It does not judge a person’s overall job performance, does not rank people, and is not designed for decisions about hiring, pay or dismissal. Every observation links to the evidence behind it so it can be checked and challenged.
Code and repositories
Public repositories are cloned without checking out files and their code is never executed; the clone is kept for a limited time to make later analyses faster. Private repositories are read through the TeamLedger GitHub App with read-only access to the repositories an organization chooses, cloned only for the duration of each analysis and deleted right after. Only derived metrics are kept. Secrets found in code are never sent anywhere.
Each workspace’s analyses are visible only to its members. Deleting a repository or a workspace deletes its analyses; deleting your account (in Settings) also deletes the workspaces only you own.
Asking not to be shown
Anyone can ask not to appear in TeamLedger analyses. Their identities are then anonymised: the name, login, avatar and links to GitHub are removed, they are left out of every person-level report, comparison and team, and their work only counts towards repository totals. This is re-applied after every new analysis.
- Yourself, everywhere: sign in with GitHub (so TeamLedger can verify it is you) and use Settings → Your own data. You do not need to be a member of any workspace.
- In one workspace: ask the team that analyses your repository; any member can exclude you from your developer page.
Technical data
Sign-in uses a session cookie and an anti-forgery cookie; there are no advertising or tracking cookies. Sessions end after 7 days without use or 30 days in total. Rate limits use a salted hash of the IP address; IP addresses are not stored.
Retention
Each repository keeps only its three most recent analyses; older ones are deleted automatically, as are old failed analysis jobs. Cached clones of public repositories expire after a few weeks without use. Everything else stays until the repository, the workspace or the account is deleted. Waiting-list entries are deleted on request.