EN·中文

Copyright and terms

What is mine, what is borrowed, and what this site records about you.

Last updated: 16 November 2026 · Drafted with AI assistance and not reviewed by a lawyer.

Copyright

© 2026 Evan Huang. All rights reserved.

Unless a page says otherwise, everything here is mine: the writing, the project descriptions, the photographs I took, and the code and design of the site itself. None of it may be republished, copied or adapted without written permission.

What copyright law already allows is untouched by this. Quoting a reasonable extract for review, criticism, news reporting, study or research needs no permission from me.

Links are welcome, and you never need to ask before linking here.

What is not allowed

Using my name, marks or the look of this site in a way that suggests work is mine when it is not, or that you are me.

Copying or rebuilding this site's own code and design — by hand, with automated tools, or with an AI that clones pages.

Reverse engineering, except where the law expressly permits it.

Scraping, crawling or bulk-copying the site, including to train AI models.

Attacking the site, or trying to reach anything on it that is not public.

Borrowed, under their own licences

Nothing above restricts the open-source work this site is built on. Each piece keeps its own licence and its own permissions.

Next.js, React, PixiJS and Tailwind CSS — MIT licence. The guide's broker also uses the Azure Functions and Azure Data Tables libraries for JavaScript — MIT licence.

The photograph on the opening screen is not mine. Its author and its licence are named on the picture itself, and that licence, not this page, governs what you may do with it.

What this site records

This site is a set of static files on Azure Storage. It sets no cookies, runs no analytics, and loads no webfonts — nothing on these pages asks your browser to fetch anything from a third party while you read.

Two things are kept in your own browser and never sent anywhere: which theme you last chose on the canvas page, and, on the admin page, a key that only I would have.

Two things do leave your browser, and only when you start them yourself. Asking the guide a question sends that question to a small function app I run, which passes it to a language model and returns the answer; I keep no record of what was asked. Starting the spoken tour opens an audio connection from your browser straight to the speech provider — the function app hands out a short-lived credential and then steps out of the path.

Microsoft hosts the site and the function app, and keeps its own server logs of requests in the ordinary way. I add nothing to them.

Back to the site