Privacy Policy
Last updated: 11 November 2026
PolyWear consists of a Wear OS watch app and an Android phone companion app ("the apps"), developed by Niccolò Cavallini as an independent personal project. This policy explains what data the apps handle. In short: your data stays on your devices and goes only to ETH Zürich's eduapp service. The developer receives nothing.
What data the apps handle
- eduapp session credential. When you sign in through the phone app, your login happens on ETH Zürich's own login pages inside a web view. PolyWear never sees or stores your username or password. After login, the phone app reads the resulting eduapp session cookie and sends it to your paired watch.
- Your class schedule. The watch app uses that session to download your schedule (course titles, codes, types, times and locations) from eduapp.
Where the data goes
- Between your phone and watch — via Google's Wearable Data Layer, which transfers data directly between your paired devices.
- To eduapp.ethz.ch — the session credential is sent to ETH Zürich's eduapp service to request your schedule, and the phone may reload eduapp in the background to renew an expired session. This is the only server the apps contact.
The apps have no backend of their own and contain no analytics, advertising, crash reporting or tracking. No data is sent to the developer or any other third party.
Storage on your devices
- The watch stores the session credential encrypted, and caches the last fetched schedule so it can show it offline.
- The phone keeps the eduapp login session in its web view storage so it can renew the watch's credential without you signing in again.
You can delete all of this at any time by clearing the apps' data or uninstalling them.
ETH Zürich
Your login and schedule are processed by ETH Zürich under its own privacy policy. PolyWear is not affiliated with or endorsed by ETH Zürich.
Children
The apps are intended for ETH Zürich students and are not directed at children.
Changes
If this policy changes, the updated version will be published on this page with a new date.
Contact
Questions about this policy? Open an issue on GitHub.