Merge pull request #5686 from segmentio/jfoskin-patch-7

device mode cookie-validity-update.md

Author: pwseg

src/connections/sources/catalog/libraries/website/javascript/cookie-validity-update.md

@@ -46,6 +46,10 @@ analytics.load('writeKey', {
 > info ""
 > Chrome has a maximum limit of 400 days for cookies. If a value is set beyond that, then Chrome sets the upper limit to 400 days instead of rejecting it. Visit Chrome's [docs](https://developer.chrome.com/blog/cookie-max-age-expires/){:target="blank"} to learn more.
 
+### Device-mode destination cookies
+
+Segment doesn't control cookie management for device-mode destinations. As a result, the way cookies are used and managed is solely determined by each individual SDK. For example, if you have concerns about destinations setting third-party cookies, Segment recommends that you consult directly with the destination providers for clarification. For instance, Amplitude, one of the destinations in the Segment catalog, provides an informative [article on this topic](https://www.docs.developers.amplitude.com/guides/cookies-consent-mgmt-guide/#abstraction-layer-for-storage){:target="blank"}.
+
 ### User settings
 
 Analytics.js automatically persists the user's ID and traits locally. You can override how and where the user ID and traits are stored when loading Analytics.js by passing in a `user` object to the load method.