Privacy

Learning without an account

Your progress is saved in your browser only and is not sent to GitDojo:

• the lessons, challenges and Practice tasks you complete, XP, the Git commands you run, the hints you reveal and the lesson you visited last;
• the practice repositories you work in, including the playground;
• small settings such as your light or dark theme and which release notes you have seen.

The PDF progress report on the dashboard is made in your browser and is not uploaded. You can clear your progress at any time with Reset learning progress on the dashboard, or by clearing this site's data in your browser.

If you create an account

Accounts are optional. Sign-in is handled by WSO2 Identity Platform (Asgardeo) on its own pages, so GitDojo never sees your password. When you sign in, GitDojo receives an account identifier and your profile's name and email address, and stores them in its database together with:

• the lessons, challenges and Practice tasks you complete, when, and the XP earned;
• per-device counts of the commands you run and playground sessions, identified by a random device ID;
• the hints you reveal, the lesson you visited last and the release notes you have seen.

This is what lets your progress follow you between devices. Progress made while signed out is never added to an account.

Certificates

When you ask GitDojo to issue a certificate, it stores:

• the certificate itself: the certificate name you entered on your GitDojo account page at the time, the award and its criteria, the issue date and your choice about showing your name publicly;
• for the Git capstone, the Git history you submit for grading and its result.

Each certificate has a public verification page that anyone with its link can open. It shows the award, issue date, credential ID and whether the certificate is valid or revoked. It shows your name only if you chose to make it public; the same applies to the signed Open Badge. The PDF always shows your name, and only you can download it. If a certificate is revoked, the reason is kept for GitDojo's records and is never shown publicly.

Cookies and browser storage

• Session cookie, only if you sign in: keeps you signed in.
• gitdojo_rate_limit: a random identifier that limits how often requests can be made, to protect the service from abuse.
• Browser storage (IndexedDB, local storage) for the progress, practice repositories and settings described above.

GitDojo uses no analytics, advertising or tracking cookies and does not sell data.

Who processes data

• Vercel hosts the site. Like any web host, it handles each request, including your IP address and browser details, and may keep logs.
• Neon hosts the PostgreSQL database that holds account data.
• WSO2 Identity Platform manages accounts and sign-in, under its own privacy terms.

How long data is kept, and your choices

Data in your browser stays until you reset it or clear the site's data. Account data is kept while your account exists, and certificates stay verifiable, because that is what they are for, unless they are revoked or deleted.

To ask what GitDojo holds about your account, or to have it deleted, contact the maintainers through the GitDojo repository on GitHub. Deleting your account data also deletes your certificates, and their verification links then show that the credential was not found.

Changes

If what GitDojo collects changes, this page is updated and the date at the top changes with it. The project's source code is public, so you can check what it does.