Before you buy a smart device, write down its exit plan

A smart device can look useful long after the software, app or online service behind it changes. Before you buy one, make a small ownership record: how long it should receive security updates, what essential job survives without the internet or an account, how you can retrieve and delete your data, and what you will do at end of support.

The record should describe the exact model and the country where you will use it. A promise for a product family, another generation or another market may not answer your question.

Start with four separate promises

Marketing pages often compress several dependencies into “support.” Record them separately:

1. Security support: the minimum update period or an exact end date, plus the event that starts the clock.
2. Essential operation: the one job you need the device to perform, and what it does when the internet, cloud service, subscription or account is unavailable.
3. Account and data exit: how to export useful data, remove the device, delete the account or recordings, and reset the hardware before transfer or disposal.
4. End of support: how notice arrives and whether your planned response is to keep limited local use, isolate, replace, resell, recycle or stop using the device.

These are different facts. A security-update promise does not guarantee every cloud feature, subscription price, mobile app or third-party integration for the same period.

Find the support clock, not just a duration

A statement such as “five years of updates” is incomplete until you know when those five years begin. The clock might start at first sale, the manufacturer's launch date, your purchase, activation or another documented event.

Google's current Nest documentation, for example, says listed connected-home devices receive automatic security updates for at least five years from the date Google starts selling the device in the US Google Store. The same page limits that promise to critical issues known to Google Nest that can be addressed with a remote software update. That is a useful model-specific statement, but it is not a universal five-year rule and the clock does not start when every buyer purchases the device.

Philips Hue publishes a different structure. Its current policy says Hue Bridge software support is intended for at least three years from purchase from an authorized reseller, while a separate section describes at least five years for certain other Hue products. The policy also separates security, quality and interoperability updates from online and app compatibility. The lesson is to save the section that actually covers the model, dependency and market you are considering.

In the United Kingdom, current product-security guidance says covered consumer connectable products sold to UK consumers must meet baseline security requirements and be accompanied by a Statement of Compliance. Treat that as jurisdiction-specific context. It does not replace reading the exact product's support statement, and this guide is not legal advice.

Save the support page with its URL and the date you checked it. Also record the model identifier from the seller's page or packaging so you can match the promise later.

Define “still useful” before checking offline behaviour

Write one essential job in plain language. “Turn the lamp on from the wall switch” is testable. “Keep all smart features” is not.

Then look for documented answers to four separate interruptions:

• the home internet connection is down;
• the manufacturer's cloud service is unavailable;
• you stop paying for an optional or required subscription;
• you remove the device from your account or delete the account.

Do not assume that “local,” “account-free” and “offline” mean the same thing. Google's current privacy documentation gives a useful illustration: it says a Nest thermostat can retain specified basic controls after the account is deleted, yet it can remain connected to the internet, communicate with Google servers and receive updates unless Wi-Fi is disconnected. That is a documented example for specified Nest products, not a result observed by Inquory and not a promise for another device.

Also identify the update path. A product may need an app, internet connection or hub to receive fixes even if its everyday control can be local. Philips Hue, for example, documents an internet connection as necessary for direct Bridge software updates. Record that dependency beside the offline fallback so “works locally” does not accidentally become “can remain safely updated without a network.”

For a low-consequence device, a physical switch may be enough. For an entry camera, alarm, lock, medical device or safety-related appliance, missing documentation is a reason to stop and seek product-specific expertise rather than infer a fallback from marketing language.

Plan the account and data exit while the product is new

An exit plan should answer:

• What useful records can you download, in which format, and through which account page?
• What data is stored only in the cloud, only on the device, or on removable local storage?
• Can individual recordings or events be deleted without deleting the whole account?
• What happens to shared household members, automations and linked services when the device is removed?
• Is there a documented factory-reset procedure for resale, return or recycling?
• Does deleting the account also reset the physical device, or are those separate steps?

Provider documentation can make these boundaries visible. Google's Home and Nest privacy documentation links separate controls for downloading an archive, deleting particular data, removing devices or homes, deleting an account and factory-resetting products. Philips Hue's current privacy notice tells people returning or selling a product to perform a factory reset. Neither example proves that every smart-device export is complete or portable, and Inquory did not run either flow.

If the product stores sensitive video, audio, access history or health information, read its exact retention and deletion documentation before purchase. A generic privacy-policy link without product-level steps is not an exit plan.

Decide the end-of-support response in advance

Write a calendar reminder before the documented minimum support period ends. At that point, reopen the policy and product notices. Check whether the manufacturer extended support, issued an end-of-life notice, changed a required service or provided a migration path.

The US Federal Trade Commission advises keeping connected-device software current, disabling features you do not need and considering whether an older device's security is out of date. Those practices help during ownership, but they cannot create a manufacturer support promise.

Your end-of-support decision should reflect consequence and exposure. A disconnected decorative light with a working physical control presents a different decision from an internet-facing camera. If you cannot establish an acceptable supported or isolated use from current product documentation, stop using the connected function and follow the manufacturer's transfer, reset and disposal instructions.

Copyable smart-device ownership worksheet

Copy this table into your notes. Fill documented facts only; keep unknowns visible.

Fictional example: a kitchen status display

This example is invented to show how the worksheet works. It is not a tested product or buying recommendation.

The fictional buyer should pause because one dependency remains unknown. A plausible assumption is not a recorded fact.

The stop condition

Do not buy yet if you cannot document all four of these for the exact model: a support clock, acceptable behaviour for your essential job during the relevant outage, an account/data/reset exit, and an end-of-support response you are willing to carry out.

An empty field can be a valid comparison result. Ask the manufacturer or seller for a durable answer, choose a product with clearer documentation, or decide that a non-connected alternative better fits the job.

Research method and limits

Inquory reopened current government and provider documentation on October 4, 2026 and used it to design the worksheet. No device was purchased, configured, disconnected, exported, reset, sold or recycled. Provider examples are illustrations of documented differences, not rankings or endorsements. Policies, product eligibility and service behaviour can change; reopen the exact model's documentation before purchase and again near end of support.