Nest Fan Scheduler Privacy

Information the app accesses

With your authorization, the app calls Google’s Smart Device Management API to discover devices available to the connection and read the selected thermostat. Responses can include device identifiers, device type, custom or room names, supported capabilities, and status such as temperature, humidity, heating or cooling activity, fan timer state, and connectivity.

Google’s authorization screen also requests access to home information, including home names, room names, and ZIP code, alongside access to the thermostat you select. The current app reads device-list and selected-device responses; it does not call separate home or room endpoints or use ZIP code to schedule the fan. It does not save home names, room names, or ZIP codes in the configuration file.

The app uses device information to let you select a thermostat, confirm fan capability, display status, and request fan timers. Google’s sdm.service permission covers broader device access. The current app’s device-control code sends only fan timer commands; it does not change temperature setpoints or heating and cooling modes.

Sign-in takes place with Google. The app does not receive or store your Google password. During setup, it processes a temporary authorization code and receives OAuth access and refresh tokens.

What is stored on your computer

• Configuration: The default .local/config.json in the project working folder stores the OAuth client ID and secret, refresh token, Device Access project ID, selected device resource name, and timer duration and interval. A custom configuration path can be supplied.
• Downloaded client credentials: The setup uses a Google OAuth client JSON file, normally kept at .local/oauth-client.json. You control this file and any other downloaded copies.
• Temporary data: Access tokens and device responses are held in process memory. The app prints selected device metadata and status, plus scheduling messages, to the terminal. It does not create a device-history database. Terminal scrollback, redirected output, or logging tools you use may retain that output.

On supported macOS and Linux systems, saved credential files use owner-only permissions (600) in a private directory (700). These are plaintext files protected by operating-system permissions; the app does not encrypt them. Files remain until you remove them, and your own backups or synchronization tools may keep copies.

Where information is sent

The local app communicates directly over HTTPS with Google’s authorization, OAuth token, and Smart Device Management services. These exchanges include the credentials needed for authorization, device identifiers, device reads, and fan timer requests. Google processes those exchanges under its privacy policy.

The app has no developer-operated backend and does not send thermostat data or tokens to the website operator. The local app does not sell Google user data, use it for advertising or AI training, or send it to analytics or AI services.

Stopping, revoking access, and deleting data

1. Stop future requests: Stop the local scheduler, for example with Ctrl+C. A fan timer already accepted by Nest expires normally. Heating, cooling, or other thermostat settings may still run the fan.
2. Revoke Google access: Remove the connection through your Google Account permissions or unlink it in Google’s Partner Connections Manager. Google’s Device Access guidance explains these controls.
3. Delete local copies: After stopping the app, remove the configuration file and downloaded OAuth client JSON, including any copies at custom paths. Remove backups and retained terminal output you no longer want. Deleting local files alone does not revoke Google authorization.

The app maintains no developer-hosted account or thermostat-data store to delete. Local deletion does not remove records Google may hold under its own policies.

This informational website

The website describes the local tool; it does not run your thermostat schedule or receive its credentials. Website hosting, access logs, and any site-wide services are separate from the local app and are covered by PepLamb’s website privacy policy.

Questions and updates

For privacy questions, use the contact information in PepLamb’s website privacy policy. Do not include passwords, OAuth tokens, client secrets, authorization URLs, or credential files in a support message.

If the app’s data handling changes, this notice should be updated with the revised behavior and date.