Last updated: 30 July 2026
01
How the site is built
mojikumi.jp is a set of static files produced by Next.js static export (output: "export"). No server-side code runs when you open a page, and there is no endpoint that takes in what you do.
There are no accounts, no contact forms, no comment threads and no newsletter sign-ups. Nothing on the site is built to receive information from a visitor.
02
What is stored in your browser
One localStorage entry, "mojikumi.theme", remembers the color theme you picked. Its value is either "light" or "dark", it decides nothing but the colors on your next visit, and it is never transmitted anywhere.
You can clear that entry from your browser settings at any time. Once it is gone, the site follows your operating system's color scheme again.
No cookies are used. With no login and no session to keep, there is nothing for one to do.
03
Analytics and advertising
There are no analytics, advertising, A/B testing, heatmap or session-recording tags of any kind. No count is kept of who visited which page.
The only scripts that run on load are the one that restores your chosen theme and Mojikumi's own typesetting code. Both finish inside your browser.
04
Outbound requests
The body typefaces (Shippori Mincho and Zen Maru Gothic) are pulled in at build time by next/font and served from this site, so no request reaches a font provider while you read. The YakuHanJP, YakuHanMP and Noto Sans JP faces used in the Playground comparison are self-hosted the same way.
As a result, ordinary browsing sends nothing to a third-party domain. Links that take you elsewhere, such as GitHub and npm, are governed by those services' own policies.
05
Text entered in the Playground
Anything you enter in the Playground is processed entirely inside your browser. It is never sent to a server, never stored and never logged, and nothing of it remains once you leave the page.
That said, the usual care applies on a shared machine or while screen sharing. Please do not paste confidential material into it.
06
Hosting provider logs
The site is served from Vercel. The provider may retain the access logs a web server ordinarily records, such as IP addresses and user agents.
These are an unavoidable part of serving the site, and they are not something we can read or make use of.
07
Changes to this policy, and how to verify it
Any change to this policy is recorded both on this page and in the history of the public repository.
Everything stated here can be checked against the site's source. If this text and the code ever disagree, treat the code as the truth, and please open an issue so the wording can be corrected.