GlucoPril Privacy Policy

Three things, and the list is short because the website does very little. Server logs, recording the ordinary facts a web server records: an IP address, a timestamp, the page requested, the browser string. Analytics, where they are running, recording which pages are read and for how long, in aggregate. And email correspondence, which is whatever you chose to send.

No account exists on this website, so there is nothing to sign into and no profile to build. No payment page exists here, so no card number, expiry date or security code is entered on this domain at any point. The forms on the contact page are checklists that transmit nothing; they are there so a telephone call or an email is shorter.

The result is that this desk holds less about a buyer than almost any other party in the transaction. The seller’s checkout holds the order. The payment processor holds the payment. The carrier holds the delivery address. This website holds a log line and, if you wrote to it, an email.

Only the first three rows belong to this desk. The fourth is here because it is the one people mean when they ask.

This website does not need a cookie to work. There is no account to stay signed into, no basket to remember and no personalisation to restore, so the pages render the same way for a first visitor and a hundredth one.

Where analytics are running, the provider may set its own cookie or use an equivalent mechanism to tell one visit from another. That is the ordinary arrangement and it is aggregate: it reports that a page was read, not who read it. Browser-level controls over cookies and tracking apply here exactly as they do anywhere else, and blocking them costs you nothing on this site.

Following the order link is the moment that changes. The seller’s checkout runs its own cookies for its own purposes, including keeping a basket and attributing the referral this desk earns a commission on. Those are the seller’s and are governed by the seller’s terms.

Only the first row is this website's. The other two belong to the checkout and are described here so the hand-off is visible.

The order link hands you to the seller’s own checkout, and from that moment the privacy terms governing you are theirs rather than these. The name, address, email and payment details entered there are collected by the seller and the payment processor, and they are the parties who hold that record.

This is worth being precise about because a handover is easy to miss. The button is on this website; the page it opens is not. Read the seller’s own privacy terms at the checkout, in the same pass in which you read the price and the return window.

When you later call +1 (302) 200-3480 about that order, you are talking to the payment processor’s desk rather than to this one. That is why it can see your order and why the website desk cannot.

Four parties, and naming them is more useful than a general statement about sharing data with partners.

The seller operates the checkout and takes the order. The payment processor takes the payment and operates the order desk. The carrier delivers the parcel and needs an address to do it. And the host serving this website sees the requests any web host sees.

This desk does not sell, rent or trade personal information, and it has very little to trade. No mailing list is operated from this website and no marketing email is sent from it.

• The seller, who operates the checkout and receives the order.
• The payment processor, who takes the payment and runs the order desk.
• The carrier, who needs a delivery address.
• The web host, which sees requests in the ordinary way.

Two kinds. Citation links point at PubMed, the National Center for Complementary and Integrative Health and MedlinePlus, all of which are public and none of which is paid for. Order links point at the seller’s checkout and are commercial: this desk earns a commission on orders placed through them, which the about page discloses in full.

Once a link is followed, the site at the other end applies its own terms. That is true of a government health page as much as of a checkout, and no site can extend its own privacy terms across a hyperlink.

Citation links carry attributes asking search engines not to treat them as endorsements, and order links are marked as sponsored. Both are conventions rather than protections, and they are followed here because they are accurate.

Ask, and it is answered. Write to [email protected] from the address the request concerns, and say what you want: a copy of what is held, a correction, or deletion. The mailbox is read Mon–Fri 9:00am–5:00pm ET.

Because the holding is so small, most of these requests are straightforward. An email thread can be deleted. A log line expires on its own. An analytics record is aggregate and usually cannot be tied to an individual at all, which is a limitation rather than a refusal.

A request about an order is a different request and goes to a different desk. The order record lives with the payment processor, and +1 (302) 200-3480 is the route to it.

This website is written for adults. The product it describes is labelled for healthy adults aged 18 and over, and nothing on these pages is directed at children.

No information is knowingly collected from anyone under 18. If you believe a child has sent something to [email protected], say so and it will be deleted.

This website is served over an encrypted connection and it is kept current. That is the ordinary standard and it is met.

The honest limit is that no website can promise perfect security, and one that does is telling you something it cannot know. What reduces the risk here is the shape of the site rather than a promise about it: there is no account, no stored payment method and no customer database, so a breach of this website would expose a mailbox and a log file.

Anything genuinely sensitive belongs on the telephone with the order desk rather than in an email to a website.

Because the website is. Most privacy policies in this category are long for a reason that has nothing to do with candour: they are written to cover every function a large retail platform might one day have, whether or not the site running them has any of those functions today.

This one describes what actually happens. A visitor reads pages, a server logs the request, an analytics provider counts the page, and some visitors send an email. If they buy, they leave for a checkout this desk does not operate. There is no fifth thing, and inventing clauses about loyalty schemes, profiles and targeted advertising would make the policy longer and less true.

The test worth applying to any privacy policy is whether you can tell, after reading it, what the site holds. If the answer is no, length was not the problem.

Changes are made on this page and the review date at the foot moves forward. There is no separate notification, because this website holds no mailing list to notify.

The current version was reviewed in September 2026. Questions about it go to [email protected].