Security and privacy

Your video, handled the way your school decides.

GroundsWatcher works with your recordings wherever they're kept today, cloud or on-site. Detection and the second look run on the GroundsWatcher box on your network, and we build a fully local setup when you want one.

Engraved still life of a brass padlock and keys on a leather register beside a campus map.
Plate I. Keys on a few named devices, never a shared password.
Six commitments

What the school can count on.

  1. No. I

    Your recordings

    Your recordings stay wherever your school keeps them: a recorder on site, a cloud service, or both. You set how long they're kept.

  2. No. II

    By role

    Staff sign in with two-factor. Each role sees only what it needs.

  3. No. III

    Logged

    Every view, alert, verdict, export and setting change is written to a chained audit log.

  4. No. IV

    Your rules

    You pick which events run on which cameras, and when.

  5. No. V

    No face lists

    GroundsWatcher doesn't identify people. It never reads faces, and plate reading stays off unless you turn it on.

  6. No. VI

    Alerts

    Alerts go to the staff you name. The picture and clip open over your network or a private link.

Built to be harder to attack

Six design rules.

Here is how GroundsWatcher is designed to be harder to attack, in plain language.

  1. Rule I

    Cameras are not exposed

    We don't forward camera ports to the internet or run a public camera website. During setup we check for forwarded ports and cloud dashboards that were left on.

  2. Rule II

    Remote access uses keys

    Remote support runs on keyed access from a few named devices, never a shared password. Remove a device and its access ends.

  3. Rule III

    Four separate network zones

    Students and guests, staff, cameras and doors, and management are kept apart by default, so a student phone can't reach a camera.

  4. Rule IV

    Encrypted backups

    Backups are encrypted by default, with a second copy away from the closet, so a failed disk doesn't erase your setup.

  5. Rule V

    Least access

    Staff use the dashboard for everyday viewing. Remote access is for our checks and updates.

  6. Rule VI

    A fully local option

    For schools that want every recording and every model on their own equipment, we build the whole system on site.

The honest ceiling

What we harden, and how far it goes.

  • No connected system is immune to attack
  • A person with a key, or physical access to the closet, remains a risk
  • Staff passwords and phishing exposure are still the school's to manage. We can help reduce them
  • Network separation is done by us at install against a written checklist. GroundsWatcher doesn't change your firewall by itself
Student data

How GroundsWatcher handles student data.

GroundsWatcher handles cameras, doors, alerts and the network around them. Student records stay in the school's student information system, and GroundsWatcher stays off that system.

We design to keep student information out of the security system. We don't claim a FERPA certification, and no product alone makes a district compliant.

Found a security issue? Email hello@groundswatcher.com.

We acknowledge every good-faith report and won't pursue the people who send them. Our security.txt has the details. This website's forms collect only what you type in. See the privacy policy.

An invitation

See it on your own cameras.

We bring the box, set it up on the cameras and doors you have, and walk your staff through it.

The careful eye on every campus.