Is Google Gemini FERPA Compliant?

Google Gemini is not "FERPA certified," and it never can be, because FERPA issues no certification to any software company. Inside Google Workspace for Education, the Gemini app is a Core Service covered by the same agreement as Gmail and Docs, and Google states that agreement supports FERPA compliance. That contract, where Google acts as a data processor under the district's instructions, is what does the FERPA work, not a badge.

So the honest answer is conditional and specific: Gemini can support a district's FERPA compliance when the district's Workspace for Education agreement actually covers it, and the district stays the responsible party throughout.

Quick Answer: No FERPA certification exists for any vendor. Google says the Gemini app, now a Core Service in Workspace for Education since August 13, 2025, "supports compliance with industry regulations like COPPA, FERPA and HIPAA" under the Workspace for Education Terms of Service and the Cloud Data Processing Addendum, with chats not human-reviewed or used to train models. Google has no published FTC COPPA Safe Harbor for Gemini, and FERPA has no equivalent to hold. The district remains accountable, and the biggest gap is a student using consumer Gemini on a personal account outside the managed domain.

This guide stays on FERPA. For the consent analysis under the other main law, see Is Google Gemini COPPA Compliant?; for the admin-console settings a district configures, see Google Gemini and Student Data Privacy: What Teachers Should Know. Here the focus is the school-official exception, Google's role as a processor, and the three-product split that decides FERPA exposure.

Gemini's FERPA Answer Rides on Your Workspace for Education Agreement

Because the Gemini app became a Core Service, its FERPA posture is inherited from the Workspace for Education contract a district already signed, not negotiated separately. Google moved Gemini and NotebookLM into the Core Services category, on by default at the top-level organizational unit, starting August 13, 2025, unless an admin opted out beforehand (Google Workspace Updates, 2025).

Core Service status is a contractual fact, and it is the load-bearing one for FERPA. It places Gemini under the same Terms of Service, the same no-advertising commitment, and the same processing terms as the older apps a district has trusted for years.

• Same agreement. Gemini sits under the Workspace for Education Terms of Service, alongside Classroom, Gmail, and Docs.
• Same processing terms. The Cloud Data Processing Addendum governs how Google handles the data.
• Same data commitment. Google states chats with Gemini are not human-reviewed or used to train its models (Google for Education, 2026).

That inheritance is why the FERPA posture here closely mirrors the one Google Classroom already operates under: both are Core Services governed by the same Workspace for Education agreement, so a district that has worked through Is Google Classroom FERPA Compliant? has already done most of the contractual reasoning Gemini needs. The difference is that Gemini generates new content from a student's prompt, which makes the no-training and retention terms more load-bearing than they are for a tool that mainly organizes assignments.

What FERPA Requires, and Why Google Is a "Processor" Here

FERPA binds the school district and restricts disclosure of education records, and it lets an outside service touch those records only through the "school official" exception at 34 CFR § 99.31(a)(1). Google's contractual role is built to fit that exception, with Google acting as a processor under the district's control.

The School-Official Exception in Plain Terms

The exception lets a school share personally identifiable information from an education record with a vendor, without individual parental consent, only when four conditions hold together:

1. The vendor performs a service the school would otherwise run itself.
2. The school keeps direct control over how the data is used and maintained.
3. The data serves only the authorized purpose, not a separate commercial one.
4. Redisclosure is barred without the school's permission.

FERPA's accountability does not transfer with the data. Enforcement runs through the US Department of Education, the penalty is loss of federal funding, and there is no private right of action after Gonzaga University v. Doe, 536 U.S. 273 (2002).

Google as a Data Processor Under the Cloud Data Processing Addendum

Under the Cloud Data Processing Addendum, Google acts as a processor of the personal data a school submits through Workspace for Education, handling it on the school's behalf and under the school's instructions (Google for Education, 2026). Google also states that Workspace for Education can be used in compliance with FERPA and is audited by independent third parties.

That processor role is how Google stands inside the school-official exception: the district instructs, Google processes, and control stays with the district on paper. It is a contractual posture, not a government certificate, the same distinction that applies to every vendor's FERPA claim.

When a Gemini Session Creates an Education Record

A Gemini session inside a managed education account generates the prompt a student typed, the response the model returned, and account-level metadata, and once that data ties to an identifiable student it can be an education record under FERPA. The definition is the same one that governs a gradebook: information directly related to a student and maintained by the school or a party acting for it.

What that means in practice for a Workspace for Education deployment:

• A prompt and its response tied to a named student account are the raw material of a potential education record.
• NotebookLM grounded in a class's own materials can pull identifiable student content into the interaction, widening what gets stored.
• Account-level metadata ties the session to a specific, identifiable user over time.

Not every interaction rises to a formal, retained education record, and much of it is transient. But a district cannot assume a Gemini prompt is ephemeral just because it reads as conversational. The FERPA-safe stance is to treat identifiable prompts and outputs as records the agreement must cover, then confirm how long they persist and who can reach them.

This is exactly why the no-training commitment and the retention timeline matter so much for Gemini specifically. A record that is processed but neither trained on nor kept beyond its purpose is far easier to hold inside a district's control than one lingering indefinitely in a system nobody set a deletion schedule for.

There is also a quieter FERPA question in who at the district can see these records. Because Gemini is a Core Service, access controls run through the same admin console that governs the rest of Workspace, so reach into a student's Gemini activity should be scoped the way reach into their Docs or Gmail already is. A district that has never mapped who can open a student's Gemini history has a control gap to close, even with an airtight agreement, since FERPA cares about actual access, not just contract language.

Three Gemini Products, Three Different FERPA Exposures

"Is Gemini FERPA compliant?" has no single answer because Gemini reaches students through three distinct channels, and only two of them sit inside a district's Workspace agreement at all. Treating them as one product is the most common way a FERPA review goes wrong.

The third row is where the real risk lives. A student who opens consumer Gemini on a personal phone, signed into a personal Google account, is outside the Workspace for Education Terms of Service completely, so none of the FERPA processing commitments discussed here apply to that session.

The paid add-on, consolidated into Google AI Pro for Education on August 28, 2025 from the earlier Gemini Education and Premium products, is confined to staff and designated adult students (Google Workspace Updates, 2025). A district should confirm in its admin console that the add-on is not accidentally assigned to under-18 accounts, since that would widen the education-record footprint the license was scoped to avoid.

The 18-and-Older Gate Shrinks the Under-18 Education-Record Footprint

Google restricts content-generation features to users an institution has designated as 18 or older, which directly reduces how much of a younger student's activity becomes an education record in the first place. Inside Google Classroom, drafting assignment or lesson material with Gemini is limited to adult accounts, enforced independently of whether Gemini is turned on domain-wide (Google Workspace Updates, 2025).

Fewer generative features available to minors means fewer prompts and outputs tied to a child's account, and a smaller footprint of stored, identifiable data is easier to keep inside a district's control. The gate does real FERPA work by narrowing what exists to protect.

One caveat keeps that benefit honest: the gate only holds if the age classification behind it is correct. Google enforces the restriction against accounts a district has designated as 18 or older, so a student misclassified during a mid-year transfer can quietly land on the wrong side of it, gaining content-generation features a district assumed were closed. The FERPA consequence is subtle but real. A misclassified young account can generate and store more identifiable data than the district's record-keeping expected, which is why verifying age-based access groups belongs on the FERPA checklist, not only the safety one.

That gate is a product-design mechanism rather than a legal one, and the full breakdown of how it operates by age band lives in Is Google Gemini COPPA Compliant?. For FERPA purposes, the point is narrower: the less a young student's account can generate, the less education-record data a district has to manage under its agreement.

What to Verify in Your Own Workspace for Education Agreement

Since Gemini's FERPA support is inherited from the Workspace agreement, the real due-diligence work is reading that agreement, not the trust page. Google's general statements describe the product; a district's signed terms are what actually bind for that district.

Three things are worth confirming in writing rather than assuming:

1. Does the agreement explicitly name Gemini and NotebookLM as Core Services, or does it predate their August 2025 addition and need an update?
2. Does the no-training commitment cover Gemini prompts and responses specifically, not just the older apps like Docs and Gmail?
3. Is there a documented retention and deletion timeline matching the specificity the FTC's 2025 COPPA amendments now expect, effective June 23, 2025 with an April 22, 2026 compliance deadline (FTC, 2025)?

The evidence framework from the pillar guide, AI, FERPA & COPPA: The Complete School Data-Privacy Guide (2026), applies cleanly to Gemini.

Security certifications sit alongside these but answer a different question. Gemini has attained SOC 1/2/3 and ISO/IEC 27001, 27701, 27017, 27018, and 42001, plus FedRAMP High authorization (Google for Education, 2026). Those verify security management, not FERPA specifically, so they support a district's confidence without being a FERPA certificate.

For instructional materials that do not require a live chat interface, a teacher can sidestep the whole student-account question. EduGenius can generate quizzes, worksheets, and slides for Grades KG-9 from a class profile set by grade level and subject, with multi-format export to PDF, DOCX, and PowerPoint, so the content is built without a student ever prompting a generative model, which keeps that workflow clear of the education-record path Gemini's interactive tools raise.

A Gemini FERPA Checklist for a District Rollout

Work the question as a short sequence rather than a single verdict, and anchor it to your own signed terms. Say you teach Grade 9 English and your district confirmed Gemini went live domain-wide after the August 2025 default; the steps below are what protect the class.

1. Confirm your Workspace agreement names Gemini and NotebookLM as Core Services, not just the older suite.
2. Get the no-training commitment for Gemini prompts in writing, separate from the general no-advertising language.
3. Check the admin console's age-based access groups, since a student misclassified as 18-plus loses the content-generation gate silently.
4. Verify Google AI Pro for Education is restricted to staff and adults, not accidentally open to younger accounts.
5. Route school-related Gemini use through managed accounts only, since a personal Google account sits outside your FERPA agreement entirely.
6. Set a review date tied to contract renewal, since Google changed Gemini's education access model repeatedly across 2025 and into 2026.

Related Reading

• AI, FERPA & COPPA: The Complete School Data-Privacy Guide (2026)
• Is Google Gemini COPPA Compliant?
• Google Gemini and Student Data Privacy: What Teachers Should Know
• Is Google Classroom FERPA Compliant?
• Is Quizizz FERPA Compliant?
• SchoolAI vs Khanmigo: Which Is Better for Teachers?