Subprocessors, integrations and transfers

Last updated: 25 September 2026

AMZSTRATEGY LLC uses providers to deliver DayInFlow. This page distinguishes the platform subprocessors from services that a customer voluntarily connects. The presence of a name does not mean that the related integration is available in every country, plan or account, nor that it has received all external commercial approvals.

1. Platform services

Necessary categories of services include application and database infrastructure, authentication, email delivery, payments and billing, SMS when enabled, on-demand AI processing, monitoring and support management. Providers observed or expected in the DayInFlow architecture include Lovable Cloud for the managed application and backend, Stripe for payments and subscriptions, Twilio for SMS, as well as the email sending and AI services configured in the production environment. The precise legal names of all entities, the processing regions, the delegated functions and the durations must correspond to the published configuration and the contractual agreements in force. We do not attribute to a provider a certification or a localization that has not been verified.

2. Customer-chosen services

When an authorized user connects a Google Calendar, Microsoft Calendar or Zoom account, DayInFlow exchanges the data necessary to synchronize availability, events or video links in accordance with the permissions approved by the account holder. Services such as Zapier, Make, n8n, WordPress, Wix, Mailchimp and Brevo can only be used via connectors or APIs actually configured by the customer. The customer remains responsible for their own settings, the permissions granted and the flows created to third parties. A connection that is not enabled does not access the customer's data.

3. Data, regions and safeguards

Data transferred to a provider is limited to the function required: for example, transaction data to the payment processor; number, text and delivery metadata to the SMS provider; address, subject and content to the email provider; prompts and authorized context to the AI provider; metadata and events to the connected calendar. Some processing may take place in the United States or in other countries where providers operate. When the law requires a specific mechanism for transfers, we apply adequacy decisions or appropriate contractual safeguards, including standard contractual clauses if necessary.

4. Updates and requests

We will update this page when an actual provider is added, replaced or terminated, indicating for each the legal identity, purpose, data category, location and relevant transfer safeguard. B2B customers will receive notice of relevant changes in accordance with the DPA. For information or substantiated objections: support@dayinflow.com.