What data does an app-connected air purifier actually collect?
WiFi-connected air purifiers raise a fair data question. See what kind of data an app-connected unit typically involves and how it relates to PDPA.
Key takeaways
- App-connected air purifiers typically collect device usage data such as on/off times, fan speed and filter status, not personal health information.
- WiFi credentials and app account details are usually linked to the app account, not to the purifier itself.
- Whether PDPA considerations apply depends on whether data is linked to an identifiable individual, not on the mere presence of an app.
- Ask any supplier for their specific app's data policy before rolling out app control across multiple rooms.
- Check the app's own privacy notice for the most accurate answer, since practices can differ between brands and app platforms.
Why WiFi-connected units raise a fair data question
It is a reasonable question to ask. A device that used to be a simple on/off box is now connected to your office WiFi network, reporting status to an app, and potentially logging usage patterns over time. Anything that joins a network raises a fair data question, whether it is an air purifier, a smart lightbulb or a printer.
Facilities and IT teams have increasingly good reason to be cautious about what connects to the corporate network. Every connected device is a small addition to your attack surface, and every app is a small addition to your data footprint, even when the underlying purpose, in this case cleaner air, is entirely benign.
Raising the question before wider rollout, rather than after, is the right instinct. It costs nothing to ask a supplier what their app actually collects, and a supplier who takes the question seriously is a better long-term partner than one who waves it away.
What kind of data an app-connected unit typically involves
For a typical app-connected air purifier, the data involved usually falls into three categories. The first is device and network data: the unit's connection status, WiFi network name, signal strength and firmware version, needed to keep the app talking to the device reliably.
The second is usage data: on/off times, fan speed settings, sleep-mode scheduling and sensor readings such as PM2.5 levels if the unit has a sensor. This is operational telemetry about the machine, not about the people in the room.
The third is account data tied to whoever set up the app: an email address or phone number used to log in, and sometimes a device nickname the user chose, like Waiting Room or Consult Room 2. AIRE's WiFi-enabled models, such as the Classic 400S and Fillo Plus, use this kind of telemetry to let you monitor several rooms from one app.
What this typically does not include is anything about specific individuals in the room, such as patient or staff identities, unless your organisation chooses to name a device after a person, which is worth avoiding for this reason alone. Specifics vary by brand and app platform, so treat this as a general picture rather than an assurance about any one specific product.
How this relates to general PDPA considerations for a business
Singapore's Personal Data Protection Act applies to personal data, meaning data that can identify a specific individual, either on its own or combined with other information the organisation holds. Device usage logs and network diagnostics on their own generally do not identify a person.
Where PDPA considerations start to apply is if your organisation links that device data to individual staff or patients, for example by naming a unit after a specific person, or by combining app account data with your own HR or patient records in a way that could identify someone.
For most offices and clinics running app-connected purifiers, the practical exposure is small: you are managing equipment status, not personal records. That said, the app account itself, if tied to a staff member's personal email or phone number, is personal data about that staff member, and your organisation's usual PDPA practices should cover it the same way they cover any other work account.
This is general context, not legal advice, and your organisation's data protection officer is the right person to confirm how it applies to your specific setup.
Questions worth asking before rolling out app control further
Before extending app control to more rooms or more staff logins, a short list of questions is worth working through with whoever manages the rollout.
- What specific data fields does the app collect, and does the supplier publish a privacy notice that says so plainly?
- Is the data stored locally, on the supplier's servers, or both, and where are those servers located?
- Who at your organisation has access to the app account, and is that access tied to individual staff logins or a single shared account?
- Does the app allow you to name devices without referencing specific people, to avoid unnecessary personal data exposure?
- What happens to the account and its data if the staff member who set it up leaves the organisation?
None of these questions require a legal background to ask. They are the same due-diligence questions you would ask about any new connected equipment joining your network.
Where to check the specific app's data practices
The most reliable source for how a specific app handles data is the app's own privacy notice, usually available within the app itself or on the supplier's website. It should describe what is collected, why, and how long it is kept.
If a supplier cannot point you to a clear, specific privacy notice for their app, treat that as useful information in itself when comparing options. AIRE's app-connected products use Tuya WiFi integration for remote monitoring, and you can read about our certifications and company background on our about page if that context is useful when comparing suppliers.
Next step
Data questions are worth asking early, not after a rollout is already underway. For an honest look at what we do and do not claim about our products, including app-connected features, see our claims verification page.
Frequently asked
What kind of data does an app-connected air purifier typically involve?
It typically involves device and network data such as WiFi connection status and firmware version, usage data such as on/off times and fan speed, and account data such as the email address used to log into the app. It does not typically include information about specific individuals in the room, unless your organisation chooses to add that itself.
How does this relate to general PDPA considerations?
Singapore's Personal Data Protection Act applies to data that can identify a specific individual. Device usage logs on their own generally do not identify a person, but the app account login, if tied to a staff member's personal email or phone number, is personal data about that staff member and should be handled the same way as any other work account.
What questions should be asked before wider app rollout?
Ask what specific data fields the app collects, where that data is stored, who at your organisation has access to the account, and what happens to the account if the staff member who set it up leaves. A supplier with a clear, specific privacy notice makes these questions easy to answer.
Does turning off app control avoid data questions entirely?
Running a unit without connecting it to WiFi avoids app-related data questions, since there is no account or network connection to manage. The trade-off is losing remote monitoring across multiple rooms, which is the main reason clinics and offices with several units choose app control in the first place.
Related reading
Not sure which model fits?
Send us your room dimensions and we'll send back a free room-by-room Air Report — the air changes each space needs, and the unit that meets them.