This policy pertains to the Orbit application utilised at check-in to a Starlight Express Room in hospital. To review Starlight's overall privacy policy, click here.
1. Data Collected and Used
This app collects minimal data necessary to perform its core functions. No personal information such as names, email addresses, or contact details is collected or stored.
1.1 NFC Card Information
Data Type: Unique Identifier (ID) from NFC cards.
Purpose: Used to log check-ins and display a welcome message for VIP users.
Storage: Temporarily stored and transmitted securely to the backend system.
1.2 Device and Network State
Data Type: Network connection status (Wi-Fi or mobile data).
Purpose: Used to verify connectivity before making API calls.
Storage: Not transmitted or stored.
Permissions Used: ACCESS_NETWORK_STATE.
1.3 Network and Nearby Device Usage (Simplified)
Purpose: The app checks for network connectivity and scans for nearby devices to support its core functionality (e.g., screen casting check-in status).
Data Handling: No personal or identifiable information is collected, stored, or transmitted during these operations.
Permissions Used: The app uses standard Android permissions to enable these features, but does not retain or share any data obtained through them.
1.4 Application Configuration Data (Stored Locally)
Data Type: Kiosk ID, Target Environment URL, Operating Mode (Read/Write).
Purpose: Used to identify the check-in terminal and server endpoint during API calls.
Storage: Stored locally on the device using SharedPreferences.
2. Data Shared
This section outlines the data transmitted to an external server.
2.1 Check-In Log Data
Data Shared:
NFC Card ID
Kiosk ID
Operating Mode (Read/Write)
A hardcoded name ("ANDROID Log")
How it's Shared: Sent via secure HTTPS requests to a Microsoft Dynamics CRM backend.
Purpose: To create a log entry for each successful NFC card scan, effectively checking in the VIP.
3. Data Sharing
No data is shared with third parties beyond the designated backend system. All transmissions are secure and limited to the check-in functionality.
4. Security
The app uses standard Android security practices to protect locally stored data. All API communications are encrypted using HTTPS.
5. User Rights
As no personal information is collected, user rights under applicable privacy laws (e.g., access, correction, deletion) are limited. Users may contact us here for any concerns or inquiries.