Smart Home Products & Project Support in Canada & US | SmartAccess ·
Ask what happens to stored data before transferring a hub
Obtain the connected-access manufacturer’s documented customer-data deletion scope across product components before transfer or disposal instead of treating removal from an app as proof that stored data is inaccessible.
A connected-access hub is being passed to another household, and the owner plans only to remove its tile from the phone app. Ask the manufacturer what that action actually does to stored customer data. NIST's consumer IoT profile includes the ability to delete stored data collected from or about the customer and home, or render it inaccessible.
Identify the exact product and its components before following a transfer procedure. A setup can involve the physical device, application, and connected services. Ask the developer for the supported transfer or disposal instructions and the scope of each data-handling step. Keep the explanation tied to the actual model and account arrangement.
For example, an app no longer displays the old hub, but the owner has no documentation explaining whether locally stored information or service-held records were addressed. Treat those as questions to resolve with the manufacturer. An absent tile is an observation about the interface, not proof of what happened to every stored record.
Use the NIST profile to make the question precise. Ask which customer or household data the documented action deletes or makes inaccessible, which components are covered, and whether a separate supported step applies elsewhere in the product. The profile is a capability framework, not a device-specific reset procedure or certification of the product being transferred.
Keep continuity of authorized access in the plan as well. Before disconnecting equipment, the responsible owner should understand what the manufacturer's procedure affects and how the household will meet its ordinary access needs. Do not perform a generic reset solely because it sounds like deletion; ask how the product's documented actions relate to the data and transfer goal.
Record the official instructions, model, affected components, manufacturer's explanation, and unresolved questions. Keep actual credentials and private household data out of public support tickets. If the developer's guidance distinguishes removing an account association from erasing data, preserve that distinction in the handover record rather than compressing both into the word reset.
Use the shop for replacement equipment after the transfer requirements and remaining household needs are clear. Compare documented support and current terms. A clear data-deletion question helps the owner finish the existing product's handover responsibly before assuming that a fresh purchase or an empty app screen completes it.
Sources and further reading
- Profile of the IoT Core Baseline for Consumer IoT Products · Read 2026-11-11
- IR 8425, Profile of the IoT Core Baseline for Consumer IoT Products | CSRC · Read 2026-11-10
This is general information. Check the relevant authority or manufacturer for the rules, compatibility and terms that apply to your situation.
More practical guides