Call OS · Chrome Extension
Privacy Policy — Send to Call OS
Last updated: June 8, 2026
Send to Call OS ("the extension") lets a signed-in Call OS user send the contacts they
select on a supported list view into their own Call OS dial queue. This policy explains exactly what the
extension accesses, why, and how that information is handled. The extension has a single purpose and does
not collect anything beyond what that purpose requires.
What the extension handles
- Contacts you select. When you click "Send to Call OS" on a supported page (such as
ZoomInfo), the extension reads the details of the rows you selected — name, company, phone
numbers, email, and business address — and sends them to your Call OS account so they appear in your
dial queue. It reads only the contacts you explicitly select, and only when you click the button.
- Your Call OS sign-in. So the contacts reach the right account, the extension signs
you in to Call OS. You can sign in through the extension popup (email and password, sent directly to
Google Firebase Authentication) or by being signed in on call-os.com. The resulting authentication
token is stored locally in your browser so you do not have to sign in repeatedly. Your password
is never stored by the extension.
How the information is used
It is used solely to perform the extension's single purpose: placing the contacts you select into your
own Call OS dial queue, and authenticating you so they go to your account.
What we do not do
- We do not sell or rent your data, or the contact data you send, to anyone.
- We do not transfer your data to third parties except as needed to provide the service — your selected
contacts go to Call OS (your own account), and sign-in goes to Google Firebase Authentication.
- We do not use your data to determine creditworthiness or for lending purposes.
- We do not collect browsing history, and we do not read pages other than the supported list views and
call-os.com.
Where data goes
- Contacts you select → call-os.com (Call OS import API), into your account.
- Sign-in → Google Firebase Authentication (identitytoolkit.googleapis.com,
securetoken.googleapis.com).
- Authentication token and your extension settings → stored locally in your browser only.
Data retention
Selected contacts are held only briefly in browser session storage until they are sent, then cleared.
Your authentication token remains in local storage until you sign out or remove the extension. Contacts
delivered to Call OS are then governed by Call OS's own terms.
Contact
Questions about this policy: ahubka15@gmail.com