Privacy Policy

CallOpsQ is a private lead intelligence, workflow, training, and phone-verification workspace for insurance professionals. This policy explains what information CallOpsQ handles and how the current product uses it.

CallOpsQ is designed to help agents decide who to call next, reduce duplicate work, protect paid validation credits, and keep each user or workspace separated from other users and workspaces.

Account information may include name, email address, organization or agency name, role, phone number when provided, access status, workspace membership, trusted-device records, and beta/founding access settings.

Workspace data may include imported leads, contacts, phone numbers, addresses, counties, ZIP codes, email addresses, notes, call outcomes, follow-up dates, appointment dates, calendar feed tokens, import history, training progress, feedback submissions, and workspace credit settings.

Validation data may include normalized phone numbers, cached validation results, provider responses, line type, carrier, callability/activity score, validation history, credit usage, source system labels, and audit records showing whether a result was cached or paid.

CallOpsQ Companion is user initiated. A user selects or highlights a phone number and chooses to verify it before Companion sends that selected phone number to the CallOpsQ backend.

CallOpsQ checks existing saved or cached intelligence before performing paid validation. If a paid validation is required, CallOpsQ requires explicit user confirmation before spending a validation credit.

Contact information, notes, email addresses, source URLs, or source-system details are saved only after the user explicitly chooses a save or note action where that workflow is available.

Companion stores its trusted-device connection credential locally using Chrome extension storage. It also keeps local workflow state, selected workflow progress, and recent verification history so the extension can reconnect and remain useful during normal work.

SunFire content-script access is limited to approved SunFire pages and is used for workflow detection and assistance. The SunFire detector reads safe page labels, headings, route context, and workflow signals. It is not intended to collect full CRM page contents or sensitive beneficiary records.

Companion does not automatically validate phone numbers, does not automatically scrape full CRM pages, does not collect browsing history, and does not expose or store Trestle, Abstract, Supabase service-role, or other provider secrets in the extension. Provider validation occurs server-side through CallOpsQ.

CallOpsQ uses workspace data to provide lead management, calling workflows, phone intelligence, import review, duplicate protection, calendar feeds, training progress, Companion connection, feedback reporting, and administrative access controls.

CallOpsQ uses validation data to show whether a phone number appears callable, to reuse cached results before spending credits, to maintain audit logs, and to protect users from duplicate paid validations.

CallOpsQ may use service providers for hosting, authentication, database storage, email delivery, phone validation, browser-extension distribution, and application infrastructure. Current implementation includes Supabase, Vercel, Chrome extension infrastructure, and server-side phone intelligence providers configured by CallOpsQ.

Provider API credentials and service-role keys are kept server-side and are not shipped inside CallOpsQ Companion.

CallOpsQ uses authentication, workspace separation, role checks, row-level access controls, server-side API calls, and credit-preflight checks to limit access and protect paid validation usage.

Beta or founding-access users should only see their own workspace data. Administrative tools are intended for approved administrators only.

CallOpsQ retains account, workspace, lead, validation, audit, feedback, and training data while the workspace is active or while the information is needed to provide the service, support the user, maintain audit history, prevent duplicate paid validation, or satisfy operational requirements.

Workspace access can be suspended, revoked, archived, or deleted by an authorized administrator according to the access controls available in CallOpsQ.

Users choose when to import leads, verify a phone number, spend paid validation credits, save contacts, add notes, connect Companion, or subscribe to a calendar feed. Companion trusted devices and calendar feed tokens can be revoked from CallOpsQ settings where available.

Users may request access changes, suspension, revocation, or workspace review through their CallOpsQ owner or administrator.

For help, visit the public CallOpsQ Support page. Authenticated users can also use the in-app Share Feedback feature to report bugs, confusing workflows, friction, incorrect information, or improvement suggestions.

This policy may be updated as CallOpsQ changes. The date at the top of the policy will be updated when material changes are made.