The FTC Safeguards Rule protects nonpublic personal information held by non-bank financial institutions. A consumer finance company's daily work sits squarely inside that definition.
It originates and underwrites credit, services a portfolio, pulls credit reports, and moves funds through ACH and payment processors.
Extending consumer credit is a financial activity under the rule, and the FTC's Safeguards Rule guidance names finance companies among the businesses covered.
Consumer and installment lenders hold high-value financial data.
Every application and account contains Social Security numbers, bank account and routing numbers, income and employment information, government ID, and full credit reports.
That is precisely the customer financial information the Safeguards Rule is written to protect.
Account takeover, synthetic-identity fraud, and business email compromise target this data directly. The rule requires MFA, access controls, and encryption; out-of-band verification of payment instructions is a best practice we add on top.
They are the same controls that defend against the most common attacks on finance companies.
A written program is the baseline, not the ceiling.
The rule requires a written information security program, a Qualified Individual, a documented risk assessment, and an incident response plan. These exist whether or not you have ever had an incident.
We produce these documents to reflect what is actually running in your environment, so the program survives an FTC inquiry or a funding-source security questionnaire rather than reading as boilerplate.
Merchant, point-of-sale, and BNPL data flows widen your perimeter.
Sales finance and buy-now-pay-later programs pull applicant data through retail and merchant partners, checkout integrations, and lead sources before a loan is ever booked. Non-bank auto finance adds dealer and DMS handoffs.
Each connection is a place Social Security numbers, bank details, and credit data can be exposed.
The rule requires you to oversee every service provider and partner that receives, transmits, or stores your customer information.
We map those data flows, document the security expectations, and fold merchant and partner oversight into your written program so the requirement is met and evidenced.
The breach-notification duty applies to every finance company, regardless of size.
A 2023 amendment added a federal notification requirement that took effect in May 2024. A notification event is the unauthorized acquisition of unencrypted customer information involving at least 500 consumers.
If you discover one, you must report it to the FTC through the FTC reporting portal. Report as soon as possible and no later than 30 days after discovery.
The under-5,000-consumer exemption relaxes certain other elements, but it does not waive this duty, and most finance companies hold information on far more than 5,000 consumers across active and paid-off accounts. The trigger is unencrypted information.
That is one more concrete reason we encrypt customer data in transit and at rest by default. We build the incident response plan, define what counts as a notification event for your origination and servicing systems, and prepare the reporting workflow.
A real event is then handled inside the window rather than improvised.
Texas and Tennessee breach-notification law sits alongside the rule.
Texas law applies alongside the FTC Safeguards Rule.
Under Texas Business and Commerce Code §521.053, anyone who conducts business in Texas and owns or licenses computerized data that includes sensitive personal information must notify each affected individual of a breach without unreasonable delay and not later than the 60th day after determining that the breach occurred.
If the breach involves at least 250 Texas residents, the Texas Attorney General must also be notified, through the electronic form on the Attorney General's website, as soon as practicable and not later than the 30th day after that determination.
Those deadlines run separately from the FTC notice due within 30 days of discovering a notification event, so your incident response plan should track each one.
Tennessee Code Annotated §47-18-2107 requires notice to affected Tennessee residents no later than 45 days from discovery or notification of a breach, but subsection (i) states that the section does not apply to an information holder subject to Title V of the Gramm-Leach-Bliley Act, and the Safeguards Rule implements sections of that title (16 CFR 314.1).
Confirm with counsel how the Tennessee exclusion applies to your business.