Privacy Policy

Browser storage

CantoBooks uses browser localStorage for your color theme, preferred reading language, last-read language and chapter, and dismissed language suggestions. These settings stay in your browser and are not sent to us.

We do not use analytics of any kind, do not set cookies, and use no third-party embeds or fonts. Everything is self-hosted.

Personal data

CantoBooks has no accounts, forms, sign-in, newsletter, or comments. We therefore do not hold personal data about visitors.

Hosting

CantoBooks is hosted on Cloudflare Pages. To serve and protect the site, Cloudflare processes connection data such as IP address, user agent, and timestamps. This is Cloudflare's processing as the hosting provider, not our collection of visitor data.

Your rights

Under the EU and UK GDPR and Korea's Personal Information Protection Act (PIPA), you may contact us about privacy. Because we hold no personal data, there is no visitor data for us to provide access to, correct, or delete. Requests about Cloudflare connection logs should be directed to Cloudflare.

YouTube API Services

CantoBooks publishes its own videos to its own YouTube channel using YouTube API Services. By using this site and channel you agree to be bound by the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy.

The API client is a command-line script run only by the channel owner. It is not a product, has no sign-in, and no visitor of this site ever authorises it. The only account it accesses is the CantoBooks channel itself.

Through the API it reads and writes data belonging to that channel: video metadata, titles and descriptions, caption tracks, thumbnails, playlists, and the comments left on our own videos. It does not access any other channel, and it collects no information about visitors to this website.

The single OAuth credential is held locally by the channel owner and is never shared. The owner can revoke the client's access at any time from the Google security settings page; revoking it immediately ends all API access, and deleting the stored token file removes the credential from this machine. API data is not retained beyond the publishing run and is never sold, shared, or used for advertising.

Contact and changes

For privacy questions, contact [email protected]. We will update this policy if our practices change.