Privacy Policy
Last updated: 2026-10-28
This page describes the site’s data practices and the third-party services it uses.
Who runs this site
This is a personal technical blog written by Jang Young Jeong (Fodev JEO), an AI product engineer based in South Korea. It is not a company. The site also offers paid reviews; inquiries can be sent by email.
- Contact: akillness38@gmail.com
- More detail: About
What this site does not do
- No site accounts. The blog does not have its own account system; commenting uses a GitHub account.
- No newsletter or payment forms. The site does not collect newsletter signups or payments.
- No server-side logs owned by me. The site is static and hosted on GitHub Pages; I do not operate a backend that records your requests.
What is collected, and by whom
The site is static HTML and uses third-party services. Their own privacy policies describe how they handle data.
| Service | Purpose | Data involved | Policy |
|---|---|---|---|
| Google Analytics 4 | Traffic measurement, such as which posts are read | When enabled, Google may receive page URLs, device and browser information, IP address and analytics identifiers or cookies | Google Privacy Policy |
| Google AdSense | Displays ads on eligible long-form post pages | Google and its partners may receive IP address, device information, cookies and other identifiers for ad delivery, measurement and, where applicable, personalisation | How Google uses data |
| Giscus (comments) | Displays comment threads backed by GitHub Discussions | On pages with comments, the browser loads Giscus even if you do not comment; Giscus and GitHub may receive technical request data such as your IP address and browser information. If you comment, your GitHub identity and comment are public on GitHub | Giscus privacy policy, GitHub Privacy Statement |
Static assets such as fonts and JavaScript libraries may be served from jsDelivr, which receives request information including your IP address. Site hosting is GitHub Pages, which may log requests per GitHub’s policy.
Analytics choice
Google Analytics is off unless you choose Accept analytics. Before you accept, the site does not load its analytics tag. Open Analytics settings in the footer to accept or decline analytics or change your choice later. The choice is stored in this browser’s local storage; if storage is unavailable, it cannot be saved and analytics is not enabled.
If you decline after accepting, the site disables analytics and reloads the page. It also attempts to remove Google Analytics cookies that scripts can read on the current path. It cannot remove cookies set on other paths of this site, cookies that browser settings block from scripts, or any other cookie. If removal fails, the Analytics settings panel shows a warning on your next visit. Clear remaining cookies in your browser settings. Changing this choice does not delete data previously sent to Google.
Cookies and advertising
Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website and other websites. Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet. Google’s own explanation is at How Google uses cookies in advertising.
- You can opt out of personalised advertising at Google Ads Settings.
- For opt-outs from third-party vendors’ use of cookies for personalised advertising across many networks at once, see www.aboutads.info or Your Online Choices (EU).
- You can also manage or block cookies in your browser; doing so may affect third-party features.
AdSense may load on eligible posts. The site’s analytics choice is separate from advertising controls; it does not set your advertising preferences. Pages without ads do not load Google’s advertising or consent code, so no Google advertising consent message appears on them. On eligible posts, a Google consent message may appear depending on Google’s account configuration and your location. This site has not verified that a message is shown to every visitor, and it does not guarantee one.
Comments
Comments are handled by Giscus, which writes them to a GitHub Discussions thread on the site’s repository. That means:
- Commenting requires a GitHub account and authorising Giscus.
- Your comment is public and stored by GitHub, not on this site.
- To delete a comment, edit or remove it in the linked GitHub Discussion, or email me and I will remove it.
Children
This site is aimed at professional software engineers and researchers. It is not directed at children under 13, and no age-gated or child-directed content is published here.
Your rights
For data held by third-party services, their privacy policies explain how to make requests:
- Analytics and ad data → see Google’s privacy information and the advertising controls above.
- Comments → manage them in GitHub Discussions, or email me.
- Anything else → email akillness38@gmail.com.
Changes
If the set of third-party services changes, this page changes with it, and the date at the top is updated. The full edit history of this page is public in the site’s Git repository.