If anyone's wondering how this works, it looks like[1] Gemini + guardrails:
> Google is proud to be named a technology partner in this vital initiative, leveraging Gemini to help more than 100 million people access critical public resources with greater speed and ease
I don't think an HTTP header would normally be considered "personal information", so I don't see why you imagine there would be a technical limitation here.
Personal information is not clearly defined so it can mean anything. My guess is the search request is not directly linked to a specific user but a session to which that session is linked to a user so there isn't an identifiable person making a search without some backend data matching.
sssilver · · focus · HN ↗
> Google is proud to be named a technology partner in this vital initiative, leveraging Gemini to help more than 100 million people access critical public resources with greater speed and ease
[1] <a href="https://blog.google/company-news/outreach-and-initiatives/public-policy/america-gov-google-public-sector/" rel="nofollow">https://blog.google/company-news/outreach-and-initiatives/pu...
hbcondo714 · · focus · HN ↗
I am left to wonder how this is technically accomplished. Is inference running in the browser? Is the model downloaded to the user’s machine?
zahlman · · focus · HN ↗
pizzafeelsright · · focus · HN ↗