Data minimization
Use allowlisted CRM properties and form fields. Exclude free-form or sensitive data that is not needed for the use case.
Security
Security is part of the workflow design—not a logo in the footer.
Arcqual is scoped around data minimization, explicit access, constrained model inputs, traceable execution, and clear ownership between your team and the implementation.
Design principles
Move the minimum data required to make the decision.
The pilot begins with a field-level data map. If a field does not improve qualification or routing, it does not need to enter the model context.
Least-privilege access
Use dedicated service credentials with access limited to the required objects, actions, and workflow environment.
Reviewable decisions
Keep source trace, policy version, reasons, confidence, route, and error state available for operator review.
Control areas
A practical baseline for agency infrastructure.
Encrypted connections
Production integrations use HTTPS/TLS endpoints. Webhook signing or provider-native authentication is used where the source supports it.
Environment-scoped secrets
API credentials belong in the orchestration environment’s secret store—not in prompts, CRM notes, or exported workflow examples.
Dedicated identities
Service accounts make access revocable and auditable without tying production workflows to an individual employee.
Versioned policy and workflow
Qualification logic, field mappings, and routing changes should move through test cases and controlled promotion.
Retries without duplicates
Idempotency keys and bounded retries reduce duplicate records and repeated downstream actions after transient failures.
Named error paths
Failures generate a visible status and owner. The workflow does not silently discard a lead or invent missing context.
LLM data policy
Model use is an architecture decision.
Provider selection, retention controls, regional requirements, and contract terms vary. Arcqual is configured around the provider and policy your organization approves.
- Constrained input assembled from allowlisted fields
- Structured output schema instead of unrestricted prose
- No credentials or secrets included in model context
- Human review when confidence or policy requires it
Example model request boundaryMinimized
Included
Service request, business context, approved commercial fields, source metadata, and qualification rubric.
Service request, business context, approved commercial fields, source metadata, and qualification rubric.
Excluded by default
Passwords, payment data, authentication tokens, unnecessary contact history, and fields outside the approved use case.
Returned
Constrained score, tier, reason codes, confidence, concise note, and review flag.
Data lifecycle
Retention follows the system that owns the record.
Exact windows are documented during architecture review. The table below describes the intended pattern, not a universal certification claim.
| Data category | Primary location | Retention approach |
|---|---|---|
| Lead record and decision fields | Your CRM | Governed by your CRM retention and deletion policy |
| Workflow execution detail | Your n8n environment or approved host | Configurable; minimize payload detail and keep only what operations require |
| Model request and response | Approved LLM provider | Determined by provider settings, plan, region, and contract |
| Credentials | Secret store | Retained until rotated or revoked; never copied into lead content |
Shared responsibility
Controls only work when ownership is explicit.
Arcqual implementation responsibility
- Document the proposed data flow and field map
- Configure bounded model inputs and output schema
- Implement review gates, error handling, and source trace
- Provide workflow handoff and operating documentation
Agency responsibility
- Approve data sources, providers, and access scope
- Manage CRM users, service accounts, and offboarding
- Maintain consent, privacy notices, and retention policy
- Review workflow changes and production outcomes
Security questions
Direct answers, scoped to your architecture.
Is Arcqual SOC 2 certified?
This site does not claim a certification that has not been independently verified. The architecture can be designed around vendors and hosting environments that meet your procurement requirements; the exact control boundary is documented before implementation.
Is lead data used to train public models?
That depends on the approved provider, plan, and data controls selected for your implementation. The architecture review records the provider policy and required settings before production traffic is enabled.
Can the workflow run in our n8n environment?
Yes, when your environment and access model are suitable. Hosting location, credential ownership, logs, backups, and operational responsibility are defined as part of the pilot scope.
Can we exclude sensitive fields?
Yes. Field-level minimization is a core design step. Only approved fields should be assembled into the qualification context.
Security review
Start with the diagram, field map, and control boundary.
We will show what moves, where it moves, which identity performs the action, and where a human can intervene.