Cookie & Similar Technologies Policy

1. Executive summary

Today’s static deployment prioritizes deterministic HTML hydration avoidance. Judaica Advisor minimizes client-side trackers; infrastructure cookies set by Cloudflare, cryptographic session renewals during edge challenges, ancillary bot intelligence may nonetheless appear transiently outside our direct authoring control. This document inventories known classes, distinguishes first vs third contexts, previews future CMP governance if experimentation analytics launch.

2. Categories we conceptualize—even if dormant

2.1 Strictly necessary & security-adjacent

Transport layer tokens, ephemeral anti-bot validations, cryptographic nonces guarding form endpoints when forms exist—classified “strictly necessary” under ePrivacy-informed frameworks when proportionate. Denial degrades resilience against volumetric scraping or sabotage—we treat inability to differentiate humans/bots under DDoS as existential hosting risk mitigation.

2.2 Performance / diagnostics & aggregated analytics

Live: GA4 loads via Google’s hosted Google tag (gtag.js) referencing measurement ID G-CP2D7768K0. Storage / cookies attributable to tagging follow Google Analytics terms and Privacy Policy—we review retention defaults periodically. Suppress tagging through browser defenses if your jurisdiction affords that choice knowing aggregate reporting may distort internal editorial prioritization dashboards only.

Roadmap: Lightweight first-party Real User Measurement snippets (potential future) capturing LCP attribution or CLS deltas remain opt-in behind consent tooling where mandates apply. Retention horizons target ≤13 months aggregates unless narrower regulatory caps emerge.

2.3 Optional marketing / personalization (not presently launched)

No remarketing drip campaigns or cross-site personalization pixels originate from Judaica Advisor at initial launch window.

3. Affiliate program cookies reside off-domain

When you affirmatively click monetized storefront CTAs embedded in matrices, retailers or affiliate routers may plant multi-domain cookies aligning commissions to publisher IDs. These cookies seldom remain under Judaica Advisor’s domain path—consult network dashboards (ShareASale, Awin, UpPromote, etc.) controlling cookie nomenclatures, durations, rotation logic. Our FTC-forward disclosure dossier cross-links methodological transparency but cannot enumerate every advertiser cookie variant—they mutate seasonally without notice upstream.

4. Browser signals

If we deploy granular toggles honoring Global Privacy Control (GPC) or analogous headers, changelog notes will annotate effective dates. Visitors may always limit third-party acceptance via hardened browser presets—understanding storefront checkout flows may degrade if requisite session cookies suppressed.

5. Localization & interplay with Privacy Policy

Interpret this Cookie Policy alongside Privacy Policy privacy principles on lawful bases / regional rights interplay. Divergence resolved in favor of the more permissive disclosures only where contradictory language existed inadvertently—consult counsel when conflicts suspected.

6. Change control

Annotated release notes summarize delta classes—especially when CMP UI surfaces or third-party analytic embeds materially expand beyond today’s CDN-only footprint.

7. Operational contact

Data protection escalations bridging cookie-specific queries: privacy@judaicaadvisor.com (mailbox monitored for privacy/CCPA inquiries—spam filters may delay routine notes).