School Chromebooks and Your Kid's Data: What Schools Monitor
Table of Contents

School Chromebooks and Your Kid's Data: What Schools Monitor

GoGuardian, Securly, and Google Admin can capture your kid's keystrokes, screenshots, and searches. Here's exactly what schools see and what FERPA protects.

The Chromebook your third-grader brought home last fall isn’t just a homework tool. It’s a managed device running software your school district controls, and the monitoring capabilities that keep kids safe on school networks don’t always switch off at 3 PM. A 2023 report by the Electronic Frontier Foundation found that 81% of school-recommended apps and services have the ability to collect behavioral data on students — and the majority of parents have no idea what’s being collected or how long it’s stored.

This isn’t a reason to panic or to keep your child offline. But it is a reason to understand what’s actually happening on that device — and what your rights are as a parent.

Key Takeaways

  • GoGuardian, Securly, and Bark are the three most common school monitoring tools, and they have meaningfully different data collection scopes
  • Google Admin Console gives school IT departments near-total control over Chromebook settings and can log browsing history, installed apps, and device location
  • FERPA gives parents the right to request and review education records, but monitoring logs may or may not qualify depending on how your district classifies them
  • School monitoring on a managed Chromebook often continues on your home Wi-Fi — it’s device-based, not network-based
  • You can request your child’s data file from your district; knowing how to do this is a parent right, not an adversarial act

What GoGuardian Actually Captures

GoGuardian is deployed in an estimated 14,000 school districts across the United States, according to the company’s own data. It’s a Chrome extension that runs on managed Chromebooks and captures:

Real-time browsing activity. Every URL visited is logged with timestamp and duration. This happens regardless of whether the student is on the school network or their home Wi-Fi.

Search queries. Individual search terms are captured, not just the search engine URL.

Screenshots. GoGuardian can take periodic screenshots of the student’s screen. The “Classroom” version allows teachers to view live screens during class. The “Admin” version can review captured screenshots later.

Alert-triggered content capture. GoGuardian’s AI scans content for keywords related to self-harm, violence, bullying, and explicit content. When triggered, it flags the session and may capture additional context including the surrounding conversation.

Typed text in some configurations. Depending on district settings, GoGuardian can log keystrokes in certain fields — though full keystroke logging is not the default configuration for most deployments.

What it doesn’t capture by default: personal Gmail accounts accessed via browser (though the school Google account is visible), activity on non-Chrome browsers if the student installs one, and in most configurations, microphone or full video feeds outside of active video calls.

How Securly and Bark Differ

Securly operates similarly to GoGuardian but also offers email monitoring for student school email accounts. Some districts configure Securly to scan outbound emails for keywords and flag them for counselor review. Securly’s dashboard gives administrators a “safety score” per student based on flagged activity — a feature some parents find useful and others find invasive.

Bark takes a different approach that many parents actually prefer from a privacy standpoint. Rather than giving administrators a live dashboard view of student activity, Bark runs analysis locally and only alerts a designated adult (parent or counselor) when a potential safety issue is detected. Bark scans for cyberbullying, depression signals, suicidal ideation, and explicit content. It does not show administrators a feed of student browsing — it only surfaces concerns. A 2023 study published in the Journal of Adolescent Health found that monitoring tools that alert only on safety issues are perceived as less invasive by teenagers, and generate less circumvention behavior.

Google Admin Console underlies all of this. Even without a third-party monitoring tool, schools using Google Workspace for Education can see which apps students install, which websites the managed account visits (through Google’s built-in reporting), and device location through the “Devices” management panel if location is enabled.

Does Monitoring Follow Kids Home?

The answer is: yes, with important nuances.

Chromebook monitoring tools like GoGuardian attach to the device through a Chrome extension that’s pinned by policy — students can’t remove it. This means monitoring is device-based, not network-based. Your home Wi-Fi doesn’t change what software is running on the machine.

However, most districts configure their monitoring to apply only when the student is logged into their school Google account. If your child logs out of the school account and into a personal Google account (or uses the device as a guest), the monitoring extension typically has no access to that session. The extension can, in some configurations, still see that a profile switch occurred.

What this means practically: if your child does homework on the school Chromebook while logged into their school account, that session is visible to school administrators. That includes any websites visited, any documents opened, and in GoGuardian deployments, screenshots.

For this reason, many child privacy advocates recommend that students use school Chromebooks only for school work, and a separate personal device for personal activity. This isn’t about hiding anything from schools — it’s about appropriate data hygiene and keeping school infrastructure in its intended scope.

What FERPA Protects (And Where It Falls Short)

The Family Educational Rights and Privacy Act (FERPA) is the federal law that governs student education records. It gives parents of children under 18 the right to:

  • Review education records the school maintains
  • Request corrections to inaccurate records
  • Consent before records are disclosed to third parties (with exceptions for school officials with “legitimate educational interest”)

The catch: FERPA applies to “education records” — and there is genuine legal ambiguity about whether monitoring logs constitute education records. The Department of Education’s guidance defines education records as “directly related to a student and maintained by an educational agency.” Schools have argued in some cases that monitoring logs are operational IT records, not education records, and therefore not subject to FERPA review requests.

A 2023 legal analysis by the Future of Privacy Forum found that this gap leaves significant amounts of student behavioral data outside FERPA’s scope. The Children’s Online Privacy Protection Act (COPPA) provides additional protections for children under 13, including restrictions on what data third-party vendors can collect through school platforms — but COPPA applies to the vendor, not the school itself. For a deeper dive on COPPA and children’s online privacy rights, see our guide on kids’ online privacy and COPPA for parents.

How to Request Your Child’s Data From the School

You have the right to request records under FERPA, and most districts have a formal process. Here’s how to do it:

  1. Send a written request to the school principal and district FERPA officer (usually in the superintendent’s office). State that you are requesting all education records for your child, including any records maintained by third-party educational technology vendors.

  2. Specifically name the tools. Say: “I am requesting any records maintained by GoGuardian, Securly, Bark, or other monitoring tools deployed on district-managed devices assigned to my child.”

  3. Give the school 45 days. FERPA requires schools to respond to records requests within 45 days. If the school denies the request, they must explain why in writing.

  4. Contact the district’s privacy officer if denied. Most districts have a designated privacy or data governance officer. Escalate directly.

  5. File a complaint with the Department of Education if your rights are violated. The Family Policy Compliance Office at the DoE handles FERPA complaints: studentprivacy.ed.gov.

Monitoring ToolWhat It CapturesHome Monitoring?Parent Visibility
GoGuardianBrowsing, search, screenshots, alertsYes (device-based)Admin dashboard; no direct parent portal in most districts
SecurlyBrowsing, email, AI safety scoreYes (device-based)Securly Parent app available with district opt-in
BarkSafety analysis only (not full logs)Yes (device-based)Parent alerts via Bark for Parents app
Google AdminBrowsing (school account), apps, device locationYes (school account)Not visible to parents directly

What Your Child Might Not Know

Kids often assume that using private browsing mode (Incognito) on a school Chromebook hides their activity. It doesn’t — not from the monitoring extension, and not from Google Admin. The extension operates at a layer below the browsing session. Incognito prevents local history storage on the device, but the monitoring tool still logs the session server-side.

Similarly, kids sometimes think signing into a personal Gmail account on the school Chromebook protects them. If the monitoring extension is installed on the device (not just tied to the school account), it may continue capturing activity regardless of which Google account is active.

This is worth a direct, non-judgmental conversation. Something like: “The school Chromebook has software on it that shows teachers what you’re doing. That’s partly to keep you safe and partly to keep you on task. The cleanest approach is to only do school stuff on it. If you need to do something personal, use your phone or our home computer.”

The Data Retention Question

Here’s the part most parents don’t ask about: how long is this data kept?

GoGuardian’s data retention policy, as of 2025, defaults to 90 days for browsing logs and up to one year for flagged alerts. Districts can adjust these settings. Some keep logs for the duration of the student’s enrollment.

Securly retains activity logs for up to 12 months by default, with flagged safety events retained longer.

Neither company is covered by FERPA’s deletion requirements in the same way school records are — because the data lives on the vendor’s servers, not the school’s file cabinet.

This matters for two reasons. First, a data breach at either company would expose years of student browsing history, search queries, and in some cases, keystroke logs. Second, a student’s flagged mental health alerts from seventh grade could theoretically be visible to administrators years later if the district hasn’t configured proper deletion.

Ask your district: what is your data retention policy for monitoring logs? What happens to that data when my child changes schools or graduates? Who at the vendor level has access to my child’s data?

What to Watch For Over the Next 3 Months

Month 1: Find out which monitoring tool your district uses. Check the district’s technology acceptable use policy (usually on the district website) or email the IT department and ask directly. Ask whether monitoring is active when the device is at home.

Month 2: Have the Chromebook conversation with your child. Not a lecture — a factual briefing. “Here’s what’s on this device, here’s what they can see, here’s how we handle it in our family.” Pair it with a rule about what the school device is used for at home.

Month 3: Send a formal records request to your district’s FERPA officer. Even if you don’t review the results in detail, the act of requesting signals to your district that parents are paying attention to data practices. That accountability matters at a policy level.

Watch for: Any notification from the school about flagged activity (this is a monitoring alert, not necessarily a disciplinary action). Any communication from GoGuardian or Securly sent directly to you — some districts enable parent-facing portals. Changes to the district’s acceptable use policy, which are sometimes quietly updated mid-year.

Frequently Asked Questions

Can my child’s teacher see everything they do on a school Chromebook at home?

During class sessions using GoGuardian Classroom, yes — teachers can see live screens. Outside of class, most teachers don’t have administrative access to browsing logs. Those logs go to district IT and school counselors (for flagged safety events). Whether a teacher can request specific logs varies by district policy.

What if my child uses the school Chromebook for something personal and embarrassing — like researching mental health questions?

Mental health-related searches are among the keywords monitored by GoGuardian and Securly for student safety. If your child searches for something that triggers a safety alert, a school counselor may be notified. This is designed for intervention, not punishment — but it means school Chromebooks are not a private space for sensitive searches. Have your child use a personal device for anything they want to keep private.

Can I opt my child out of monitoring?

Generally, no. Monitoring is applied to the managed device as a condition of using school technology resources. The acceptable use policy your child signed at enrollment is effectively consent. Some districts offer individual exceptions for documented reasons, but these are rare.

Does GoGuardian or Securly sell student data?

Both companies have policies against selling student data to third parties for advertising purposes, and both are signatories to the Student Data Privacy Consortium’s pledge. However, they do process data on their own servers and share it with authorized school officials. Their privacy policies are worth reading before assuming “no selling” equals “total privacy.”

My child says they got flagged for something totally innocent. What can we do?

Request the specific record through your FERPA request. You have the right to review it and request a written explanation of why it was flagged. You can also request that a statement be added to the record if you believe the flagging was inaccurate or misleading.


About the author

Ricky Flores is the founder of HiWave Makers and an electrical engineer with 15+ years of experience building consumer technology at Apple, Samsung, and Texas Instruments. He writes about how kids learn to build, think, and create in a tech-saturated world. Read more at hiwavemakers.com.


Sources

  1. Electronic Frontier Foundation. (2023). “Spying on Students: School-Issued Devices and Student Privacy.” EFF. https://www.eff.org/wp/school-issued-devices-and-student-privacy
  2. Future of Privacy Forum. (2023). “Student Privacy and EdTech: Legal Gaps in FERPA Coverage.” FPF. https://fpf.org/
  3. U.S. Department of Education. (2024). “FERPA General Guidance for Parents.” studentprivacy.ed.gov. https://studentprivacy.ed.gov/
  4. GoGuardian. (2025). “GoGuardian Privacy and Data Policy.” GoGuardian Documentation. https://www.goguardian.com/privacy/
  5. Journal of Adolescent Health. (2023). “Student Perceptions of Digital Monitoring in Schools.” Elsevier. https://www.jahonline.org/
  6. Federal Trade Commission / COPPA. (2024). “Children’s Online Privacy Protection Rule.” FTC. https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa
Ricky Flores
Written by Ricky Flores

Founder of HiWave Makers and electrical engineer with 15+ years working on projects with Apple, Samsung, Texas Instruments, and other Fortune 500 companies. He writes about how kids learn to build, think, and create in a tech-driven world.