Adomo Help Center

Platform Guide

Getting Started

Log in to your Adomo dashboard at app.adomo.ai to access all platform features. Your dashboard provides an overview of key metrics, recent activity, and quick actions.

Dashboard Overview

The main dashboard displays real-time data about your business operations, including sales performance, customer interactions, and team productivity.

Roles and Permissions

Adomo supports role-based access control. Administrators can assign roles to team members to control access to different modules and data. Contact your account administrator to request permission changes.

Integrations

Available Integrations

Adomo connects with popular business tools including email providers, calendar apps, payment processors, and communication platforms.

Setup

Navigate to Settings > Integrations to view available connectors. Each integration includes step-by-step setup instructions and configuration options.

Troubleshooting

If an integration is not syncing properly, verify your API credentials, check that the third-party service is operational, and review the sync logs under Settings > Technical > Integration Logs.

Account Management

Creating an Account

Visit app.adomo.ai/signup to create a new account. You will need a valid email address and will be asked to verify it before accessing the platform.

Password Reset

Click "Forgot Password" on the login page to receive a reset link via email. The link expires after 24 hours. If you do not receive the email, check your spam folder or contact support.

Profile Updates

Update your name, email, phone number, and notification preferences under My Profile in the top-right menu.

Billing and Subscriptions

Plans and Pricing

Adomo offers flexible plans to match your business needs. Visit adomo.ai/pricing for current plan details and feature comparisons.

Managing Subscriptions

View and manage your subscription under Settings > Billing. You can upgrade, downgrade, or cancel your plan at any time. Changes take effect at the start of your next billing cycle.

Invoices

Download invoices from Settings > Billing > Invoice History. Invoices are generated on the first of each month and sent to your billing email address.

Who is this for? This article has two parts. For Users covers how to use the meeting agent in your Zoom calls. For Admins covers how to set Adomo up in Zoom and control what the agent is allowed to do.

The Adomo meeting agent joins your Zoom meetings as a quiet participant, listens for a wake word, and responds when spoken to. It can pull a report, look up a customer, draft a follow-up, or kick off a process on the spot, on behalf of whoever asked.

The agent acts as a real teammate: it only does what the person asking is authorized to do, every action is logged, and anything that would need sign-off under your DOAG policy is declined in the meeting rather than run without approval.

For Users

What you can ask the agent to do

Anything Adomo can do for you outside the meeting, phrased in plain English. For example:

• "Adomo, what was last quarter's pipeline coverage for the West region?"
• "Adomo, pull up the renewal process for Acme and tell me where it stands."
• "Adomo, draft a follow-up email to the customer summarizing what we just agreed."
• "Adomo, kick off the vendor onboarding SOP for the company we just discussed."

The agent replies in the meeting as text shown in the Adomo in-meeting panel. Actions that would require sign-off under your DOAG policy are not executed in the meeting - the agent declines and explains that the action needs approval, and the denial is logged on the session. Run the action from the Adomo app afterward to go through the normal approval flow.

When the agent is (and isn't) listening

The agent only acts when it hears a wake word your admin has configured (by default "Adomo", "Hey Adomo", or "Hi Adomo" - matching is fuzzy, with a sensitivity threshold your admin can tune). Until then, nothing is processed by the LLM. Speech is transcribed live by Zoom's own real-time media service, and the agent receives only the lines it needs to respond to.

You'll see a visible indicator in the Adomo in-meeting panel whenever the agent is listening for a wake word, and a second indicator when it's actively processing a request. Session records (wake-word hits, agent responses, tool calls, and denials) are kept on the meeting session and visible to admins under Meetings > Sessions.

Link your Zoom account (one-time)

So the agent can act "as you" during meetings, you link your Adomo account to your Zoom identity once:

1. In Adomo, open Integrations > Zoom.
2. Click Link Zoom Account.
3. Sign in to Zoom and approve the permissions.
4. You'll be returned to Adomo with a Linked status showing which Zoom account you linked.

You can check your status (Linked / Expired / Error) and unlink at any time from the same page.

If you don't link your Zoom account, the agent still listens in meetings you're in, but will treat you as an external participant: it will answer general questions but won't use tools or take actions on your behalf.

Unlink your Zoom account (revoke access)

You can revoke the meeting agent's access to your Zoom identity at any time:

1. In Adomo, open Integrations > Zoom and click Unlink. This deletes the stored Zoom token immediately and stops the agent from acting on your behalf; your status returns to unlinked.
2. To also remove Adomo's access on Zoom's side, sign in at marketplace.zoom.us, open Manage > Added Apps, find the Adomo app, and click Remove. We recommend doing both.

After you unlink, the agent treats you as an external participant in meetings: it will answer general questions but won't use tools or take actions on your behalf until you link again.

Join a meeting with the agent

If your workspace has installed the Adomo Zoom app, the agent is already available in your meetings. It joins automatically when real-time media starts for a meeting covered by the Adomo Zoom app - there is no separate invite step. You can pause it at any time with the Pause button in the Adomo panel.

During the meeting you can open the Adomo panel in Zoom to see:

• Whether the agent is connected
• Actions the agent is running or has completed, with their results
• The agent's responses
• A chat box for messaging the agent directly

What the agent will not do

• Take actions beyond your own permissions. If you can't do it in the Adomo app, the agent can't do it for you in the meeting either.
• Act on behalf of someone who hasn't linked their Zoom account. External participants get general answers only, no tool use.
• Bypass approvals. Anything that requires a human sign-off outside the meeting is not executed in the meeting: the agent declines, and you run the action from the Adomo app afterward.
• Auto-escalate. If a request needs admin or builder permissions you don't have, the agent tells you that in plain language rather than trying anyway.

User FAQ

Can I mute the meeting agent?

Yes. The agent only acts on wake-word hits, so simply not using the wake word is the easiest "mute". You can also disable the Adomo app for a specific meeting from the Zoom apps panel.

What if two people say the wake word at once?

Requests are handled one at a time in the order they were spoken; a second request is queued and answered after the first finishes. The session log shows which participant each response was for.

Can I review what the agent did?

Session review is an admin feature. Ask a workspace admin to open Meetings > Sessions, where every wake-word hit, agent response, tool call, and denial for your meeting is logged.

For Admins

Setting up the meeting agent has four pieces:

1. Create a Zoom Marketplace app and connect it to Adomo.
2. Configure what the meeting agent is allowed to do.
3. Have users link their Zoom identities.
4. (Optional) Review meeting sessions in the admin panel.

1. Create a Zoom Marketplace app

Before you start, you need:

• A Zoom account with Real-time Media Streams (RTMS) available and enabled in your Zoom account settings.
• A Zoom user with Marketplace developer rights.
• Workspace admin rights in Adomo.
• Go to marketplace.zoom.us and sign in with a Zoom account that can create apps for your organization.
• Click Develop > Build App and choose the General App type.
• Set the app's Redirect URL to the OAuth Callback URI shown on the Zoom integration's Configure form in Adomo (open Integrations > Workspace, find Zoom, and choose Configure). Set the Webhook Endpoint URL to the webhook URL shown in Meetings > Agent Config after you set the Zoom App Name (see step 2 below). Copy both exactly - they're specific to your workspace.
• Under Scopes, add the scopes needed for the meeting agent:
  • user:read:user and user:read:email - identify the user who installs the app
  • The RTMS scopes Zoom requires for real-time media access
  • Any additional scopes for tools you plan to expose (for example, cloud recording read if you want the agent to reference past meetings)
• Under Event Subscriptions, subscribe to the RTMS meeting events: meeting.rtms_started, meeting.rtms_stopped, and meeting.rtms_interrupted.
• In the Zoom app's App Credentials section, copy:
  • Client ID
  • Client Secret
  • Secret Token (Adomo calls this the Webhook Secret Token)
• In Adomo, paste each value into the matching field on the Zoom integration's Configure form, then save. Adomo verifies the configuration and reports success or a specific error.
• Publish or distribute the app according to your org's Zoom policy. Most customers use an internal ("intra-account") app so only people in your Zoom account see it.

If credentials later expire or get revoked, the connection will show as Expired or Error on the Zoom integration page with a link to re-authenticate.

If sessions show the agent never receiving audio, confirm RTMS is enabled for your Zoom account and the RTMS event subscriptions were added in step 5.

2. Configure the meeting agent

Open Meetings > Agent Config and set:

• Zoom App Name - a URL slug that must match your Zoom Marketplace app. Adomo shows the resulting webhook URL to paste into Zoom.
• Status - the Enabled / Disabled toggle for the workspace. You must save the configuration before you can enable it. Disabled means no new agent sessions start, even if the Zoom app is installed.
• Model - the LLM model name the agent uses (free text, for example claude-sonnet-4-6).
• System prompt - the base instructions for the agent (tone, guardrails, what to decline). A sensible default is prefilled.
• Wake words - one or more trigger phrases (by default "Adomo", "Hey Adomo", and "Hi Adomo"), plus a similarity threshold controlling how close a spoken match must be.
• Tool Access - which workspace tools the agent may invoke during meetings. Participants' own permissions and your DOAG policy still apply. If a tool isn't checked here, the agent cannot call it during a meeting, even if a user has access to it in the app.

If you haven't configured the meeting agent, users can't start sessions. There is no implicit default set - this is intentional, so nothing runs in live meetings without admin consent.

Enabling or disabling the agent takes effect on the next meeting start. Meetings already in progress continue until they end.

3. User identity linking

For the agent to act on behalf of a specific participant, that participant must have linked their Adomo account to their Zoom identity.

• Users do this themselves from Integrations > Zoom: click Link Zoom Account, sign in to Zoom, and approve the permissions.
• Each user manages their own link from that page, where they can see their status (Linked / Expired / Error) and unlink at any time. There is currently no admin roster of link status.
• If a user's link shows Expired, have them re-link from the same page; the old token is replaced. Until then, the agent treats them as an unlinked external participant.

What happens to participants who aren't linked. The agent treats them as unauthenticated external participants: they can ask general questions and get LLM-only answers, but the agent will not call tools or take actions on their behalf. This is the conservative default and cannot be loosened.

4. Review meeting sessions

Meetings > Sessions shows every meeting the agent has joined, with:

• Zoom meeting UUID, status, start and end times, and duration
• Counts of transcript lines, wake-word hits, tool invocations, and policy denials, plus a timeline of each wake-word hit (participant and matched word), agent response, tool invocation, denial, and error
• Errors or reconnection events (for example, if the RTMS stream dropped mid-meeting)

Use this panel to audit the agent's behavior and debug failed sessions.

Revoke the Zoom integration

To remove Adomo's access to Zoom for the whole workspace:

1. Stop new sessions. In Meetings > Agent Config, switch Status to Disabled. No new agent sessions will start; meetings already in progress finish normally.
2. Clear the connection in Adomo. Open Integrations > Workspace > Zoom > Configure and remove the stored credentials (Client ID, Client Secret, and Webhook Secret Token), then save. Adomo stops making Zoom API calls and the connection shows as not configured.
3. Uninstall the app on Zoom's side. Sign in at marketplace.zoom.us with a Zoom admin or the developer account that owns the app, open Manage > Added Apps, and Remove the Adomo app. This deauthorizes Adomo and revokes the OAuth tokens Zoom issued. If you no longer need the app at all, delete or deactivate the Marketplace app itself as well.

Individual users can revoke their own link without affecting the rest of the workspace by unlinking from Integrations > Zoom (see Unlink your Zoom account under For Users).

What happens to data. Unlinking or clearing the configuration removes the stored Zoom tokens right away. Session records already captured (wake-word hits, agent responses, tool calls, and denials) remain under Meetings > Sessions for your workspace's audit-log window; contact your account team to delete them sooner or about specific retention requirements.

Security model (what the agent can and can't do)

• Per-user scoping. When the agent invokes a tool during a meeting, it uses the requesting participant's identity and credentials, not a shared service account. If the participant can't do something in the Adomo app, they can't do it via the agent either.
• No privilege escalation. If a request requires admin or builder permissions the participant doesn't have, the agent declines in plain language and logs the denial in the audit trail.
• No ambient authority for external participants. Anyone without a linked Adomo identity gets LLM-only answers.
• Approvals are not bypassed. Actions that would require sign-off under your DOAG policy are not executed in the meeting - the agent declines, explains that the action needs approval, and the denial is logged on the session. The participant can run the action from the Adomo app afterward to go through the normal approval flow.
• Everything is logged. Every wake-word hit (who triggered it and which word matched), every response the agent gave, every tool call, and every denial is recorded on the meeting session and available in the admin panel.

Admin FAQ

Can I limit the agent to certain meetings?

Yes. The Adomo Zoom app is installed per user / per meeting in the standard Zoom Marketplace way. Combine that with the Tool Access list to control both where the agent runs and what it can do when it does.

Can I disable the meeting agent for the whole workspace temporarily?

Yes. Switch the Status toggle to Disabled in Meetings > Agent Config. Active meetings continue until they end; no new meetings will use the agent.

How do I rotate Zoom app credentials?

Update them in the Zoom Marketplace, then paste the new values into the Zoom integration's Configure form (Integrations > Workspace > Zoom > Configure) and save. The old values are overwritten.

How do I revoke Adomo's access to Zoom?

See Revoke the Zoom integration above. In short: set Status to Disabled in Meetings > Agent Config, clear the credentials on the Zoom Configure form, and uninstall the Adomo app from marketplace.zoom.us. Individual users can unlink their own Zoom account from Integrations > Zoom.

What about data retention?

Session records (wake-word hits, agent responses, tool calls, and denials) are kept on the meeting session and visible to admins under Meetings > Sessions. Contact your account team about retention requirements.

Does the agent join meetings without anyone inviting it?

It joins automatically when real-time media starts for a meeting covered by your Adomo Zoom app. If the app isn't installed on a given meeting, the agent doesn't join.

Can I restrict which tools the agent uses for which users?

Tool access is enforced by each user's existing Adomo permissions. To limit what a specific user's agent can do, adjust that user's role and tool access the same way you would for the rest of the Adomo app.

Who is this for? Everyone who approves work in Adomo, plus a short section for admins on authority policies, delegation, and external approvers.

Adomo's core promise is that AI proposes and humans decide. When a process reaches a step that needs a person, it creates a decision request, routes it to the right approver, and waits. This article covers how to respond, what your options are, and how routing and escalation work.

For Users

Where approvals reach you

• Your channels. Adomo messages you through the channels in your preference order (Email, SMS, Slack, Microsoft Teams, Google Chat, WhatsApp, mobile push), with a button or secure link to respond. See Notifications (for Users) to set these up.
• The Approvals page. Everything waiting on you, in one list, with a second tab showing what you've already responded to.
• The mobile app. Approvals are a first-class screen; respond from your phone in a couple of taps.

Your response options

Every decision shows you the context: what's being asked, the relevant data, and any attached documents. Depending on how the process was built, you'll see some or all of:

• Approve - the run continues.
• Reject - the run stops (or takes the rejection path the process defines).
• Request revision - send feedback in your own words. Adomo reruns the relevant steps with your feedback applied and brings the result back to you. Processes can cap how many revision rounds are allowed; once the cap is reached, the revise option is disabled and you choose one of the remaining actions instead.
• Edit - correct the data directly before approving (for example, fix a number or reword a draft email). Your edit is recorded alongside the approval.

Some processes define custom options beyond these (for example, Escalate). Whatever you choose, the decision is attributed to you by name, timestamped, and permanently logged.

Reminders and what happens if you don't respond

Adomo sends each request on the first of your preferred channels it can reach you on. Processes can define reminder schedules ("remind daily after two days") and a timeout: when the window passes with no response, the request escalates to the next approver in the chain, and the timeout is logged. You never silently block a process by being busy.

I approved something by mistake. Can I undo it?

No - a recorded decision can't be reversed, and the run continues from your approval. What you can do: open the run's timeline to see what has executed so far, pause the process to stop further runs, and tell the process owner or your workspace admin right away. If data was changed in a connected system and you need help unwinding it, contact [email protected].

Out of office or on vacation? Delegate your approvals

Ask your workspace admin to set up a delegation: your approval authority is temporarily granted to a colleague for a defined period, in full or only for specific kinds of decisions. Everything your delegate approves is logged as approved-by-delegation, so the trail stays clean.

For Admins

Authority policies

Under Settings > DOAG policy, you can define policies that gate specific action types behind authority levels and thresholds, for example:

• An analyst can approve variances up to $10,000; anything larger escalates to a manager, then a VP, then an executive.
• Contract approvals over a defined duration always require legal.

When a run hits a gated action, Adomo evaluates the policy at that moment: if the requesting person (or the AI agent) has sufficient authority, the action proceeds; if not, it automatically escalates to the next level in the chain. Policies can define an agent ceiling: a maximum authority level for AI agents. When set, any action requiring authority above that ceiling automatically escalates to a human in the chain. Every authority decision is logged with the policy and the evaluation that produced it.

To create or update a policy, open Settings > DOAG policy > Import and drop in your policy document. Adomo drafts the roles, action types, thresholds, rules, and escalation paths from it; review the draft, then click Activate Policy to replace the active policy in that category.

Policies are versioned. A run executes under the policy version active when it ran, so historical runs stay auditable even after you change the rules.

Delegations

Set up time-bounded delegations under Settings > DOAG policy > Delegations: click Create Delegation and pick the delegate user, the scope (all of their authority or only specific roles or action types), and the start and end dates. Delegations expire automatically, can be revoked early, and every use is logged.

External approvers

Some decisions belong to people who don't sign in to Adomo (outside counsel, auditors, a customer contact). Register them under Settings > DOAG policy > External Authorities with a name and a contact method. The channel for that contact method (for example Email or SMS) must already be enabled under Settings > Communication > Channels. They receive each request through that channel with a secure link and respond from there; their decisions are logged like anyone else's. For SMS contact methods, you must attest the person's consent on record first (see Channels Setup (for Admins) and SMS Messaging and Opt-In).

Admin FAQ

Can one decision require multiple approvers?

Yes. Decision steps support sequential chains (one after another) and parallel groups, depending on how the process is built.

Where do I see the full decision history?

Every run's timeline shows each decision: who was asked, on which channels, when they responded, what they chose, and any edits or revision feedback.

What if the assigned approver has left the company?

Update the process's assignees, or rely on the timeout escalation to move the request up the chain. Deactivating a user does not delete their past decisions; the audit trail is permanent.

Who is this for? End recipients of Adomo SMS messages, and the mobile carriers who require a publicly reachable description of how consumers consent to receive messages from our numbers. This article is the canonical URL Adomo submits for SMS registration (10DLC, toll-free, short code).

Adomo sends SMS messages on behalf of our customers (workspace admins) to reach their own team members and approved contacts with operational, transactional, and notification content. Adomo itself does not send marketing SMS, and does not use any third party's phone number without that third party's explicit opt-in.

Who we are

• Brand name: Adomo
• Operating entity: CXO AGI, LLC
• Website: adomo.ai
• Support: [email protected], +1 (866) 995-4498
• Privacy policy: adomo.ai/privacy-policy
• Terms and conditions: adomo.ai/terms-conditions

What messages we send

Adomo SMS messages are strictly operational. They fall into these categories:

• Approval requests. A short summary of an item awaiting the recipient's decision, plus a secure link to review and respond.
• Status updates. Confirmation that an approval was recorded, that a process completed, or that a scheduled job ran.
• Direct user-to-user notifications. When another authorized member of the recipient's workspace directs Adomo to notify the recipient about a specific piece of work.

We do not send marketing messages, promotional offers, or third-party advertising via SMS.

How consumers opt in

Adomo SMS is never sent to a phone number until the owner of that number has given explicit, affirmative consent to receive SMS through the Adomo app. There are two equivalent consent flows, both of which record the consent with a timestamp so that proof of opt-in is retained for the lifetime of the relationship:

1. Self-service consent in the Adomo app. The recipient signs in to Adomo, opens Settings > Notifications, and enters their own mobile phone number as a contact method. Inline with that phone number, Adomo displays a consent checkbox labeled with the workspace's SMS disclosure text and a View consent terms link to the workspace's published consent terms. The default disclosure text is: > I consent to receive transactional SMS from this platform at > the number above. Reply STOP to opt out. Msg & data rates > may apply. (Workspace admins may customize this text. A View consent terms link to the workspace's published consent terms is always shown next to the checkbox.) The recipient must explicitly tick the checkbox to consent. Adomo records the consent boolean and timestamp on the contact method. Until the box is ticked, Adomo will not dispatch any SMS to the number; outbound notifications fall through to the next channel in the recipient's preferences.
2. Admin attestation for external authorities. When a workspace admin provisions an SMS contact method for an external authority (for example, an outside approver who does not sign in to Adomo directly), the admin sees the same disclosure text and the same checkbox in the admin External Authorities tab and attests, on the record, that the external authority has consented out-of-band (typically via a signed agreement, a written authorization, or an equivalent record the workspace keeps on file). As with user self-consent, Adomo blocks SMS dispatch to the number until the attestation is recorded.

Adomo does not purchase, rent, or otherwise acquire phone numbers from third-party lists, and does not send SMS to any number whose record does not carry a recorded consent.

Message frequency

Message frequency varies with the recipient's workspace activity. Typical recipients receive approximately 1 to 10 messages per week. Busier workspaces or higher-volume approvers may receive more. A typical workspace sends no marketing SMS.

Message and data rates

Message and data rates may apply. Adomo does not charge the recipient for messages; however, standard messaging rates from the recipient's mobile carrier apply.

How to get help

Reply HELP to any Adomo SMS message to receive support contact information. The auto-reply directs questions to [email protected], the support address of our operating entity, CXO AGI, LLC, monitored by the same support team. You can also email [email protected] or call +1 (866) 995-4498.

How to opt out

At any time, the recipient may stop receiving Adomo SMS messages by any of these methods:

• Reply STOP to any Adomo SMS. The following keywords are all recognized and handled automatically: STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT. The number is added to our suppression list immediately, one confirmation message is sent, and no further SMS will be dispatched to the number.
• Reply HELP to any Adomo SMS to receive support contact information (the reply directs questions to [email protected]). HELP and INFO are both recognized.
• Untick consent or remove the number in the app. Sign in, open Settings > Notifications, and either untick the SMS consent checkbox or remove the mobile phone number from the contact methods list. SMS dispatch stops immediately.
• Contact support. Email [email protected] or call +1 (866) 995-4498. We will remove the number from all outbound SMS within one business day.

Opting out of SMS does not cancel the recipient's Adomo account or remove them from their workspace. The recipient may continue to receive approval requests and notifications through other channels (email, Slack, Microsoft Teams, Google Chat, WhatsApp, in-app, mobile push) if they have configured them.

After opting out, the recipient may opt back in at any time by re-ticking the consent checkbox in Settings > Notifications, or by replying START (or UNSTOP or YES) to an Adomo number.

Data handling

• Phone numbers are stored encrypted and are used only for the purposes described above.
• Adomo does not share, sell, rent, or trade phone numbers with third parties. Phone numbers may be shared with our downstream SMS delivery providers (for example, Twilio) strictly to deliver the messages the recipient has opted in to receive.
• When a number is removed (by opt-out or by deleting it from Settings > Notifications), Adomo retains it only as required for regulatory record-keeping (typically proof of consent and opt-out history) and otherwise deletes it from active systems per our data retention policy.

Full details are in our Privacy Policy.

Sample messages

A typical Adomo approval SMS to a workspace member looks like this:

[Adomo] Approval needed: Q2 Marketing Spend Increase. Requested by Jane Smith. Log in to respond.

A typical Adomo approval SMS to an external approver looks like this:

[Adomo] Approval needed: Increase Q2 marketing spend ($42,000 threshold). Requested by Jane Smith. Approve: https://app.adomo.ai/a/ab12cd34 | Reject: https://app.adomo.ai/r/ab12cd34 | Reply STOP to opt out, HELP for help

For carriers and compliance reviewers

If you are a mobile carrier, aggregator, or compliance reviewer evaluating Adomo for messaging registration, please reach out to [email protected] for additional documentation, consent-flow screenshots, and sample traffic.

Who is this for? Anyone who connects a Google Workspace account (Gmail, Drive, Calendar, Docs, and the rest) to Adomo, and admins who need a plain-language summary of how Adomo handles that data. This is the canonical Help Center page describing Adomo's use of Google user data and how to delete it. The full legal text is in our Privacy Policy.

When you connect Google Workspace, Adomo only acts on your behalf to run the features and workflows you ask it to. This article explains what we access, what we keep, and how to turn it off and delete it.

What Adomo accesses, and why

Adomo requests Google access only to power features you can see in the product — for example reading and drafting email, finding and editing the documents you point it at, scheduling calendar events, or posting to a Chat space. Google's consent screen lets you grant or decline each permission individually; any feature that needs a permission you declined simply stays unavailable until you grant it.

By default, Adomo's access to Drive, Docs, Sheets, and Slides is per-file: it can only open files you create with Adomo or pick for it through the Google file picker. It cannot browse or search the rest of your Drive. (Self-hosted customers can choose a broader Drive mode; your admin will tell you if that applies to you.)

How we use it (Limited Use)

Adomo's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements:

• We use Google Workspace data only to provide the features you use in Adomo.
• We do not sell it, use it for advertising, or assess credit-worthiness with it.
• We do not transfer it to others except to provide those features with your consent, for security, or to comply with the law.
• We do not let people read your Google Workspace data except with your consent, for security, to comply with the law, or in aggregated and anonymized form.

We do not use your Google Workspace data to train generalized AI or machine-learning models. When a workflow uses AI, your data is sent to the AI provider only to carry out that specific task, and our AI providers are contractually prohibited from training general models on it.

What we keep, and for how long

• Connection token — kept (encrypted) while your Google Workspace account is connected, so scheduled and recurring workflows can run on your behalf. Removed when you disconnect.
• Account identifier (your Google email and name) — kept while connected; deleted within 30 days of disconnecting.
• Workflow history — records of which features ran, kept for your workspace's audit-log window.
• Live workflow content — the actual email/file/calendar content a workflow touches is processed in the moment and not kept, unless you explicitly save it (for example, into your knowledge base).

Disconnect and revoke access

1. In Adomo, go to Settings → Integrations → Google Workspace and click Disconnect. This stops all Google API calls and removes the stored connection token.
2. To also remove Adomo's access on Google's side, visit myaccount.google.com/permissions, find Adomo, and click Remove access. We recommend doing both.

Request deletion of your data

Disconnecting removes the connection token immediately. To also delete any Google Workspace content that a workflow saved (for example in your knowledge base) or that remains in workflow history, email [email protected] (or open a ticket from the Help Center). We action verified deletion requests within 30 days, except where we must retain limited records for security, fraud prevention, or legal compliance.

If your whole workspace is closing, your admin can request deletion of the entire workspace's data the same way.