Our commitment
Reading about intimate care, cycles, menopause, sleep, skin, hair, or wellbeing can reveal sensitive context even when you never type a symptom or diagnosis. Women's Daily Care therefore treats care-topic browsing and related inferences as sensitive and avoids using them for advertising profiles.
This notice is intended to address consumer-health-data laws where they apply, including Washington's My Health My Data Act and similar state requirements. It supplements the general Privacy Policy.
Categories and sources
Women's Daily Care currently has no accounts, assessments, quizzes, symptom tools, precise-location features, first-party checkout, or email enrollment. When a reader requests a page, Cloudflare processes the requested URL together with standard network, header, device, timestamp, and security information supplied by the reader's browser so it can deliver and protect the site. Our application does not persist the raw page request.
The Phase 1 reports at go.womensdailycare.com/report-cranberry and go.womensdailycare.com/report-cranberry-brief load Meta Pixel, which processes the fixed eligible report URL and standard browser, device, network, cookie, referrer, and attribution information for PageView, ViewContent, and OutboundClick events. Women's Daily Care supplies no custom event parameters and sends no Lead or Purchase from the browser. General editorial care-topic pages and untracked report candidates are outside this Pixel flow, and the tracked reports collect no symptom, diagnosis, quiz answer, form text, email address, or phone number.
The Phase 1 reports also use a temporary PostHog diagnostic to measure page visits and governed presentation handoffs by CTA location. Its custom event fields are limited to a schema version, the fixed eligible report path and corresponding fixed variant, and one allowlisted CTA-location label; they exclude query strings, referrers, source keys, fbclid, merchant URLs, form data, symptoms, and contact information. A separate 20% replay sample diagnoses scrolling and interaction friction. Text, inputs, element attributes, query strings, and URL fragments are masked or removed; console logs, network contents, performance data, autocapture, heatmaps, person profiles, surveys, cookies, and local storage are disabled. The integration does not load on other pages or when Global Privacy Control or Do Not Track is present, uses 30-day retention, and is scheduled to stop by August 23, 2026 or after 50 useful mobile sessions are reviewed, whichever occurs first.
The reviewed FemiCore flow generates a random Women's Daily Care click identifier, stores that identifier with the offer, deployment stage, fixed page variant, whether a valid fbclid was present, and an approved opaque source key when present. A small same-origin script copies one allowlisted source key and one valid fbclid from the landing URL into the managed redirect. The application does not store the raw fbclid or copy arbitrary UTM values, audience data, or health information. It sends the random identifier as ClickBank's aff_sub1 value and passes the valid fbclid unchanged to the verified merchant destination. A later ClickBank conversion postback can add the minimized transaction and attribution fields listed in the general Privacy Policy. These records can reveal interest in or purchase of a women's-health product even though they contain no explicit symptom, diagnosis, raw care-page URL, raw ad click value, email address, IP address, or user agent.
ClickBank's separate Facebook integration for affiliate tastemake is active and configured to send InitiateCheckout, Purchase, and Upsell events to Meta when the traffic source is marked facebook. Women's Daily Care does not send these events from the browser or forward its D1 records to Meta.
The route reads Cloudflare's approximate country and state or region code only to determine whether the pilot handoff is available. The application does not store that location in the managed affiliate ledger.
If a future feature would collect symptoms, conditions, reproductive or sexual-health information, treatment or medication details, measurements, biometric data, precise location, product use tied to an individual, or an inference about health status, that feature requires a separate notice and valid authorization before release.
Purposes for collection or use
Where care-related request data is processed, it is used to deliver the page a reader requested, protect the service, measure paid-report visits and presentation handoffs, temporarily diagnose paid-report scrolling and interaction friction, apply the pilot's location rules, attribute a reader-requested merchant handoff and resulting transaction, honor privacy choices, and respond to a request the reader initiated. We do not use symptoms or diagnoses to determine insurance or employment, set a price, or create a health-condition audience.
Retention and deletion
Cloudflare controls retention for the standard delivery and security records it processes under the connected account settings and terms. Women's Daily Care does not persist the raw care-page request in its application.
PostHog diagnostic events and session recordings use 30-day retention, and new PostHog collection is scheduled to stop by August 23, 2026 or after 50 useful mobile sessions are reviewed, whichever occurs first.
The application deletes managed outbound-click records after 90 days and minimized ClickBank conversion records after 180 days through scheduled deletion and a second check before accepting another record. A verified deletion request can be propagated to the applicable operational record, subject to lawful exceptions and the limited identifiers available to locate it.
Consent and withdrawal
The Phase 1 paid reports do not display a separate on-page consent banner before Meta Pixel or the temporary PostHog diagnostic loads. The complete PostHog integration—including its two named events and sampled, content-masked replay—does not load when the browser sends Global Privacy Control or Do Not Track. Where applicable law requires consent or signed authorization for a collection, sharing, or sale of consumer health data, we will obtain it before making that flow available. The initial affiliate pilot has no consumer-health-data consent or sale-authorization control, so the compensated route is unavailable in jurisdictions currently identified as requiring one for this flow.
A reader may withdraw an applicable consent through the privacy-request route below. The initial pilot does not rely on consumer-health-data consent and must not be expanded to a blocked jurisdiction without a separately reviewed control.
Consumer health data rights
Where applicable, you may confirm whether we collect, share, or sell consumer health data; access the data and a list of relevant recipients; withdraw consent; and request deletion, including deletion communicated to covered processors or affiliates. You may also appeal a refusal.
Submit a request or appeal to privacy@womensdailycare.com with “Consumer health data request” in the subject line. We will use reasonable verification and will not require you to create an account. An authorized agent may submit a request with evidence of authority where law permits.
Changes to this notice
We will not materially expand the collection, use, or disclosure of consumer health data without the notice and consent required by applicable law. The operator is SEASONS PRESENTS LLC, 118 Sierra Bonita Ct., Mapleton, UT 84664, United States. Questions and requests may be sent to privacy@womensdailycare.com.