Why does Debian ship Google API keys with Chromium?

I have a file called /etc/chromium.d/apikeys which has the following contents,

# API keys assigned to Debian by Google for access to their services like sync and gmail.
 
export GOOGLE_API_KEY="AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k"
export GOOGLE_DEFAULT_CLIENT_ID="811574891467.apps.googleusercontent.com"
export GOOGLE_DEFAULT_CLIENT_SECRET="kdloedMFGdGla2P1zacGjAQh"

Why does Debian ship Google API keys though to begin with? You don't need an API to go to gmail.com? What happens if I nuke this file? You can see it's part of upstream chromium,

$ dpkg -S /etc/chromium.d/apikeys
chromium: /etc/chromium.d/apikeys

What part of chromium functionality requires these keys?