HoneyPower Privacy Policy

Very little, and the reason is structural rather than virtuous. This website does not take payment, does not run a checkout, does not hold an account system and has no view of the seller’s order records. There is no order database here to protect because there is no order database here at all.

What that leaves is ordinary web serving and the emails people choose to send.

Seven rows. The four “No” rows are the ones that matter, and they are the direct consequence of this site not being a shop.

A privacy policy on a supplement website usually runs to several screens, and most of it describes a shop. It explains how checkout data is encrypted, how an account is created, how a saved card is stored, how an abandoned basket triggers an email.

None of that happens here. This website has no checkout, no account system, no basket and no card storage, so a policy describing those things would be describing somebody else’s infrastructure and telling a reader nothing true about this one.

The commonest defect in this category is exactly that: a template policy promising protections for data the site does not hold. It reads as thorough and it is the opposite, because a reader cannot tell which sentences apply. So this page names the seven categories that exist, says which four of them sit with the seller instead, and stops.

A buyer’s data on this product sits in two places and the split matters when you want something done about it.

Myhoneypower runs this website. It holds server logs, aggregate page statistics and any email sent to the editorial address. It holds no order, no payment and no name unless you wrote one in an email.

The seller’s checkout takes the order. It holds the name, the delivery address, the payment and the order history, and the order desk works from those records. A request about order data has to go to that desk, because this one cannot reach it.

Two organisations. A request sent to the wrong one has to be redirected by hand.

This website does not set advertising cookies and does not run a retargeting pixel. Nothing here follows a reader to another website.

What it does use is ordinary web infrastructure. A font file is requested from Google’s font service, which sees the request the way any content delivery network does. Server logs record requests. Aggregate statistics record which pages are read, without tying that to a person.

The links in the reference lists point at PubMed, the NIH Bookshelf and a handful of government consumer pages. Those are external sites with their own policies, and following one of them takes you into somebody else’s. Every such link on this site opens in a new tab and carries a nofollow attribute, which is a statement about search engines rather than about privacy, but it does mean you will still have this page where you left it.

• No advertising cookies and no retargeting pixel.
• No cross-site tracking and no data sold to anybody.
• No marketing email from this website. It has no list to send one to.
• Fonts are requested from Google Fonts, which sees the request.
• Citation links leave for PubMed and NIH pages with their own policies.
• Aggregate page statistics only, never tied to a purchase or a person.

The site is a set of static pages. There is no database behind it, no login form and no server-side code accepting input from a reader, which removes most of the attack surface a shop has to defend.

Pages are served over an encrypted connection. Assets carry a content hash in their URL so that a returning visitor receives the current version rather than a cached old one, which matters here because a corrected page is the mechanism this desk uses to fix a mistake.

The practical consequence for a reader is short. There is nothing to sign into, nothing to be locked out of, and no credential belonging to you that this website could lose.

You can ask what this website holds about you, ask for it to be corrected, and ask for it to be deleted. Write to [email protected], which is staffed Mon–Fri 9:00am–5:00pm ET.

In practice the answer for most readers is short, because most readers have never sent an email and therefore appear here only as a line in a server log. That is not a dismissal of the question; it is the honest answer to it, and it is more useful than a paragraph of rights language implying a file exists.

Requests about order data are a different matter and belong to the seller’s desk. The order system holds the name, the address, the payment and the order history, and this desk can neither read it nor change it.

This page was last reviewed in September 2026. When it changes, the review date at the foot of the page moves forward, which is the only change notice this desk publishes and is more honest than a banner nobody reads.

If something here is wrong, it is worth telling us. A privacy page describing data a site does not hold is the commonest defect in this category, and the only way it gets found is a reader noticing that a sentence does not match what he can see.