Skip to content

Privacy Policy

This policy describes how moderngitacademy.com handles information. It reflects what the site is actually built to do, rather than a generic template.

Modern Git Academy is a static website. Every page is pre-rendered HTML, CSS and a small amount of JavaScript, served as files.

The site itself has no accounts, no login, no comments and no database. It sets no cookies and carries no advertising. It uses Plausible Analytics — a cookieless, aggregate-only service that records page views and a small set of named events without any personal identifier; the “Analytics” section below says exactly what it receives. Learning progress is kept in your own browser and never sent anywhere (see below). Beyond the aggregate analytics described below, nothing you do on the site is transmitted to us.

At the time of writing, this site does not:

  • Set any cookies of its own.
  • Use browser local storage or session storage for tracking. (Your theme preference and your learning progress are stored locally in your browser and never transmitted — see “Learning progress” below.)
  • Run Google Analytics, or any analytics that sets cookies, fingerprints devices, or tracks a person across sites. The one analytics service it uses is cookieless and aggregate-only — see “Analytics”.
  • Include advertising, advertising networks or retargeting pixels.
  • Embed social media widgets, share buttons or tracking pixels.
  • Load fonts, scripts or images from third-party content delivery networks, with one exception: the Plausible analytics script, loaded from plausible.io.
  • Operate any account system, contact form or comment system. There is no active newsletter or mailing list yet: no email provider is configured, the Modern Git Weekly signup form is disabled and submits nothing, and no email has been sent to anyone. When a provider is chosen this page will name it, and the address will go from your browser to that provider directly — never through this site — with confirmation by email (double opt-in) and an unsubscribe link in every message.
  • Sell, rent or share personal information. It does not collect any.

The site uses Plausible Analytics, operated by Plausible Insights OÜ and hosted in the European Union, to understand which pages are read and which features are used. It was chosen because of what it does not do: it sets no cookies, stores no IP address, builds no profile of an individual, and does not track anyone across websites.

What is sent. When you load a page, a small script from plausible.io sends: the page URL, the referring site (if any), and the browser’s declared user-agent. From the request Plausible derives browser family, operating system, device type and country, then discards the IP address. The site also sends a small number of named events — for example lesson_completed, knowledge_check_completed, practice_completed, learning_session_completed, recommendation_shown, learning_feedback_submitted — which carry the event name and, at most, a count, a fixed category or a public content identifier (a lesson route, a scenario name, a session slug, a reason code). Practice events include an approximate active-time bucket (for example “2–5 minutes”), counted only while the tab was visible and you were interacting. No event carries a quiz answer, a command you typed, an email address, an assessment answer, or anything that identifies you, and no identifier persists from one day to the next.

What is stored. Aggregate counts only. Plausible’s data policy states that it does not store anything that could identify an individual visitor; a daily-rotating hash is used to count unique visitors within a single day and cannot be reversed or joined across days. The full description is in Plausible’s data policy.

Where it is switched off entirely. Download pages (/dl/…) load no analytics script at all and send no events. Their address contains the token that authorises the download and, after a purchase, a Stripe checkout reference; neither may reach a third party, so the script is omitted from those pages and the site’s event dispatcher refuses to send anything from them. Commerce events elsewhere carry only a product identifier, a placement and a price figure — never an order reference, a download link, or an email address, which are stripped before sending even if a future component tries to include one.

Who can see it. The site’s operator, as aggregate charts. It is not sold, shared or combined with any other data.

Opting out. Plausible honours no cookie because it sets none. Content blockers that block plausible.io stop the script entirely, and the site works identically without it. Disabling JavaScript has the same effect.

Like any website, this site is delivered by a web server, and web servers necessarily receive certain information in order to send you a page. Depending on the hosting provider, that typically includes:

  • Your IP address
  • The page you requested
  • Your browser’s user agent string
  • The referring page, if your browser sends one
  • The date and time of the request

This is standard HTTP request data. It is generally retained by the hosting provider in server logs for operational purposes such as delivering content, diagnosing faults and mitigating abuse.

“Mark lesson complete”, saved lessons, knowledge-check scores (including which concepts a check missed, which drives the “Recommended next” block), the labs you have started, browser Practice Mode results, short-session progress, challenge checkpoint results and the My Academy dashboard all read and write your browser’s local storage under a single key. That data never leaves your device: there is no server to send it to, and the site makes no request containing it. It is not linked to any identity. Clearing site data removes it, and the “Reset all progress” control on My Academy does the same. The export control on My Academy writes the same data to a file you keep; nothing is uploaded.

The browser Git simulator in Practice Mode runs entirely in the page: the commands you type are interpreted by JavaScript against an in-memory model and are never sent anywhere, and the simulator cannot read your files. Two small per-visit flags — a dismissed recommendation, a feedback choice already recorded on this page — are kept in session storage and vanish when the tab closes.

The “How did this go?” control after exercises sends one analytics event carrying the page’s public identifier and a fixed category (“unexpected output”, “missing prerequisite”, “unclear explanation”, “environment mismatch”). There is no text box; nothing you type anywhere on the site is transmitted.

The site offers light and dark modes. Your choice is stored in your browser’s local storage so the site does not flash the wrong theme on your next visit.

This value never leaves your device. It is not a cookie, is not transmitted to any server, and is not used for identification. Clearing your browser’s site data removes it.

The site’s search is powered by Pagefind, which runs entirely in your browser. A search index is generated at build time and served as static files; when you search, your browser downloads the parts of the index it needs and matches locally.

Your search queries are not sent to a server, not logged, and not visible to the site operator.

Lessons link to external documentation — the Git project, GitHub, Microsoft, Apple, Ubuntu, Homebrew and similar sources. Those sites have their own privacy practices, which this policy does not cover.

Following an external link means your browser contacts that site directly. This site has no involvement in and no visibility into what happens after you leave.

This site is aimed at software developers and engineers. It is not directed at children, and it does not knowingly collect information from anyone, of any age. It does not operate any collection mechanism.

Where data protection law applies, individuals generally have rights of access, correction, erasure and objection in relation to personal data held about them.

Because this site operates no account system, and its analytics store no identifier, it holds no personal data through which an individual could be identified — there is nothing to access, correct or erase. Any request concerning server logs would need to be directed to the hosting provider, which acts as processor for that data.

Material changes to how this site handles information will be reflected here. If tracking, analytics or any form of data collection is introduced, this page will name the service and describe what it collects before or at the time the change goes live.

For any question about information handling, or to request details of the publisher not shown above, use the contact page.

This policy describes the site’s actual technical behaviour, and that description is complete: the site sets no cookies, loads one third-party script (Plausible’s, from plausible.io), and collects no personal data. Those statements are verifiable from the page source and from the browser’s network panel.

Anything the site does not do is not described here in the abstract. If tracking, analytics or any form of collection is ever introduced, this page will name the service and describe what it collects before or at the time that change goes live.