Privacy Policy — AVA Contact Sync

Effective 15 September 2026. Published by Atlas Veterinary Hospital.

AVA Contact Sync copies a client’s name, phone number and email address from Atlas Veterinary Hospital’s practice management system into Atlas Veterinary Hospital’s own Google Contacts account, so the practice phone system can show a name when that client calls.

It sends this information to Google and to nobody else. There is no AVA server. There is no analytics, no telemetry, no advertising and no third-party service of any kind. Nothing is sold, rented or shared.

Who this extension is for

AVA Contact Sync is an internal tool. It was built by Atlas Veterinary Hospital for the computers at its own reception desk, and it is listed on the Chrome Web Store only so those computers can install and update it through Chrome instead of by hand.

It is configured to work with one specific Google account and one specific practice management system. It is not offered as a product to other practices and it will not do anything useful if installed elsewhere.

What information the extension handles

Client contact details. When a member of staff saves a client record, the extension reads from that page:

Those five things are all that is sent to Google or kept afterwards. While the form is being examined the extension may also read the value of a second or third phone field on it; those values are discarded immediately and are never stored or transmitted.

No clinical or veterinary record is read, stored or transmitted. The extension does not read patient, species, breed, diagnosis, treatment, prescription, appointment or billing information. Fields whose label or name suggests a patient rather than a client are refused outright, as are password fields, hidden fields and dropdowns.

The staff member’s Google account address. The extension asks Google for the email address of the account it has been authorised against. It uses this for one purpose: to confirm it is signed in as the practice’s own account, and to refuse to write anything if it is not. This is what stops client details from being written into a staff member’s personal Google Contacts.

The practice’s existing Google Contacts. To decide whether a client already exists, the extension reads the names, phone numbers, email addresses and labels of the contacts in the practice’s Google Contacts account.

Where information is sent

Only to Google, and only to these addresses:

AddressWhy
people.googleapis.com Reading and writing the practice’s Google Contacts
www.googleapis.com Checking which account an access token belongs to
oauth2.googleapis.com
accounts.google.com
Signing in to Google

That is the complete list. The extension contacts no other server, including any server belonging to Atlas Veterinary Hospital. Google’s handling of the data it receives is governed by Google’s Privacy Policy.

What is stored on the computer

Everything below is kept in the browser’s own extension storage (chrome.storage.local) on that one computer. None of it is placed in Chrome Sync, so none of it is copied to Google’s servers or to any other machine by the extension.

WhatContains
A local copy of the practice’s Google Contacts For each contact: Google’s identifier for it, first name, last name, phone numbers, email addresses, and which labels it carries. Kept so that Google does not have to be re-queried on every save.
A record of recent sync attempts For each attempt: the time, the client’s name, what happened (created, updated, unchanged, skipped or error) and why.
The most recent result The last client synced, what happened to them, and any value the extension refused to use.
Settings On/off switches and formatting preferences. No personal data.
A short list of very recent saves A client’s name, phone number and email address, for the sole purpose of ignoring an identical save repeated within twenty seconds.
Sign-in state Which Google account the extension has verified itself against, when it was checked, and a short irreversible fingerprint of the access token. If Chrome is signed in to the wrong account, that account’s email address is stored here too, so the popup can say which one it found.
A page diagnostic report Written only when a staff member clicks Inspect this page. It records the structure of the form — field labels, names and whether each was filled in — to help fix the extension after a practice-management update. It does not record the value of any field. It does include the page address and up to 120 characters of any on-screen message the page displayed, which on some pages includes a client’s name.

The extension does not itself store a reusable Google credential. Signing in is handled by Chrome, which holds the access token. The one exception is an optional explicit-account sign-in mode, switched off in the configuration published here; if a future administrator turns it on, an access token valid for about an hour is kept in the same local storage.

Retention. The record of sync attempts keeps at most 500 entries and discards anything older than 30 days, pruned each time a new entry is written. The local copy of Google Contacts is refreshed on a schedule and reflects whatever is currently in the practice’s account.

Deletion. Disconnect from Google, in the extension’s popup under Tools, signs the extension out and clears the local copy of Google Contacts. Removing the extension from Chrome is what deletes everything, including the record of recent sync attempts. Neither action changes anything in Google Contacts itself.

What the extension does not do

Google API Services and the Limited Use requirements

AVA Contact Sync’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically: the data obtained through the Google People API is used only to provide and improve the contact-syncing function described in this policy; it is not transferred to others except as necessary to provide that function, for security purposes, or to comply with applicable law; it is not used for advertising; and no humans read it except where the practice’s own staff do so in the course of running the practice, or where required by law.

The extension requests two Google scopes:

ScopeWhat it is for
.../auth/contacts Creating and updating the practice’s contacts, and applying the “Atlas Clients” label
.../auth/userinfo.email Confirming which account it is signed in as, so it can refuse to write to the wrong one

Clients of the practice

If you are a client of Atlas Veterinary Hospital and you want to know what contact details the practice holds for you, or you want them corrected or removed, contact the practice directly using the details below. Removing a contact from the practice’s Google Contacts removes it from the phone system.

Changes to this policy

If this policy changes, the effective date at the top changes with it, and the updated version is published at the same address. Material changes will also be noted in the extension’s Chrome Web Store listing.

Contact

Atlas Veterinary Hospital
stan@atlasveterinaryhospital.com