Purpose and status
This site is a static set of files. Its authored code does not create accounts, submit forms, set analytics cookies, embed advertising, request location, or load third-party fonts, videos, trackers, or remote scripts. The menu interaction runs in the reader’s browser. The site does not provide a newsletter, comments, a checkout, or a preference center.
Editorial method
If hosted through GitHub Pages, the hosting service may process ordinary technical request data such as IP address, device or browser details, requested path, time, security information, and service logs. That processing belongs to the hosting provider and any real future operator under their applicable terms and policies. This fictional statement does not claim to control or retain that infrastructure data.
Scope and limitations
The single external editorial link in the main feature points to a separately operated website. Following it leaves this static publication. The markup does not append tracking parameters or load that destination merely because a reader opens a Dim Room Desk page. Readers should inspect any destination’s current privacy practices before sharing data or making a purchase.
Contact and governance
The example contact address is non-monitored and should not receive personal data or privacy requests. There is no reader database behind it. If interactive features are added in the future—such as a form, analytics, embedded media, a commerce tool, or a social widget—this notice would need a fresh data-flow review before those features are enabled.
Reader responsibility
Build scripts, source image files, screenshots, validators, local reports, and deployment evidence are kept outside the deployed public manifest. The public files contain only pages, local presentation assets, images, crawl instructions, and a sitemap. This separation reduces accidental disclosure of development material, but it does not promise anonymity across networks or hosting infrastructure.
Limits of this notice
Static delivery limits what this authored code collects, but it does not eliminate processing by browsers, access providers, security tools, or a future host. Readers who need stronger privacy should use controls appropriate to their circumstances and avoid sending sensitive data to example addresses. A future operator must replace this demonstration text before introducing any interactive or remote feature that changes the information flow. That review should inventory each data recipient, the purpose of every request, retention decisions, a meaningful contact route, and the controls available to the people affected. Plain wording is part of that review, not a substitute for it.
