Privacy policy
Last updated: October 30, 2026.
Nest Home Integration is operated by its owner for personal use with the owner’s own home devices. This policy describes the current integration; it must be updated if the application’s data practices change.
Data accessed and purpose
With the owner’s authorization, the integration can access home information, including home and room names and zip code, and thermostat information such as device identifiers, settings, temperature setpoints, and sensor data. This information is used to connect and operate the owner’s personal home integration. The initial setup test stores device identifiers and names; it does not build a historical sensor database.
Credentials and storage
Google OAuth credentials allow the integration to access the authorized devices. The current setup stores the client secret and refresh token in the owner’s macOS Keychain. Access tokens are used in memory. Device identifiers and configuration details are stored in local setup files. Credentials are not included in those documentation files.
Use and sharing
The integration communicates with Google to authenticate and retrieve authorized device data. The operator does not sell this data, use it for advertising, or make it available as a public service.
Retention and control
Local configuration and device inventory are retained until the owner deletes them. Credentials are retained until removed or replaced. The owner can revoke access through Google’s Partner Connections Manager. Revoking access does not automatically remove previously saved local files; those must be deleted separately.
Google user data
The application’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Contact
The operator’s support email is displayed on the Google OAuth consent screen.