Privacy Policy

Last updated: 2 October 2026

This Privacy Policy explains how Bluum (“Bluum”, “we”, “us”), operated by Bluum Journal LLC, 16192 Coastal Hwy, Lewes, DE 19958, United States, collects, uses, and protects your personal information when you visit bluum.blog or use our services. By using the site you agree to this policy.

1. Information we collect

• Information you give us — your email address when you subscribe to the journal or request product purchase details, and any details you send us by email.
• Usage data — pages viewed, approximate location (from IP), device and browser type, and how you interact with the site.
• Cookies & similar technologies — including advertising and analytics pixels (see Section 5).

2. How we use your information

• To manage journal subscriptions and product product-interest requests.
• To send you the content you requested and relevant updates (you can opt out any time).
• To measure and improve the performance of our site and advertising.
• To keep the service secure and comply with our legal obligations.

3. Legal bases (EEA/UK users)

We process personal data on the basis of your consent, our legitimate interests in operating and improving Bluum, and to perform our contract with you. You may withdraw consent at any time.

4. Sharing your information

We do not sell your personal information. We share it only with service providers who help us run Bluum (e.g., hosting, email, and analytics/advertising platforms such as Meta Platforms, Inc.), under agreements that require them to protect it, and where required by law.

5. Cookies, analytics & advertising

We use cookies and pixels to run the site, measure traffic, and understand the effectiveness of our advertising — including the Meta (Facebook) Pixel and similar tools. These may set cookies that help us and our advertising partners show and measure ads. You can opt out of marketing and personalization using the button below or your browser privacy settings. We also honor Global Privacy Control and Do Not Track.

When you allow personalization, the journal stores a signed reading-assignment cookie for up to 30 days so that a channel’s article variation stays consistent. Declining personalization, Global Privacy Control, or Do Not Track prevents this assignment storage. Administrator sessions use a separate secure eight-hour cookie.

Google Tag Manager (container GTM-PZT5TGXR, loaded through ss.bluumpeptides.com) loads by default on public pages and activates analytics and advertising tags configured by Bluum, unless you opt out or your browser sends Global Privacy Control or Do Not Track. These tools may process page visits, campaign information, cookies and device information. They do not run in private administration or draft previews. Klaviyo loads when you allow marketing and processes website activity and uses cookies to support marketing analysis and signup forms. Your separate marketing-cookie preference is remembered for up to 30 days. Klaviyo tracking does not run in our private administration or draft previews.

Allow marketing and personalization Opt out of marketing and personalization

To protect access to video presentations, our server records public page requests with their time, page, IP address, available country, referring domain, user agent, selected campaign parameters, and access decision. We do not store referrer query strings, arbitrary URL parameters, or email addresses in these security logs. These logs use no additional browser cookies or fingerprinting and are separate from optional advertising and personalization. Authorized administrators can use these request signals to show selected visitors an article without video. They do not establish a visitor’s identity.

6. Data retention

Security visit history has no automatic time expiry or request-count cap and remains stored until we choose to delete it. Administrator-created access rules remain until changed or disabled. Access to security logs and rules is restricted to authenticated administration.

We keep personal data only as long as needed for the purposes above, then delete or anonymize it.

7. Your rights

Depending on where you live (e.g., under GDPR or the CCPA), you may have the right to access, correct, delete, or port your data, and to object to or restrict certain processing. To exercise these rights, contact us using the details below.

8. Children

Bluum is not directed to children under 16, and we do not knowingly collect their personal information.

9. Changes

We may update this policy from time to time. We will post the updated version here with a new “last updated” date.

10. Contact

Questions or requests? Email us at [email protected] or write to Bluum Journal LLC, 16192 Coastal Hwy, Lewes, DE 19958, United States.

Journal subscriptions

If you submit a journal subscription form, we collect your email address, your consent, the article and reading variant, and the source and campaign parameters in your link. These details help us deliver the editorial emails you request and understand which campaigns generate subscriptions. A configured subscription provider processes submissions on our behalf. You can withdraw consent or request deletion by contacting [email protected]. The journal does not save emails locally in your browser. If the subscription destination is unavailable, the form reports that it could not confirm the signup.

Store product offers

When you submit a product enquiry, we collect your email, the product you are interested in, your consent, and source and campaign information. Klaviyo processes these requests using our existing Bluum mailing list. With your consent, you may receive product offers and marketing emails, including existing welcome messages. Your most recent product interest may be recorded on your subscriber profile. You can unsubscribe from our emails at any time. An enquiry is not a purchase or an order.

Content experiments and saved audiences

When you allow personalization, we use a signed first-party browser cookie for up to 180 days to keep experiment versions consistent, recognize enrollment in earlier phases, and include your browser in a saved audience matching a chosen source, time window or other condition. Saved audiences can be reused in later content experiments or video-access rules. We store a pseudonymous browser key, enrollment times, version assignments, audience membership, and aggregate request, outbound-click and successful-signup counts. Freezing an audience stops new additions and preserves existing members. Clearing or expiring the browser cookie can prevent us from recognizing that browser again.

Requests may be matched using their page, campaign parameters, referring domain, user-agent-derived operating system/browser/device, IP address or subnet, and the hosting platform's approximate IP location: country, region, city, nearby postal code, continent and timezone. IP location can be absent or inaccurate, especially with mobile networks or VPNs; it is not a verified residence. Approximate coordinates can be used for radius matching during a request but are not retained in visit logs. We do not use fingerprinting or treat IP addresses as a person's identity.

A matching request may be redirected to an administrator-selected external HTTPS website. A rule can forward campaign tags and click IDs or other ordinary query parameters; credential-like parameter names and private preview controls are excluded. No full query string is saved in security visit history. The destination website has its own privacy policy.

Without consent, or when Global Privacy Control or Do Not Track is enabled, we do not set or use the experiment browser identifier or add the browser to a saved batch. Current-request conditions may still select a version or control video access without recognizing returning visitors. Conditions that require unavailable audience membership or location use normal routing unless a rule explicitly targets missing data. Experiment configuration, enrollments, saved audience members and results have no automatic expiry and remain until an administrator chooses to remove them. Security visit history also has no automatic expiry or request-count cap. You can change your personalization preference above, clear browser cookies, or contact us about stored data.