SB 391 gives the Chancellor of the California Community Colleges the authority to create a data‑request fee policy covering access to individually identifiable data and student records held by the Chancellor’s office. The legislation requires that any such policy be reviewed and approved by the Board of Governors, updated periodically, posted prominently online, and written to comply with federal and state privacy rules.
The bill limits the permissible use of fees to recover substantial costs for compiling, extracting, or programming data and carves out exemptions for most state agencies, undergraduate and graduate students seeking data for their own studies, and community college faculty conducting individual research—while expressly allowing fees in certain research releases to the University of California, the California State University, or the State Department of Education. For compliance officers and research administrators, the measure shifts how data operations are funded and raises practical questions about definitions, fee design, and equitable access to state education data.
At a Glance
What It Does
Authorizes a Chancellor‑level fee policy for requests that seek individually identifiable or student data and binds that policy to board approval, periodic revision, public posting, and adherence to FERPA and California privacy law. It confines chargeable work to significant data compilation, extraction, or programming performed by the Chancellor’s office.
Who It Affects
Affects external researchers and private entities that request granular student data, the Chancellor’s Office (which must develop and administer the fee policy), and higher education research offices—particularly at UC, CSU, and the State Department of Education, which the bill treats differently from other state agencies. Undergraduate/graduate students and community college faculty are explicitly exempted from fees for their individual projects.
Why It Matters
The bill formalizes cost recovery for data provisioning, potentially shifting operational costs from the Chancellor’s office onto outside researchers or institutions while requiring governance and privacy safeguards. That changes budgeting incentives for data teams, could affect who can afford access to system data, and creates new compliance obligations around fee administration and privacy review.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 391 creates a permissive authority—not a mandate—for the Chancellor of the California Community Colleges to adopt a policy charging fees when researchers request access to individually identifiable or student data controlled by the Chancellor’s office. The statute confines billable activity to what it calls “significant data compilation, extraction, or programming” done by the office; in practice, that means the Chancellor can charge only where fulfilling a request requires non‑routine technical work that would otherwise impose a cost on the office or the requester.
Before charging any fees, the Chancellor must take the policy to the Board of Governors for review and approval, commit to periodic revisions, and publish the policy prominently on the Chancellor’s website. The bill ties the policy to existing privacy law: it must be consistent with FERPA and California Civil Code section 1798.24, so any fees and disclosures must be designed against that legal backdrop.
The measure does not prescribe fee schedules, caps, or timelines for processing requests; those operational details are left to the Chancellor’s policy development process.The statute sets out explicit exemptions. It bars fees to most state agencies but creates an exception that allows fees when data are released for research to the University of California, the California State University, or the State Department of Education.
It also prohibits charging undergraduate and graduate students seeking data for their own studies and community college faculty seeking data for individual research. Notably, the bill is silent on fee waivers, cost‑sharing arrangements, or how to handle commercial requests versus academic ones, leaving those tradeoffs to implementing rules.Taken together, the law provides a governance framework and legal guardrails but leaves substantial discretion to the Chancellor’s office over how to price access, how to define “significant” technical work, and how to operationalize privacy compliance.
For system data managers and researchers, the practical questions will be the forthcoming policy’s definitions, the structure of any fee schedule, and the administrative procedures for approving, billing, and contesting charges.
The Five Things You Need to Know
The Chancellor may adopt a fee policy that applies to requests for individually identifiable data and student data held by the Chancellor’s office.
Any fee policy must be reviewed and approved by the Board of Governors, revised periodically, and posted prominently on the Chancellor’s website.
Fees are limited to compensating the Chancellor’s office for “significant data compilation, extraction, or programming” required to fulfill a request.
The policy must comply with federal and state privacy statutes, explicitly naming FERPA (20 U.S.C. § 1232g) and California Civil Code § 1798.24.
The statute exempts most state agencies, undergraduate and graduate students doing individual studies, and community college faculty doing individual research—while permitting fees for releases to UC, CSU, or the State Department of Education.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Permissive authority to implement a fee policy
This subsection grants the Chancellor discretionary authority to put a data‑request fee policy in place; it does not require the Chancellor to charge fees. That permissive phrasing lets the office weigh the system’s budgetary needs and research priorities before deciding to adopt charges.
Board oversight, periodic revision, and public posting
Any policy the Chancellor develops must go to the Board of Governors for review and approval, must be revisited periodically, and must be made publicly accessible in a prominent location online. Practically, this creates a governance loop (policy design → board approval → public transparency) and gives the Board a checkpoint to shape fee structure and procedures.
Privacy compliance requirement
The policy must conform to federal and state privacy protections, explicitly calling out FERPA and California Civil Code § 1798.24. That requirement frames how the office must evaluate requests and structure any data releases, but the statute does not spell out technical or de‑identification standards.
Scope of recoverable costs
This provision narrowly ties fees to compensation for significant technical work—compilation, extraction, or programming—performed by the Chancellor’s office. It signals the legislature’s intent to allow cost recovery for non‑routine staff and IT effort rather than routine administrative tasks, but it leaves “significant” undefined.
Exemptions and the odd exception for certain higher‑ed recipients
Subsection (c) lists who cannot be charged: state agencies (generally), students (undergraduate and graduate) for their own studies, and community college faculty doing individual research. However, it carves out an exception permitting fees when data are released for research purposes to the University of California, the California State University, or the State Department of Education—an asymmetry that will matter to institutional research offices and budget planners.
This bill is one of many.
Codify tracks hundreds of bills on Education across all five countries.
Explore Education in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Chancellor’s Office: Gains a statutory mechanism to recover staff and IT costs tied to fulfilling complex data requests, which can help stabilize data operations without depending solely on general fund allocations.
- Community college students and faculty: Undergraduate and graduate students working on their own projects, and individual community college faculty researchers, retain fee‑free access to data covered by the statute.
- Board of Governors and public stakeholders: The requirement for board approval and public posting increases transparency around who pays for data services and how access is governed.
- System data users reliant on predictable access: Institutions that coordinate with the Chancellor’s Office may benefit if cost recovery funds are reinvested into faster, better data services.
Who Bears the Cost
- Independent and institutional researchers outside the specified exemptions: Non‑student academics, private sector researchers, and nonprofit investigators may face new fees for requests that require significant technical work.
- University of California, CSU, and State Department of Education research units: The statute explicitly allows fees for research releases to these entities, meaning they may shoulder charges for accessing Chancellor‑held data.
- Private companies and consultants: Firms seeking individuated data for analysis or product development may be required to pay for the Chancellor’s office’s technical work to prepare datasets.
- Chancellor’s Office administration: Developing, seeking board approval for, publishing, and periodically revising a fee policy will create administrative and legal workload that may require additional staff or contractor support.
- Small research projects with limited budgets: Projects that are neither student work nor faculty individual research could be priced out if fees are set to fully recover significant technical costs.
Key Issues
The Core Tension
The bill pits two legitimate goals against each other: preserving affordable, open access to public education data (particularly for students and individual faculty) versus enabling the Chancellor’s office to recoup real technical costs of preparing complex datasets; resolving that trade‑off requires implementation choices about definitions, fee design, and prioritization that the statute intentionally leaves to administrative policy.
SB 391 sets boundaries around when fees may be charged, but it leaves critical operational choices to the Chancellor’s forthcoming policy. The bill does not define key terms—most notably “significant” data compilation, “researcher,” or the technical meaning of “individually identifiable data” in this context—so the Chancellor’s policy will effectively set thresholds for when charges apply.
The statute also omits pricing methodology, fee caps, timing for billing and payment, and standards for dispute or appeal, which are predictable flashpoints in implementation.
Another tension arises from the exemptions structure. The broad exemption for state agencies with an explicit carve‑in for UC, CSU, and the State Department of Education creates an inconsistent treatment among public institutions that will require a policy rationale: why charge major public university systems but not other state agencies?
Finally, by permitting cost recovery the bill improves fiscal alignment but risks creating an access differential where well‑funded institutions can buy complex extracts while smaller researchers cannot. That trade‑off between equitable access to public data and sound cost allocation is unresolved in the text and will surface in practice as the policy is drafted and applied.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.