Privacy Policy

What we store

When you use the site without signing in, your done and planned marks, favorites, and personal notes are stored in this browser's local storage. Clearing browser data may remove them.

If you create an account and sign in, we store the name and email you provide, data needed for login, and the entry statuses, favorites, notes, and update times synced to your account. A cookie keeps your login session active. You can export your checklist as a CSV file.

When you create an account, we record the IP address and browser language of the sign-up request. Each sign-in session stores the IP address and browser identifier (user agent). We use these only for account security, abuse prevention and troubleshooting. They are kept with the account or session and deleted with the account. To prevent automated abuse, some actions are rate-limited per account or per browser: the site stores a randomly generated identifier cookie (hlb_bid, valid for one year, containing no personal information) in your browser. The server keeps only a one-way hash of it or of your account, for at most one day. When you sign in with WeChat, the verification code and a random account or browser identifier are sent to the site operator's WeChat verification service to confirm your identity and limit attempts. Your IP address is not sent.

The site is delivered through the Cloudflare network and hosted by Vercel, and Zeabur hosts the account database. These providers may process technical request information to deliver and protect the service. This site currently has no paid checkout.

How we use it

We use this information to provide reading, checklist storage, cross-device sync, account access, and necessary security maintenance. We do not sell your personal checklist or email address.

Usage analytics

We use Google Analytics to understand page visits, reading, checklist actions and sharing tools. Google may use cookies and process device and visit information. Our custom events contain coarse action types, language and success or failure. They do not include names, email addresses, notes, search text, edited sharing captions, individual suggestion choices or checklist snapshots. Page addresses sent by our tracking code exclude query strings and anchors. Local development and preview deployments do not send these events.

You may block analytics through your browser or a content blocker; the reading and checklist features remain available. Sharing images are generated on your device. Copying or downloading does not publish them; sending them to a social platform is your choice.

Your choices

You can use a local checklist without registering. To export records, use the CSV export in My Checklist. To ask about or request deletion of your account and server-side checklist data, email [email protected].

Changes and contact

If how we handle data changes materially, we will update this page and its date. For privacy questions, contact [email protected].

Daily tasks and leaderboard

Without signing in, drawn tasks and check-in dates stay in this browser. When signed in, new task selections, dates and completion timestamps are saved to your account. Older local records stay in your browser and are not automatically uploaded or counted on the leaderboard. Days follow your device's time zone: your browser sends the time zone name (for example, America/New_York) with each request. It is used only to work out the current date and is not stored.

Joining the leaderboard is optional. It shows only the separate nickname you provide and your day counts (total, current streak and this month), never your email, task details or daily history. Leaving removes your nickname and score from the leaderboard while keeping your personal records. You can undo today's check-in. Contact support to request deletion of all server-side check-in records.

A shared daily-task link contains only a public task identifier. A share image may include your selected task, completion status and the day's date; review it before sending. Analytics for daily tasks record only coarse actions such as draw, complete, undo, join and leave, never nicknames, task contents or check-in history.

Advertising, cookies and your choices

Eligible public pages use an advertising partner with scripts served from Adsterra (bauval.org, profitableratecpmnetwork.com). The network may receive your IP address, browser and device information and use cookies to deliver and measure ads, limit frequency and prevent fraud.

Ads load on eligible public pages after passing the PVUV check. The site no longer offers an advertising toggle, and earlier site-level advertising opt-outs no longer control loading. Browser Global Privacy Control signals still disable advertising. Visit statistics have a separate regional setting: first visits in the EEA, UK, Switzerland or an unknown location show a choice prompt; elsewhere they start enabled. We use the hosting platform’s country signal without retaining your IP address, city or precise location for this decision. The region result is cached for up to 24 hours and refreshed in the background; failed checks fall back to the browser time zone. Changing existing settings reloads the page to stop loaded optional scripts. Manual choices are saved in this browser for 180 days. Disabling optional services does not affect reading, checklists or sign-in.

We do not use personal notes, individual checklist choices, health information, sexual orientation or financial hardship for ad targeting, or intentionally send names, email addresses or account identifiers to advertising services. Google Analytics follows your statistics settings and has ad personalization signals disabled.

When usage analytics is enabled, we also count submitted checkup choices and entry opens, done, planned, favorite and removal actions on this site, grouped by day and source page. These requests omit login cookies. The counter table stores no accounts, visitor identifiers, IP addresses, notes or individual questionnaires, and these choices and entry data are not sent to Google Analytics or advertising services. Retakes and repeated actions count again: totals measure submissions and actions, not unique people.

Answering together

Answering together verifies participants through their signed-in accounts. Nicknames and answers are encrypted by the server and saved in the database, not stored locally in your browser. You can continue on another device using the same account. Content has no expiration date and is kept until any participant deletes the entire conversation. For each question, only participants who have submitted that question can see answers from others who have submitted it. Unsubmitted drafts are not returned to other participants. The invitation link can be used to join this conversation; send it only to people you want to invite. Deleting the conversation immediately makes all participants’ answers and the invitation link unavailable. Question pages do not load ads, analytics, or third-party customer support scripts. Creation and answer endpoints limit request frequency by account. Expired rate-limit records are cleaned up during subsequent requests.

Ad traffic protection (PVUV)

Public pages with ads use self-hosted PVUV to assess whether a visit is likely human. Checks process browser and device characteristics, screen size, language, an interaction flag, and the IP and connection information accompanying the request. When website analytics is enabled, the site also sends basic pageviews to PVUV for PV/UV and traffic-quality statistics. Chapter and article URLs are grouped by category; query strings and anchors are removed, and referrers are reduced to their origin. Specific reading topics, checklist actions, account identifiers and form contents are not sent. Disabling analytics stops pageview reporting while preserving pre-ad checks. Ads load only for a clean verdict in enforced strict mode. Suspicious visits, bots, crawlers and failed checks receive no ads. Automated assessments can make mistakes.

PVUV uses anonymous visitor and first-source cookies (_pv_id, _pv_ft, up to 396 days), a session cookie (_pv_sid, 24 hours) and a verdict-state cookie (_pv_v, 7 days). The local-storage _pv_id remains until cleared. When browser GPC is enabled, neither PVUV nor ads load. Website analytics continues to follow its separate settings.