The FTC Safeguards Rule protects nonpublic personal information held by non-bank financial institutions. A title company's daily work sits squarely inside that definition.
It collects borrower and seller financial data, holds funds in escrow, and exchanges information with lenders.
Title and settlement companies hold high-value financial data.
Every file contains Social Security numbers, bank account and routing numbers, wire instructions, and loan details. That is precisely the customer financial information the Safeguards Rule is written to protect.
Wire 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 closings.
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 lender security questionnaire rather than reading as boilerplate.
Vendor oversight is part of compliance.
Title operations rely on production platforms, escrow-accounting systems, and underwriter portals. The rule requires you to oversee the service providers that handle your customer information.
We inventory those vendors, document the security expectations, and fold vendor oversight into your written program so the requirement is met and evidenced.
The breach-notification duty reaches every covered title operation.
A 2023 amendment to the rule 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 within 30 days of discovery.
The under-5,000-consumer exemption eases certain other elements, but it does not relax this obligation. The duty applies to the smallest covered agency as well as the largest. The trigger is unencrypted information.
So encrypting customer data in transit and at rest is both a core safeguard and a direct way to reduce notification exposure.
We build the incident response plan, define what a notification event means for your closing and escrow systems, and prepare the reporting workflow. A real event is then handled inside the window.
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.