Scope
This Privacy Policy applies to the Call OS website, desktop application, hosted services, and support channels. It does not replace the privacy terms of third-party services you connect, such as your telephony, identity, billing, CRM, or AI providers.
Owner IQ, the business database that can be searched from inside Call OS, is a separate service with its own Privacy Policy and Terms of Service. When you move a record from Owner IQ into Call OS, the Call OS copy is handled under this Policy.
“Call OS,” “we,” “us,” and “our” refer to the provider of the Call OS service. “You” includes individual users and the organization that authorizes their use.
Information we collect
Account and subscription information
We may receive your name, email address, user identifier, organization, access tier, authentication status, subscription status, and support history. Payment card data is handled by the payment processor and is not intended to be stored directly by Call OS.
Lead and CRM information
Information you import, select from Owner IQ, capture through an approved extension, or create in the workflow may include company and owner names, phone numbers, email, title, address, industry, company size, website, notes, follow-ups, appointments, DNC status, provenance, and related business context.
Call and workflow information
Depending on your configuration, Call OS may process call identifiers, phone numbers, timestamps, duration, connection state, outcome, disposition, transcript, summary, quality review, follow-up details, appointment status, keyboard or voice actions, and diagnostic events. Audio may be processed in real time for transcription, outcome detection, live assistance, screener handling, or voice features. Reps may also record notes and observations about the people they speak with, such as title, objections, or how a conversation went.
Call recordings
Call OS records connected calls, including both the rep’s audio and the other party’s audio. Recordings are saved on the rep’s device and uploaded to the Google Drive of the manager your organization designates (or of the account holder when there is no organization). Authorized managers in your organization can play and download them. Recordings are transcribed and may be summarized or reviewed for quality.
Voice and live listening
If a rep uses voice features, Call OS processes voice samples and the text to be spoken, which can include a prospect’s name and company. If your organization uses remote calling or live listening, call audio is relayed in real time to the authorized rep or manager; the live relay itself does not store it.
Intelligence and research information
Call OS may process company and owner context, research queries, generated dossier fields, public-source references, and call-derived signals. Research about a company drawn from the public web may be reused across Call OS customers so the same company is not researched twice; it is about the business, not about your calls.
Device and usage information
We may collect app version, operating status, feature settings, error reports, updater status, device-local identifiers, IP address, browser or operating-system information, and product interaction events needed to run, secure, improve, and support the service.
How we use information
- Authenticate users and apply account, plan, and usage limits.
- Load, sort, enrich, display, dial, update, and restore authorized lead queues.
- Provide transcription, live assistance, screener handling, dispositions, appointments, follow-ups, history, analytics, and support.
- Sync authorized CRM, event, and per-number performance information across approved devices.
- Improve reliability, diagnose failures, prevent duplicate or unsafe state transitions, and distribute updates.
- Process billing, trials, promotions, cancellation requests, and account communications.
- Protect Call OS, users, prospects, and the public from fraud, abuse, security threats, and unlawful use.
- Comply with law and enforce agreements.
Local and cloud storage
Call OS uses a mixed local-and-cloud model. Some queue state, device preferences, working files, runtime controls, audio settings, recordings, and cached information can remain on the user’s device. Authenticated cloud services store or synchronize account, queue, CRM, call record, transcript, event, performance, research, support, and subscription information, and recordings are kept in your organization’s Google Drive as described above.
Your organization controls the data it chooses to import and the connected services it enables. Removing a local copy does not necessarily remove a synchronized cloud record, and deleting a cloud record does not necessarily erase an independently retained copy held by a connected third party.
Signals shared across customers
Each organization’s records stay within that organization. A narrow set of signals about phone numbers and companies is shared across all Call OS customers, because it protects the people being called and cuts wasted dials:
- Numbers reported as disconnected, invalid, or asking not to be called. A reported number may be suppressed for every customer. Other customers receive only the number’s status. The report itself, which can include the call’s transcript, is visible only to the user who made it and to our staff who review reports.
- Counts of dial attempts and answers per number and area, used for reach statistics and to rank numbers and areas. These are counts, not call content.
- Marks that a number was confirmed to reach the listed business.
- Research about a company drawn from the public web.
These signals never include recordings, transcripts, notes, dispositions, appointments, CRM or imported records, or information from services you connect. Other customers are never told which organization or user a signal came from. We keep a record of where each shared signal came from and the basis for using it.
Signals from your organization’s calls are not added to the Owner IQ database, and are not licensed to anyone, unless your organization agrees to that in a separate written agreement.
Retention
We retain information for as long as reasonably needed to provide the service, maintain the working history requested by users, comply with law, resolve disputes, enforce agreements, and protect the system. Retention varies by data type and customer configuration.
Local files, recordings, and caches remain until removed by the user, an updater, or the application. Recordings in your organization’s Google Drive stay under your organization’s control there. Some company-level research may be cached for a defined freshness window and refreshed later. Suppression of a number reported as asking not to be called is kept so the request keeps being honored. Billing, security, and audit records may be retained longer where required.
Your choices and rights
You may update certain account, CRM, queue, follow-up, DNC, display, voice, and calling settings in the product. You may request access, correction, deletion, portability, or restriction where applicable by emailing privacy@call-os.com. We may need to verify your identity and the authority of your organization before fulfilling a request.
Users can disconnect supported third-party integrations through the relevant product or provider controls. Your organization may also control retention, exports, administrative access, and account closure.
Security
We use administrative, technical, and organizational safeguards designed for the nature of the information processed, including authenticated access, user-scoped records, provider-specific credentials, controlled synchronization, and product-state protections. No system is completely secure, and we cannot guarantee that unauthorized access, loss, or misuse will never occur.
Report suspected security issues to security@call-os.com. Do not send passwords, API keys, payment details, or unredacted prospect lists by email.
Outbound calling and recordings
You and your organization are responsible for the legal basis, list provenance, suppression handling, calling hours, consent, disclosures, and recording or transcription rules that apply to your outreach. Some states require every party’s consent before a call is recorded; because Call OS records connected calls, your organization must give any notice and obtain any consent those laws require. Call OS features do not create permission to call, record, transcribe, enrich, or retain information.
Configure the service to match the laws, contracts, and policies that govern your use. If you are not authorized to process a record, do not load or call it through Call OS.
International use, children, and changes
Call OS is designed for business use and is not directed to children. Do not use the service if you are not old enough to enter a binding contract or if your organization has not authorized you.
Information may be processed in the United States and other locations used by service providers. Where required, your organization is responsible for appropriate transfer and processing terms.
We may update this Policy as the product, law, or providers change. Material changes will be identified by a new effective date or other reasonable notice.
Contact
Privacy questions and rights requests: privacy@call-os.com
General product support: support@call-os.com