Wingman

Privacy Policy

Last updated: November 16, 2026

This policy explains how Fundmore LLC, doing business as MCA Pilot and Wingman ("Wingman", "we", "us"), collects, uses, shares and protects information when brokerages and their team members use Wingman at wingman.fund, and when merchants interact with a brokerage through Wingman. Wingman is a product of the same company that operates MCA Pilot.

Summary

  • Wingman is a business tool. Brokerages use it to text business owners from their own lead lists, help those owners complete a funding application, and hand interested owners to the brokerage's team.
  • For the leads, conversations and applications a brokerage handles in Wingman, the brokerage decides what is collected and why. We process that information on the brokerage's behalf.
  • The most sensitive application fields (Social Security number, date of birth, driver's license number and EIN) are encrypted by us before they are stored.
  • If you sign in with Google, we use only your verified email address to find your existing Wingman account. We do not use Google data for advertising, we do not sell it, and we do not use it to train AI models.
  • We do not sell personal information.
  • Questions or requests: support@mcapilot.com.

1. Who we are and who this policy covers

Wingman is operated by Fundmore LLC, 1958 East 13th Street, Brooklyn, NY 11229, United States. This policy covers:

  • Brokerage users: brokers, funders and their team members (owners and reps) who have a Wingman account.
  • Merchants: owners and staff of the businesses a brokerage contacts through Wingman, for example by text message or through an application link.
  • Visitors to wingman.fund.

MCA Pilot, our deal-management product, has its own privacy policy at mcapilot.com/privacy-policy.

2. Our role for the information brokers bring

A brokerage brings its own lead lists to Wingman and uses Wingman to talk to those leads and collect their applications. For that information, the brokerage decides what to collect and why, and is the party responsible for it (the "controller", or under California law the "business"). We act as its service provider (processor): we handle that information on the brokerage's behalf and to provide Wingman to it.

If you are a merchant and want to access, correct or delete information a brokerage holds about you, please contact that brokerage. You may also contact us and we will pass your request to the brokerage and help it respond.

For a brokerage user's own account, sign-in and billing information, we are the party responsible, and you can contact us directly (Section 15).

3. What information we collect

Brokerage accounts

  • Your name, email address, role (owner or rep) and the brokerage you belong to.
  • Sign-in information: a password stored only as a one-way hash (never in readable form), single-use sign-in and password-reset codes stored only in hashed form, and the time and method of your last sign-in.
  • If you sign in with Google, the information described in Section 4.
  • Brokerage settings, and API keys you provide to connect your own services (such as your texting account). These keys are stored encrypted.
  • Billing information. Card details are collected and held by Stripe; we keep Stripe identifiers, billing status and invoice records.
  • If you turn on text alerts: the mobile number you enter, the wording of the consent you gave, the time, IP address, and browser details of your sign-up, single-use confirmation codes stored only in hashed form, and when you confirmed or turned the alerts off.

Lead information a brokerage provides

Brokerages import lead lists, usually spreadsheets they have purchased or built. These may include business names, owner names, phone numbers, email addresses, business addresses, industry and other details the list contains. Before texting, a brokerage may choose to check phone numbers against a litigation-risk list using its own account with that list provider.

Text conversations and lead notes

Wingman sends and receives text messages with merchants through the texting account the brokerage connects. We store the messages, delivery status, and opt-out requests. To keep replies relevant, Wingman keeps notes about each lead drawn from the conversation and the application (for example, the amount a merchant said they need), including AI-generated summaries. When a merchant asks for a phone call, we record the request and pass it to the brokerage's team.

Application information

When a merchant opens an application link and fills in the form, we collect what they enter, which may include:

  • Business details: legal name, "doing business as" name, entity type, address, phone, email, industry, start date, state of incorporation, EIN, requested amount, purpose of funds, monthly revenue range, existing advances and credit score range.
  • Owner details: name, title, ownership percentage, email addresses, phone numbers, home address, Social Security number, date of birth and driver's license number.
  • The merchant's electronic signature on the credit authorization, and the signed document.
  • Documents the merchant uploads, such as business bank statements, and the figures we read from them (for example deposits, balances, statement periods and the last four digits of the account number).

Support messages

When you contact us for support, we keep what you send us, our replies, and any attached files.

Technical information

When you use Wingman we receive standard technical information such as IP address and browser or device type. We use it to keep the service secure (for example, to limit repeated sign-in attempts) and to tell real application opens apart from automatic link previews.

Wingman uses only cookies that are needed for it to work: a session cookie that keeps you signed in, a short-lived cookie that protects the Google sign-in step, and a cookie that remembers which sign-in method you used last. We do not use advertising or analytics cookies.

4. Sign in with Google

Brokerage users can sign in to Wingman with their Google account. This is the only way Wingman uses Google user data.

  • What we request. Google's basic sign-in permissions: openid, email and profile. We do not request access to Gmail, Google Drive, Google Calendar, your contacts or any other Google service.
  • What we use. Your email address, and Google's confirmation that it is verified. We use it only to find your existing Wingman account and sign you in. Signing in with Google does not create an account: if no active Wingman account matches the email, sign-in is refused.
  • What we keep. We record that your last sign-in used Google, and when. We do not store your Google account identifier, profile name or picture, or any Google access token.
  • What we never do. We do not sell Google user data or transfer it to advertising platforms, data brokers or information resellers. We do not use it for advertising. We do not use it to develop, improve or train generalized artificial intelligence or machine learning models, and we do not send it to the AI providers listed in Section 7. We do not use it to determine credit-worthiness or for lending decisions. People at our company do not read it unless you ask us to, it is needed for security, or the law requires it.
  • Your control. You can stop using Google sign-in at any time and sign in by email instead. You can remove Wingman's access from your Google Account at myaccount.google.com/permissions.

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

5. How we use information

  • To provide Wingman to brokerages: importing leads, drafting and sending text messages, reading replies, honoring opt-outs, collecting applications and documents, getting the credit authorization signed, and passing interested merchants, call requests and completed applications to the brokerage's team.
  • To deliver completed applications into the brokerage's MCA Pilot workspace when it uses MCA Pilot, or into another system it connects.
  • To run accounts and billing: sign-in, account emails, invoices and payment.
  • To support and improve Wingman for the brokerage, including reviewing the quality of messages Wingman drafts.
  • For security and to prevent abuse, and to comply with law.

We do not use merchant information for our own marketing, and we do not use it to make credit or lending decisions. Funding decisions are made by brokerages and funders, not by Wingman.

6. How we use AI

Wingman uses AI models from the providers listed in Section 7 to draft text replies to merchants, review drafts before they are sent, understand what a merchant's reply means, keep notes about each lead, map the columns of an imported spreadsheet, and read the figures on uploaded bank statements. Each provider receives only the content needed for that task and returns a result to us.

Brokerages control how much Wingman does on its own. Depending on a brokerage's settings, drafts may be reviewed by a person before sending, or sent automatically. Brokerages can turn AI replies off.

7. Our service providers

We rely on service providers (sub-processors) to run Wingman. The table below describes them by category and names the AI providers that draft replies to merchants, read bank statements, and index lead notes. Each receives only the information it needs to perform its service for us.

  • Application hosting and infrastructure

    What it does for us
    Running Wingman, routing requests to our AI providers, and security checks on public forms
    Information it may process
    Web requests and responses, including IP address and browser details, operational logs, and the content of AI requests and responses as they pass through.
  • Database hosting

    What it does for us
    Primary application database
    Information it may process
    Account, lead, conversation and application data. The most sensitive fields are encrypted by us before they reach the database.
  • File storage

    What it does for us
    Document storage
    Information it may process
    Documents merchants upload, such as bank statements, kept in private storage.
  • Background job processing

    What it does for us
    Scheduled and background tasks
    Information it may process
    Event and job data needed to run those tasks, which may include personal information.
  • Text messaging

    What it does for us
    Text messaging, through the account the brokerage connects, and the text alerts we send to Wingman users
    Information it may process
    Phone numbers and the content of text messages sent and received.
  • Email delivery

    What it does for us
    Email delivery
    Information it may process
    Recipient email addresses and email content, such as sign-in emails, broker notifications and application links sent to merchants.
  • Electronic signature

    What it does for us
    Electronic signature of the credit authorization
    Information it may process
    The merchant's application details and signature on the authorization document.
  • Address lookup

    What it does for us
    Suggesting addresses on the application form
    Information it may process
    The address text a merchant types.
  • Billing and payments

    What it does for us
    Billing and payments for brokerages
    Information it may process
    Billing contact and payment details. Full card details are held by our payment provider, not by us.
  • Customer support and help-center tools

    What it does for us
    Receiving and answering support requests, including with AI features, and keeping our help articles current
    Information it may process
    What you send us, what we send you, and attached files. This can include sensitive merchant and owner details when a message or file contains them.
  • Internal team tools

    What it does for us
    Email, notes, search, and AI assistants our team uses to support you and run Wingman
    Information it may process
    Support and operations notes, which can include merchant and owner details.
  • Reply classification

    What it does for us
    AI processing (sorting merchant replies by intent)
    Information it may process
    The text of a merchant's reply and the recent conversation, used to sort the reply by intent.
  • Anthropic, PBC

    What it does for us
    AI processing
    Information it may process
    Conversation text and lead details needed to draft and review replies, summarize conversations, and map spreadsheet columns and application fields. For document reading, the bank statement being read.
  • OpenAI

    What it does for us
    AI processing (text embeddings)
    Information it may process
    Short notes about a lead and its conversation, turned into search vectors.
  • Google LLC

    What it does for us
    Sign in with Google and AI document reading (Gemini API)
    Information it may process
    For sign-in, your Google identity as described in Section 4. For Gemini, the bank statement being read.

Integrations a brokerage turns on. When a brokerage uses MCA Pilot, completed applications and documents are delivered to its MCA Pilot workspace, which MCA Pilot's privacy policy covers. When a brokerage connects another system, such as its own CRM, they are delivered there. When a brokerage turns on litigation-risk screening, phone numbers are checked with a litigation-screening provider using the brokerage's own account.

8. When we share information

We do not sell personal information. We share information only:

  • With the brokerage a lead or application belongs to, and with that brokerage's authorized team members according to their role. Reps see the leads assigned to them.
  • With our service providers in Section 7, to run Wingman.
  • With integrations the brokerage turns on, as described in Section 7.
  • For legal and safety reasons, when the law requires it or to protect the rights, property or safety of our users or others.
  • In a business transfer, such as a merger or sale of assets. Any transfer of Google user data will follow the Limited Use requirements, including asking for your consent where required.

Mobile information. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not shared with any third parties.

Text alerts. Wingman users who turn on text alerts get call alerts at the number they confirmed. Message frequency varies. Message and data rates may apply. Reply STOP to cancel or HELP for help. The full terms are in the text alert terms.

9. How we protect information

  • Social Security numbers, dates of birth, driver's license numbers, EINs and brokerage API keys are encrypted by us with AES-256-GCM before they are stored, in addition to the encryption our database provider applies.
  • Information moves to and from Wingman over encrypted connections (TLS).
  • Each brokerage's data is kept separate from every other brokerage's data, enforced in the database.
  • Uploaded documents are kept in private storage, never publicly accessible.
  • We work to keep personal and financial details out of our logs.

No system is perfectly secure, and we cannot guarantee that information will never be accessed, disclosed, changed or destroyed without permission.

10. How long we keep information

We keep information for as long as the brokerage uses Wingman and as needed to provide it, and afterward as needed for legal, compliance and dispute purposes. That includes the records of messages, deliveries, approvals and opt-outs, which we keep after an account closes. We also keep information longer where the law requires or permits it (for example, for tax, accounting or billing records).

Applications a merchant starts but stops working on are closed after a period of inactivity. When that happens we delete the application's Social Security number, date of birth and driver's license number, its uploaded documents, and its application link, and we archive the copy held by our signing service. After a credit authorization is signed and delivered, the copy held by our signing service is archived as well.

When we no longer need information, we delete or anonymize it. Where that is not immediately possible (for example, in backups), we keep it secure and isolated until it can be deleted.

11. Your choices and rights

  • Merchants: stopping texts. Reply STOP to any text to stop further texts from that brokerage through Wingman. You can also ask the brokerage directly.
  • Merchants: your information. Contact the brokerage that reached you (Section 2), or contact us and we will help.
  • Brokerage users. You can ask us to access, correct or delete your account information at support@mcapilot.com. Some records, such as billing records, are kept where the law or a legitimate business need requires it, and we will tell you which.
  • Withdrawing consent. Where we rely on your consent, you can withdraw it at any time by contacting us. This does not affect processing that happened before.
  • Do Not Track. There is no settled standard for browser Do Not Track signals, so we do not currently respond to them. We do not track you across other websites.

12. Additional rights for US state residents

Depending on where you live (for example California, Colorado, Connecticut, Utah or Virginia), you may have the right to:

  • know whether we process your personal information, and access it;
  • correct inaccurate personal information;
  • delete your personal information;
  • get a copy of personal information you gave us;
  • opt out of the sale of personal information, targeted advertising, or profiling that produces legal or similarly significant effects (we do none of these); and
  • not be treated differently for using these rights.

Sensitive information. We use sensitive information (such as Social Security numbers, driver's license numbers, dates of birth and bank statements) only to provide Wingman to the brokerage that collected it. We do not sell it, use it for advertising, or use it to infer characteristics about anyone, so we do not offer a separate way to limit its use.

Making a request. Email support@mcapilot.com. For information we process for a brokerage, we will direct your request to that brokerage and help it respond. We will verify your identity before acting, using information we already hold where we can. You may use an authorized agent; we may ask for proof that the agent is authorized. We respond within 45 days, and may extend that once by 45 more days if needed, with notice and a reason.

Appeals. If we decline your request, you can appeal by emailing support@mcapilot.com. We will respond in writing within the time your state's law allows (for example, 45 days in Colorado and 60 days in Connecticut and Virginia). If your appeal is denied, you may contact your state Attorney General.

California "Shine the Light". California residents may ask once a year, free of charge, which personal information we disclosed to third parties for their direct marketing in the past year. We do not make such disclosures.

13. Children

Wingman is a business tool for adults. We do not knowingly collect information from anyone under 18. If you believe we have, contact us and we will delete it.

14. Changes to this policy

We may update this policy from time to time. The "Last updated" date at the top shows when it last changed. If we make material changes, we will post a notice here or tell brokerage users directly.

15. Contact us

Questions, requests or complaints about this policy: email support@mcapilot.com or write to:

Fundmore LLC
1958 East 13th Street
Brooklyn, NY 11229
United States

This policy is governed by the laws of the State of New York, without regard to its conflict-of-laws rules.

Wingman is operated by Fundmore LLC.