Insight into cookies used by Sanity.io and clarification on the purpose of the sanitySession cookie.
4 repliesLast updated: Mar 2, 2023
hey there, for german/eu law we need to soecifiy what every cookie does on a page. We fetch data from sanity on the fly and it seems that sanity stores some cookies in the frontend:• osano_consentmanager_uuid
• osano_consentmanager
• sanitySession
• _uetvid
Can someone give me some insights about what these cookies do?
• osano_consentmanager
• sanitySession
• _uetvid
Can someone give me some insights about what these cookies do?
Could you clarify where you’re seeing these cookies? I’m not seeing any of those. Edit: I am now seeing a
sanitySessioncookie after leaving the Studio open for a bit. The value looks like an auth token, but for me it doesn’t match up to my logged in user. I’ll see if I can find anything out.
Hi Christian. I found out from the team that a while back, some consent manager cookies were configured to
<http://sanity.io|sanity.io>(rather than the intended target of
<http://www.sanity.io|www.sanity.io>), so if you visited our website in that period, then you got these cookies. Depending on their expiry date, they’ll continue to show up for you on subdomains, but not for new users or once you clear them out. There is nothing being done with them on the API domains.
sanitySessionis your personal Sanity token.
Great, thats very good to know!
Many thanks for the quick reply, this makes sense
Was this answer helpful?
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
