Google Contacts Sync for the DEVS-AVAX desktop application

Why Google access is requested

When an operator connects a Google account, DEVS-AVAX requests the standard Google identity scopes openid and email together with the Google Contacts scope https://www.googleapis.com/auth/contacts. The identity scopes are used to identify the connected Google account, keep durable AVAX contact links isolated between different Google accounts, and display account information to the operator. The Google email address is display metadata; the stable OpenID Connect account identifier is used for durable account separation.

The Google Contacts scope lets the application search for an existing Google contact using approved exact email or phone identifiers, link an existing contact, create a contact after explicit operator confirmation, and synchronize an already linked contact after explicit operator confirmation.

Name alone is not treated as a contact match. Google contact changes are not performed silently: creating a contact or synchronizing an existing linked contact requires an explicit operator action in DEVS-AVAX.

What the feature does not do

The current Google Contacts Sync feature does not delete Google contacts. Disconnecting Google authorization removes or revokes the application's local Google authorization state; removing an AVAX link does not delete the Google contact. The requested Google identity scopes do not give DEVS-AVAX access to Gmail, Google Drive or Google Calendar content.

Privacy and support

Details about Google account identity metadata, Google user data access, AVAX data sent to Google Contacts, local token protection and retention behavior are provided in the DEVS-AVAX Google Contacts Privacy Policy. Use of DEVS-AVAX is also subject to the DEVS-AVAX Application Terms.

For support or questions about this integration, contact Process Logix at contact@process-logix.com.