Skip to content
Arcqual
Security and ownership

Your CRM, your Gemini key, your workflow boundary.

The workflow runs in the customer's own automation environment and uses their own Gemini API credentials. Arcqual does not store customer lead data.

Data path

No hidden Arcqual data layer.

Approved fields move from your CRM-connected workflow to your Gemini account and back to your CRM. Arcqual does not store customer lead data.

01

Your credentials

CRM and Gemini credentials remain in your controlled automation environment.

02

Minimum useful context

A field allowlist limits model input to the information required for qualification.

03

Visible outputs

Scores, summaries, and actions are written to the CRM for review and audit.

Shared responsibility

Clear ownership from implementation to operation.

Your team approves access, data fields, model account, and qualification policy. Arcqual configures, tests, documents, and hands over the workflow.

Agency controls

CRM permissions, Gemini account, retention settings, lead policy, and production approval.

Arcqual delivers

Architecture, mappings, workflow logic, error handling, test cases, and operating documentation.

Review the boundary

Start security review with the actual data path.