Insights
Internet of Things privacy: what your connected devices reveal
Check what connected devices collect, share and retain. Use a privacy worksheet, offline-feature checks and a device retirement checklist.
On this page
Internet of Things (IoT) privacy is about what connected devices collect about you, who can use that data and how much control you have. Risks include unwanted collection, sharing, long retention and access by people you didn't authorize.
In short:
- Follow the data. Check the device, app, cloud service and account separately.
- Separate sharing from updates. Check whether you can disable optional collection while keeping security updates.
- Plan deletion early. Check local reset and cloud deletion instructions before retiring a device.
What your connected devices can reveal
Connected devices may collect more than you'd expect from their main function, as Canada's consumer IoT checklistOpens in a new tab warns. Collection covers what gets recorded, while sharing covers who receives it. Retention means how long that information stays stored.
Imagine a recording device in a shared room. It could capture household members and guests, not just its owner. Consider telling guests about recording or turning the device off while they're nearby.
Security and privacy overlap, but they answer different questions. Strong sign-in controls help restrict access to authorized users, according to Federal Trade Commission (FTC) guidance for IoT makersOpens in a new tab. A strong password doesn't answer whether the vendor collects or shares more data than you want.
Follow your data from device to account
Map the full data lifecycle: collection, transmission, storage, access, use and deletion. The Internet Society's IoT privacy briefOpens in a new tab says you should understand where your information has gone and how long it's kept. A cloud service stores or processes information on remote servers.
Use the worksheet below for each device. These are places to investigate, not a claim that every device uses every path. For each entry, record a supporting manual page, privacy notice or setting, then label it documented, observed in a limited check or unknown.
Fill in this first part with what gets collected, where it goes and who can access it.
| Data location | Collected data | Destination purpose | Allowed access |
|---|---|---|---|
| Device | ___ | To: ___ / Why: ___ | ___ |
| Companion app | ___ | To: ___ / Why: ___ | ___ |
| Cloud service | ___ | To: ___ / Why: ___ | ___ |
| Account access | ___ | To: ___ / Why: ___ | ___ |
| Third-party integrations | ___ | To: ___ / Why: ___ | ___ |
| Hypothetical recording camera | Recorded video | Destination and purpose unknown | Unknown |
Use this second part to track retention, deletion, opt-out choices and the evidence behind each entry.
| Data location | Retention period | Deletion opt-out | Evidence status |
|---|---|---|---|
| Device | ___ | Delete: ___ / Opt out: ___ | Source: ___ / Status: ___ |
| Companion app | ___ | Delete: ___ / Opt out: ___ | Source: ___ / Status: ___ |
| Cloud service | ___ | Delete: ___ / Opt out: ___ | Source: ___ / Status: ___ |
| Account access | ___ | Delete: ___ / Opt out: ___ | Source: ___ / Status: ___ |
| Third-party integrations | ___ | Delete: ___ / Opt out: ___ | Source: ___ / Status: ___ |
| Hypothetical recording camera | Unknown | Deletion and opt-out unknown | Example only / Unknown |
The camera row is an example, not a finding about a real model. Its vendor-specific fields stay unknown until you find evidence. A limited observation only supports what you saw under those conditions, not a complete account of where data goes.
Compare the features you'll keep and the data you'll share
Apply the same checks to a device you're considering and one you already own.
| Privacy check | What to check | Choice impact |
|---|---|---|
| Necessary collection | Data needed for each feature | Accept only collection that fits your needs |
| Optional sharing | Separate opt-outs and update settings | Favor opt-outs that preserve security updates |
| Data recipients | Recipients and reasons for sharing | Decide whether those uses are acceptable |
| Data retention | Storage periods and deletion scope | Favor clear, usable deletion controls |
| Account access | User permissions and access removal | Match access to each person's needs |
| Offline features | Exact functions available without internet | Keep essential functions in your comparison |
| Update support | Support period and delivery method | Check continued security support |
| Cloud dependence | Functions requiring the vendor's service | Account for losing service access |
Optional collection and security updates need separate answers. Ask the manufacturer whether you can decline additional data-collecting features without losing updates. Don't assume a broad consent switch controls both.
Offline use is also a feature-by-feature question. Some functions may work without internet access while others need it. Local operation doesn't, by itself, show that the device has no cloud account or sends no data when connected.
Keeping a supported device can be reasonable when its documented controls meet your needs. Favor clear answers about collection, access and deletion over vague privacy claims.
Change the settings that affect your privacy
Change only devices and accounts you own or administer. Save the original settings so you can restore them if access or a needed feature stops working.
1. Review optional collection and sharing.
Check what information setup asks for and whether it's required. Turn off optional automatic sharing, such as location sharing, where supported. Keep security update settings separate from optional feature consent.
2. Check users and connected services.
Review who can access the device, its settings and its data. Remove access and third-party integrations you no longer need, using the vendor's documented controls.
3. Review recording around other people.
Check recording settings for shared spaces. Consider notifying guests or turning recording devices off while they're nearby.
4. Strengthen sign-in controls.
Use a strong, unique password for each device or service. Enable multifactor authentication where available, which asks for another form of proof when you sign in.
5. Check updates and needed features.
Keep security updates enabled and check how the manufacturer delivers them. After changing privacy settings, confirm that your required functions still work. If they don't, restore the affected setting and check the documented tradeoff.
Network segmentation separates devices into groups with access limits. It addresses access boundaries, not the vendor's collection or retention choices. It doesn't prove that all tracking has stopped or erase data already held elsewhere.
Before using any network app, check compatibility with your device, hub or router. Confirm which traffic would use it. Don't assume connecting one device puts your whole home network under those controls.
Check what still works without the internet
A proposed home check can help you understand offline features, but it isn't a privacy audit. Use only a nonessential device you own or administer. Exclude medical, safety-critical and essential alarm devices, and save the settings needed to restore access.
1. List the documented offline features.
Start with the manufacturer's instructions for your model. Note which functions should work without internet access and which require its service.
2. Choose a supported, reversible method.
Temporarily remove internet access only if the device's instructions provide a suitable method. Skip the experiment if you can't safely restore access.
3. Check the functions you need.
Choose relevant functions, such as local controls or viewing a stored recording, where the device supports them. Record the model, software version, settings, functions checked and duration. Write down what worked and what didn't.
4. Restore access and compare the result.
Restore the original connection and settings, then confirm normal operation. If results differ from the documentation, check the model and settings before drawing a conclusion.
A function working offline proves only that it worked under the recorded conditions. A failure doesn't identify its cause. Neither result proves that collection stopped, that stored data won't upload later or that cloud copies were deleted.
Clear your data before you stop using a device
You need authority over the device and account before changing or deleting their data. Deletion may be irreversible, so preserve anything you need first.
1. Decide whether you're pausing use or retiring the device.
For a temporary pause, use the documented controls to stop recording or turn the device off. Don't treat that as deletion.
2. Read the retirement instructions and save needed data.
Check the manual or manufacturer's website for data removal and factory reset instructions. Preserve records you want to keep before following them.
3. Check data held outside the device.
Look for separate instructions covering cloud history, account unlinking and connected services. Check the required order, deletion scope and backup retention. These are vendor-specific checks, not universal capabilities.
4. Remove local data and reset as directed.
Follow the manufacturer's process for removing device data and restoring factory defaults. Handle removable storage separately if present, using the relevant instructions.
5. Check the reset result and dispose of the device responsibly.
Confirm that the device reaches the manufacturer's expected reset state. That supports completion of the reset process, not proof that every copy is gone. Use a responsible disposal route if you aren't keeping or transferring it.
Unplugging a device or restoring factory defaults doesn't prove that cloud records, backups or every local copy have been erased. Keep the off-device deletion checks separate from the reset checklist.
Where doxx.net fits. doxx.net supports encrypted Domain Name System (DNS) lookups and domain filteringOpens in a new tab. Use its supported encrypted-DNS configuration for the lookups you want to protect; changing a resolver address alone doesn't establish encrypted DNS. After checking compatibility and traffic coverage, you can create a doxx.net account, download the app and connect a device or agentOpens in a new tab.