Is storing a position in a page anywhere close to "uniquely identifying a user"? I'm no expert but this seems fine?

I would like to contribute in this project.

Yes, it's more that it fails some online compliance checks, and given that I'm using shouldUpdateScroll to ignore the scroll position, it's also redundant. Perhaps this should be a feature request to update shouldUpdateScroll to be a more generic scrolling override option.

So this file is the relevant one: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-react-router-scroll/src/scroll-handler.tsx

As it's just a React context you should be able to override the default by providing your own Provider. Does that work?

I am not a lawyer, but I have worked quite a bit with the GDPR. There is no scenario where scroll position could be considered to be PII! That said, it is a reasonable feature request so if someone wants to contribute then please go ahead. Are you planning to do this, @devbhansingh ?

Hi, I'd like to take up this issue.

A ref doc about this subject: https://www.termsfeed.com/blog/gdpr-scrolling-not-consent/
As @ascorbic mentioned, I'm not a lawyer too and my understanding is the scrolling act on a webpage cannot be considered consent. This is a reasonable feature but not because of GDPR compliance.

It might be worth clarifying for all the non-Europeans, like myself, who were still confused after reading to this point. The implied issue here is that scroll position is kept in session storage and the implementation of that session storage is using cookies. So this is running afoul of a requirement that the user consent to the use of HTTP cookies.

Also, I'm not a lawyer. And whoever made this law wasn't a web developer ;)

Are there tests around this?