Privacy_policy_url cannot be empty – field not found in Google Home Console

Configuration Voice Assistant
1

Hello,

I changed the URL of my Home Assistant instance and now I need to recreate my Google Assistant integration.

I followed your excellent guide (which I had already used successfully before), but I keep running into the following error:

 Error creating account linking for project(xxxxxxxxx) due to 
(INVALID_ARGUMENT: com.google.identity.accountlinking.error.AccountLinkingException:
<eye3 title='INVALID_ARGUMENT'/> generic::INVALID_ARGUMENT: privacy_policy_url cannot
be empty [type.googleapis.com/util.MessageSetPayload='[google.rpc.error_details_ext] { 
message: "privacy_policy_url cannot be empty" }']).Please try saving again.

Has something changed (again) in the console?

I can’t find this field anywhere in the form.

1 Like
2

Same here…

1 Like
3

Same here too

4

Hello,

I am seeing the same error when creating a new Cloud-to-Cloud integration in Google Home Developer Console:

“INVALID_ARGUMENT: privacy_policy_url cannot be empty”

What I already verified:

  • Google Auth Platform > Branding is fully configured and saved
  • Homepage, Privacy Policy, and Terms URLs are set
  • Authorized domain is set
  • Company profile in Google Home Developer Console was submitted and is now “In review”
  • The privacy policy URL is publicly reachable
  • Home Assistant endpoints are reachable, and /api/google_assistant responds correctly
  • I reproduced the issue in a brand-new project, in incognito mode, and from another device/browser

So this does not look like a missing field on my side. It looks like the Google Home Developer Console is still not reading the saved privacy policy configuration when saving Cloud-to-Cloud setup.

Could Google please confirm whether this is a known console/backend issue, and if there is any workaround?

Thank you.

5

Same, any fix?

6

same here…i’m still try from last week…

7

Google team seems aware of the problem and are working on a fix Google Issue Tracker

8

It works now !