Law Stack Exchange is a question and answer site for legal professionals, students, and others with experience or interest in law. It only takes a minute to sign up.
Sign up to join this community
Do I need a GDPR "coockie" banner if I implement not a unique identifier but only a naive counter?
My web app check a key presence in local storage. Key is the same for all. If it's not found - call /increment api (with no message or data at all) and create one. If it already exists - do nothing. Just like "warrant canary". I like to call it reverse personification.
The GDPR covers information that can be used to identify a person. But a mere counter does not offer this possibility.
Do not link database entries to this cookie. For the GDPR, it does not matter whether personal data is stored directly in the cookie, or is merely indexed by this cookie.
