Questions to ask before rolling out connected air purifiers

Key takeaways

• A wider rollout raises the stakes on data privacy well beyond a single test unit
• Ask specifically what data the app collects and where it's stored
• Read the app's own privacy policy directly rather than relying on a sales summary
• Involve IT or compliance before scaling beyond a pilot
• Keep a written record of the answers for your own files

Why a wider rollout deserves more scrutiny than a single test unit

Some AIRE units, including the Classic 400S and Fillo Plus, offer WiFi app control, and the KJ100F offers app control as well, letting you monitor and adjust settings remotely. Testing this on one unit in one room is low stakes: a single account, a single device, limited exposure either way.

Rolling the same app out across every floor of an office, or every room of a clinic, changes the picture. Now you're asking multiple staff members to create accounts, potentially connecting the app to a shared office network, and generating a larger volume of usage data across the organisation. That's a reasonable point to pause and ask questions you might not have asked when it was just one unit on a desk.

This isn't specific to any one brand's app. It's a sensible step before scaling any connected device across a workplace.

Questions about what data the app collects and where it's stored

• What specific data does the app collect, beyond basic operating settings like fan speed and schedule?
• Is any data tied to individual user accounts, or is it aggregated at the device level?
• Where is the data stored, and does that location matter for your organisation's own data handling policies?
• Does the app share data with any third party, and if so, for what purpose?
• Can data collection be limited or turned off while still using core app functions?

A vendor should be able to answer these plainly. Vague or evasive answers to straightforward questions are themselves useful information when deciding whether to scale up.

Checking the app's own privacy policy directly

Don't rely solely on a sales conversation summary of what the app does with data. Read the actual privacy policy published by the app itself, since that's the document that legally governs what's collected and how it's used, regardless of what a verbal explanation suggests.

If the policy is vague, outdated, or hard to find, that's worth factoring into your decision independently of anything else about the product. A connected device is only as trustworthy, from a data standpoint, as the policy governing the app that controls it.

It's also worth checking who publishes the policy, the device manufacturer directly or a separate app platform the device connects through, since that affects who you'd actually be dealing with if a question or concern came up later.

Involving your IT or compliance team before scaling up

Whoever manages your organisation's data policies should review a connected device rollout before it happens at scale, not after. They're best placed to judge whether the app's data practices align with your organisation's own obligations, including how personal data is handled under Singapore's data protection framework.

This is a straightforward step to fold into procurement for any connected office equipment, not just air purifiers, and it's much easier to do before dozens of units and accounts are already in use than to retrofit a review afterward. Adding a short data-privacy checkpoint to your standard procurement process for any new connected device means this question gets asked consistently, rather than depending on whoever happens to be leading a particular rollout remembering to raise it.

Documenting the answers for your own records

Once you've asked these questions and reviewed the privacy policy, keep a written record of what you found and any conditions attached to the rollout. This becomes useful if a colleague asks about it later, if your organisation's data practices are reviewed, or if you're comparing this vendor against another in future.

A short internal note covering what was asked, what was answered, and what your IT or compliance team concluded is enough for most organisations, and it saves reconstructing the review from memory if the question comes up again down the line. Keeping this alongside your other procurement documentation also means a future audit or a new team member reviewing existing vendor relationships has a clear trail to follow, rather than having to start the whole review over again from scratch.

Next step

See our claims verification policy for how we approach honest, checkable statements about our products, including what our connected units do and don't do.

Frequently asked

Why does a wider rollout deserve more data-privacy scrutiny than a single unit?

Because scaling up means more staff accounts, potentially a shared office network connection, and a larger volume of usage data generated across the organisation, all of which raise the stakes compared with testing one unit on a single desk.

What questions should be asked about data collection and storage?

Ask what specific data the app collects beyond basic settings, whether it's tied to individual accounts, where it's stored, whether it's shared with third parties, and whether data collection can be limited while keeping core functions working.

Should IT or compliance be involved before scaling up?

Yes. Whoever manages your organisation's data policies is best placed to judge whether an app's data practices fit your obligations, and it's far easier to review this before a large-scale rollout than to retrofit a check afterward.

Which AIRE products offer WiFi or app control?

The Classic 400S and Fillo Plus offer WiFi app control, and the KJ100F offers app control as well. Other models in the range operate without app connectivity, so check the specific product page if this feature matters for your rollout.

Related reading

• How We Verify Our Claims