Privacy
What TestDojo keeps, what it doesn't, and where your data goes. Last updated 27 October 2026.
The short version
- You don't need an account to practise. Nothing you type on a practice page is sent to us.
- Your progress, badges and settings are saved in your own browser, not on a server.
- There are no ads and no tracking cookies. Visits are counted with Cloudflare Web Analytics, which doesn't use cookies or identify you.
- Signing in with GitHub is optional and only used for the Challenges. Your code is saved in your own GitHub repo.
- TestDojo has no database. We don't sell, share or collect data about you.
Saved in your browser
TestDojo uses your browser's local storage so the site remembers you between visits. This data stays on your device and is never sent to TestDojo:
- Settings: light or dark theme, the Help toggle, whether you've seen the Help tip, your preferred language and operating system on the setup guides, and which sidebar groups are open.
- Progress: practice pages you've tried, playground challenges you've solved, badges you've earned, and challenges you've passed.
- Practice data: the shop cart, the last practice order, and the email on the practice login page if you tick “Remember me”.
- Challenges: unsaved drafts of your code, your chosen framework and language, which repo you picked, and whether you've finished the setup.
To remove all of it, clear this site's data in your browser settings (often under “Cookies and site data”). You'll lose your progress and badges.
Practice pages and forms
The forms, logins, shop and checkout are for practice only. Nothing you enter is sent to a server; it's handled by the page in your browser. Files you pick on the upload page stay on your device too.
Please use made-up details. Don't enter real passwords, addresses or card numbers. The checkout lists test card numbers to use instead.
GitHub sign-in (Challenges only)
The Challenges let you write code here and run official checks in GitHub Actions. To do that, you sign in with GitHub and install the TestDojo Challenges app on one repo you choose. If you never sign in, none of this applies.
Once you've signed in and installed the app, TestDojo can:
- see your GitHub username and avatar, to show who's signed in;
- read and update the solution files in the repo you chose, when you click Commit & push;
- start the test workflow in that repo, and read its results and output, when you click Run test.
It can't see or change any other repo. Your code, commits and test runs live in your repo on GitHub, under GitHub's own terms. The setup asks you to make that repo public, so anyone can see what you put in it.
Signing in sets three cookies. They're only sent to TestDojo's /api address, and page scripts can't read them:
| Cookie | What it's for | Kept for |
|---|---|---|
td_oauth | Protects the sign-in step against forgery | 15 minutes, or until sign-in finishes |
td_at | The GitHub access token that lets TestDojo act for you | About 8 hours |
td_rt | Gets a new access token so you stay signed in | Up to about 6 months |
These tokens are only stored in those cookies in your browser. TestDojo's server uses them for each request you make and doesn't keep a copy.
To stop: click Sign out on the Challenges page, which deletes the cookies. You can also remove the app in GitHub under Settings › Applications and revoke its access under Authorized GitHub Apps.
Hosting and visit statistics
TestDojo runs on Cloudflare. Like any web host, Cloudflare processes the details of each request (your IP address, browser and the page you asked for) to deliver the site and protect it from abuse.
We use Cloudflare Web Analytics to count visits. Each page loads a small
script from Cloudflare (static.cloudflareinsights.com) that reports the page
address, the site you came from, your browser and device type, your country, and how
fast the page loaded. It doesn't use cookies or store anything in your browser, and it
doesn't identify you or follow you across other sites. TestDojo only sees the totals,
such as how many people visited each page.
Other services your browser connects to
- Google Fonts supplies the site's fonts, so your browser requests them from Google (Google Fonts privacy).
- cdnjs (run by Cloudflare) supplies the code editor on the challenge pages.
- GitHub supplies the starter code for the challenges and handles sign-in (GitHub privacy statement).
Links to other sites, such as download pages in the setup guides, follow those sites' own privacy policies.
If you email us
Messages to TestDojo's contact address are forwarded to the maintainer's inbox. We use your email address and message only to reply to you, and we don't share them.
Changes and questions
If what TestDojo stores ever changes, this page will be updated first, with a new date at the top. Questions about privacy? Get in touch.