Connected apps

1. How connections work

Every connection uses the provider’s own sign-in and consent screen (OAuth 2.0). You approve the access listed on this page; the provider then gives Dmand AI a token, which we store encrypted. We never receive, store or send the password of a connected account. A token works only for the account that approved it, and only within what that account is allowed to see.

2. Google Workspace mailboxes

Connect a Gmail or Google Workspace mailbox so sequence emails are sent from it and replies come back into Dmand AI.

1. Limits. No other Google scope, and no access to Drive, Calendar, Contacts or any other Google service. Dmand AI has no function that deletes email, although Google’s description of the scope includes deletion. Each mailbox is connected by its own owner; we do not use domain-wide delegation, so we cannot reach a mailbox that was not connected.
2. For Workspace administrators. Google Workspace can block apps that ask for Gmail access until an administrator allows them. In the Google Admin console, go to Security, then API controls, then App access control, add Dmand AI (search by name or by the OAuth client ID shown in the Dmand AI connection dialog) and allow it. Users can then connect their mailboxes.
3. Turning it off. Remove the mailbox in Dmand AI, remove Dmand AI at myaccount.google.com under Security and third-party apps with account access, or have your administrator remove it. Sending and mailbox access stop at once.

Google API disclosure. Dmand AI’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. Microsoft 365 and Outlook mailboxes

The same job for Microsoft 365, Outlook and Exchange Online mailboxes. Dmand AI is published with Microsoft as a verified publisher and uses delegated permissions only, so it acts only for the person who signed in.

1. Limits. No other permissions, no application permissions, and no access to OneDrive, SharePoint, Teams, calendars or contacts. Dmand AI has no function that deletes email.
2. For Microsoft 365 administrators. Under Microsoft’s default consent settings, users cannot grant the mail and mailbox settings permissions themselves. An administrator approves Dmand AI for the organization, directly or through Microsoft’s admin consent workflow, before users can finish connecting.
3. Turning it off. Remove the mailbox in Dmand AI, revoke the permissions at myapplications.microsoft.com, or have your administrator remove them in the Microsoft Entra admin center under Enterprise apps.

4. Salesforce

Keep accounts, contacts and leads in step between Salesforce and Dmand AI, using the field mappings and sync direction you choose.

1. Limits. Only the Account, Contact and Lead objects, and only the fields you map. No administrative access, no setup or metadata changes, and no record deletion. The connection works with the permissions of the Salesforce user who approved it, so Dmand AI cannot see or change anything that user cannot.
2. How the sync behaves. The sync runs on a schedule, aiming for about every 15 minutes for each object; timing varies with Salesforce limits. It copies values as they are at each sync, as the Terms of Service describe.
3. Turning it off. Disconnect in Dmand AI, or revoke access in Salesforce Setup under Connected Apps OAuth Usage. Sync stops at once.

5. HubSpot

The HubSpot connection does the same job as the Salesforce one for HubSpot contacts and companies: it reads and writes only the records and fields you map, in the sync direction you choose, with the permissions of the HubSpot user who approved it. HubSpot shows the exact permissions on its consent screen before you approve. To turn it off, disconnect in Dmand AI or uninstall Dmand AI under Connected apps in your HubSpot settings.

6. Slack

A notification shows the sender’s name, the subject, a short snippet and a link to the conversation in Dmand AI. Dmand AI does not read messages in your channels. To turn it off, uninstall the Dmand AI app in Slack’s app management.

7. Claude and other AI assistants

This connection runs the other way: you add the Dmand AI connector to your AI assistant and sign in with your Dmand AI account. The assistant can then search and read Dmand AI data with your account’s access and Credits, and asks before it spends a Credit. What you retrieve is delivered into your account with the assistant’s provider, under that provider’s terms and the data license in our Terms of Service. To turn it off, remove the connector in your assistant’s settings.

8. Managed mailboxes

Managed mailboxes are set up by Dmand AI on Google Workspace or Microsoft 365, on sending domains we hold for you, and connected to your Users’ sender profiles in the same way as the mailboxes above. They do not need any approval from your own Google or Microsoft administrators. They belong to you, and we transfer them on request, as the Terms of Service describe.

9. What we store and what we never do

1. What we store. Encrypted access tokens; the emails Dmand AI sent; replies and their thread identifiers, shown in the inbox; bounce and delivery events; and the CRM records and fields you sync. All of it is stored on Google Cloud in the United States.
2. What it is used for. Only to provide the features you connected the app for.
3. What we never do. Sell data from connected accounts, use it for advertising, or use it to train AI models. Our staff do not read message content except with the User’s agreement for a specific message, where needed to investigate a security problem or abuse, or where the law requires it.
4. When you leave. Synced records and mailbox data are Customer Data, deleted as the Data Processing Addendum describes.

10. Questions

Security and IT teams can write to hello@dmand.ai for more detail about any connection before they approve it.

Company

Launcheazy Inc

Mail

Privacy requests, Launcheazy Inc, 360 S Baywood Ave, San Jose, CA 95128

Email

hello@dmand.ai