Service providers.
The fine print.
Effective date: October 21, 2026.
This register describes the principal providers involved in Daciel’s current public acquisition and business-service workflows. A provider is used only for the feature concerned. Some act as processors; others also act independently for payments, telecommunications or domain-registration obligations.
This is a functional register, not a claim that every provider processes every account, or a substitute for the approved subprocessor and location schedule in a signed agreement.
1. OVHcloud — infrastructure
The current public website and acquisition API run on an OVHcloud VPS. Infrastructure can process hosted application records, request metadata and operational logs. Region and residency requirements should be verified for the applicable deployment before a contractual commitment is made.
2. OpenRouter and inference providers — AI
OpenRouter routes model requests. The inference provider for a selected model receives the prompt, necessary context and supported attachments. Providers can include OpenAI, Anthropic, Google, Qwen and others depending on the configured model and routing. The relevant endpoint’s location, retention and training rules must be checked for a restricted workflow; this list is not a promise that all models share one policy.
3. Stripe and Lemon Squeezy — payments
Stripe handles payments made through Stripe checkout. Legacy services can also use Lemon Squeezy, which acts as merchant of record for its checkout. The provider shown during the purchase receives payment and billing information; Daciel keeps the references and subscription state needed to manage the account.
4. Resend — transactional and subscription email
The public acquisition service uses Resend to deliver inquiry acknowledgments and newsletter confirmation or subscription messages. Delivery involves recipient addresses, message content and delivery metadata. Newsletter recipients must confirm enrollment and can unsubscribe.
5. Cloudflare — domain and DNS services
Cloudflare is used for domain and DNS workflows where configured. Domain services involve registrant and administrative details, DNS records and applicable registration information. Registry and registrar policies can require verification, disclosure or retention independent of Daciel’s application settings.
6. Twilio — communications
Twilio supports telephony and messaging integrations where enabled. Processing can include phone numbers, message content, delivery or call metadata, and recordings or transcripts if the relevant feature is enabled. Availability, verification and carrier requirements depend on the country and number type.
7. Google and performance measurement
Where configured, Google Analytics and advertising tags receive measurement events under the consent choices described in the cookies notice. Infrastructure and application diagnostics can also process technical errors and performance events. Optional measurement is distinct from essential account and security operations.
8. Customer-selected integrations and changes
Apps a business connects can receive the information authorized for their functions. Review those apps’ own terms and permissions. For a current contractual supplier schedule, locations or a proposed supplier restriction, contact Daciel before connecting the workflow. Any formal notice and objection process follows the applicable agreement.