Protecting Merchant Data in a Funding Shop

Walk past any desk on a busy funding floor and count the sensitive documents in view. An application with the owner's Social Security number and date of birth. Four months of business bank statements. A driver's license photo. A voided check with routing and account numbers. Sometimes a tax return. That is a complete identity kit, and most shops collect dozens of them every week.

Merchants hand all of this over because they need capital, often quickly. They are trusting you with information that could empty their accounts or open credit in their name. Protecting it is part of treating merchants fairly, it is increasingly expected by funders and regulators, and a breach can end a small shop's reputation in a single news cycle.

This is a practical walk through where merchant data leaks in a typical funding operation and how to close each gap. It covers habits and controls, not law. For your specific legal obligations around privacy and data security, speak with qualified counsel.

Pre-flight summary

A funding file is a complete identity kit; treat it that way.
Collect documents through a portal so copies do not multiply across inboxes and phones.
Use role-based access and two-factor sign-in so visibility matches the job.
Log exports and downloads to deter and detect insider data theft.
Keep only what you need, for as long as counsel advises, and delete the rest.

Leg 01Follow one file from inbox to funded

Start by tracing a single hypothetical deal. A landscaping company applies through a web form. The owner emails three statements and texts a photo of a fourth because one month's PDF would not download. A broker forwards everything to their personal email to work on it at home. The file is shotgunned to six funders as attachments. Two weeks later the deal funds, and copies of the statements now live in at least a dozen places.

Each of those copies is a point of exposure: the broker's phone camera roll, a personal inbox with a weak password, six funder inboxes you do not control, a shared drive folder named Deals 2025. Most data problems in funding shops are not sophisticated attacks. They are documents sitting in too many places with too many people able to open them.

Leg 02Collect documents in one controlled place

The first fix is upstream: stop documents arriving through scattered channels. When merchants upload directly into a branded portal, the statements land on the deal record instead of in a broker's inbox or text thread. That one change removes the most common copies.

FundPilot's merchant portal gives each client a branded place for applications and document uploads, and everything attaches to the deal automatically. Brokers still talk to the merchant, but they no longer need to forward a PDF to themselves to get work done.

Send merchants a portal link instead of asking them to email or text statements.
Discourage photos of documents on personal phones; if one arrives, move it to the deal and delete the original.
Avoid shared drive folders as the system of record for funding files.
Treat personal email accounts as off-limits for merchant documents, full stop.

Leg 03Limit who can see the sensitive fields

Not everyone on your floor needs to see a full Social Security number. A broker working a deal may need the merchant's statements and contact details; an investor in a syndication needs deal economics but almost certainly not the owner's identity documents. A referral partner may only need to know a deal's stage.

Role-based access lets you match visibility to the job. Owners and managers see what they need to supervise; brokers see their own pipeline; investors and partners see a narrow slice. When a broker leaves, their access ends the same day, and the deals stay with the company.

Pair access control with two-factor sign-in for everyone. A stolen password alone should never be enough to open a funding file.

Most funding-shop data leaks are not hacks. They are documents in too many places, open to too many people.

Leg 05Watch for the quiet exit

Insider risk in a funding shop usually looks mundane. A broker who is planning to leave starts exporting lead lists or downloading files in bulk during the last few weeks. Without logs, you find out when merchants mention that a competitor called them using details only your shop had.

An audit trail of exports, downloads and changes turns that from a mystery into a record. You can restrict who is allowed to export at all, review unusual activity, and have facts in hand if you ever need to take action. Just as important, a visible audit trail discourages the behavior in the first place.

FundPilot records every export, download and change in a full audit trail, and role-based access decides who is allowed to export in the first place.

Leg 06Decide what to keep and what to delete

Data you no longer hold cannot leak. Many shops keep every document forever by default, including dead deals from years ago with full identity packages attached. That is a liability with no upside.

Work with counsel to set a written retention policy: what you must keep for funded deals, how long, and what happens to declined or abandoned applications. Then make deletion a routine rather than a someday project, and make sure it actually removes files from every place they live, not just the CRM view.

List every place merchant documents currently live, including inboxes and phones.
Consolidate new files into one controlled system with a portal for intake.
Set roles so each person sees only what their job needs.
Turn on two-factor sign-in for every account.
Restrict and log exports and downloads.
Adopt a counsel-reviewed retention schedule and run it on a calendar.

Questions from the floor

Is it acceptable for merchants to email bank statements?

Plenty of merchants will email documents no matter what you ask, and refusing them outright can stall a deal. The better approach is to make the portal the easiest path: send a link, explain it keeps their information off email, and move any emailed files onto the deal record promptly. Over time, most merchants are happy to use a secure upload once it is offered.

Should brokers be able to see full Social Security numbers?

That depends on your workflow, but many shops find brokers rarely need the full number once an application is complete. Restricting sensitive fields to the people who process applications reduces exposure if a broker account is compromised. Decide based on the actual tasks each role performs, and review the setting whenever your process changes.

What legal obligations do we have around merchant data?

Obligations can come from privacy and data-security laws, funder agreements and industry expectations, and they differ by jurisdiction and by the type of data involved. This article covers practical habits rather than legal requirements. Ask qualified counsel to identify which rules apply to your shop, including any requirements for notifying people after a security incident.

merchant data securityMCA data protectionbank statement securitySSN protection brokersfunding shop access controlbusiness funding privacy

General information only — not legal, tax or financial advice. Rules for telemarketing, texting, recording, disclosures and data retention vary and change; confirm current requirements with qualified counsel.