However, Safari does not (currently) cap cookies set with the Set-Cookie HTTP header. Why? Because creating a setup that makes use of the Set-Cookie header requires developer resources and is always a deliberate decision how to handle first-party persistence. ITP’s main beef is against third-party JavaScript libraries executing code that repurposes first-party storage for something other than firs