A user agent SHOULD NOT send a Referer header field if the referring resource was accessed with a secure protocol and the request target has an origin differing from that of the referring resource, unless the referring resource explicitly allows Referer to be sent. A user agent MUST NOT send a Referer header field in an unsecured HTTP request if the referring resource was accessed with a secure protocol.
In other words, it's not guaranteed that this Referer header is set. One can of course choose to remove the query parameter.
Yes, that’s the part about interactions and consent. The intent then is to circumvent that? A case of those pesky matters of security and respect for human dignity getting in the way of SEO?
