If you’re holding off on demand-response enrollment, privacy is probably why: Can the utility see my schedule? Can they control my thermostat at will? What data do they collect?
These are legitimate questions, and the answers are more reassuring than you’d expect.
What Utilities Can Do (Demand-Response Enrollment)
When you enroll in a demand-response program, you’re authorizing the utility to do a specific, limited set of things:
Send temperature adjustment signals during declared peak events. During a demand-response event (which happens ~10–30 times per year), the utility can send a signal that raises your cooling setpoint (or lowers your heating setpoint) by a specified amount, typically 2–4°F, for a specified duration, typically 1–3 hours.
View your thermostat’s current temperature reading during events (in some program implementations). This is used to verify participation and calculate credits.
Access schedule and mode information in some deeper integrations. The utility’s visibility into your data varies by program and thermostat platform: ecobee and Nest both have documented APIs that specify what data is shared with utility partners.
That’s the scope. Not your home network. Not other devices. Not location data beyond what’s needed for program delivery.
What Utilities Cannot Do
Access your home Wi-Fi network. The thermostat communicates with the utility through the thermostat manufacturer’s cloud (ecobee’s servers, Google’s servers), not through a direct connection to your router. The utility never has access to your local network.
Permanently modify your settings or schedule. Demand-response events are temporary. Your schedule returns to normal after the event automatically. The utility has no persistent write access to your configuration.
Turn your thermostat off. No demand-response program turns off heating or cooling entirely. They modestly adjust setpoints, within limits you can configure.
Override your manual controls. If you manually adjust the thermostat during an event (either at the device or in the app), your manual setting takes effect immediately. This is a universal feature across all major programs.
Penalize you for opting out. Opting out of a specific event may reduce your credit for that event, but you can’t be penalized by the utility for exercising manual control in your own home.
Your Controls
Comfort limit setting: Most programs let you set a temperature threshold below which the utility cannot push. For example, you can set a 76°F minimum in summer. The utility can’t raise your cooling setpoint above that.
Event opt-out: You can opt out of individual events by manually overriding the thermostat or selecting “opt out” in the thermostat app. Most programs don’t penalize for occasional opt-outs.
Program disenrollment: You can disenroll from the demand-response program entirely through your utility portal or thermostat app. No penalty beyond losing future credits.
What Your Thermostat Already Knows
Before worrying about what the utility can see, consider what your thermostat manufacturer already collects:
- Indoor temperature readings (continuous)
- Occupancy and motion data (if sensors present)
- Scheduling and setpoint history
- Energy consumption estimates
- Location data (if geofencing enabled)
ecobee, Google (Nest), and Honeywell collect this data under their own privacy policies, regardless of demand-response enrollment. Demand-response programs access a subset of this data that the thermostat manufacturer shares through their API: typically temperature readings and current mode.
Read your thermostat manufacturer’s privacy policy if this is a concern. The utility’s data access is generally narrower than what the manufacturer already has.
How to Enroll With Peace of Mind
Read the demand-response enrollment terms: they must disclose what data they access and what control rights you’re granting. If a specific term concerns you, contact the program administrator before enrolling.
Set a comfort limit: most programs let you configure a threshold that constrains how far they can adjust your setpoint. Set it conservatively.
Test the override: after enrollment, manually override the thermostat once to confirm it responds immediately, which it will.
Review annually: demand-response program terms can change at renewal. Review the terms when you re-enroll each season.
See Smart Thermostat Demand Response Programs: How to Earn Bill Credits for program details.
See Demand Response Payout Comparison: Which Utility Pays the Most? for what you earn by enrolling.
Frequently Asked Questions
Can the utility control my thermostat whenever they want?
No, only during declared demand-response events, which happen ~10–30 times per year during peak periods. Outside of events, the utility has no control over your thermostat.
Does the utility have access to my home network?
No. Thermostat communication goes through the thermostat manufacturer’s cloud servers (ecobee, Google, Honeywell). The utility communicates with those servers through an API. It never has a direct connection to your home network.
Can I override the thermostat during a demand-response event?
Yes, always. Manual override is immediate and cannot be blocked by the utility. Opting out of a specific event may reduce your credit for that event in some programs but won’t affect your enrollment status.
What if I want to disenroll from demand response?
Disenroll through your utility portal or thermostat app at any time. No penalties: you stop receiving credits.
What data does the utility actually see?
Typically: your thermostat’s current temperature and current mode during events, and in some implementations, your general schedule. They do not see occupancy data, location data, or other household information. The specific data shared depends on the program and thermostat manufacturer’s API.
Is demand-response data sold to third parties?
This varies by utility and program. Read the enrollment terms: they must disclose data use. State PUCs rate-approve most utility demand-response programs, which limits how they can use data. If this concerns you, ask the utility before enrolling.