Privacy Policy for the GLPro Website

Two kinds of information arrive here by different routes. One you type on purpose. The other is written by the web server the moment a page is requested — as it is on every website you have ever opened.

Nobody is asked to register and no part of this website sits behind a login. Server logs are operational records rather than a profile: not joined into a picture of a visitor, not sold, and not used to follow anybody from page to page.

The pages on this domain set no cookies of their own. There is one script on the site and it does four small jobs: it opens the mobile menu, it shows the buy bar once the first screen has scrolled away, it writes the year into the footer, and it fades sections in as they come into view. None of them stores anything.

There is no analytics tag, no advertising pixel, no session identifier and no cross-site tracking script here. That is checkable: open the page source and the script list is two entries long, one of which is the structured data a search engine reads.

One outside request does leave the browser. Typefaces are fetched from Google’s font service, which sees the request and the IP address that made it; every image is served from this domain. The checkout is a separate system on its own domain with its own policy, and this website cannot reach inside it.

There are two addresses on this website and they see different things. The website desk, [email protected], handles the pages themselves: corrections, privacy requests, press and anything about what is written here. It cannot see orders, which is a limitation rather than a policy.

Order support, [email protected] and +1 (720) 738-6364, handles tracking, changes, cancellations and refunds. An order question sent to the website address has to be forwarded first, so the right desk is worth the extra second.

The form on the contact page asks for four things: a name, the email address the order was placed with, the order ID from the confirmation email, and what you need. The order ID is the field that does the work.

Send no card numbers, no security codes and no medical detail by email to either address. Neither desk needs them and neither asks for them.

Card details are entered at the checkout, which is an encrypted payment system operated for the seller. They do not pass through these pages and they are not stored on this website at any point, before, during or after an order.

What comes back to this desk is what an order needs: a name, a delivery address, an email address, an order ID and which pack was bought. That is enough to send a parcel, answer a tracking question and issue a refund.

Nobody here can read a full card number, and nobody here will ever ring and ask for one — a request like that is not from this desk. Orders are placed at the checkout rather than over the phone, which is the arrangement described on the where to buy page.

An order record lives for as long as it can still be needed. The refund window is sixty days, a delivery question can arrive later than that, and the accounting obligations attached to a sale run longer than either — so the record is kept across that period, and not out of interest afterwards.

Email correspondence is kept while a question is open and for a period after it closes, so a follow-up two months later has context. Server logs are short-lived operational data.

A deletion request can be made at any time. Where a record has to be retained for tax or accounting reasons that part is kept and the rest removed, and the reply says which is which.

A parcel cannot reach a doorstep without a small number of other parties seeing the address, so the honest answer is a short list rather than a flat no.

• The checkout operator and the card network, who process the payment.
• The order support desk, which handles tracking, changes, cancellations and refunds.
• The carrier that delivers the parcel, which needs the name and the address.
• Anyone a law or a lawful request obliges this desk to tell, which has its own narrow rules.

Customer details are not sold, rented, swapped or handed to a marketing list, and there is no mailing list here to be added to. Glproformula trades from 270 Lafayette Street, Suite 1203, New York, NY 10012, USA, and returns go to a separate address printed on the refund page.

No form on this website asks about your health, your medication or a diagnosis, and no field exists for any of the three. An order record is a record of a purchase, not a medical record, and it should never be treated as one.

The list that matters is the one you keep for yourself. The FDA’s advice is to bring a list of every supplement and medicine you take, with the amounts, to every appointment, which is a list this desk neither holds nor wants.

MedlinePlus puts the companion instruction just as plainly: tell the person managing your care about any dietary supplement you use. A capsule bought here belongs on that list like anything else, and the disclaimer says why it matters in this category.

The site is served over an encrypted connection, the checkout is encrypted separately, and card details are never stored on this website. Those three together remove the most common way a small retail desk leaks a customer.

Access to order records is limited to the people who answer order support and handle returns. There is no marketing team here with a copy of the list, because there is no marketing list.

Two addresses are genuine: [email protected] for the website and [email protected] for orders, with the order line on +1 (720) 738-6364. Anything arriving from a different address asking for payment details did not come from this desk — forwarding it to the website address is a help rather than a nuisance.

You can ask what is held about you, ask for it to be corrected, and ask for it to be deleted. None of the three costs anything and none of them requires a reason to be given.

Include enough to be found: the name and email address used, and the order ID if the request is about an order. A request that cannot be matched to a record cannot be actioned, and the reply will say so rather than guess at whose data is meant.

A confirmation goes back when the request has been carried out, naming what was removed and anything that had to be retained for accounting. Where a record sits with the checkout operator rather than here, the reply says that too, so the request can be pointed at the right system.

This page carries a review date, and the date moves when the page does. It last moved on September 18, 2026. There is no archive of previous versions, so the page in front of you is the policy in force.

Corrections are made on the page itself rather than in a footnote, which is the same rule the rest of this website follows. If something here is wrong, incomplete or out of date, [email protected] is the address that fixes it and the review date moves forward with the change.