The fact that most of these are capturing query parameters:

  "u": "https://www.google.com/search?q=target",

indicates that are capturing tons of authentication tokens. So this goes way beyond just spying on your browser history.

▲ cess11 6 hours ago | parent [-]

If a service is sending auth tokens as URL parameters, stop using it. Those are always public.

	▲	dangets 5 hours ago \| parent [-]
		I don't disagree with the advice (especially for long lived tokens), but query parameters are encrypted during transit with https. You still need to worry about server access logs, browser history, etc that might expose the full request url.