[Lex Computer & Tech Group/LCTG] [ PFIR ] Gemini AI may already be enabled by default in your Gmail -- Google says it will share with law enforcement, etc. I DO NOT TRUST GOOGLE.

Sat Jan 17 09:53:26 PST 2026

1. What has changed in their policies?   This comparison (https://policies.google.com/privacy/archive/20250701-20251211?hl=en-US) suggests nothing I can see other than some tweaks to incorporate State privacy regulations.  You can go and look at prior terms of service and see they’ve been willing to share data with government and law enforcement since at least 2004 (https://policies.google.com/privacy/archive/20040701?hl=en-US)

2. How does turning off AI features affect their handling of our data?

I’m not saying that government surveillance isn’t a concern, or that the current administration might not be a particular concern, just that not much has changed as far as Google goes.  

> On Jan 17, 2026, at 11:06, OLGA P GUTTAG <opg1000 at rcn.com> wrote:
> 
> Though Google had our info since we started using their products, their stated policy was to protect any information they had about us from outsiders, including the govt. Now, as they happily cooperate with the current administration, if Trump decides to, say, deport all Chinese-Americans and needs to find some reason, getting all email/docs for these people from Google is pretty much guaranteed. 
> 
> So what is different now is Google’s change in how they protect our info.
> 
> Olga
> 
>> On Jan 17, 2026, at 10:39 AM, Adam Broun <abroun at gmail.com> wrote:
>> 
>> Google has always had access to Gmail, Docs etc in order to sell advertising.  And they’ve always been good at searching/indexing it.  So what's different now?
>> 
>> 
>> 
>>> On Jan 17, 2026, at 09:47, Stan Rose via LCTG <lctg at lists.toku.us> wrote:
>>> 
>>> If it's Gemini you want to avoid, then you will have to stop using SIRI because Apple has announced they will partner will Google to use Gemini in Siri.
>>> 
>>> https://www.macrumors.com/2026/01/13/google-gemini-siri-capabilities-report/
>>> 
>>> 
>>> Stan
>>> stan_rose at alum.mit.edu <mailto:stan_rose at alum.mit.edu>
>>> 
>>> 
>>> On Fri, Jan 16, 2026 at 11:13 PM OLGA P GUTTAG via LCTG <lctg at lists.toku.us <mailto:lctg at lists.toku.us>> wrote:
>>>> Lauren has also advised users to stay away from Google docs, since that is the next place they will start pushing Gemini. Sounds like moving everything away from Google is in my near future - SIGH.
>>>> 
>>>> Olga
>>>> 
>>>> 
>>>> 
>>>> > On Jan 16, 2026, at 10:26 PM, Drew King 65 via LCTG <lctg at lists.toku.us <mailto:lctg at lists.toku.us>> wrote:
>>>> > 
>>>> > I read about this last week. I've already gone into Gmail and turned everything off but thanks for telling everybody. I was going to send out a link that had instructions but your instructions are correct. 
>>>> > 
>>>> > I'm in the process of getting off gmail. I already have a new posting company for my email I just need to move the last month's worth of mail over to my new hosting company and update my DNS I plan on getting this done before the end of the month. 
>>>> > 
>>>> > Bye bye Gmail for me. 
>>>> > 
>>>> > I'm also moving towards encrypting all of my inbound mail on the mail server so even the new hosting company and Google can't read my mail . 
>>>> > 
>>>> > As far as Gemini is concerned I limit my use of it to questions regarding Google products mostly android. 
>>>> > 
>>>> > 
>>>> > ===============================================
>>>> > ::The Lexington Computer and Technology Group Mailing List::
>>>> > Reply goes to sender only; Reply All to send to list.
>>>> > Send to the list: LCTG at lists.toku.us <mailto:LCTG at lists.toku.us>      Message archives: http://lists.toku.us/pipermail/lctg-toku.us/
>>>> > To subscribe: email lctg-subscribe at toku.us <mailto:lctg-subscribe at toku.us>  To unsubscribe: email lctg-unsubscribe at toku.us <mailto:lctg-unsubscribe at toku.us>
>>>> > Future and Past meeting information: http://LCTG.toku.us <http://lctg.toku.us/>
>>>> > List information: http://lists.toku.us/listinfo.cgi/lctg-toku.us
>>>> > This message was sent to opg1000 at rcn.com <mailto:opg1000 at rcn.com>.
>>>> > Set your list options: http://lists.toku.us/options.cgi/lctg-toku.us/opg1000@rcn.com
>>>> 
>>>> ===============================================
>>>> ::The Lexington Computer and Technology Group Mailing List::
>>>> Reply goes to sender only; Reply All to send to list.
>>>> Send to the list: LCTG at lists.toku.us <mailto:LCTG at lists.toku.us>      Message archives: http://lists.toku.us/pipermail/lctg-toku.us/
>>>> To subscribe: email lctg-subscribe at toku.us <mailto:lctg-subscribe at toku.us>  To unsubscribe: email lctg-unsubscribe at toku.us <mailto:lctg-unsubscribe at toku.us>
>>>> Future and Past meeting information: http://LCTG.toku.us <http://lctg.toku.us/>
>>>> List information: http://lists.toku.us/listinfo.cgi/lctg-toku.us
>>>> This message was sent to rosesta at gmail.com <mailto:rosesta at gmail.com>.
>>>> Set your list options: http://lists.toku.us/options.cgi/lctg-toku.us/rosesta@gmail.com
>>> ===============================================
>>> ::The Lexington Computer and Technology Group Mailing List::
>>> Reply goes to sender only; Reply All to send to list.
>>> Send to the list: LCTG at lists.toku.us      Message archives: http://lists.toku.us/pipermail/lctg-toku.us/
>>> To subscribe: email lctg-subscribe at toku.us  To unsubscribe: email lctg-unsubscribe at toku.us
>>> Future and Past meeting information: http://LCTG.toku.us
>>> List information: http://lists.toku.us/listinfo.cgi/lctg-toku.us
>>> This message was sent to abroun at gmail.com.
>>> Set your list options: http://lists.toku.us/options.cgi/lctg-toku.us/abroun@gmail.com
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.toku.us/pipermail/lctg-toku.us/attachments/20260117/e5936618/attachment.htm>