Menu

Data, kept in proportion

Privacy policy

The information the site handles, why it is needed, who may receive it, and the choices available to you.

Effective August 11, 2026

Scope and operator

SEASONS PRESENTS LLC operates Women's Daily Care. This policy covers womensdailycare.com, go.womensdailycare.com, and services that link to this policy. The operator's business mailing address is 118 Sierra Bonita Ct., Mapleton, UT 84664, United States. Separate merchant, social platform, affiliate-network, and advertiser services have their own privacy practices.

Because the publication discusses daily care and health-adjacent topics, we apply a heightened privacy posture even when information may not legally qualify as health data in every jurisdiction.

Information we collect

Women's Daily Care currently offers no accounts, forms, quizzes, symptom tools, community posts, or newsletter enrollment. Publisher pages do not run advertising tags. The Phase 1 reports at go.womensdailycare.com/report-cranberry and go.womensdailycare.com/report-cranberry-brief load Meta Pixel and send standard PageView and ViewContent events when a page loads and a custom OutboundClick event when a reader chooses a presentation link. Those events contain no Women's Daily Care custom parameters. Our browser code does not send Lead, InitiateCheckout, Purchase, or Upsell events.

Meta's Pixel code can process the page URL and query string, referrer, IP address, browser and device information, timestamp, and Meta identifiers, and can set or read Meta cookies such as _fbp and derive or use _fbc. The paid pages load this code without a separate on-page consent banner under the operator's initial United States campaign decision. The privacy choices below remain available, and the compensated route is unavailable in Washington, Nevada, outside the United States, or when an eligible location cannot be determined.

For a temporary page-usability review, those same Phase 1 reports send PostHog one fixed-schema pageview on each eligible visit and one fixed-schema handoff event when a reader chooses a governed presentation link. The custom fields are limited to a schema version, the fixed eligible report path and its corresponding fixed variant, and one allowlisted CTA-location label; they do not include query strings, referrers, source keys, fbclid, merchant URLs, form data, symptoms, or contact information. Session replay is separately limited to a 20% sample of visits lasting at least three seconds and is used to understand scrolling, layout problems, and interaction friction. All visible text, form inputs, and element attributes are masked; cross-origin frames and canvas content are blocked; console logs, network headers and bodies, performance capture, autocapture, heatmaps, surveys, and person profiles are disabled; and URL query strings and fragments are removed. The integration does not write PostHog cookies or local storage, does not load on other Women's Daily Care pages, and does not load when the browser sends Global Privacy Control or Do Not Track. PostHog receives an anonymized network request, the two named events when applicable, and sampled masked interaction data. Records use 30-day retention, and temporary collection is scheduled to stop by August 23, 2026 or after 50 useful mobile sessions are reviewed, whichever occurs first.

Cloudflare processes standard request and security data—including IP address, requested URL and query string, request headers, user agent, timestamps, and security or diagnostic signals—to deliver and protect the sites. Our application does not persist raw page requests, IP addresses, user agents, raw fbclid values, care-topic browsing tied to a person, or raw ClickBank postback payloads.

When a reader chooses the reviewed FemiCore merchant link, our managed redirect generates and stores a random Women's Daily Care click identifier with the offer, deployment stage, fixed page variant, whether a valid fbclid was present, and—when the landing URL contains one approved opaque source key—the corresponding source key. A small same-origin script copies only an allowlisted source key and one valid fbclid into the merchant-link request; it sets no browser storage and makes no separate network request. Missing, duplicate, oversized, or malformed values are discarded, and arbitrary UTM values are not copied. The redirect stores only whether fbclid was present—not its raw value—and passes the valid value unchanged to the verified FemiCore destination for ClickBank attribution. The random identifier is added as ClickBank's aff_sub1 value; the page variant and source key are not sent to the merchant.

Before permitting the merchant handoff, the application reads Cloudflare's approximate country and state or region code to apply the pilot's location rules. It does not add that location to the managed click record.

Our ClickBank integration can receive and store a minimized conversion record in Cloudflare D1: event type, event time, event identifier, receipt and order identifiers, affiliate and vendor nicknames, commission and transaction amounts, currency, ClickBank click identifier, the random Women's Daily Care click identifier, tracking type, environment stage, and receipt time. In production, the receiver accepts the record only when that identifier matches a production FemiCore click already recorded by our location-gated route. These records are sensitive by context because the offer identifier and conversion can reveal interest in or purchase of a women's-health product.

Separately, ClickBank's Facebook integration for affiliate tastemake is active and configured to send server-side InitiateCheckout, Purchase, and Upsell events to Meta using ClickBank's event, order, value, currency, and attribution data when the traffic source is marked facebook. ClickBank owns that server-side connection. Women's Daily Care does not send a Lead or Purchase from the paid page and does not forward its D1 click receipt or raw ClickBank postback record to Meta.

Sanity tooling is installed for a future governed build-time content workflow, but Sanity is not configured in the current production site and does not receive browser requests. Current publisher pages are generated from versioned, typed content in the site build.

  • Correspondence you choose to send to a published email address, including your address, message, and reply history.
  • Standard network, device, URL, header, timestamp, and security data processed by Cloudflare for delivery and protection.
  • Paid-report PageView, ViewContent, and OutboundClick event data processed by Meta, including standard browser and attribution information described above.
  • Fixed-schema PostHog pageview and presentation-handoff events on eligible Phase 1 visits, plus a 20% sample of masked scrolling, pointer, viewport, and page-interaction replay data, subject to the controls described above.
  • The minimized managed-click fields listed above, including an approved opaque source key when present, when a reader chooses a compensated FemiCore link.
  • Minimized ClickBank conversion fields listed above when its authenticated server-to-server postback is used.
  • ClickBank conversion and attribution data used by ClickBank to send the configured InitiateCheckout, Purchase, and Upsell events to Meta.

How we use information

We use information only for a documented purpose: deliver and secure the site; respond to requests; honor privacy choices; send requested communications; maintain editorial and affiliate records; measure paid-report visits and presentation handoffs; temporarily diagnose paid-report scrolling and interaction friction; attribute resulting transactions; detect abuse; comply with law; and establish or defend legal claims.

We do not ask for or send symptoms, diagnoses, quiz answers, form text, email addresses, or phone numbers through the Phase 1 paid reports. Meta receives the eligible fixed report URL and the limited events described above; general editorial care-topic pages and untracked report candidates remain outside this advertising flow.

When information is disclosed

Cloudflare processes request and security data for hosting, content delivery, protection, and the D1 conversion ledger. Meta processes the paid-report Pixel events described above. PostHog processes the temporary fixed-schema pageview and presentation-handoff events and the masked Phase 1 replay sample described above. ClickBank processes affiliate attribution, can send the minimized postback to our Cloudflare receiver when that separate connection is enabled, and sends the configured filtered server-side conversion events to Meta through its active Facebook integration. Porkbun forwards the published womensdailycare.com role addresses to the operator's business inbox. Professional advisers, authorities when legally required, or a successor in a properly governed business transaction may also receive information when necessary.

When a reader chooses the reviewed FemiCore link, FemiCore and ClickBank receive the browser request, a valid fbclid when present, and the random aff_sub1 click identifier. They control their own sites, cookies, purchase flow, and privacy practices. Because this paid measurement and compensated attribution exchange could be treated as a disclosure, sharing, sale, or targeted advertising under some laws, the initial outbound pilot is unavailable in Washington, Nevada, outside the United States, or when the application cannot determine an eligible location. Women's Daily Care does not send its D1 receipt or raw ClickBank postback record to Meta; ClickBank's separately configured Meta integration sends the downstream events described above. Any expansion requires an updated legal, consent, platform-policy, and data-flow review before activation.

Retention

Cloudflare controls retention for its essential delivery and security records under its service settings and terms. Meta controls retention for Pixel events and associated identifiers, and ClickBank and Meta control the server-side events sent through ClickBank's Meta integration, under their respective settings and terms. PostHog diagnostic events and session recordings use the shortest available 30-day project retention, and temporary collection is scheduled to stop by August 23, 2026 or after 50 useful mobile sessions are reviewed, whichever occurs first. Porkbun and the receiving mailbox retain correspondence under their respective settings. 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 it accepts another record. A lawful accounting, dispute, fraud, security, or preservation obligation may require a separately documented hold outside this operational ledger.

Your privacy rights

Depending on where you live, you may request access, correction, deletion, portability, or restriction; withdraw consent; object to certain processing; or opt out of sale, sharing, or targeted advertising. We will not discriminate against you for exercising a privacy right.

Send a request to privacy@womensdailycare.com. We may verify that you are the person connected to the request, may request authorization for an agent, and will explain any permitted denial and available appeal. The Your Privacy Choices page describes the request path and opt-out signals.

Security and minimization

Verified controls include HTTPS, restricted account credentials, separated callback secrets, strict provider and account allowlists, payload minimization, no application storage of raw page requests, raw fbclid values, or postback payloads, no Women's Daily Care forwarding of D1 records to Meta, and a route-limited PostHog configuration that allows only two fixed-schema events, masks sampled replay content, disables browser persistence and person profiles, and honors Global Privacy Control and Do Not Track. No system is perfectly secure, so we also minimize what the service receives and maintain an incident-response process.

Children and teens

The service is designed for a general adult audience and is not directed to children under 13. We do not knowingly collect personal information from children under 13. Paid campaigns and age-restricted product content will use the age controls required by law and platform policy. A parent or guardian may contact privacy@womensdailycare.com about information submitted by a child.

International readers

The initial service is operated for a United States audience. Access from another country may involve transfer to the United States, where privacy laws may differ. International expansion requires a separate territorial, transfer, cookie, and representative assessment before marketing to that jurisdiction.

Changes and contact

We will update this policy when the implementation, vendors, purposes, or law materially changes. The page will show the revision date, and material changes will receive an appropriate additional notice. Privacy questions and requests may be sent to privacy@womensdailycare.com. The legal operator is SEASONS PRESENTS LLC, 118 Sierra Bonita Ct., Mapleton, UT 84664, United States.