Compliance Updates8 min read

Borrower Data and Records: What Lenders Keep and Why

By Michael Dunleavey
•November 19, 2026
A borrower record passing a lock, an audit check and a retention clock into one protected record

Borrower data safeguards are the controls around a borrower's personal information, plus the records that show what was checked and what was decided. For a lender, the practical test is simple: for any file, can you show where the borrower's data went, what was decided, and how long the record is kept?

This is checkpoint 2 of 5 in the LASER Credit Access® series on the path from online application to human review. Checkpoint 1 covered consent and notices: what a borrower authorizes at the application. Checkpoint 2 picks up the moment that authorization is given, when the borrower's information starts to move through your process.

What counts as borrower data

Borrower data is more than the application form. It starts with what the borrower typed in: name, address, date of birth, income, the details of the loan they want. It grows as the file moves. A credit report is added. An identity check returns a result. A reviewer adds a note. A decision is made, and the lender records why.

Each of those items is information about a person, and each one has to live somewhere. The lender's job is to know where, to protect it while it is there, and to keep it only as long as the lender's own policy says. That is why this checkpoint has two halves: safeguards (protect it) and records (prove what happened and keep it for the right time).

Where borrower data goes after the application

At the second step on the compliance view, the application details are collected once and saved to the record. One record means one place to look when someone asks what happened to a borrower's information. Without it, the same details end up in an inbox, a spreadsheet, a PDF and a loan system, and nobody can say which copy is the real one.

Borrower personal information is encrypted at rest and in transit, including data sent to and from service providers. If an identity verification provider receives the borrower's details, as consented at checkpoint 1, that data is included.

Illustration: application details flowing into one protected record, with locked connections out to the service providers that receive borrower data

One record, one place to look. Data that moves on to a service provider moves protected.

Service providers: the list you should be able to produce

A service provider is any outside party that receives borrower data to do a job for the lender: a credit bureau, an identity verification provider, a document or e-signature tool, a hosting or software vendor. Most lenders use several, and the list tends to grow without anyone deciding it should.

The GLBA Safeguards Rule covers borrower personal information, including data sent to service providers. Our guides to the GLBA Safeguards requirements and the FTC Safeguards Rule for non-bank lenders cover the rules behind it. In plain terms, the rule does not stop at your own front door. Data you send to a provider is still borrower data, and you are still the one expected to know that it is going there.

A good working list answers three questions for each provider (our suggestion, not a legal requirement):

  • What does it receive? Which fields, and for which step of the process.
  • Why does it receive them? The job it does for you, tied to a step on your own compliance view.
  • Who owns the relationship? One named person who can say what the contract and the settings are.

If you cannot produce that list in a few minutes, that is the first thing to fix, and it costs nothing but an afternoon.

Illustration: three linked steps for each service provider, what it receives, why it receives it, and who owns the relationship

For each provider, three answers: what it receives, why, and who owns the relationship.

What the audit trail holds

Results and decisions are kept in the audit trail. That means the record shows what each check returned and what the lender decided. When the question is "why was this file handled this way," the trail is the answer.

An audit trail earns its keep in three situations. A borrower disputes an outcome and you need to show what was checked. A colleague takes over a file and needs to see what happened before they arrived. An examiner or auditor asks for the file and expects it to explain itself. In all three, the lender who can open one record and read the sequence is in a better position than the lender who has to reconstruct it from several systems.

The trail also makes consistency visible. If two similar files were handled differently, the record shows where they diverged, and you can decide whether the difference was a reasoned exception or an error.

Illustration: a check, a decision and a saved file check flowing in sequence into one record with a timestamp

Checks and decisions in one sequence, so the record explains itself.

How long records are kept

Retention is set by the lender. The default setting is 25 months, and timed deletion is configurable. Timed deletion means records are removed on a schedule that follows the lender's own written policy, not on whoever remembers to do it.

There is no single number that fits every record. Retention periods vary by institution and by record type, and some records carry their own, longer periods under other rules: our AML and KYC requirements guide covers the CIP record periods. Your counsel confirms which apply to you.

Two habits make retention easier to defend. First, write the period down, per record type, in your own policy. Second, make sure what the system does matches what the policy says. A policy that says one thing while the settings do another is harder to explain than either on its own.

Illustration: a record moving through a lender-set retention period to timed deletion, with a named owner and a protected end state

The lender sets the period, and timed deletion follows the written policy.

Retention stays in the lender's hands. Confirm your own period with your compliance counsel.

Four checks for your own process

These are questions for your team and your counsel, not conclusions.

  • Do you know every provider that receives borrower data? A list is the starting point, with the three answers above next to each name.
  • Can you show results and decisions in one trail? Scattered records are hard to produce, and the effort of producing them is itself a finding.
  • Is your retention period written down, and does it follow your own policy? An unwritten policy is hard to defend, and an unfollowed one is harder.
  • Do you know who can delete records, and when? Deletion should follow the written policy, and the person who can do it should be named.
  • A free one-page checklist covers these checks and a few more: the Borrower Data and Records Checklist. It is a resource for your own process, not an app feature.

    A ten-minute test you can run this week

    Pick one closed file from last quarter. Set a timer for ten minutes and try to answer five questions from the record alone:

  • What information did the borrower give, and where is it saved?
  • Which outside providers received any of it?
  • What was checked, and what did each check return?
  • What was decided, and by whom?
  • When is this record due to be removed under your own policy?
  • If you answered all five without opening a second system, the checkpoint is working for that file. If you could not, you have found the exact step to fix, and a specific gap is easier to close than a general worry. Run the same test on a second file from a different loan type before you decide what to change.

    Where this sits in the five checkpoints

  • Consent and notices
  • Data safeguards and records (this post)
  • Identity, fraud and watchlist screening
  • Credit pull: permissible purpose and legal basis
  • Review and adverse action
  • Each checkpoint rests on the one before it. Consent tells you what the borrower agreed to. Safeguards and records tell you what happened to the information afterward. Next week: identity comes before credit.

    Talk it through with your team

    If you would like to map the five checkpoints to your own policies, we are glad to help. It is a short conversation, and you set the agenda.

    General reference point, not legal advice. Each lender confirms its requirements with its own compliance counsel.

    Consistency of Process – Identical Loans Scored Identically.

    borrower data retentionloan record retentionaudit trail

    Frequently Asked Questions

    Where does borrower data go after the application?

    Application details are collected once and saved to the record. Borrower personal information is encrypted at rest and in transit, including data sent to and from service providers.

    Does the GLBA Safeguards Rule cover service providers?

    Yes. The GLBA Safeguards Rule covers borrower personal information, including data sent to service providers.

    What is kept in the audit trail?

    Results and decisions are kept in the audit trail, so the record shows what was checked and what was decided.

    How long are records kept?

    Retention is set by the lender. The default setting is 25 months, and timed deletion is configurable. Confirm yours with your compliance team.

    Is data sent to service providers protected?

    Yes. Borrower personal information is encrypted at rest and in transit, including data sent to and from service providers.

    Can a lender set its own retention period?

    Yes. Timed deletion is configurable to your own retention policy. The default setting is 25 months. Confirm yours with your compliance team.

    Michael Dunleavey

    Founder — LASER Credit Access

    Michael Dunleavey has worked in lending since 2002, at Virginia Commercial Finance, CIT Small Business Lending, CapitalSource and SunTrust Bank, where compliance training and testing were part of the job. Michael designed the LASER Credit Access app and oversees its development, and designed its COMPLY compliance engine after a year of research.

    Ready for a more consistent credit process?

    Discover how LASER Credit Access streamlines compliance and decisioning natively inside Salesforce — unified in a single app, ready from day one.