Here are answers to some common questions about Device Access. You’ll find information about Device Access for Individuals and Commercial developers as well as where to sign up to get the latest updates.
What is Device Access and why are you launching it?
In May, we published a clear set of privacy commitments so Nest customers can understand how our technology works, and explain the safeguards we have in place to protect and secure their sensitive data. With Device Access, we're now offering our third-party ecosystem partners more ways to integrate with Nest products, but doing it built on a foundation of privacy and security.
Device Access lets qualified partners securely access and control your Nest products with their apps and solutions. This gives you more choice in how you control your home. We require Device Access developers to go through an additional security assessment to help keep your data private and secure.
What data security measures are used?
Device Access developers will have to have their proposed use case reviewed, pass an annual security assessment and agree to our Terms of Service before they are approved, so we can make sure each developer has the right data protections and safeguards in place that meet our privacy and security standards.
To learn more about how Google Nest protects user data, read our FAQs on privacy.
How are “Works with Nest”, “Works with Hey Google” and “Nest Device Access” different?
Works with Nest (WWN) was the original way that approved third-party partners could access and control your Nest products. They were fully integrated with a Nest product and could check and change its status. Existing Works with Nest connections will continue to work for those users who have a non-migrated Nest Account in the Nest app.
Which partners are currently on Nest Device Access?
What happens to my Works with Nest connections?
What if my Works with Nest partner connection isn't available in Nest Device Access or Routines?
Information for developers
How do I learn more about becoming a Device Access developer?
Will developers have access to a developer console to manage their integrations?
Will developers have to pay for the commercial annual security assessment?
What happens if I fail the annual security assessment?
What happens to my Works with Nest developer integrations?
What is the Device Access Commercial review process?
Works with Nest had a sandbox for personal integrations. Can I do that with Device Access?
Yes, in the Device Access for Individuals sandbox you can directly control your own Nest devices for your private integrations and automations. These smaller integrations do not require a security audit or review, and have a limited number of allowed users.
If you would like more information, see the Device Access site.