Log inBook a demoStart free trial
Log inStart free trial

Legal

Subprocessors

The providers that process customer data for Dmand AI, what each one does and where it processes the data.

Effective

Last updated

Revision history

In short

Effective

Dmand AI runs on Google Cloud in the United States, behind Cloudflare. A small set of providers help us run the Platform: AI model providers for research and drafts, Stripe for payments, Twilio for calls, PostHog for product analytics, and the mailbox and deliverability providers behind managed mailboxes. Each is bound by a written agreement, processes data in the United States, and may use it only to provide its service to us. We email customers 30 days before we add one.

Key takeaways

  • Every subprocessor processes data in the United States
  • Each is bound by written data protection terms
  • 30 days notice before we add a new one
  • AI providers are set not to train on our data

1. What a subprocessor is

A subprocessor is a company we use that processes Customer Data, the data our customers bring to the Platform, so that we can provide the Platform to them. Our Data Processing Addendum allows us to use the subprocessors on this page and sets the rules they work under.

2. Our current subprocessors

Dmand AI subprocessors
SubprocessorWhat it does for usWhere
Google Cloud PlatformHosting, storage and backups for the Platform and all Customer DataUnited States
CloudflareNetwork security, the web application firewall and access control in front of the PlatformUnited States
Google WorkspaceSign-in for our staff’s access to our infrastructure, and hosting and sending for managed mailboxes when a customer chooses GoogleUnited States
Microsoft 365Hosting and sending for managed mailboxes when a customer chooses MicrosoftUnited States
OpenAIAI research columns and AI-drafted emails: the business fields of a record and the User’s instructionUnited States
AnthropicAI research columns and AI-drafted emails: the business fields of a record and the User’s instructionUnited States
TwilioPhone numbers and calls for the dialer, and call recordings when a User turns recording onUnited States
StripePayment processing. We do not store card numbersUnited States
PostHogProduct usage analytics in app.dmand.ai: feature events and errorsUnited States
Email verification providerChecks whether an email address can receive mail before a sequence uses itUnited States
Mailbox warm-up providerWarms up managed mailboxes before they send sequencesUnited States

Our accounts with OpenAI and Anthropic are set so that nothing we send is used to train their models.

3. Our own staff and contractors

Our staff and contractors in the United States and India may access Customer Data to run, support and secure the Platform. They do so under written confidentiality obligations and role-based access controls, and they do not read the content of customer emails except as the Data Processing Addendum allows.

4. How we choose and bind subprocessors

  1. Before we use a provider, we review its security, where it processes data and its history of incidents.
  2. Each one signs a written agreement with data protection and confidentiality terms, and may use Customer Data only to provide its service to us.
  3. We remain responsible to our customers for what our subprocessors do with their data.

5. Providers that are not on this list

  1. Apps a customer connects. Salesforce, HubSpot, Slack and the Google or Microsoft mailboxes a User connects are the customer’s own services, chosen by the customer. See Connected apps for what we access in each.
  2. Sources of our database. The public records and licensed data providers behind Profile Data supply data to us; they do not process Customer Data. The Privacy Policy describes them.
  3. Website tools. The analytics and marketing tools on dmand.ai are described in the Cookie Policy.

6. Notice of changes

We update this page and email the account owner of every customer at least 30 days before a new subprocessor starts processing Customer Data. A customer may object on reasonable data protection grounds by writing to hello@dmand.ai within those 30 days, as the Data Processing Addendum describes. The dates of past changes are in the revision history below.

7. Contact

Company
Launcheazy Inc
Mail
Privacy requests, Launcheazy Inc, 360 S Baywood Ave, San Jose, CA 95128
Email
hello@dmand.ai

Revision history

Revisions by date
DateWhat changed
November 2, 2026First published list.

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)
Read the Cookie Policy