SkieIs the connection between Skie and the managed devices encrypted?
Yes. Devices talk to Skie over HTTPS, and DNS lookups to the filter use encrypted DNS. On top of that, policy bundles are signed and device reports are signed with a per-device key, so content is protected as well as the connection. Wi-Fi profiles are stored encrypted.
Encryption in transit is the minimum for any device management tool, and Skie provides it. Sync traffic between the device and the Skie service goes over HTTPS. DNS lookups go to the filtering service over encrypted DNS, which also stops a network from reading or changing them on the way.
Encrypting a connection does not by itself prove who is on the other end, or that the message is intact. That is why the content is also signed. Each policy bundle carries a cryptographic signature that the device verifies, and each report from the device is signed with that device's key.
At rest, Wi-Fi profiles that admins store for provisioning are held encrypted. Data for the enterprise product is stored in an India region, Mumbai, on Google Cloud, and nightly backups run. Access depends on the roles the organisation grants, and Skie owners and technicians can see data for support, as set out in your agreement.
Android itself encrypts device storage by default on modern versions, so a device that is lost is not an open book. Skie does not include a screen-lock requirement setting yet.
Practical tip: if your IT security team wants documentation, ask for it during the pilot. Be specific about what you need, such as where data sits, who has access and how keys are handled, and expect an answer based on the agreement, not a generic brochure.