HealthBook

Privacy notice

How information is handled when you use HealthBook.

Browsing HealthBook

HealthBook provides public articles, recipes and an optional AI assistant without accounts or sign-in. HealthBook does not create user profiles or use site analytics trackers. Advertising services, when configured, are described below.

Our hosting and delivery providers process technical information needed to serve and protect the website, such as IP addresses, requested URLs, browser information, and security or diagnostic logs. This notice does not promise that visiting a website creates no server logs.

Search

Article filtering happens in your browser. A submitted search is included in the page URL so that a filtered view can be revisited. That URL may be stored in browser history and may be received by the hosting service when loaded or shared. Do not enter private medical information into search.

HealthBook AI conversations

Using the assistant is optional. Do not share names, contact details, medical records, or identifying information. HealthBook does not create health profiles or save chat conversations in its database. Our application does not log messages, AI responses or API credentials.

The latest messages are kept temporarily in this tab’s session storage so that you can move between the compact assistant and its full page. History expires after 30 minutes of inactivity when the assistant is next checked. Choose “Clear conversation” to remove it immediately. Closing a tab normally ends its session, but a browser’s session-restore feature may restore it; clear the conversation when using a shared device. If session storage is unavailable, the assistant uses memory for the current page only. Messages are not stored in LocalStorage or included in URLs.

Questions are sent to the HealthBook server only when you select Send. In preparation mode, no messages are sent to an AI provider. When enabled, the current question, limited recent conversation, and optional public HealthBook page metadata will be sent through Hugging Face and its selected inference provider. No browsing history, page query strings or unrelated browser data are sent. Provider handling is subject to Hugging Face’s data practices and those of the selected provider.

Abuse protection uses counters and a daily-changing, keyed hash of a network address, not raw IP addresses or conversation text. Counters expire within a day; expired rows are removed in bounded batches during later requests. Hosting services may retain their own security logs. Chat responses are marked not to be cached or indexed and are never turned into public pages.

Advertising and analytics

HealthBook uses reserved advertising positions. A banner labelled “Advertisement preview” is a temporary image, not a paid advertisement. When a publisher is configured, Google’s AdSense script loads to connect the site; live units remain paused until advertising is enabled, a slot is configured, and the site’s consent integration permits requests. Google may process technical information such as your IP address and browser details and, where permitted, use cookies. See how Google uses information from partner sites. Ads stay outside AI conversations. HealthBook does not include chat text in ad requests or use it for advertising targeting. Site analytics are not currently enabled.

External websites

Source links take you to independently operated websites with their own privacy practices. HealthBook does not control those services. Review their notices before providing information there.

Your choices

You can use your browser’s controls to manage history, permissions, and cookies. Where applicable, use “Privacy & cookie settings” in the footer or Google’s US opt-out link to review your advertising choices. Ads remain paused while a required choice is unknown or declined. Public content remains readable without creating an account. Avoid sharing sensitive details through URLs or external services.

Questions and changes

See Contact & corrections for the current contact arrangements. This page will be updated if the website’s data practices change; the date above identifies this version.