Home Assistant Nest Link
Effective 21 September 2026
This application has one user, collects nothing, shares nothing, and has no server. Everything below is detail supporting that sentence. If any part of this policy ever stops being true, this page will be updated before the change takes effect.
An individual, for personal use in a private residence. There is no company, no staff and no other user. Contact: DanielGMusto@gmail.com.
Only data about the operator’s own Nest device, retrieved from Google’s Smart Device Management API under authorisation granted by the operator’s own Google account:
| Thermostat state | Current temperature, humidity, HVAC mode, operating status and target setpoint |
|---|---|
| Device metadata | Device name, type, and the structure or room it is assigned to |
| Camera livestream | The live video stream from a Nest smart display located in the operator’s garage, viewed on demand |
| Camera events | Motion, sound and person-detection notifications from that same device |
| Camera snapshots | Still images associated with the events above |
| Change events | Notifications delivered via Google Cloud Pub/Sub when any of the above changes |
No other Google account data is requested or accessed. Not contacts, not calendar, not mail, not location history, not files, not profile information beyond what is strictly required to complete the OAuth sign-in.
This application accesses the camera built into a Nest smart display in the operator’s garage, so that the video, motion and person-detection events already produced by that device can be viewed and acted on within the operator’s own home-automation system rather than only in a vendor’s mobile app.
That video is streamed on demand to software running on the operator’s own hardware, on a private home network. It is not recorded to, relayed through, or stored on any external service by this application, and it is not accessible to anyone other than the operator.
No other camera, doorbell or microphone in the residence is connected to this application. Access to any device can be withdrawn individually at any time, as described below.
Directly from Google’s API to a self-hosted Home Assistant instance running on hardware the operator owns, on a private home network. There is no intermediate server, no cloud service, and no hosted component operated by this application.
Thermostat readings, and any camera event or snapshot the operator chooses to keep, are stored in that instance’s local database so that history and automations work, exactly as with every other device in the home. That database is on the operator’s own hardware and is not replicated to any external party.
Device history — readings, events and any retained snapshots — is kept locally under Home Assistant’s own retention settings and can be purged by the operator at any time. Because no copy exists anywhere else, deleting it locally deletes it completely.
Access can be withdrawn at any moment from Google Account permissions. Revocation is immediate: the application loses all ability to reach any device, and no further data can be retrieved.
OAuth credentials and tokens are stored on the operator’s own equipment on a private network, are not transmitted to any third party, and are not embedded in any distributed software — this application is not distributed at all.
This application is not directed at children and has no users other than its operator.
Any change will be published on this page with a revised effective date. As there are no other users, no notification mechanism exists or is required.