SkieWho owns the data in Skie?
The customer owns the data. The organisation that uses Skie decides what is recorded about its students, devices and policies, who inside the organisation sees it and what is done with it. Skie holds it as a service provider to run the product. Put the exact terms in your agreement.
Skie is software the organisation uses. The structure you build, the students you add, the policies you write and the records the devices produce belong to your organisation. Skie runs the service and looks after the infrastructure, but it does not take ownership of your records.
In data protection terms this normally makes the school the controller and Skie a service provider acting on its behalf. The contract between you should say so, including what Skie may do with the data, how long it is kept after the agreement ends and how you can get a copy.
That last point deserves care. A downloadable backup and the lost-device police report are available today, but a full export of an organisation's data is not available yet. The team is working on it. If an exit plan matters to you, ask for the process in writing.
Ownership also brings responsibility. The organisation is responsible for the notices it gives, the consent it collects, the roles it assigns and the requests it answers. Skie provides the controls: roles, page access, audit log, the narrow data set and the India region storage for the enterprise product.
A practical tip: when you read your agreement, look for four things in particular. Who owns the data, what Skie may use it for, how long it stays after you leave and how you get it back. If any of the four is vague, ask for a clear sentence.