SkillsAdd

thedaviddias/front-end-checklist

third-party-cookies

Use when reviewing a website for privacy compliance, third-party resource loading, or cookie consent implementation.

First seen Aug 11, 2026

Installation

$ npx skills add thedaviddias/front-end-checklist --skill third-party-cookies
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

setup-browser-cookies Similar name
garrytan/gstack

Import cookies from your real Chromium browser into the headless browse session. (gstack)

309 installs

Also in this package

Other skills from thedaviddias/front-end-checklist · top by installs.

npx skills add thedaviddias/front-end-checklist
frontend-checklist-global 96 color-contrast 22 animation-performance 22 https 19 pdf-size 18 word-count 18 image-optimization 18 cumulative-layout-shift 18 mobile-testing 18 quality 17

Browse all from thedaviddias/front-end-checklist

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 74.1K
License MIT
Default branch main
Open issues 5
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
category
privacy
priority
medium
difficulty
intermediate
estimatedTime
20
source
frontendchecklist.io
url
https://frontendchecklist.io/en/rules/privacy/third-party-cookies

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,327 B
  • docs SUMMARY.md 143 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 5 installs

SKILL.md

Avoid third-party cookies

Third-party cookies enable advertising networks to build detailed behavioral profiles of users across every site they visit — without users being aware. Regulatory penalties for non-compliance with GDPR reach up to 4% of global annual turnover.

Quick Reference

  • Third-party cookies are set by a domain other than the one the user is visiting — typically by ad networks, analytics, or embedded widgets
  • Chrome is removing third-party cookie support and all major browsers now block or restrict them
  • Use the Network DevTools panel to identify Set-Cookie headers from third-party domains
  • GDPR (EU), CCPA (California), and PECR (UK) require informed consent before setting non-essential cookies
  • Alternatives: first-party data collection, privacy-preserving analytics (Plausible, Fathom), server-side tracking

Check

Open the browser DevTools Network panel and Application panel (Cookies section). Identify all cookies set by domains other than the current domain. Check for tracking pixels, analytics scripts, and advertising tags that set cross-site cookies.

Fix

Audit and remove unnecessary third-party scripts. Replace cross-site tracking with privacy-preserving first-party analytics. Ensure any remaining third-party cookies are gated behind explicit user consent via a cookie consent mechanism.

Explain

Explain what third-party cookies are, how they enable cross-site tracking, why browsers are blocking them, and how GDPR/CCPA regulate their use.

Code Review

Review server config, headers, forms, and integration points related to Avoid third-party cookies. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/privacy/third-party-cookies