What trouble can spreadsheet data exchanges cause?

FCRA exposure for obtaining or sharing consumer information without a permissible purpose, GLBA Safeguards Rule findings for unencrypted and uncontrolled transfers, breach-notification duties in every state, and failed creditor or client audits that require showing who accessed what, when, and why.

How does EnrolledHits replace spreadsheet exchanges?

Accounts arrive over encrypted SFTP or API and identifiers are hashed on arrival, so raw consumer data is never stored and no raw file exists to exchange. Access is provisioned per company and named user, every search is logged with its purpose, and results expire.

The Spreadsheet Problem — PII by Email Is the Risk

Q: What is wrong with exchanging consumer data by spreadsheet?

There is no check on permissible purpose before the data moves, no security controls on the file once it does, and no audit trail afterward. Copies multiply with every forward, and a single emailed file can hold thousands of Social Security numbers, sometimes with no password protection.

How it works today

Lists by email

Enrollment files and placement files cross inboxes as spreadsheet and CSV attachments — the industry’s default file format is also its biggest exposure.

No gate on purpose

A spreadsheet never asks why you want the data. Whoever holds the file holds everyone’s information in it — whether or not they have a permissible purpose for a single row.

Copies that never die

Every forward is a new uncontrolled copy. Attachments get downloaded, re-saved, and kept for years. You cannot recall, expire, or audit a spreadsheet.

The trouble that comes with it

The legal exposure

Permissible purpose. Consumer information obtained or shared without one is an FCRA problem — for the party that pulled it and the party that received it. The purpose has to exist before the data moves, not be invented after.
Safeguards. The GLBA Safeguards Rule expects encryption in transit, controlled access, and oversight of how service providers handle customer information. An emailed spreadsheet has none of the three.
Breach math. One compromised inbox can mean thousands of Social Security numbers. Every state has a breach-notification law, and the sender of the file owns the headline, the notification costs, and the regulator’s questions.

The business exposure

Audits you cannot pass. Creditor and client audits ask a simple question: show us who accessed what, when, and why. A spreadsheet has no answer to any of the three.
Contracts you can lose. Placement and servicing agreements increasingly require documented security controls. “We email it” is not a control.
Data you cannot defend. If a file surfaces somewhere it shouldn’t, there is no log to prove what was in it, who sent it, or who opened it — because there never was one.

The fix: matching without the file

EnrolledHits was built to retire the spreadsheet. The exchange still happens — the raw data doesn’t:

No raw data, ever

Accounts arrive over encrypted SFTP or API, every identifier is converted to a one-way hash on arrival, and matching happens entirely on those hashes. There is no master spreadsheet of consumers to steal, forward, or lose — because it never exists.

Every search has a reason, on the record

Access is provisioned per company, per named user. Searches run under the customer’s account and purpose, and every query and hit is written to an append-only audit log — the answer to “who accessed what, when, and why” is a report, not a shrug. Results are delivered to the account that asked, and they expire.

Stop emailing the spreadsheet

The full treatment — hashing, tokenization, access control, retention — is on our Privacy, Security & Compliance page. This page is operational education, not legal advice.

The spreadsheet problem — questions

What is wrong with exchanging consumer data by spreadsheet?

Three things: there is no check on permissible purpose before the data moves, no security controls on the file once it does, and no audit trail afterward. Add that copies multiply with every forward, and a single emailed file can hold thousands of Social Security numbers with no password at all.

What trouble can it cause?

FCRA exposure for obtaining or sharing consumer information without a permissible purpose, GLBA Safeguards findings for unencrypted, uncontrolled transfers, breach-notification duties in every state if an inbox or laptop is compromised, and failed creditor audits that ask who accessed what, when, and why.

How does EnrolledHits replace the spreadsheet?

Accounts move over encrypted SFTP or API and are hashed on arrival — raw identifiers are never stored, so no raw file exists to exchange. Access is provisioned per company and named user, every search is logged with its purpose, and results expire. The match still happens; the exposure doesn’t.

The spreadsheet problem