Who sees what

GitHub decides

Kaptimus never invents a permission. Who may see an account, and who may change what it monitors, follows the roles people have on GitHub:

• Owners — an organization's owners, or the owner of a personal account — see everything and are the only ones who can tick or untick the account.
• CI/CD Admins (an organization role on GitHub) see the whole account, view only.
• Admins of some repositories see only those repositories, view only.
• Everyone else sees nothing — not even that the account uses Kaptimus.

Seeing an account someone else installed

Sign in, then use the box "Can't see an account?" on the Accounts page (it is also on the dashboard while you have no account). Type the organization, or owner/repository, or paste a GitHub link, and press Find. Kaptimus asks GitHub what you may see there and adds it. If you have no role, the answer is the same whether or not the account uses Kaptimus.

When a role changes

• Before an owner's tick or untick is saved, Kaptimus asks GitHub whether they are still an owner. If not, the save is refused and the account disappears for them.
• Every night Kaptimus asks GitHub again about every person with access, and removes what GitHub no longer confirms. Nothing is ever added by itself.
• So a person who loses a role on GitHub can still view — never change — until that night's check.

What Kaptimus asks GitHub for

Read-only, and nothing about your code: your Actions runs and jobs, repository names, runner details, organization members and their roles, and your email address at sign-in. The full list is on the Privacy policy.