Cloudy CMS: Player App
Player App Privacy Notice
Effective date: 22 September 2026
Operator: Cloud By Day Group Pte. Ltd.. This notice covers the player application only. The full privacy policy covers the whole service, including the web dashboard, and lists every service provider involved.
1. What the app is
The Cloudy player is installed on display hardware owned and operated by a business. It plays media assigned from the Cloudy dashboard. The app has no end-user accounts and is not intended for personal use by consumers.
2. What the app sends
The app transmits the following to our servers (cloudycms.app) over an encrypted connection:
- Device identifiers: a device ID generated at linking, an authentication token, and an organisation ID. These identify the screen, not a person.
- Push notification token, used solely to deliver control commands such as sync content, set volume, or reboot.
- Technical data: platform type, screen dimensions, storage used, installed content version, sync results, and playback status.
- Network address at linking. When the screen is linked, we record the IP address of its network and use it to look up an approximate city, so the operator can recognise the screen in their dashboard. We keep both the address and the approximate area. No precise position is collected.
3. Camera
Some screens run an optional audience-measurement feature. It is off by default and must be switched on by the operating business for that specific screen.
During normal measurement:
- Camera frames are analysed on the device and discarded immediately. No image or video is transmitted or stored.
- No facial template or other biometric identifier is created. Nobody is identified, and a returning person cannot be recognised.
- Emotion and ethnicity are never measured. Age and gender are estimated only where the operating organisation has turned on audience demographics, on the device, as per-play counts in three age bands from 20 upward. No per-person record is kept.
- Only aggregate numbers leave the device: viewer counts and durations in milliseconds, plus indicators of how reliable the measurement was.
- The camera runs while content is playing, and briefly after it stops.
Neither images nor per-face geometry leave the device, at any time and by any route.
4. What the app does not collect
The app does not collect names, email addresses, contacts, stored photos, microphone audio, precise location, financial information, or browsing history from anyone near the screen.
5. Sharing
The push token is processed by Google solely to deliver control messages to the device. The linking IP address is processed by a geolocation provider solely to resolve an approximate city. The app checks for updates with our mobile-update provider, and playing YouTube content connects the screen to Google as any player would. Camera images during a remote check go to our storage provider only. None of this is used for advertising. The full list of service providers is in the main privacy policy.
6. Retention and deletion
Device data persists while the screen is linked. Unlinking archives the screen: it stops receiving content, but its record and history are retained so past reporting still makes sense. Permanently deleting the archived screen, or deleting the organisation, erases it. See data deletion to request removal.
7. Security
All data is transmitted over HTTPS. Authentication tokens are held in protected system storage on the device and are not exposed to other apps. On our side, a device token is held as a cryptographic hash once the screen has collected it.
8. Contact
Cloud By Day Group Pte. Ltd.
Data Protection Officer: dpo@cloudycms.app
General enquiries: support@cloudycms.app