← Back to Home

Privacy Policy

Last Updated: August 2, 2026

1. Introduction

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").

1.1 Two Products, Two Very Different Data Paths

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.

  • Sales Process AI (the hosted application). We host the application and store your data. Sections 2 through 12 apply in full, including the Google Workspace integration described in Section 3.
  • HubSpot MCP Connector. A tool server your own ChatGPT or Claude calls. We hold no credentials for your CRM, your email, or your calendar, and we cannot reach any of them. Your AI reads your systems using connectors you have authorised directly with HubSpot, Google or Microsoft, sends us the text of the lead it wants analysed, receives the analysis, and writes the result back itself. Section 14 governs this product, and the Google integration in Section 3 does not apply to it.

2. Information We Collect

2.1 Information You Provide Directly

  • Account and profile information: your name, business email address, company name, job title, and password (if applicable).
  • Support communications: information you send us when contacting customer support.

2.2 Information We Collect Automatically

  • Log data (IP address, browser type, device information, timestamps).
  • Usage data (features used, pages viewed, actions taken within the app).

2.3 Information From Google (via Google OAuth)

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.


3. Mailbox Integration (OAuth) — How and Why We Access Your Mail and Calendar

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).

3.1 Offline Access (Refresh Tokens)

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:

  • Keep your Google connection active for the duration of your session, so you are not asked to repeatedly re-authenticate as access tokens expire while you use the app.
  • Check your tracked threads for new replies and reflect them in your pipeline.
  • Run a scheduled daily sync on our servers, described below.

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.

3.2 Gmail Scopes We Request

ScopeWhat It Lets Us DoWhy We Need It
gmail.readonlyRead 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.composeCreate draft emails, and send a draft you have set up to sendTo 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.

3.2a Sign-In Scopes

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:

ScopeWhat It Lets Us DoWhy We Need It
openidAssociate you with your Google identityStandard sign-in — identifies which account authorised the connection
userinfo.emailSee your primary Google account email addressTo identify your account and link the connection to it
userinfo.profileSee your basic profile info (name, profile picture)To display your name and avatar in the app

3.3 Google Calendar Scope We Request

ScopeWhat It Lets Us DoWhy We Need It
Read calendar eventsView events on your calendar, including titles, times and attendeesTo 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.

3.4 Microsoft Scopes We Request

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.

ScopeWhat It Lets Us DoWhy We Need It
offline_accessObtain a refresh tokenSo you are not asked to re-authenticate repeatedly during a session
Mail.ReadRead messages in your mailboxTo find meeting-notetaker summary emails (Otter, Fathom, Fireflies, etc.) and file them against the matching lead automatically
Mail.SendSend mail as youTo send a follow-up you have reviewed and approved
Calendars.ReadRead events on your calendarTo log meetings against the right lead
offline_accessMaintain access to data you have given it access toTo 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.

3.5 Scopes We Do Not Request

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.


4. How We Use Your Mail and Calendar Data

4.1 Finding Meeting Notes in Your Mailbox

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:

  • Messages from known meeting-notetaker services — a fixed list of sender domains (Otter, Fathom, Fireflies, Granola, tl;dv, Read.ai, Circleback, Grain and similar), because those services email a summary after each call.
  • Messages containing a lead's own saved email address — so a follow-up you forwarded to yourself from another mailbox is recognised and filed against that lead.

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.

4.2 Meeting Context

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.

4.3 Drafting and Sending Emails

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:

  • Scheduled send — you review a specific drafted follow-up and choose a time for it to go out. Only that message, at that time, is sent.
  • Auto mode — a setting on the follow-up job list. While it is on, follow-ups that you have already drafted are sent automatically when they fall due, without a further review step. It applies only to follow-ups that already have a drafted subject and body; the Service never composes and sends an email you have not seen. You can turn it off at any time, and it is off until you enable it.

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.


5. Artificial Intelligence Processing

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:

  • Google Gemini API (the default)
  • Anthropic Claude API
  • OpenAI API
  • Azure OpenAI Service, using your own Azure endpoint, in which case the content goes to your Azure tenant rather than to OpenAI directly

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:

  • Categorize a reply by sales stage and generate a short "insight card" for your dashboard.
  • Classify notes you paste or upload, and file each part under the right pipeline stage.
  • Produce stage analyses and the cross-stage lead summary.
  • Draft follow-up emails, which are always shown to you before anything is sent.
  • Decide whether a lead is due a follow-up, and when.

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:

  • Content is transmitted solely to process that specific request. We do not retain it with the provider beyond the request, and we do not send it to any provider other than the one you selected.
  • We do not use your mail or calendar content to train Gemini, Claude, any OpenAI model, or any other general-purpose AI/ML model, and we do not permit our AI subprocessors to do so. Where Google data is involved this is in compliance with the Google API Services User Data Policy, including its Limited Use requirements; the same restriction is applied to every provider listed above.
  • The AI-generated output (the category label and insight card) is stored in our database (see Section 6) so it can be displayed back to you in your dashboard — it is not shared with any other user, company, or the public.
  • This processing is automated. It does not involve a human reviewer reading your client's email as part of the AI pipeline, except in the limited circumstances described in Section 7.3 (security, legal compliance, or with your consent).

6. Data Storage & Security

We use Supabase as our database infrastructure provider to store the following categories of data:

Data TypeWhat's StoredPurpose
OAuth TokensYour Google OAuth access tokens and refresh tokensTo maintain your Google connection and enable background email tracking and automation
Email TicketsSnippets of client email content (sender, subject, relevant body text) tied to a tracked threadTo power your sales pipeline view and history
AI-Generated CRM CardsCategory labels and summarized insights generated by GeminiTo display insights on your dashboard
Profile InformationName, email address, company detailsAccount management and communication

Security Measures

  • OAuth tokens are stored using industry-standard encryption at rest and in transit (TLS/SSL for data in transit, AES-256 or equivalent for data at rest).
  • Access to production databases is restricted to authorized personnel on a need-to-know basis.
  • We conduct regular reviews of our security practices and, where applicable, undergo Google's OAuth verification and security assessment process (e.g., CASA — Cloud Application Security Assessment) required for apps requesting restricted or sensitive scopes.
  • You may request deletion of your stored tokens and associated data at any time (see Section 9).

7. Data Sharing & Third Parties

7.1 We Do Not Sell Your Data

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.

7.2 Service Providers (Subprocessors)

We share data only with infrastructure and service providers strictly as necessary to operate Sales Process AI, including:

  • Supabase — database hosting, authentication, and storage of your account data, leads, notes and generated insights.
  • Vercel — application hosting and the serverless functions that run the app, including the daily scheduled job described in Section 3.1.
  • Cloudflare — hosting for the HubSpot MCP Connector service and its rate limiting.
  • Stripe — payment processing and subscription billing. Stripe receives your email address and payment details; we never see or store your card number.
  • Google — Gmail and Google Calendar APIs where you connect a Google account, and the Gemini API where Gemini is your selected AI provider.
  • Microsoft — the Microsoft Graph API where you connect a Microsoft account, covering sign-in, Outlook mail and Outlook calendar.
  • Anthropic — the Claude API, only where Claude is your selected AI provider.
  • OpenAI — the OpenAI API, only where OpenAI is your selected AI provider.
  • Microsoft Azure OpenAI — only where you have selected Azure and supplied your own endpoint, in which case content is processed in your own Azure tenant.

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.

7.3 Other Disclosures

We may disclose information if required to:

  • Comply with a legal obligation, subpoena, or court order.
  • Protect the rights, property, or safety of Sales Process AI, our users, or the public.
  • Investigate potential violations of our Terms of Service.
  • With your explicit consent for a purpose not otherwise described here.

7.4 Business Transfers

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.


8. Your Rights & Controls

8.1 Revoking Access

You can disconnect Sales Process AI from your Google Account at any time in two ways:

  1. Within the Sales Process AI settings page, or
  2. Directly through Google's Third-Party Apps with Account Access page.

Once revoked, we will no longer be able to access your mail or calendar data, and any stored refresh token will become invalid.

8.2 Data Access, Correction, and Deletion

You may request to:

  • Access a copy of the personal data we hold about you.
  • Correct inaccurate data.
  • Delete your account and associated data (including stored OAuth tokens, email tickets, and AI-generated cards).

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).

8.3 Client Contacts (Third Parties)

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.


9. Data Retention

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).


10. International Data Transfers

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.


11. Children's Privacy

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.


12. Changes to This Privacy Policy

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).


13. Google API Services User Data Policy Compliance

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:

  • We only use Google user data to provide or improve user-facing features that are prominently visible in our app's interface (e.g., email tracking, AI insight cards, meeting context).
  • We do not use Google user data for serving advertisements.
  • We do not allow humans to read Google user data unless: (a) we have your affirmative consent, (b) it is necessary for security purposes, (c) it is necessary to comply with applicable law, or (d) our use is limited to internal operations and the data has been aggregated and anonymized.
  • We do not transfer Google user data to third parties except as necessary to provide or improve user-facing features consistent with your explicit consent, for security purposes, to comply with the law, or as part of a merger/acquisition (with continued protection under this policy).

14. HubSpot MCP Connector

This section governs the HubSpot MCP Connector only. Where it conflicts with anything above, this section controls for that product.

14.1 What the Connector Is

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.

14.2 We Hold No Credentials to Your Systems

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.

14.3 What We Receive, and For How Long

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.

14.4 What We Do Store

  • Your account record: an internal identifier, your Stripe customer identifier, and the email address you paid with.
  • Your subscription status as reported by Stripe, so we can tell whether your access is active.
  • An AI provider key, only if you choose to add one. Stored to run the analysis on your behalf. You can remove it at any time.
  • Access counts used for rate limiting, which record that a request occurred and when. They do not record what was in it.

We do not store the leads you analyse, the analysis produced, or any CRM content.

14.5 AI Processing

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.

14.6 Your Connector URL

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.

14.7 Cancellation

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.


15. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or your data, please contact us at:

Sales Process AI

Email: KL774@cornell.edu

Address: 116 Oak Ave, Ithaca, NY 14850

This Privacy Policy should be read together with our Terms of Service.