CommitPath AI — Privacy Policy
Last updated: October 20, 2026 · Effective date: October 20, 2026
1. Who This Policy Covers
This policy describes how Fortis Logic LLC, doing business as CommitPath AI ("CommitPath," "we," "us"), collects, uses, and shares information when you use our sales qualification and pipeline platform (the "Service"), including our web application, the Salesforce Canvas–embedded version, and our API.
It also covers our public website at www.commitpath.ai, which anyone may read without an account. Most of this policy is about information we hold because you or your organization are a customer; section 2a is the part that applies to you if you have simply visited the website, and it is deliberately short, because we collect very little there.
If your organization has a signed enterprise agreement or Data Processing Agreement with us, and it conflicts with this policy, that agreement controls.
2. Information We Collect
Information You Give Us Directly
- Account information: name, work email, password (stored only as a bcrypt hash — we never store or can retrieve your actual password), organization name, role (rep, manager, or executive).
- Deal and pipeline data: everything you enter about a deal — company names, contact names and emails, qualification answers across whichever frameworks you use, notes, pain points, deal values, close dates, and free-text you provide to CommitPath AI features.
- Billing information: handled directly by Stripe, our payment processor — we never see or store your card number. We retain your billing history, subscription status, and monthly CommitPath AI usage totals.
Information We Collect Automatically
- Usage data: pages viewed, features used, and general product analytics, collected via PostHog.
- Error and performance data: collected via Sentry when something goes wrong, to help us fix it. This can include request details but is configured to avoid capturing full request bodies where they'd contain deal content or credentials.
- Recognized browsers: so we can tell you when your account is signed into from somewhere new, we keep a one-way hash of a random identifier stored in a cookie on each browser you sign in from, a coarse description of it ("Chrome on macOS"), and when it was first and last used. We do not store your IP address, your location, or the full browser identification string, and we cannot work out where you were from any of it. An entry is deleted the next time you sign in if it has not been used for 90 days, and every entry is deleted with your account. The first browser you use is recorded without sending you anything; after that, a browser we have not seen before triggers a notice to you — the only person who can tell us it was not you.
- Last sign-in: the date and time each user most recently signed in, stored once per account and overwritten rather than kept as a history. It exists so an organization's executives can see which accounts are no longer being used, and so we can carry out the access reviews our security commitments require. It is recorded at most once an hour, so it shows that an account is in use and not how long anyone worked. We do not use it to monitor individual productivity, and it is not shown to anyone outside your own organization.
- Audit log: every privileged or destructive action taken in your organization's account — role changes, data exports, integration connections and disconnections, deal reassignments, account deletion — is logged with who did it and when, visible to your organization's executives. This exists for your organization's own security and accountability, not for our use.
Information We Collect on Our Website
Nothing, unless you agree to it first. Our website sets no advertising or analytics cookies and loads no third-party script until you have been asked and have said yes. If you say no, or simply close the notice without choosing, nothing is loaded and nothing is sent to anyone. Saying no costs you nothing: every page works exactly the same way.
If you do agree, we use:
- PostHog — to count which pages people read and which of them lead to someone signing up. We ask it not to record your session, not to capture the text you click on, and not to build a profile of you as an individual visitor.
- LinkedIn — to show CommitPath advertising on LinkedIn to people who have visited this site. This sets LinkedIn's own cookies and tells LinkedIn your IP address and that you visited. We do not learn who you are from it, and we do not receive your email address through it.
You can change your mind at any time by clearing this site's cookies and site data in your browser, which returns you to being asked again.
If you ask us to tell you when CommitPath AI opens, we store the email address you give us, the fact that you asked, and when. Nothing else — not your name, not your IP address, not which pages you read. We use it for exactly that one message and nothing else, every message carries a one-click unsubscribe, and unsubscribing is permanent: an address that has unsubscribed is not re-added if the form is filled in again. You can ask us to delete it at any time at support@commitpath.ai.
We do not identify individual visitors. We do not use any service that resolves a visitor's IP address to a named person or company, and we do not add anyone to a mailing list because they visited a page.
Information From Connected Third-Party Accounts
If you choose to connect a third-party account, we access only what that integration needs to function, and never more:
| Provider | What we access | What it's used for |
|---|---|---|
| Salesforce | Opportunity records you sync, and — if you enable it — real-time change events for Opportunities you've already synced from CommitPath | Two-way pipeline sync; embedding CommitPath inside your Salesforce org (Canvas) |
| HubSpot | Deal records you sync, and change notifications for those deals | Two-way pipeline sync |
| Slack | Ability to post messages to channels you configure | Deal notifications and weekly digests you opt into |
| Microsoft (Outlook + Teams) | Email metadata (subject, sender, recipients, timestamp — never message body) for matching against your known deal contacts; ability to draft emails and post to Teams channels you configure; calendar event metadata (subject, attendees, time — never event descriptions or attachments) | Automated activity logging against your deals; follow-up drafting; Teams notifications; suggesting possible new deals from upcoming meetings with people outside your organization (see "Suggested deals from your calendar" below) |
| Google (Calendar and Meet) | Calendar event details (title, time, attendee email addresses and display names, and the Google Meet meeting code — never event descriptions or attachments); for Google Meet calls hosted by the connected account where transcription was turned on, the transcript text and participants' display names; the email address of the connected Google account | Creating the follow-up meetings you ask for (with a Meet link, inviting only the attendees you choose); automated activity logging against your deals; suggesting possible new deals from upcoming meetings with people outside your organization (see "Suggested deals from your calendar" below); producing qualification answers from Meet transcripts, applied to the deal automatically and locked (see "Google Meet transcripts" below) |
| Zoom | Ability to draft follow-up communications referencing your meetings | Follow-up drafting |
| DocuSign | The document you send for signature, and the signer's name and email address you enter. Completed envelopes are returned to us with the signed copy. | Sending agreements and contracts for electronic signature, and recording when one is signed |
| Fireflies.ai | Full text transcripts of calls you have recorded with Fireflies, including the meeting title, date, and attendee email addresses, delivered to us by Fireflies when a transcript is ready | Producing qualification answers, each shown with the sentence from the call it was drawn from. Answers from a recorded call are applied to the deal automatically and locked, so they cannot be quietly edited — a rep who disagrees records a challenge against the answer instead. A per-deal call history you can read back; matching each transcript to the right deal by attendee email |
On Google specifically: CommitPath's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. CommitPath does not access Gmail: "Draft in Gmail" opens Gmail's own compose window in your browser, filled in by CommitPath, and nothing is sent to or read from your Gmail account by us. Data from Google Calendar and Google Meet is used only for these user-facing features, each visible in the product: (1) creating follow-up meetings you request; (2) detecting and logging real interactions against your existing deals, by matching event attendees against contacts you've already added to a deal; (3) suggesting possible new deals from upcoming calendar events that include attendees outside your organization's email domain (described below); and (4) turning transcripts of Meet calls into qualification answers, applied to the matching deal automatically and locked, and a call history on that deal (described below). We do not use this data for advertising, we do not sell it, we do not use it to train or improve generalized AI or machine-learning models, and people at CommitPath do not read it except with your permission, where needed for security or to comply with the law. We keep only the data described above.
Suggested deals from your calendar: If you connect Google or Microsoft, CommitPath periodically looks at your upcoming calendar events for attendees whose email domain is different from your organization's, who are not already a contact on one of your deals, and who are not an obvious non-person (a meeting-room resource or an automated sender). For each such person we store their email address, their display name if the calendar provides one, a company guess derived from their email domain, and the title and time of the event, and we show this to you as a possible new deal. Nothing becomes a real deal unless you confirm it; you can dismiss a suggestion, and dismissing it does not block that person from being suggested again for a genuinely different future event. This is the only purpose for which we read upcoming (as opposed to past) calendar events.
On Fireflies.ai specifically: Fireflies is a call-recording and transcription service you operate under your own account and your own recording-consent obligations; CommitPath does not record calls and cannot start or stop a recording. If you connect Fireflies, it sends us the full text of a transcript once Fireflies has produced it. That transcript contains the words of everyone on the call, including people who are not CommitPath users. We use it to (a) produce qualification answers, each shown alongside the quoted passage it was drawn from. Answers drawn from a recorded call are applied to the deal automatically and then locked. Nobody at your company can silently change what a call said — that is the point of recording it. A rep who believes an answer is wrong raises a challenge against it, with a reason, which is kept on the record and can be overturned by someone with the authority to do so. Answers you type or paste in yourself are different: those are proposed for your review and stay editable, because you wrote them. (b) keep a readable call history on the matching deal; and (c) match the transcript to a deal by comparing attendee email addresses against your deal contacts. Transcripts are stored in full so the call history remains readable. You are responsible for obtaining any consent to record and transcribe a call that applies where you and the other participants are located, before the call is recorded; CommitPath's role begins only after Fireflies has already produced a transcript.
Google Meet transcripts: If you connect Google Calendar & Meet, CommitPath checks the connected account's calendar for recent Google Meet calls that account hosted and, when a transcript exists for the call (transcription is a Google Workspace feature someone on the call must turn on), stores the transcript text with the meeting title, date, and the email addresses of the other invited attendees. It is then handled exactly like a Fireflies transcript: it is matched to a deal by attendee email, and used to produce qualification answers that are applied automatically and locked, each shown with the sentence it came from, and challengeable rather than silently editable. As with Fireflies, you are responsible for obtaining any consent to record and transcribe a call that applies where you and the other participants are located; CommitPath does not start or stop transcription.
We never see your password for any connected account. Every connection except Fireflies uses OAuth, where you authorize access directly with the provider and we receive only a token. Fireflies does not offer OAuth; instead you copy an API key from your Fireflies settings and paste it into CommitPath. In every case the token or key is stored encrypted (AES-256-GCM) and never in plain text.
3. How We Use Your Information
- To provide the Service: storing your deals, computing qualification scores, generating the CommitPath AI features you use, and syncing with the CRMs and tools you connect.
- To generate your organization's daily briefing, weekly digest, and forecast — computed from your own pipeline data, visible only to your organization.
- To process payment and manage your subscription.
- To communicate with you about your account, security, and material changes to the Service.
- To monitor for and prevent abuse, fraud, and security incidents.
- To improve the Service, using aggregated or anonymized usage patterns — never your deal content, and never data from Google Calendar, Google Meet, or other connected accounts beyond the specific feature it was collected for.
What we do not do: we do not sell your data. We do not use your deal content, notes, or connected-account data to train AI models — CommitPath AI features call Anthropic's API directly for each request; your data is not used to train Anthropic's models under our agreement with them. We do not share your data with third parties for their own marketing purposes.
4. Who We Share Information With
- Sub-processors who help us run the Service: Anthropic (CommitPath AI features), Stripe (billing), Resend (transactional email), Sentry (error monitoring), PostHog (product analytics, and website analytics if you agreed to it), LinkedIn (website advertising, only if you agreed to it), WorkOS (enterprise SSO, if your organization uses it), and our hosting and storage providers (Render, which runs our application servers and database; Vercel, which serves the web app; and Backblaze, which holds our off-site backups as an encrypted copy it cannot read). Each processes only what's needed for its function and is contractually restricted from using your data for its own purposes.
- The third-party tools you connect (Section 2) — only the data your own sync and automation settings actually send.
- Other members of your organization, according to your role: reps see their own deals, managers see their team's, executives see the whole organization — enforced the same way in our infrastructure as it's shown in the product.
- Legal and safety: if required by law, subpoena, or to protect the rights, property, or safety of CommitPath, our users, or the public.
- Business transfers: if CommitPath is acquired or merged, your information may transfer as part of that transaction, subject to this policy or a successor policy you'll be notified of.
We do not sell your personal information, as that term is defined under CCPA or any other law.
5. Data Retention
We retain your data for as long as your account is active. If your subscription ends but you don't delete your account, we keep your data for up to 12 months so you can pick up where you left off, and then permanently delete it. If you or your organization deletes your account, deal data, users, and connected integrations are permanently removed — there is no soft-delete or recovery grace period once you confirm deletion (see Section 7). Audit log entries describing an account deletion itself are retained independent of the deleted account, since the record of an action has to be able to outlive the thing it describes.
Backups are a separate matter, and we would rather say so than let you assume otherwise. Deletion removes your data from the live service immediately, as described above. It does not reach the encrypted backup copies we keep so that a failure on our side cannot lose your work. Those copies are retained for up to 3 days (point-in-time recovery) and 7 days (logical backups) with our hosting provider, and for up to 30 days in off-site storage that is deliberately immutable — nobody, including us, can alter or delete it within that window, which is the property that makes it useful against ransomware and against a stolen credential. So a deleted account's data can persist in backups for up to 30 days after deletion, and then rotates out. A backup is never used to restore an individual account; it is restored whole, in a disaster, and there is no mechanism to extract one organization from one.
If you disconnect an individual integration, we delete the stored access credentials for that connection immediately; historical sync records already created remain as part of your deal history unless you delete the underlying deals.
6. Security
We encrypt OAuth tokens at rest (AES-256-GCM) and passwords as salted bcrypt hashes — never in plain text, in either case. Sessions use signed, httpOnly cookies. We apply role-based access control so a user only ever sees data their role permits, enforced server-side, not just hidden in the interface. We maintain an audit log of privileged actions.
We hold no third-party security assessment, and we would rather you read that here than discover it in a questionnaire. CommitPath has not been audited: there is no SOC 2 report and no penetration test has been performed. Our Security page lists what we do and do not have, in full, and we will say so there when that changes.
No system is perfectly secure, and we cannot guarantee absolute security of your information.
7. Your Rights and Choices
- Access and export: an executive on your organization's account can export a complete copy of your organization's data (deals, stakeholders, interactions, users, and more) at any time from Account Settings, as a downloadable file. This does not include other organizations' data, raw payment card details, or stored authentication credentials.
- Deletion: an executive can permanently delete your organization's entire account from Account Settings. This is irreversible.
- Correction: you can edit your own deal data, profile, and settings directly in the product at any time.
- Integration disconnection: disconnect any connected provider at any time from your integrations settings; this revokes our access to that provider going forward.
If you are in the EEA, UK, or another jurisdiction with similar data protection law, including the General Data Protection Regulation (GDPR), you may also have rights to restrict or object to certain processing, and to lodge a complaint with your local data protection authority. Contact us using the details in Section 11 to exercise these rights.
If you are a California resident, you have rights under the CCPA/CPRA to know what personal information we collect, to request deletion, and to not be discriminated against for exercising these rights. We do not sell personal information, so there is no "opt out of sale" to exercise.
8. International Data Transfers
CommitPath is hosted in the United States: our application servers and database run on Render in Oregon, and the web app is served by Vercel. If you access the Service from outside the United States, your information will be transferred to and processed in the United States.
9. Children's Privacy
CommitPath is a business-to-business product intended for use by working professionals and is not directed at, or intended for use by, anyone under 18. We do not knowingly collect information from children.
10. Changes to This Policy
If we make a material change to how we handle your data — including any change to what we access or how we use data from Google or Microsoft Workspace scopes — we will update this page and, for material changes, notify you directly (email or an in-product notice) before the change takes effect. Continuing to use the Service after a change takes effect constitutes acceptance of the updated policy for non-material changes; material changes affecting restricted-scope data require your affirmative consent before we begin the new use, consistent with Google's API Services User Data Policy.
11. Contact Us
Fortis Logic LLC, doing business as CommitPath AI
350 Sansome St, Suite 820 PMB 1057
San Francisco, CA 94104, United States
support@commitpath.ai
If you have questions about this policy or want to exercise any of the rights described in Section 7, contact us at the email above.