Skip to content
>_Rong

Search the full text of every article — titles, tags, categories and article content.

Legal

Privacy policy

How this website handles your data. Last updated 19 September 2026.

Who runs this site

This website is operated by Rong as a personal technical publication. Questions about this policy can be sent to bunbunrong993@gmail.com.

What this site collects directly

There are no reader accounts. You can read every article without submitting anything at all.

If you like an article or a comment

A blog_visitor cookie is set in your browser containing a random identifier — not a name, an email address or an IP address. It exists only so the same browser cannot like the same thing twice, and so your own likes show as yours when you come back. It is set the first time you like or comment, never by simply reading, and it is not shared with anyone.

If you post a comment

The name you type and the text of your comment are stored in this site's database, together with the random identifier above and the time you posted. No email address is asked for and no IP address is stored. Comments are reviewed before they appear publicly, and once published your name and comment text are visible to anyone reading the article.

To have a comment removed, use the contact details below. Removal is permanent.

One other thing is stored in your browser: a theme value in localStorage, recording whether you chose the light or dark colour scheme, and — if you have commented — the name you last posted under, so you do not have to retype it. Both stay on your device, and clearing your browser storage removes them.

Hosting

The site is hosted on Vercel, which processes standard server request data (IP address, user agent, requested URL, timestamp) in order to serve pages and protect the service from abuse. This is described in Vercel's own privacy documentation.

Analytics

This site uses Vercel Web Analytics to count page views and see which articles are read. It records the page visited, the referring page, and coarse device and country information.

It sets no cookies and stores no identifier in your browser, so it cannot follow you between sessions or across other websites. Measurements are reported to this site's own domain rather than to a third-party host, and are only ever used in aggregate. A content blocker will stop it.

Advertising

No advertising is shown on this site today. The intention is to fund it through Google AdSense, and the AdSense script is loaded so that Google can review the site, but no ad placement is configured and no advertisement is served.

Because that script comes from Google, Google may still set or read cookies on your browser while it is present. If and when ads do start appearing, they will sit in a single placement below the article body, never inside it, and this section will describe the advertising cookies in full. In the meantime you can review or turn off personalised advertising at any time in Google Ads Settings, or opt out of third-party vendors at aboutads.info/choices.

Cookies summary

PurposeSet byStatus
Theme preference (local storage, not a cookie)This siteAlways
Anonymous identifier for likes and comments (blog_visitor)This siteOnly if you like or comment
Analytics (cookieless — no identifier stored)Vercel Web AnalyticsEnabled
AnalyticsGoogle AnalyticsNot used
AdvertisingGoogle AdSense and partnersNo ads served
Newsletter email address (stored by the provider)—Not used

External links

Articles link to external documentation, repositories and other sites. Those sites have their own privacy practices, and this policy does not cover them.

Your rights

This site stores two things itself, in its own database: the comments people write — the name typed, the comment text and the random identifier described above — and which articles a browser has liked. To see, correct or delete either, email bunbunrong993@gmail.com with the article and the name you used, and it will be removed. Removal is permanent.

Everything else described above is held by a third party, so requests about it need to go to the relevant one: Google for analytics or advertising, or the hosting provider for server logs. If you are unsure where a request should go, ask at the address above.

Changes to this policy

This policy is versioned with the rest of the site in Git. Material changes update the date at the top of this page. See also the terms of service.