SkieWhat data does Skie collect from managed devices?
Skie collects what it needs to run device management: the device's identity, its location where the organisation has switched that on, the list of installed apps, its compliance status and the rules applied to it. It does not collect message content, call logs, audio, video or photos.
Think of the data in two groups. The first is identity: the device's IMEI, serial number and enrolment ID, linked to the student, group, school and organisation it belongs to. This is how Skie knows which device is which, and how it recognises a device that has been reset.
The second is status. Skie records which apps are installed, which policy and app list apply, whether each protection reads back as correctly applied, when the device last checked in and whether it has raised any breach events. Location is part of this where the organisation uses it. Insights, the daily analytics view, are built from these same status records.
What is left out matters as much. Skie does not read private messages, does not record audio or video, does not read call logs, does not capture photos and does not log what a student types. There is no hidden mode.
The organisation decides how much of the optional data it wants to use. A school that does not want location can leave it off. A school that wants it can limit who sees it through page access by role, and should tell families clearly. The organisation, not Skie, is responsible for the notices and the written policy that go with it.
A practical tip: write down your own list of data fields before you meet parents. Using the groups above, you can describe in four or five lines exactly what the device reports. Short and specific beats long and legal.
- Collected: device identity, location (if used), installed apps, compliance status, applied rules
- Not collected: messages, call logs, audio, video, photos
- No hidden mode on any device