Last Updated: August 2, 2026
Welcome to Sales Process AI ("we," "us," "our," or the "Company"), a B2B sales automation and customer relationship management (CRM) platform designed to help sales teams manage outreach, track email conversations, and organize client information.
This Privacy Policy explains what information we collect, how we use it, who we share it with, and the choices you have, particularly regarding the mail and calendar data we access through Google or Microsoft, which is central to how the hosted application works.
By connecting a mailbox to Sales Process AI or otherwise using our services, you agree to the practices described in this Privacy Policy. If you do not agree, please do not use the application or connect your Google Account.
This policy is intended for business users ("you" or "User") who use Sales Process AI on behalf of their organization, as well as any individuals whose information may pass through the platform (e.g., prospects and clients who email our Users, referred to as "Client Contacts" or "Third-Party Data Subjects").
We offer two products, and what we hold differs sharply between them. Which sections of this policy apply to you depends on which you use.
When you connect a Google or Microsoft account, we collect mail and calendar data as described in detail in Section 3 below. This is the most sensitive category of data we handle, and we take extra care to explain it clearly.
Sales Process AI connects to your mailbox and calendar to automate sales workflows. You connect either Google or Microsoft, and we ask for permission ("scopes") through that provider's own consent screen. You will always see exactly what we are requesting on that provider's own consent screen, Google's or Microsoft's, and you can decline or revoke access at any time (see Section 8).
We request offline access, which means Google issues us a refresh token in addition to a short-lived access token. This allows Sales Process AI to:
This includes processing that happens while you are logged out. Once a day, at 13:00 UTC, our servers run a scheduled job against the accounts you have connected. That job reads replies on threads you are tracking, reads calendar events for meetings with your leads, pulls contacts from HubSpot if you have connected it, and schedules follow-up reminders for qualified leads that do not already have one pending. It runs whether or not the app is open and whether or not you are signed in. That is what makes a reply or a booked meeting already be waiting for you when you next open the app, rather than only appearing once you log in and the page refreshes.
Revoking access, as described in Section 8, stops this job for your account immediately, because the refresh token it depends on is what you are revoking.
| Scope | What It Lets Us Do | Why We Need It |
|---|---|---|
| gmail.readonly | Read the content of messages returned by two specific searches (described below) | To find meeting-notetaker summary emails (Otter, Fathom, Fireflies and similar) and follow-up emails you have forwarded that contain a lead's saved address, so the notes are filed against the right lead automatically. We do not browse or list your general inbox — every fetch is a targeted search. |
| gmail.compose | Create draft emails, and send a draft you have set up to send | To let you prepare proposal, onboarding and follow-up emails from AI-generated content. By default every one is saved to your Gmail Drafts folder for you to send yourself; it is also used to deliver a follow-up you have scheduled, or that auto mode sends when due (see Section 4.3 — both are off unless you turn them on). This scope cannot read your existing mail. |
We do not use these permissions to delete your emails, apply labels, or mark messages as read. Email we prepare is created as a draft in your Gmail account for you to review and send yourself, unless you have explicitly scheduled that follow-up to send or enabled auto mode (Section 4.3). We do not request gmail.modify or full-mailbox access.
Alongside the scopes above, connecting Google grants three standard, non-sensitive sign-in permissions, which is why Google's consent screen lists six items in total rather than three:
| Scope | What It Lets Us Do | Why We Need It |
|---|---|---|
| openid | Associate you with your Google identity | Standard sign-in — identifies which account authorised the connection |
| userinfo.email | See your primary Google account email address | To identify your account and link the connection to it |
| userinfo.profile | See your basic profile info (name, profile picture) | To display your name and avatar in the app |
| Scope | What It Lets Us Do | Why We Need It |
|---|---|---|
| Read calendar events | View events on your calendar, including titles, times and attendees | To log meetings against the right lead and show when you last spoke to them |
This scope is read-only. We cannot create, edit, move or delete anything on your calendar.
If you connect a Microsoft account instead of Google, we request the following through Microsoft's own consent screen. These are the exact scopes; there are no others.
| Scope | What It Lets Us Do | Why We Need It |
|---|---|---|
| offline_access | Obtain a refresh token | So you are not asked to re-authenticate repeatedly during a session |
| Mail.Read | Read messages in your mailbox | To find meeting-notetaker summary emails (Otter, Fathom, Fireflies, etc.) and file them against the matching lead automatically |
| Mail.Send | Send mail as you | To send a follow-up you have reviewed and approved |
| Calendars.Read | Read events on your calendar | To log meetings against the right lead |
| offline_access | Maintain access to data you have given it access to | To keep your connection working in the background without asking you to sign in again every hour |
Microsoft's handling of your data under these permissions is governed by Microsoft's Privacy Statement. You can review and revoke application access at any time in your Microsoft account permissions.
We request no Google Drive access of any kind, and the HubSpot MCP Connector requests no scopes at all, from any provider, because it never connects to your systems. The permissions involved in using the Connector are the ones you grant directly to HubSpot's own connector and to your AI's mail connector, under those companies' terms rather than ours. Earlier versions of the Service stored documents in your Drive; that was removed, and the Service now stores its documents in our own database as described in Section 6. If you previously granted Drive access, you can revoke it at Google's permissions page (see Section 8.1) with no effect on the Service.
When a sync runs — either on its daily schedule or when you press "Sync now" — our backend runs two specific, targeted searches against your connected mailbox. It does not list, browse or scan your inbox generally:
Both searches are limited to messages received since the previous sync. From a matching message we read the sender, subject, date and body, so that the meeting note can be filed against the correct lead and (as described in Section 5) turned into AI-generated insights.
We read calendar events to work out when you last met a lead and to attach meeting context to the right record. We do not write to your calendar.
When you use a feature that prepares an email (such as sending proposal or update cards to a lead), Sales Process AI creates a draft email in your Gmail account, pre-filled with AI-generated content for you to review, edit, and send. By default, that is where it stops: the draft sits in your Gmail Drafts folder and you take the final action of sending it yourself.
Two optional features, both off unless you turn them on, allow the Service to send a prepared email for you:
In both cases the Service sends only to the email address saved on that lead, and only the content held in that follow-up's draft. It never sends to anyone else, and it never sends anything other than a follow-up you set up.
Sales Process AI sends content to a third-party AI provider to produce the analysis you see in the app. You choose which provider in your profile settings, and your choice determines which company receives that content:
What we send: only the material relevant to the request you triggered. Depending on the feature, that is the subject and body of a tracked email, the text of meeting or call notes you have added, the content held in a lead's context log, or the calendar details of a meeting with that lead. We send this to your selected provider to:
The daily scheduled job described in Section 3.1 can trigger this processing while you are logged out.
The MCP Connector product is different. If you use the HubSpot MCP Connector, MeOH does not connect to your CRM, your mailbox, or your calendar at all. Your own AI assistant reads those and passes the text to us in a single request; we return the analysis and retain nothing. Where you have not supplied a provider key, we do not call any AI provider ourselves — we return the analysis specification and your own assistant produces the result, so the content never reaches us in the first place.
How this data is used — and how it is not used:
We use Supabase as our database infrastructure provider to store the following categories of data:
| Data Type | What's Stored | Purpose |
|---|---|---|
| OAuth Tokens | Your Google OAuth access tokens and refresh tokens | To maintain your Google connection and enable background email tracking and automation |
| Email Tickets | Snippets of client email content (sender, subject, relevant body text) tied to a tracked thread | To power your sales pipeline view and history |
| AI-Generated CRM Cards | Category labels and summarized insights generated by Gemini | To display insights on your dashboard |
| Profile Information | Name, email address, company details | Account management and communication |
We do not sell, rent, or trade your personal data, your Google data, or your Client Contacts' email data to third parties for marketing or advertising purposes — ever.
We share data only with infrastructure and service providers strictly as necessary to operate Sales Process AI, including:
The four AI providers are listed as alternatives, not as a set that all receive your data. Only the one you have selected in your profile settings ever does. If you use the HubSpot MCP Connector without supplying a provider key, none of them receives anything from us, for the reason given in Section 5.
These providers are contractually bound to use data only to provide services to us and are prohibited from using it for their own independent purposes.
We may disclose information if required to:
If Sales Process AI is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change and any choices you may have.
You can disconnect Sales Process AI from your Google Account at any time in two ways:
Once revoked, we will no longer be able to access your mail or calendar data, and any stored refresh token will become invalid.
You may request to:
To make a request, contact us using the details in Section 15. We will respond within a reasonable timeframe and in accordance with applicable law (e.g., GDPR, CCPA).
If you are a Client Contact who has emailed a Sales Process AI user and wish to inquire about, or request removal of, data related to your correspondence, please contact us directly at the email in Section 12; we will work with the relevant User to address your request.
We retain your data for as long as your account is active or as needed to provide the service. If you delete your account or revoke Google access, we will delete or anonymize your stored OAuth tokens, email tickets, and AI-generated content within 30 days, except where retention is required for legal, security, or legitimate business purposes (e.g., resolving disputes, enforcing agreements).
If you access Sales Process AI from outside the country where our servers are located, your information may be transferred to, stored, and processed in a different country. We take steps to ensure appropriate safeguards are in place in accordance with applicable data protection laws.
Sales Process AI is a business tool intended for use by professionals and is not directed at, nor knowingly used by, individuals under the age of 18. We do not knowingly collect personal information from children.
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or for other operational reasons. We will update the "Last Updated" date at the top of this policy and, for material changes, provide additional notice (such as an email or in-app notification).
Sales Process AI's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In summary, this means:
This section governs the HubSpot MCP Connector only. Where it conflicts with anything above, this section controls for that product.
The Connector is a tool server. Your own ChatGPT or Claude account calls it. You add a private URL to your AI's connector settings, and from then on your AI can ask it to analyse a lead, judge whether a follow-up is due, recommend a stage change, screen leads against a description, or draft a follow-up email.
We do not hold access tokens, API keys, passwords or any other credential for your CRM, your email or your calendar, and we have no ability to reach any of them. Your AI reads and writes those systems using connectors you have authorised directly with HubSpot, Google or Microsoft, under those companies' own terms.
This means we cannot access your CRM records, mailbox or calendar on our own, at any time, for any reason, including at your request. If you want us to see a record, your AI has to send it to us.
When your AI calls the Connector it sends the content it wants analysed: typically the text of notes, meeting summaries, calls and emails logged against one lead, along with the lead's name and pipeline stage. That content may include personal data about your Client Contacts.
We process that content in memory to produce the analysis and return it. We do not write it to a database, a log, or any other durable store. Once the response is returned, it is gone from our systems.
The analysis we return is sent to your AI, which writes it into your CRM. We keep no copy.
We do not store the leads you analyse, the analysis produced, or any CRM content.
If you add your own provider key, the content is sent to that provider under your own account and their terms apply to you directly. If you do not add one, the Connector returns the analysis specification to your AI and your own ChatGPT or Claude performs the analysis, in which case the content never leaves your AI at all.
Your Connector URL contains a private identifier and functions as a credential. Anyone holding it can use your subscription. Treat it as you would a password, and contact us if you believe it has been exposed.
When your subscription ends, the Connector stops responding on the next request. Everything it previously produced remains in your own CRM, under your control, unaffected. To delete your account record, contact us using the details below.
If you have any questions, concerns, or requests regarding this Privacy Policy or your data, please contact us at:
This Privacy Policy should be read together with our Terms of Service.