This policy describes MyWeightLab’s current website configuration. The publication uses WordPress on AWS Lightsail and Cloudflare for DNS, proxying and security. We do not offer medical consultations or a patient-record service.
Reading the site
Our servers and infrastructure providers process technical information needed to deliver pages and protect the service, such as IP addresses, request details, browser information and security events. Hosting is currently in Tokyo, Japan; Cloudflare may process traffic through its global network. Provider terms and applicable safeguards govern their processing.
Cookies and analytics
WordPress uses essential authentication cookies for signed-in users. Cloudflare may use security cookies or challenges when needed. We save your optional analytics preference in localStorage for up to 180 days. You can change it using Cookie settings. Advertising integrations are not enabled. Read our cookie policy for details.
Optional Google Analytics 4
When our Google Analytics connection is available, it loads only after you accept optional analytics. Rejecting analytics prevents this integration from loading Google tracking code. Advertising storage, advertising user data and personalized advertising remain denied. Changing your choice to reject disables further collection and removes this integration’s Google Analytics cookies; it does not erase information already received by Google.
With your consent, Google Analytics measures visits to public pages and interactions with editorial features, such as The Essentials, the Drug Tracker, related articles and source links. It uses browser identifiers and technical data to produce reports; this is not anonymous measurement. We do not send contact-form contents, newsletter email addresses, names, medical histories, body measurements or treatment-use information to Google Analytics. Public article topics are not statements about a visitor’s medical condition.
Search measurement uses a fixed list of public editorial topics, such as retatrutide or protein. Other searches are recorded as “other”, rather than sending your original query. Tracking URLs omit unrelated query parameters and fragments; referrers are reduced to their website origin. Google’s network necessarily receives technical connection information when an accepted analytics request is sent. Our hosting and security logs may separately contain request details.
Signed-in users and nonproduction environments are excluded from this Google integration. Google Analytics account access is restricted to authorized operators. Google has its own processing practices, described in its privacy policy. Any advertising, newsletter or affiliate integration must be assessed and disclosed before it starts collecting data.
Cloudflare Web Analytics
Cloudflare Web Analytics is active on the site through a JavaScript beacon automatically added by Cloudflare’s proxy. This measures page usage and performance for site statistics. The service can summarize page paths, referring websites, countries, device and browser types, and page-loading metrics. This existing Cloudflare feature operates separately from the WordPress integration settings.
Cloudflare states that Web Analytics uses neither cookies nor localStorage to collect usage metrics, does not fingerprint individual visitors, and does not track individuals across its customers’ websites. These analytics-specific statements do not mean that ordinary hosting and security processing described above stops. Read Cloudflare’s Web Analytics privacy description, data collection documentation and metrics and dimensions for details. We do not use these statistics to create advertising profiles. Any future change to analytics, advertising or similar tracking requires an updated policy and any applicable consent controls.
Editorial contact messages
The contact form asks for an email address and message, with an optional name. These are stored in the private WordPress editorial inbox to handle the request, not added to a mailing list. Live inbox messages are scheduled for deletion after 30 days. A short-lived salted network hash helps limit abusive submissions; it is not used to build a reader profile. Please avoid sensitive health information.
Newsletter
The newsletter interface is currently a preview and does not accept subscriptions. A provider, operational sender identity and subscription/privacy process must be configured before email collection begins.
Access, retention and security
Authorized site administrators can access correspondence. Technical logs and backups have separate operational retention; deleting a live message does not immediately erase an older backup. We use restricted administrator access and protected credentials, but no online system can promise absolute security.
Your questions
Use Contact for a privacy request and describe the data concerned without sending identity documents or medical records initially. We may need appropriate verification to handle a request. Applicable rights and requirements depend on jurisdiction. The operator must maintain accurate legal contact information and review this policy whenever the actual data-processing setup changes.
External sites
Source links lead to other organizations with their own privacy practices. This policy does not control those sites. Our publication is intended for adults, and we do not knowingly solicit children’s personal information.