Privacy Policy for Smart Home Status

Effective date: November 3, 2026

Smart Home Status is the owner-selected release name for the app previously called Local UPnP Things. This policy continues to cover the same iOS app and its existing installation identity.

Smart Home Status is an independent iPhone and iPad app for checking supported accessories already added to Apple Home and using optional local UPnP/SOAP device tools. It is provided by MeOnMesh. The app does not require a developer-operated cloud account.

Optional Apple Home access

The app asks for Home access only when you choose Connect. With permission, it reads accessible homes, scenes, accessory and service names, identifiers, supported characteristics and current responses. Supported HomeKit/HAP and Matter accessories already in Apple Home use Apple's HomeKit API. Support depends on the characteristics Apple exposes; the app does not create its own Matter fabric or pairing service.

Checks compare current responses with your chosen power goals. Checklist corrections require your explicit selection, review and Apply. In Devices, an explicit On or Off tap authorizes a single compatible power control; the app checks current responses before sending a command and reads again to verify it. These single-device intents stay in memory and do not create a saved checklist or Home scene. Home access is optional: local network tools remain available if you decline it. You can change Home access in iOS Settings.

Home data is not sent to advertising services, analytics services or a developer-operated server, and is not used for advertising, marketing or profiling. Apple manages its own Home data, Apple Account, home-hub and network services under Apple's privacy policy.

Optional local network tools

In version 1.1 and later, local discovery may begin when you launch or return to the app, subject to iOS Local Network permission and an admission interval. You can also select Devices → Local network and choose Scan or another explicit local action. The app may use Bonjour/mDNS, local descriptor probing, SSDP/UPnP diagnostics, local HTTP device descriptions and SOAP requests to discover and control compatible local devices. These tools require the same Wi-Fi/LAN and may handle local device names, IP addresses, model and firmware information, serial numbers and device responses.

The app does not upload this local device information to a developer-operated server or provide it as advertising context. Home and local-network records use separate providers. In version 1.1 and later, in All devices, a local row may be hidden when a unique manufacturer and serial-number match identifies the same Apple Home accessory. Names and IP addresses alone are not used to establish a match. The Local network filter retains local records; control does not silently fall back between providers.

Optional Wi-Fi setup in version 1.1 and later

From Devices → Local network → +, you may choose to set up a compatible Wemo device. Supported iOS versions use Apple's accessory picker and explicit Wi-Fi join approval; manual entry is available where supported. Previously allowed setup networks are permissions remembered by iOS, not an unrestricted nearby Wi-Fi scan. The app reads the selected device's identity and network list, reviews your chosen home network, sends credentials only after you choose Connect, and verifies the same device on the home network before saving it.

The Wi-Fi password stays in memory for the setup flow and is sent directly to the chosen device's local setup service; this setup uses local HTTP rather than TLS. It is not deliberately saved in app files, logs, analytics or a developer-operated server. iOS and the accessory maintain their own Wi-Fi credentials and accessory permissions. Setup does not automatically factory-reset devices or retry credential submissions. Apple Home pairing is a separate user-chosen system flow.

Optional local group files in version 1.2 and later

You can create app-local groups containing supported local Wemo devices and explicitly export or import their configuration as JSON files. Groups store a group identifier and name, ordered member names and model hints, exact Wemo device identities (UDNs), and an optional group favorite. These groups remain separate from Apple Home accessories, scenes and checklists. Importing a group never sends a power or setup command; you review matching devices and choose what to save.

Exporting shares group identifiers and names, member names and model hints, ordered UDNs, a source collection label (currently “Local network”), the export time, file format kind and version, and, only if selected, group favorites. The format does not export device power state, control rules, Wi-Fi or settings passwords, credentials, Apple Home permissions or advertising choices. Names and UDNs may reveal information about your home. You choose the file destination and recipients; anyone receiving the file can read its contents.

The app does not send these group configurations to a developer-operated server or advertising service. App-local group storage uses iOS file protection and may be included in device backups. Exported files are stored in the Files location you select and may be synced by that file provider under its own settings and policies. Deleting a group or uninstalling the app does not remove exported files, recipient copies or backups; manage those copies with the relevant file, backup or recipient controls.

Information stored on your device

Your app-local checklists store a list identifier and title, exact home/accessory/service/characteristic references and desired Boolean power goals. The checklist folder is excluded from backup and uses iOS complete file protection and restricted file permissions. Current Home names, live responses, capabilities, reports, correction selections and approvals are not saved in that checklist store or synchronized by an app-operated cloud service.

Local network tools may separately save known device metadata, local descriptor/control/event URLs, favorites, custom labels, display order, last-seen time and last-known state. Appearance preferences such as the selected background are also stored locally. Unlike the checklist folder, local device metadata is not excluded from device backups. Apple Home and iOS may maintain their own data independently of this app.

Advertising, consent and device storage

The main app includes Google AdMob and Google User Messaging Platform (UMP). A shared region reserves space for a banner above the bottom Home, Devices, Checklists and Settings navigation, outside scrolling content. App launch starts a UMP information check with Google, independently of Home access or local Scan. The footer is hidden during keyboard entry. The app checks UMP information and any required consent form before requesting ads; version 1.1 also requires native tracking authorization as described below. Required privacy options are available from Settings → Advertising → Ad privacy choices. If the privacy check fails, ads are suppressed and device tools remain usable.

Ad requests disable personalization and publisher first-party IDs and include a non-personalized-ads signal. The app disables the Mobile Ads SDK's crash-reporting feature. Version 1.0 does not request Apple's tracking permission. In version 1.1 and later, the app requests native App Tracking Transparency permission after the applicable advertising-consent check. It starts Google Mobile Ads and requests banners only when both consent and tracking authorization permit it. Denying, restricting or leaving tracking undecided prevents ad requests without blocking home or local-network features. You can change tracking permission in iOS Settings. UMP consent information may still be updated to maintain privacy choices; it is separate from Apple's tracking permission. No separate Firebase analytics SDK is included. Home data, local device details, group configurations, checklist goals and check/correction events are not supplied as ad targeting, keywords, content URLs or publisher user IDs.

Non-personalized ads are not data-free and do not remove consent requirements. Google's advertising and consent services may use IP addresses (including approximate location inferred from them), device or other identifiers available under your settings, advertising interactions, product interactions, performance information and diagnostics. In version 1.1 and later, if you grant tracking permission and applicable consent permits ads, Google may use device identifiers, including IDFA, to link advertising data with data from other companies’ apps or websites for advertising measurement. Tracking permission does not change this app’s non-personalized-ad request policy. They may use SDK/device storage for consent choices, frequency capping, measurement, fraud prevention, security and compliance. Disabling one SDK feature does not mean Google's services process no data.

You can manage available choices through Ad privacy choices and iOS privacy settings. Where a choice limits or prevents advertising, the basic tools remain available. Learn more in How Google uses information from apps that use its services and Google's privacy policy. This policy page contains no advertising tags or consent-message scripts.

Accounts and support

The app has no developer-operated sign-in or user account. Apple Home may require an Apple Account managed by Apple. If you contact support, the email address and information you choose to provide are used to respond to your request. Please do not send Wi-Fi passwords, accessory setup codes, household identifiers or other device secrets.

Deletion and privacy requests

You can delete an app checklist in the app or uninstall the app to remove its local app data from that installation. Copies of local device metadata may remain in device or iCloud backups and must be managed using Apple’s backup controls. Deleting a checklist or uninstalling does not remove Apple Home accessories, scenes or Wi-Fi settings. To manage Apple's Home data, use Apple's Home and privacy controls. To manage data held by Google's services, use the privacy controls and request processes described in Google's policy; uninstalling this app does not itself delete data held by Google.

For questions or privacy requests about information you provided directly to MeOnMesh, contact meonmesh@gmail.com. We do not maintain a server copy of your Home or local-device records to retrieve or delete.

Children

The app is designed for people managing home-network devices and is not directed to children under 13. We do not knowingly collect personal information from children. Contact us with any concerns.

Non-affiliation

Smart Home Status is independent software. It is not affiliated with or endorsed by Belkin, Wemo, Apple, Google or standards organizations.

Changes

This policy may be updated when the app's behavior or third-party services change. The effective date above will be updated when changes are made.