A WA parliamentary question probes the privacy implications of an app provided by an Indian company on the Patient Entertainment System, focusing on data access and procurement processes. The response confirms data access possibilities and lack of local procurement rationale.

AnsweredQoN 5732Legislative Assembly
Asked
13 November 2019
Portfolio
Deputy Premier; Minister for Health; Mental Health

QuestionView source ↗

I refer to the response to Question on Notice 5480 in relation to the apps provided by IDZ Digital Pty Ltd on the Patient Entertainment System, and ask: (a) Will the Minister table the Incoming Sponsorship Authorisation Form; (b) Can the Minister confirm this company is established in India, and if so why a local company was not chosen; and (c) Can the Minister confirm whether IDZ Digital is provided with any of the following details as per their privacy policy, as a result of the app being on the Patient Entertainment System: (i) IP address and computer/mobile device identifiers (such as device ID, advertising ID, MAC address and IMEI); (ii) Data about the device, such as device name and operating system, browser type and language; (iii) Data collected with advertising cookies; (iv) Coarse location data (country or city-specific); (v) Demographic data (such as to determine the coarse location of IP addresses); (vi) Data for advertising and analytics purposes; and (vii) Patient identifying data (names, ages, genders etc.)?

AnswerView source ↗

Answered
11 February 2020
Response time
6 days
I am advised:
(a) Yes. See tabled paper no.
(b) Yes; reason unknown.
(c)(i) Content can read: Device ID, IMEI, Advertising ID.
Content cannot read: MAC address.
(ii) Content can read: Device Name, Operating System, Browser Type, Device Language.
(iii) This is possible, given current permissions.
(iv) Content can read: Coarse Location (city specific).
(v) No.
(vi) This is possible, given current permissions.
(vii) No.

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.

Explore more