Let’s talk about one sentence on Google’s privacy page, and the condition they bolted onto the end of it on the sixteenth of October.
For five years, that sentence read like this: we don’t show you personalized ads based on your content from Drive, Gmail, or Photos.
Read it again in your head, because that was a promise with a full stop at the end of it. Not a policy. A promise. It held from July 2021 through seventeen revisions of the same document without a single word moving.
As of the sixteenth, it reads: we don’t show you personalized ads based on your content from Drive, Gmail, or Google Photos, unless you choose to make data from these services available to other Google services that support personalized ads.
That’s the event.
No breach. No outage. No executive sweating under a committee’s lights. A bullet point in a legal document got a clause attached to it, and the clause points directly at the feature a lot of people switched on this year because it made their assistant smarter.
Here’s the mechanism, plainly.
Google has a thing called Personal Intelligence. You turn it on, and Search or Gemini gets to read your Gmail, your Drive, your photos, so it can answer questions with actual context instead of guesses. You ask it when your bond payment comes out, it reads the statement. You ask what that rash looked like last time, it looks at the photo. It’s genuinely useful. That’s why people opted in. Beta at the start of the year, wider rollout since.
The policy change says that if you’ve made that data available to services that support personalised ads — and Search does — then Search can process it “to personalize content, including ads.” A new explanatory note names Personal Intelligence by name.
Google’s line is careful. Ads won’t be based directly on your inbox or your photo library. Fine. But read what their own help page says the ads are based on: “summaries, excerpts, generated media, and inferences from your relevant media, emails, and files.” And then, in the same document, this: where an email or file is brief, or particularly relevant to answering the question, “the summary may just be the email or file.”
So the protection is a semantic gap between the raw thing and a compressed version of the raw thing. And Google’s own help page closes that gap in one sentence.
Now the part people are skipping past.
This is not a story about a company reading your email. Companies have been reading email for twenty years and mostly you knew. This is a story about purpose. You gave a permission for one reason. The permission got applied to a different reason. And the place where that expansion happened was not a conversation with you — it was a diff between two versions of a legal page, published on a Friday, effective immediately.
Nothing about that is illegal. That’s what makes it worth ten minutes of your morning.
Think about what is actually sitting in a person’s inbox.
The quote from the oke doing your paving, with the cash price at the bottom. The invoice from the specialist you saw in March and told nobody about. The letter from the school about fees going up. The bond statement. The message you typed to your brother three times and deleted twice before you sent it anyway. A confirmation for a flight you haven’t told your boss about.
That’s not a dataset. That’s the most honest diary most adults will ever keep, and they keep it by accident.
The machine doesn’t need to understand your soul. It needs your receipts. Receipts tell it what you’re about to spend on, worry about, hide, and cancel. That’s the whole commercial map, and it arrives pre-classified because you wrote it yourself in plain language to a person you trusted.
And understand the asymmetry here, because it’s the real injury. You can’t see the inference. There’s no page that shows you what Google decided you are based on the specialist’s invoice. You can’t correct it, you can’t contest it, and you can’t tell whether the ad you saw came from that or from something you searched in 2019. The profile exists. The person it describes has no access to it.
That is what “personalised” has always meant in practice. Personalised for them. Described to you.
So what’s the operator lesson, because I’m not here to make you feel bad about your Gmail.
If you build anything that touches customer context — and in 2026 that’s most businesses, not just tech companies — the thing you are now selling is not features. It’s the answer to a question your customer is starting to ask out loud: what exactly did you do with what I told you?
Write the purpose down in one sentence. Not a policy. A sentence a human would say. “We read your invoices to build your VAT return, and nothing else.” Then hold the line on that sentence even when the growth team asks for one more use case, because the second use case is where the trust dies and it always looks reasonable at the time.
Set an expiry on the access. Ask again next year. A permission that never has to be renewed isn’t a permission, it’s a permanent grant of authority that nobody re-examines.
And keep a receipt. Timestamped, plain language, something you could hand a customer if they asked on a Tuesday afternoon. If you can’t produce that in under a minute, you don’t have consent — you have a checkbox and a hope.
That’s not compliance theatre. That’s the one place where a small business can beat a giant, because the giant has already spent its credibility and can’t buy it back with an interface tweak.
If you want to check your own account, and I’d do it today rather than think about it: My Account, Data and privacy, Personalization settings, Manage Personalized Recommendations in Search services. That’s the page. Turn it off if you don’t want this, and know that turning off Personal Intelligence alone doesn’t do the same job — they’re separate switches, and the policy change lives in the space between them.
Here’s the thing that stays with me, though. The sentence didn’t get deleted. If they’d deleted it, someone would have noticed and there’d be a headline and a statement and a small apology. Instead the sentence is still there, word for word, and it means something different now.
A promise you can edit after the fact isn’t a promise. It’s a position. And positions move when the business needs them to.
So the question worth carrying out of this isn’t whether you trust Google. Trust is the wrong frame; it’s how we got here. The question is whether the permission you gave still describes what’s actually happening. If you can’t answer that in a sentence, you don’t have an answer — you have their answer.
Nobody’s going to email you about this one.
You have to go and read the diff.