How Google Assistant Actions are built
Google allows third-party developers and Google developers to build Actions for Google Assistant through its platform, Actions on Google. All developers who want to integrate with Actions on Google must agree to the applicable terms and policies, and all Actions built for Google Assistant undergo policy reviews before they can be published.
We continually invest in developers by supporting them with the tools and capabilities they need to build helpful and engaging experiences through Assistant. All developers have access to our technical documentation to learn how to develop different types of Assistant experiences. Developers can also use the Actions console, which offers testing and release management tools, reviews for Actions to ensure they follow policy guidelines, performance analytics, and integrations with Google Cloud services. We also make Google technologies available to developers to help them build successful Actions, including features for selling goods, promoting their Actions, and connecting users to their existing account information.
Some Action developers, including Google developers, may have access to resources and data not otherwise available to all developers, due to legal and privacy-related concerns, scalability issues, and considerations to protect Google’s confidential, proprietary information and business. For example, we occasionally make newer Assistant technology available to early adoption partners for testing and feedback, with the ultimate goal of bringing that technology to the rest of the developer community. We may also work with third-party partners and Google developers to build custom integrations with Assistant to create an improved experience for users, and as a first step toward creating a generalized solution for all developers.
- Information that doesn't identify users, such as:
- Aggregated and anonymized data about how users interact with a developer’s Action. For example, Actions on Google developers can view analytics data through the Actions Console.
- Other information that does not personally identify users, but is useful for developers, such as device type and capabilities, locale, and time zone.
- If a user chooses to use Assistant to interact with a developer’s Action, we may share information that relates to that interaction, such as:
- A system generated transcript of a user’s request or its underlying intent or arguments. For example, when a user is talking to a third-party Action, Assistant sends the text transcription of their request to the Action so that the developer can respond.
- With permission from the user, Assistant may share their personal details, such as their email address, name, location, phone number, or payment information, to fulfill their request. For example, to help fill out a form on the web, place a food order, or make a restaurant reservation.
- When users choose to link their Google Accounts with their accounts for a developer’s app or device, we share their basic account information, such as a name, email address, or profile picture, with the developer to facilitate the link.
Developers also share certain data with Google to fulfill user requests and enable their integrations with Assistant, including:
- Information for linking to user accounts, so that users can use Assistant to interact with their accounts for third-party features like Actions, media, smart home and productivity services.
- Content and data libraries, to help Assistant fulfill user requests through the developer’s service. For example, some media providers allow Google to index their media catalog so that users can play content through Assistant. Providers can also share media playlists of users who have linked their accounts, so that those users can ask Assistant to play their playlists.
- Actions on Google developers share data with Google to enable interactions with their users. For example, developers can specify what data is stored in a per-user or per-household data store, which can be reset by the user, so that their Action can remember the user in subsequent interactions. Developers also provide fulfillment responses to answer user requests.
- Third-party devices where Assistant is built-in, such as speakers and TVs, share users’ Assistant queries and related data with Google, so that users can use Assistant through that device.