I did not want student names in the system

When I first started building Edventory, I did not want a single staff or student name in it. The plan was a completely agnostic platform that cared about devices and nothing else. No names, no rosters, nothing sensitive. Just hardware.

I held that line for a while, and then reality pushed back. To track repair costs honestly, you have to know who had the device when it broke. To do help desk work, you need to know who is asking. To manage a fleet across buildings, you need to connect devices to the people using them. The agnostic version was clean, but it could not do the job all the way, so the system grew to include people. That was the right call, and it changed my responsibility.

Once you hold names, you are holding sensitive data about kids, and in education that is not a casual thing. FERPA and COPPA are not boxes to check, they are the floor. I have watched the vendor world treat student data carelessly for years, and I did not want to be one more company doing that.

So the way Edventory handles people is shaped by that. Bringing data in is meant to be controlled and purposeful. Syncing from your MDM and from Google makes setup painless, and it also means I am reading the roster you already maintain instead of building a second copy that lives forever. Data is encrypted. There is a retention purge so old data does not pile up indefinitely just because nobody got around to deleting it. The default posture is to hold what the work requires and not hoard the rest.

I started out wanting to hold nothing. I ended up holding what the job needs and treating the rest as a liability, not an asset. For student data, that is the right instinct to build on.