Cookie Infrastructure at Meta
summary
Meta enforces cookie behavior with a central cookie schema and a mandatory developer API that only allows reads/writes by inum identifiers so code can’t quietly set cookies, returns null for disallowed optional cookies, and lists TTLs for a one‑place 400‑day rollout. Third‑party control uses Content‑Security‑Policy headers served per request to block embeds when users decline, plus an internal mapping of first‑party domains (eg. fbcdn.net) and router changes that force full page reloads so CSP updates take effect. inum IDs provide an auditable inventory.
AI-written summary · about
chapters (5)
- 0:00Introduction and context
- 2:15Cookie consent challenges
- 5:13Implementing cookie schemas
- 10:13Managing third-party cookies
- 12:49Challenges and conclusions








