Telemetry & Storage

Cookie Policy

We employ lightweight, functional cookies and server-side telemetry to deliver sub-second page performance, measure ad attribution, and safeguard form security.

Last Revised: September 2026Applicability: All WebSocial Studio Properties

How WebSocial Studio Classifies Cookies

Strictly Necessary / Functional

Always Active

Essential for enabling page navigation, securing lead capture forms against CSRF attacks, and preserving your UI rendering state across Next.js sub-routes.

Examples: Session identifier tokens, CSRF security nonce, Load-balancer routing sticky cookies
Lifespan: Session or up to 24 hours

Analytics & Core Web Vitals

Performance

Anonymous telemetry measuring Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and device viewport dimensions via Google Analytics 4.

Examples: _ga, _ga_* (Google Analytics), Next.js internal route prefetch telemetry
Lifespan: Up to 12 months

Marketing & Ad Attribution

Campaign Measurement

Allows WebSocial Studio to measure ROAS on our case-study acquisition campaigns across Meta (Instagram/Facebook) and Google Ads.

Examples: _fbp (Meta Pixel), _gcl_au (Google Conversion Linker)
Lifespan: 90 days

How to Manage or Revoke Cookie Permissions

You have full autonomy over your browser storage. You can configure your browser to block third-party cookies, alert you when a cookie is placed, or wipe all cached telemetry upon closing your session.

  • Google Chrome: Settings → Privacy and Security → Third-Party Cookies.
  • Apple Safari: Preferences → Privacy → Prevent Cross-Site Tracking.
  • Mozilla Firefox: Settings → Privacy & Security → Enhanced Tracking Protection.

Questions Regarding Our Tracking Systems?

Reach out to our engineering team for technical disclosures regarding server-side CAPI or analytics pipelines.

contact@websocialstudio.comRead Full Privacy Policy