Business data processing.
The fine print.
Effective date: October 21, 2026.
This overview explains the operational roles to agree before connecting business and customer information. It is not a substitute for a signed data-processing agreement or a country-specific transfer agreement.
1. Controller and processor roles
A business generally determines why and how its customer information is used in its store, website and communications. Daciel processes that information to deliver the authorized service. Daciel separately handles account, billing, support and website-inquiry information for its own operational purposes as described in the privacy notice.
2. Scope and instructions
Before onboarding, identify the relevant data subjects, data categories, purposes, integrations, retention needs, permitted agent actions and authorized contacts. Limit imported information and permissions to what the workflow needs. Do not use the general inquiry form to supply a production customer database.
3. Procurement and contractual requirements
For a DPA or security review, use the contact page and identify your business and proposed scope. Agree the processing instructions, confidentiality, security measures, supplier authorization, rights-request assistance, incident handling, audit arrangements, return/deletion and any international-transfer terms in the applicable contract. A public pricing page does not establish a bespoke residency, response-time or certification commitment.
4. AI, integrations and subprocessors
AI requests may pass through OpenRouter to an inference provider. Email, telephony, hosted payments, domains and connected applications involve their own providers and permissions. Review the service-provider register and the specific workflow configuration; an external provider’s retention or role is not uniform across all features.
5. Requests and offboarding
If a person contacts Daciel about records controlled by your business, we may direct the request to the business and assist according to the applicable agreement. Plan exports, integration revocation, domain transfers, number porting and deletion before offboarding. Records retained for legal obligations and backup lifecycle limitations must be addressed in the applicable arrangement.