Privacy notice

01 What is available now

Google and WeChat reader sign-in have not yet completed provider setup and are unavailable. Reading, copying links, and sharing do not require an account. This notice also explains how information will be handled when sign-in is enabled.

02 Sign-in and interaction information

When sign-in is enabled, the website temporarily receives identity information returned by the provider. The current account implementation stores only the provider, its stable user identifier, your display name, and account creation and update times. It does not store profile photos or email addresses, or request the Google email permission. We do not ask for or collect your Google or WeChat password.

Likes, saves, and comments are linked to your reader account and the relevant article. Comment records include the text you submit, the submission time, and moderation status and information.

03 How the information is used

The provider identifier confirms your identity. Your display name appears in your account and comments. Interaction records remember likes and saves and support comment moderation. Google and WeChat accounts remain separate; matching names do not merge them.

To reduce repeated requests and abuse, the system temporarily stores request counts. Sign-in request counts use a hash derived from an IP address; the original IP address is not written to that rate-limit record.

04 What is public and where it is stored

Approved comments publicly show their text, display name, and submission time. Pending comments are available only to their author and site administrators. Rejected comments are not public. Do not put passport details, addresses, phone numbers, or other information you want to keep private in a comment.

Sites hosts the website. Reader accounts and interaction records are stored in the website's Cloudflare D1 database. Administrators can manage comments and associated records. Google, WeChat, and hosting services also process sign-in requests or information needed to operate their services under their own policies.

05 Cookies and retention

When sign-in is enabled, necessary cookies maintain your reader session and verify authorization. A reader session lasts up to 30 days. Signing out invalidates the current session. Authorization verification expires after 10 minutes. Clearing browser cookies requires signing in again.

Account and interaction records remain available for future use; signing out does not delete them. There is currently no automatic schedule for deleting account records. The system clears expired authorization, session, and rate-limit records in batches.

06 Your choices and other providers

You may read without signing in. After signing in, you can remove likes and saves and delete your own comments. There is currently no self-service option to delete an entire account. For questions, corrections, or deletion of other account information, contact the site owner; account ownership must first be confirmed.

Please also read the relevant provider's privacy policy when using third-party sign-in. Revoking authorization at the provider does not automatically delete records already stored on this website.