Skip to content

6 Home Assistant Privacy & Offline Questions: Surviving Outages, Isolating Cameras, Keeping Voice Local

The privacy risk in a smart home is rarely a hacker breaking in. It is defaulting everything to the cloud — device state, voice, and video all sitting on a vendor server. Home Assistant's whole point is taking that control back. These six questions cover "how much survives an outage" and "how to stop private data leaving the house", each with config you can use today.

For local protocol choices start with Zigbee setup and Matter/Thread. The isolation and remote-access details are in Remote access and external security.

1. Does HA still work when the internet dies

Short answer: it depends on the protocol.

Still runs: Zigbee, Z-Wave, Matter, Thread, and LAN-only Wi-Fi devices (ESPHome, Tasmota, Philips Hue local mode). A door sensor firing the hallway light, or temperature triggering the AC, all complete inside the LAN and fire in milliseconds with the modem unplugged.

Stops: cloud-only devices with no local API, the remote app, and online add-on store updates.

Rule: buy local-first. Only devices on local protocols make the whole home outage-resistant; cloud-only gear goes dark the moment the WAN drops.

2. How to isolate cameras and locks

When these are compromised, the leak is the most private space in the house. The fix is network isolation, not "just use a strong password".

  • Put them on a separate VLAN / subnet that only reaches the management LAN where HA lives, with no public exposure.
  • Open no inbound ports and wire nothing to a vendor cloud push channel.
  • Adopt them through local protocols (ONVIF, LAN RTSP) and store footage on a local NAS, not a vendor cloud.

Rule: even if a camera firmware is exploited, it stays trapped inside the LAN. Isolation beats passwords.

3. Do not default remote access to a cloud

Nabu Casa is one-click but a paid subscription with the pipe in a third party's hands. For control, three free paths:

  • Cloudflare Tunnel: run cloudflared on the box, tunnel to your domain, no public IP, no port forwarding.
  • Tailscale / WireGuard: join phone and box into one private network, so HA is only reachable once you are "home".
  • All three expose zero public ports, far safer than raw forwarding.

Rule: keep the remote-access pipe in your own hands; do not default to a cloud.

4. Will your voice assistant send what you say to the cloud

Default Alexa, Google, and XiaoAI all use cloud recognition, so commands and audio leave the home. To stop that:

  • Disable cloud recording and use HA's built-in conversation integration for local commands.
  • For more, run local Whisper for speech-to-text so sensitive commands never leave the house.
  • Keep internet microphones out of private rooms (bedroom, study).

Rule: for private voice, never use cloud recognition. Local conversation or Whisper is the floor.

5. 2FA and user roles

When several people touch the system, roles must be clear, or a family member edits an automation and you spend hours chasing a "ghost change".

  • Admin account enables 2FA (Settings → Security → Two-step verification), TOTP is enough.
  • Family members get a "standard user" that controls devices and sees dashboards but cannot open the integrations or automation editors.
  • Build one large-font, minimal Lovelace view for elders; keep complex config hidden.

Rule: tighten the admin, enable 2FA, give family read-only control, and design panels around the least technical person.

6. Can logs and the database leak privacy

Yes, if you record everything. Recorder logs every state change of every entity by default, including locks, camera status, and occupancy.

  • Use include/exclude in recorder to log only what you care about, not dozens of one-off sensors.
  • Configure logs to never print tokens or plaintext passwords.
  • Grant external integrations the minimal scope their token needs: read-only if that is enough.

The full permission and backup picture is in the deployment guide.

Rule: privacy leaks hide in "log everything" and "over-scope tokens". Narrow recorder and minimize tokens.

How to configure recorder so it does not log private data

Many homes record dozens of sensors into the database, which is essentially a minute-by-minute diary of the whole household; if that file is ever exported, the daily routine is laid bare. Use include to keep only what you care about and exclude to drop the noise:

# configuration.yaml
recorder:
  include:
    entities:
      - light.living_room
      - lock.front_door
      - binary_sensor.garage_door
    domains:
      - sensor
  exclude:
    entities:
      - sensor.phone_battery
      - sensor.tv_power_draw

The same caution applies to the logger. A chatty integration can dump tokens into home-assistant.log, so set a quieter level for it:

# configuration.yaml
logger:
  default: info
  logs:
    homeassistant.components.some_cloud: warning

Rule: recorder is a common privacy leak. Include to narrow, exclude to trim, and keep only history you will actually look at — not a surveillance log of the household.

The three most-overlooked privacy points

First, the vendor cloud push channel. Many people think they are safe because they did not install the app, but as long as the device still reaches the vendor cloud for push, the camera and lock state still leave the house. Real isolation cuts its outbound link at the network layer, not by ignoring the app on your phone.

Second, tokens in logs. At default log levels some integrations print the full reply, which can include a plaintext token. Once you hold that token, raise the log level for the component or mute it in the logger config.

Third, family account scope. A read-only account is not only about "preventing accidental edits"; it is also a privacy boundary — not every household member should see every lock-open event. The tighter the roles, the less privacy leaks by accident.

The 3-minute privacy self-check

Run this checklist whenever you add a device or a new integration; privacy drifts as the system grows.

Check Passes when Fails when
Outage test Core automations still run with the modem unplugged Cloud-only devices all die
Camera VLAN Camera IP cannot ping the public internet A firmware hole is exposed outward
Remote channel Tunnel or Tailscale, no public port A port is scanned and reached
Voice recognition Local conversation or Whisper Conversations leave the house
Account roles Family read-only, 2FA on Accidental edits, stolen account
Recorder Include narrowed, no tokens in logs Whole-house activity as a log

Tick each box; if one fails, fix that one before moving on.

Where to start if you are already cloud-locked

If your home is already full of cloud-only gear, do not try to rip it all out in one weekend. Start with the highest-value, most-private devices: move cameras and locks onto a separate VLAN first, switch remote access to a tunnel next, and replace one cloud device with a local-protocol one each time it breaks or you expand. The goal is not purity; it is reducing how much of your private life sits on someone else's server. Small, repeated moves capture most of the privacy gain without a big-bang rewrite that you will abandon halfway. Privacy is a direction, not a switch you flip once; treat each new device as a small decision rather than waiting for a perfect clean-slate moment. Even moving just the cameras off the vendor cloud is a real, measurable win, and it is the place most people should begin rather than aiming for a perfect all-local home on day one.

The 6-point pre-flight checklist

  1. Buy local protocols so automations survive outages (Q1).
  2. Put cameras and locks on a separate VLAN, never public (Q2).
  3. Remote access via Cloudflare Tunnel / Tailscale, not a cloud (Q3).
  4. Turn off cloud voice, use local conversation / Whisper (Q4).
  5. Admin enables 2FA, family gets read-only accounts (Q5).
  6. Narrow recorder, never log tokens, minimize token scope (Q6).

Bottom line: HA's privacy advantage is not one switch; it is a whole set of choices that keep control local. Each of these six steps moves one notch toward "local-first, minimal leakage", and together they make a home that survives outages and stays private.