> ## Content Index
> Fetch the complete content index at: https://www.discernibleinc.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Your Vendor’s Defaults Are Your Disclosures
- URL: https://www.discernibleinc.com/your-vendors-defaults-are-your-disclosures/
- Published: 2026-11-18T13:00:00.000Z
- Updated: 2026-11-18T13:00:00.000Z
- Description: When a vendor changes its defaults, your privacy promises change too. Google’s AI-or-no-Search choice for schools shows why to promise only what you control.
- Author: Melanie Ensign
- Tags: Privacy Communication

When a vendor changes its defaults, every customer that has to explain those defaults to someone else inherits both the change and the challenge of reconciling it with any promises they’ve already made.

Earlier this month, Google said it would turn off Gemini, Gemini Notebook, Gemini in Classroom, and Google Search for K-12 student accounts until school administrators turn them on. Schools can turn each one on separately, but the Search Google will offer schools includes AI Overviews and AI Mode, and Google hasn't described a version without them. Google told [The New York Times ](https://www.nytimes.com/2026/11/03/us/google-search-schools-restrict-ai.html?ref=discernibleinc.com)that students in schools that ban AI will not have access to search. Google frames this as giving schools "more choice.” Mmmm, k. 

Most of the coverage to date has focused on the tradeoff itself. I want to focus a moment on what happens next as thousands of districts pick a setting, and then assume the responsibility of explaining what it means to families. Every one of those communications will make a claim about how Google’s product behaves.

## **One announcement, thousands of explanations**

The vendor only has to announce a change once, but customers have to explain it thousands of times, to people the vendor will never talk to (but whose data they collect).

Obviously, school districts don’t write Google's terms or develop its products, but for better or worse, they’re best positioned to tell parents what their children's accounts can and can't do (how convenient for vendors, huh?). When a district says something like "AI is off for grades K through 8," families don't read that as a description of a setting Google created, but as a promise from the district.

This issue isn't unique to schools. In fact, security and privacy teams make these claims constantly in trust centers, security questionnaires, privacy notices, and customer emails. Many of the statements that these assets assert describe vendor systems — and vendors can change, misconfigure, or reclassify without asking you. When that happens, people come to you with questions, not the vendor.

## **Private information has co-owners**

Sandra Petronio's [Communication Privacy Management theory](https://api.pageplace.de/preview/DT0400.9780791487853%5FA40633703/preview-9780791487853%5FA40633703.pdf?ref=discernibleinc.com) describes how when you share private information with someone, they become a co-owner of it, meaning they’re expected to follow agreed rules about who else gets access and how. Petronio calls it boundary turbulence when a co-owner breaks those rules, through a mistake, a misunderstanding, or a choice. I’ve used a similar classification when it comes to security and privacy incidents: [hiccups, f\*ckups, and give ups](https://www.discernibleinc.com/what-is-a-security-or-privacy-incident-hiccups-f-ck-ups-and-give-ups/). 

*Note: We’re talking about stakeholder expectations here, not legal definitions. Even if the law says you’re not the owner, that doesn’t define public perception.* 

In a vendor relationship, the rules people expect you to follow include your contract, the vendor's terms, and the settings you configured. The family, customer, or employee who trusted you with their data never sees those rules. What they do see is how you described them in any proactive or reactive communications.

That creates an asymmetry where vendors control the system, but you control the promises. When turbulence hits, a vendor can fix its code, while you have the more difficult challenge to repair relationships, and you have to do it with people who put trust in you, not the vendor. 

## **What could go right: promise what you control**

In my previous post “[What Could Go Righ](https://www.discernibleinc.com/what-could-go-right/)t,” I made the case for asking what could go right, not just what could go wrong. Here’s what that looks like for vendor promises. You can’t control the vendor’s product or business decisions, but you can control what you promise.

To illustrate this point, statements in the left column below are examples of things that can be rendered invalid the moment your vendor breaksdown while statements in the right column can survive because they describe what you did and what you'll keep doing, regardless of the vendor. It also commits you to checks that can catch future failures, which is really what gives the promise value.

Remember, not to hedge by making claims more vague – they’re not helpful in earning credibility or trustworthiness. Instead, be more specific about who did what and how you'll know if it's still true.

| A claim about the vendor                               | A claim about you                                                                                                           |  |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- |  |
| AI is off for students in grades K through 8.          | We turned AI off for grades K through 8, and we check that setting at every level each month.                               |  |
| Customer data is encrypted at rest.                    | We require encryption at rest in every vendor contract, and we verify it during our annual review.                          |  |
| Our provider doesn't use your content to train models. | We reviewed our provider's terms, and they say your content isn't used for training. If those terms change, we'll tell you. |  |

## **When the vendor removes the middle option**

A bundled choice is still a choice, but it's often not the one people think they're making. Most of the time, our job is to make the trade visible to the people who have to decide.

That actually starts with a vendor’s terms, not their product features. For example, [eWeek reviewed](https://www.eweek.com/news/google-search-schools-reject-ai/?ref=discernibleinc.com) Google's education service classifications and found that Search falls under Additional Services, unlike Classroom and Gemini for Education, which are Core Services. For a district, that differantiation decides which agreement governs students' searches, and a school board or administrator weighing "Search with AI or no Search" needs to understand that distinction before it votes.

At the very least, a useful briefing for decision-makers answers the following questions for each option:

1. What do students, customers, or employees gain?
2. What do they give up, including data handled under terms you didn't negotiate?
3. What will you have to tell them, and can you keep that promise if the vendor changes something again?

This process doesn’t require you to take a public position against a vendor and you may still end up choosing their product, but it does require you to be honest with the people deciding, so they choose knowing the real terms — that’s the part your organization will ultimately be responsible for. 

## **Read your vendor's defaults like they're yours**

Go through your trust center, privacy notices, and questionnaire answers as soon as possible. Mark every sentence that's really a claim about someone else's system, and suggest a rewrite that makes it a claim about what you did. Then put a regularly-scheduled check-in on your calendar to make sure it’s still true over time.

To the people you answer to, your vendor’s defaults will end up being your disclosures. Best to get ahead of that now. 

---

*Want to practice this? This week's Discernible Experience puts you in a school district's privacy office after a vendor bug breaks a promise to families.* 

*Click *subscribe* at the top of the page & sign up for our weekly Discernible Debrief newsletter to access our scenario library and get new scenarios delivered to your inbox every week.*