Learn about Google Nest Device Access

We've published a clear set of privacy commitments so Nest customers can understand how our technology works and what safeguards we have in place to protect and secure their sensitive data. With Device Access, we're 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.

Device Access developers must have their proposed use case reviewed, pass an annual security assessment and agree to our Terms of Service before they're 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.

Works with Google Home (WWGH), formerly Works with Hey Google, enables Google Assistant to control all your connected devices. In the Google Home app, you can create Routines to start one or more of your devices automatically.

Device Access allows partners to integrate Google Nest devices into their smart home ecosystem. With Device Access, third-party partners can directly access and control your Nest products, only after they pass our use case review and an annual security assessment from one of our authorized testers. For example, if you have a security system that offers a Device Access integration, you'll be able to view and control your Nest camera and other products directly from your security provider's app. Each year, partners will be required to update their security assessment to validate they continue to meet security requirements.

Some of our partners, like Vivint and IFTTT, have built integrations with us through Device Access. For information about how to use a Nest device with a partner's devices or services, check the partner's website.

If you're a Commercial developer or a Nest customer interested in Device Access, you can find more information on our Device Access site. Check the page for the latest updates.

Yes, we have a console for qualified Commercial developers with approved integrations, as well as for Individuals. To get started, visit the Device Access Console, accept the Terms of Service and pay a nominal non-refundable fee.

Yes, there's an annual cost on a case-by-case basis. One of our authorized testers determines the scope of work based on your particular use case. Once you apply for commercial development, you'll receive more information.

If you fail the annual security assessment, you have 30 days to fix any issues that were flagged. Once you have fixed these issues, you can schedule a reassessment.

There's a qualifying review process that includes an annual security assessment and use case assessment you have to go through before we accept your application for the Device Access Program. Developers will have to pass this annual security assessment, agree to the applicable Device Access Program terms that include our user data policy, and other additional review requirements before they're approved.

Individual Access is for smart home enthusiasts to participate in Device Access. This allows you to directly control your own Nest devices for your private integrations up to a certain number of users and without a formal review process. It also provides partners with a chance to test their integrations before they submit for Commercial access. Commercial access opens up the integration to a wider audience and requires a complete review process, including an annual security assessment.

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 don't require a security audit or review, and have a limited number of allowed users.

If you'd like more information, see the Device Access site.