When a university issues you a Google Workspace or Microsoft 365 account, it feels like a personal account. It has your name on it. You use it for email. You store documents there. But the account belongs to the institution, not to you — and that distinction has real consequences for what university IT departments, administrators, and legal counsel can access.
Every year, students store personal files in institutional cloud storage without understanding what they’ve consented to. And every year, students are surprised when those files become relevant in disciplinary proceedings, Title IX investigations, or legal matters.
This guide explains what institutional cloud storage can see, what the law does and doesn’t protect, and how to keep genuinely personal files separate from university-managed systems.
The FERPA Problem: An Outdated Framework for Cloud Storage
The primary federal law governing student privacy is the Family Educational Rights and Privacy Act (FERPA), enacted in 1974. It was written for paper records in physical file cabinets. It has not been substantially updated for an era where students’ entire academic and personal lives pass through cloud-based platforms.
FERPA protects educational records — grades, enrollment status, disciplinary records, and related institutional data. It does not comprehensively protect:
- Personal files you store in a university-issued Google Drive
- Emails sent through your university email account
- Documents in university-issued OneDrive or SharePoint
- Files uploaded to university learning management systems like Canvas or Blackboard
The legal theory applied by most institutions: the cloud storage account is a service the university provides for academic purposes, and the university as the account administrator has access to the contents.
Courts and administrative bodies have generally upheld institutional access to university-provided cloud accounts in disciplinary and legal proceedings. Your .edu cloud account is not your private cloud account, even when it contains personal content.
What Universities Can Actually Access
University IT departments and administrators can typically access:
Email: Institutional email accounts are almost always accessible to the IT department and can be subject to legal holds or preservation orders in litigation. University counsel may review email contents in response to subpoenas, public records requests, or internal investigations.
Cloud storage files: Google Drive and OneDrive files on institutional accounts are accessible by administrators. Google Workspace for Education provides an admin console that allows IT staff to access any user’s content. The same is true for Microsoft 365 education accounts.
Learning management system submissions: Anything submitted to Canvas, Blackboard, Moodle, or similar systems is retained by the institution. This includes drafts, revisions, and version history, not just final submissions.
Shared documents and collaboration history: Version history, comment threads, and collaboration logs in institutional Google Docs or Office files are accessible to administrators and subject to institutional retention policies.
Accounts on devices enrolled in university MDM: If you use a university-owned laptop, or enrolled your personal device in the university’s mobile device management (MDM) system for email access, the MDM profile may give the institution broader access than you realize.
The Shadow Data Problem in Higher Education
A 2026 report from EdTech Magazine identified a growing problem in universities: shadow data. This refers to institutional data — student records, grades, personal identifiers — that ends up in personal cloud accounts, personal devices, or unsanctioned applications because students and faculty find unofficial tools more convenient than official ones.
The problem flows both ways. A student who stores a personal journal in their university Google Drive creates shadow personal data in an institutional system. A professor who downloads a class roster to a personal spreadsheet creates shadow institutional data in a personal system.
For students, the practical consequence of shadow data is this: the separation between personal and academic life that you might assume exists in your cloud accounts probably doesn’t. Personal files in university storage are subject to institutional policies. Institutional data on personal devices creates its own liability.
The fix is structural: personal files should live in personal accounts. Academic files should live in institutional accounts. These should not be the same accounts.
Specific Situations Where Institutional Access Has Mattered
Disciplinary proceedings
Universities routinely access institutional email and cloud storage files in the course of disciplinary proceedings. Students who store personal journal entries, private correspondence, or notes about personal matters in their university accounts have found this content reviewed by administrators in ways they did not anticipate.
Title IX investigations
Federal law requires universities to investigate complaints of sexual harassment and related misconduct. In the course of these investigations, institutional accounts — including cloud storage — may be reviewed. Content that seems unrelated to the complaint may still be examined.
Subpoenas and public records requests
State universities may be subject to public records laws that require disclosure of institutional communications. A subpoena to the institution in civil litigation may capture email and file storage from institutional accounts.
Account termination at graduation
Your university account expires. Often 6-12 months after graduation, access is cut off. Any personal files you stored in that account are then inaccessible unless you download them first — and many students don’t realize this until it’s too late.
The Right Separation: Personal Files Go Elsewhere
The practical prescription is straightforward: treat your university account as a work account for academic purposes only. Keep your personal files — photos, journals, personal documents, creative writing, private correspondence — in a separate account that belongs to you, governed by terms of service you’ve chosen, rather than institutional policies you may never have read.
This separation matters most for:
Personal photos: Don’t store personal photos in your university Google Drive. Use a personal account or a dedicated private storage service.
Health and mental health information: Medical documents, therapy notes, health records you’ve scanned — these should not be in institutional storage.
Financial documents: Bank statements, tax forms, financial aid calculations with personal notes — personal account only.
Private writing: Journals, personal notes, creative writing, private correspondence — institutional systems were not designed for this, and you should not assume the privacy protections that a private system would provide.
Anything you wouldn’t want your Dean of Students to read: That’s an imperfect but useful heuristic.
Setting Up a Separate Personal Account That You Own
Several options exist for genuinely personal cloud storage:
- A personal Google account (separate from university-issued Google Workspace) has different terms and doesn’t come with institutional admin access. But Google’s broader data-use terms apply, including potential use for AI training.
- A personal iCloud account you control and pay for independently.
- A privacy-focused storage service that explicitly does not use uploaded content for advertising or AI training.
When choosing a personal storage service, the key questions: Who administers the account? Can they access your files? What do they do with your data after you upload it?
daftei is designed for exactly this use case: personal files that belong to you and only you. Files are encrypted in transit (TLS 1.3) and at rest (AES-256). The service doesn’t analyze your content, doesn’t use it to train AI models, and doesn’t sell data. It’s available on iOS, Android, and web — so it works alongside whatever devices your university issues. The 5 GB free tier covers most personal document and photo needs; Pro is unlimited.
Importantly: daftei is not an institutional service. Your university cannot issue an admin request to access a personal daftei account. What you store there is governed by your relationship with daftei, not your university’s IT policies.
Before You Graduate: The Download Checklist
If you’re in your final year, start the download process now. Universities commonly terminate account access 30-180 days after graduation.
From your university Google account, use Google Takeout to export your Drive contents. From university OneDrive, use the desktop sync client to download everything.
Then decide: does any of this belong in a personal, private archive? Notes from a class you loved, projects you’re proud of, records of your academic career — these may be worth keeping. If so, move them to a storage account you own and will keep past graduation.
Anything you want private and long-term — personal photos from college, journals, personal correspondence — make sure they’re already in a personal account, not waiting in institutional storage for an expiration timer you didn’t know was running.
What a University Education Doesn’t Include
A university education includes access to enormous resources — libraries, research databases, professional networks, infrastructure. What it doesn’t include is a private digital life. The accounts a university issues exist to support the academic relationship between you and the institution. They were never intended to be, and should not be treated as, your personal cloud storage.
Understanding this distinction — and acting on it — is one of the more practical things a student can do to protect their privacy during and after their time at university.