Subprocessors

Last updated: October 21, 2026

These are the service providers that process personal data for dmswift. We update this page before we add a provider that handles customer data; write to privacy@dmswift.com to be told about changes.

Always used

• Oracle Cloud Infrastructure (Oracle) - hosts the application, its database and uploaded media. All customer and audience data. Region: Oracle Cloud Infrastructure, Israel Central (Jerusalem) region.
• Cloudflare - DNS for our domains, and routing of mail sent to our @dmswift.com addresses; where configured, private storage for off-site database backups (kept up to 30 days). Global network; United States.
• Google - Sign in with Google (your name, email and Google account ID); Firebase Hosting for the marketing website dmswift.com (no account data); Google Fonts for the dashboard only, on app.dmswift.com (your IP address); the marketing website does not use it. United States.
• Meta Platforms - the Facebook and Instagram APIs dmswift operates through. Content, replies and messages go to Meta when a customer publishes or sends them; Meta sends us comments, messages and insights for connected channels. United States / Ireland.
• Dodo Payments (Dodo Payments, Inc. and its group companies) - our Merchant of Record: checkout, payment, invoices, sales tax or VAT, and refunds. Dodo Payments receives your billing details directly and acts as an independent controller for them under its privacy policy. United States / India.

Used when configured or turned on

• Resend - sends service emails such as address verification and password resets (recipient address and the email content). United States.
• Browser push services (Google, Mozilla, Apple - whichever your browser uses) - deliver dashboard notifications, only if you enable browser notifications. The notification text passes through them.
• AI providers you choose - Anthropic, OpenAI, Google (Gemini), Groq or OpenRouter, only when a customer adds their own API key for built-in AI features. The text needed for the task (for example the message being answered and knowledge-base entries) is sent to that provider. The customer chooses the provider; without a key, nothing is sent.

Integrations a customer sets up themselves - webhooks to their own systems, a WhatsApp notification gateway, or an AI agent they connect through our API, OAuth or MCP server - receive the data that customer sends them, under the customer's responsibility.