Your data in Airloom.

Signing in with MyDyson

When you sign in, Airloom sends your email, password and verification code to Dyson’s authentication service for your selected account region. It uses the resulting session token to retrieve devices and local pairing information. If you select Include remote access, it also requests device-scoped Dyson cloud credentials.

Sign-in runs inside Airloom using macOS networking. Airloom does not save your MyDyson password, verification code or account token as a persistent account session. Dyson processes these requests under its own privacy practices.

Pairing and local control

Airloom stores your purifier’s identifiers, name, MQTT topic information and local connection credential, and optional remote credential in macOS Keychain. When you select Dyson cloud or Automatic in Settings, commands and readings travel through Dyson’s cloud over encrypted WebSockets. Your connection preference is saved per purifier. Automatic permits Dyson cloud fallback when local access is unavailable. The selected purifier preference is stored locally in app settings. Optional weekly schedules, their target purifier identifiers, requested settings and last execution results are stored on this Mac. Forgetting pairing also removes these schedules. Discovery information and reported controls are held in the running app. Sensor history and timestamps are stored locally for up to 30 days, indexed by purifier identifier. Use Clear history to delete it; forgetting pairing also removes the corresponding local history.

After pairing, Airloom discovers and controls purifiers over your local network. Local device communication uses the purifier’s MQTT protocol over TCP. Airloom has no Makepad cloud service for purifier readings and contains no advertising or tracking SDK.

Choose Forget paired purifiers to remove the saved Keychain pairing and disconnect sessions. This does not delete your Dyson account. The selected-device preference is separate from the saved credentials.

System controls and optional integrations

macOS controls communicate with the running app through a private local bridge. Fully quitting Airloom ends device connections and makes its integrations unavailable.

If you configure an MCP client, it can receive device identifiers, names, reported state, sensor readings, timestamps and control results, and can request device changes. Airloom does not include account passwords or device credentials in these responses.

Your chosen client may store tool results or send them to its provider. Its privacy policy and authorization settings apply. Review those settings before enabling the integration.

Support and this website

If you email hello@makepad.fr, Makepad receives the message, email address and any information you choose to include so that we can respond. Do not include passwords, verification codes or purifier credentials. Redact personal information from screenshots.

This website has no account form, advertising or application analytics added by Makepad. Its hosting providers process technical request information needed to serve and secure the site. Email and hosting providers also process information in delivering their services.

For questions about information you have shared with support, including a request to delete a support conversation, contact hello@makepad.fr. Dyson and your MCP provider manage requests concerning information held in their own services.

CSV exports

Export CSV saves sensor readings to a location you choose. These files exclude device identifiers and credentials. Exported files are not removed by Airloom’s history retention or Forget pairing; delete them yourself when no longer needed.

Changes

We will update this page when Airloom’s data handling changes. The date above identifies this policy version.

Optional notifications and updates

Notification thresholds, quiet hours, connection preferences and named presets are stored locally. Purifier-keyed cooldown timestamps limit repeated alerts. Notifications may display reading or filter information according to your macOS settings. Forgetting pairing clears presets, connection choices, cooldowns and delivered Airloom notifications.

Manual or opt-in automatic update checks request signed release information from airloom.makepad.fr. The hosting server receives normal request metadata, including IP address and user agent. Airloom does not enable Sparkle system-profile reporting. Updates ask for installation approval.