SkieIs our data separated from other organisations using Skie?
Yes. Each organisation is its own tenant, and data, users and devices are kept apart so one customer cannot see another's. People see only their organisation, and within it only the part their role covers. Skie does not publish details of its internal architecture, so ask the team for specifics your security review needs.
A shared service has to keep customers apart. In Skie, your organisation is the top of your own structure, and everything under it, schools, branches, groups, students and devices, belongs to it. Another organisation using Skie has its own structure and cannot reach yours.
Inside the organisation, the separation continues by role. A class admin sees their group, a branch head sees the branch, a school admin sees the school, and the organisation admin sees the whole. Page access can be switched per role. Skie owner and technician roles belong to the Skie team for support.
Devices are identified individually. Each has its own key and identity based on IMEI, serial and enrolment ID, and policies sent to it are signed, so a device rejects anything that does not verify. That means a device cannot simply be told to follow another organisation's rules.
Your data is hosted on Google Cloud in an India region (Mumbai) for the enterprise product. See data stored in India. The third parties involved are the hosting provider and the DNS filter provider. The connection is encrypted with HTTPS.
What Skie does not do is make claims no honest provider can make. It does not say the system cannot be attacked, and it describes controls rather than guarantees. If you are running a formal security review, ask the team for the documentation they have, and read children's data and school devices for the data side of a school deployment.
Practical tip: review who holds organisation-level roles each term. Fewer people with the widest view is the simplest way to protect your own data.