Student Data Privacy in AI: FERPA and COPPA
FERPA and COPPA checks for school AI tools: vendor terms, approved model endpoints, student-data retention, and request records.
266 posts on industry verticals.
FERPA and COPPA checks for school AI tools: vendor terms, approved model endpoints, student-data retention, and request records.
FERPA applies to AI tools that touch education records. Here''s when the school official exception covers your AI vendor, and when it doesn''t.
Microsoft states that Copilot Studio is covered under its HIPAA Business Associate Agreement and permits agents to handle protected health information. That gives healthcare buyers a documented BAA path. The deployment still needs a route inventory, safeguards, access controls, connector review, audit evidence, and confirmation that every service touching PHI remains inside the agreement.
SpaceXSI publishes a BAA request path for customers using its APIs, and its Enterprise Terms require both an executed BAA and the Zero Data Retention-enabled API before protected health information is submitted. That public evidence establishes conditional API eligibility, not blanket HIPAA compliance for every Grok product. Healthcare teams must verify the executed agreement, order form, API route, ZDR status, subprocessors, customer controls, and exact workflow before sending PHI.
Zoom AI features can support a HIPAA-regulated workflow when the customer has a Business Associate Agreement with Zoom, the selected AI feature is available under that BAA, and the organization configures and governs the workflow. Availability can vary by feature. This guide separates the contract decision from the customer controls needed before protected health information enters a Zoom AI workflow.
Perplexity publicly describes its Enterprise offering as HIPAA compliant and its security program as using HIPAA-aligned safeguards. Those statements do not replace a signed Business Associate Agreement or identify the exact services and features covered by it. A healthcare organization should keep PHI out until it has the executed BAA, covered-service schedule, account configuration, data-flow map, and customer control evidence for the intended workflow.
Wealth-management AI requests should reduce household profiles to the fields an approved task needs, then verify the adviser, application, provider account and route before transmission. SEC Regulation S-P safeguards and FINRA guidance anchor this pre-transmission policy, while advice, supervision, records and provider-internal processing stay with their established owners.
Claude can support HIPAA-regulated workloads only when an eligible Anthropic commercial service is covered by an accepted Business Associate Agreement, HIPAA mode is activated where required, the chosen capability is included, and the healthcare organization applies its own access and audit controls. This guide follows one PHI-bearing request through those four gates and marks the exact limits of API enforcement.
ChatGPT can support HIPAA-regulated work only inside an eligible OpenAI product, under a signed Business Associate Agreement, with covered features and the healthcare organization's own safeguards in place. Consumer access and a generic enterprise subscription are insufficient answers for a deployment review. This guide traces a PHI-bearing request through the product, contract, feature, minimum-necessary, and audit checks that determine eligibility.
AI governance gives General Counsel a traceable path between a legal obligation, the policy approved to address it, and the evidence produced when employees or agents use an LLM. The legal team should own the interpretation, decision rights, privilege rules, and escalation triggers while security and engineering implement the controls.
AI procurement should define the evidence, control access, incident duties, model-change notice, data-use limits, and exit rights the business needs before vendor selection. The procurement lead owns a repeatable gate that converts AI risk requirements into scored evidence and contract terms, then hands production monitoring to named control owners.
Shadow AI in media and publishing can move confidential source material and embargoed copy into unapproved LLM services. Unpublished manuscripts and licensed assets can follow, as can legal-review notes. This article defines the editorial data at risk, separates input control from output provenance, and sets out request-level enforcement for authenticated HTTP AI traffic.