Gramm-Leach-Bliley Act: privacy, safeguards and what it means for AI vendors
The Gramm-Leach-Bliley Act (GLBA) requires banks and credit unions to tell consumers how they share personal financial information, let them opt out of some sharing, and protect customer information with a written security program. For community banks it creates recurring work on privacy notices, information security and vendor oversight, including any AI vendor that handles customer data.
Updated on
What the Gramm-Leach-Bliley Act is
The Gramm-Leach-Bliley Act (GLBA) is a 1999 federal law. Much of it changed how banks, securities firms and insurers could affiliate. For a community bank today, the part that matters most day to day is Title V, which deals with customer privacy and information security.
Title V has three practical pieces:
- The Privacy Rule. What a bank must tell consumers about how it shares their nonpublic personal information, and when it must let them opt out.
- The safeguards requirement. A written information security program to protect customer information.
- Pretexting provisions. A ban on obtaining customer information from a financial institution under false pretenses.
The Privacy Rule and Regulation P
For banks and credit unions, the privacy requirements are implemented by Regulation P (12 CFR Part 1016), which the CFPB administers. The main obligations are:
- Initial privacy notice. Give customers a clear notice of your privacy policies and practices when the customer relationship begins.
- Annual privacy notice. Provide a notice each year while the relationship continues, unless the bank qualifies for the exception added by Congress in 2015. Broadly, that exception applies when the bank shares information only in ways that do not trigger an opt-out right and has not changed its policies. Confirm whether your bank qualifies before you stop sending notices.
- Opt-out right. Before sharing nonpublic personal information with nonaffiliated third parties outside the rule's exceptions, give consumers notice and a reasonable chance to opt out, and honour opt-outs.
- Limits on reuse. Restrictions on what third parties can do with information they receive, and on sharing account numbers for marketing.
Regulation P includes a model privacy form. Banks that use it correctly get a safe harbor for the content of the notice.
The safeguards requirement for banks
Section 501(b) of GLBA requires financial regulators to set standards for safeguarding customer information. For banks these are the Interagency Guidelines Establishing Information Security Standards, issued by the OCC, Federal Reserve and FDIC. The NCUA has its own version for credit unions in 12 CFR Part 748. Non-bank financial companies follow the FTC's Safeguards Rule instead.
Under the Interagency Guidelines a bank must:
- Have a written information security program, approved by the board
- Assess reasonably foreseeable risks to customer information
- Put controls in place to manage those risks, and test them
- Train staff
- Oversee service providers: use due diligence in selecting them, require them by contract to protect customer information, and monitor them
- Adjust the program as risks and systems change
- Report to the board on the program at least annually
The agencies also expect a response program for unauthorized access to customer information, including notice to customers in certain cases. Separate rules require banks and credit unions to notify their regulator quickly after significant computer-security incidents. The FFIEC IT Examination Handbook describes how examiners review all of this.
Pretexting
GLBA makes it illegal to obtain customer information from a financial institution by false or fraudulent statements, such as calling a branch while pretending to be the customer. Banks are expected to train staff and use authentication controls that make pretexting hard. Social engineering by phone and email is the modern form of the same problem, and voice cloning makes caller authentication more important, not less.
The manual work GLBA creates
- Privacy notices. Reviewing sharing practices each year, deciding whether the annual notice exception applies, updating the notice, and tracking delivery and opt-outs.
- Information security program. Keeping the risk assessment, policies and control inventory current, and writing the annual board report.
- Vendor oversight. Due diligence questionnaires, SOC report reviews, contract checks and ongoing monitoring for every vendor that touches customer data. The 2023 Interagency Guidance on Third-Party Relationships sets out what the FDIC, Fed and OCC expect.
- Training and testing. Staff training records, social engineering tests and evidence for examiners.
- Exam evidence. Pulling all of the above when the IT or compliance exam begins. See bank examination preparation.
What GLBA means for AI vendors
An AI vendor that processes customer information is a service provider under the safeguards requirement. Before you send it customer data, your due diligence should answer:
- Where is the data stored and processed, and can it stay in an environment the bank controls?
- Is customer data used to train models? It should not be, unless the bank has explicitly agreed.
- Who can access the data, and is every access logged?
- Which subcontractors, including model providers, see the data?
- Does the vendor have an independent audit report, such as SOC 2?
- Will the vendor notify the bank of incidents quickly enough to meet the bank's own obligations?
- How is data returned or deleted when the contract ends?
Treat the model provider behind an AI tool as part of the chain. If a vendor sends prompts containing customer data to a third-party model, that model provider is a subcontractor your due diligence should cover. Ask how prompts and outputs are retained and who can see them.
Also look at what the AI system can do, not only what it can see. An agent that can read a customer file but cannot send email, change records or call outside services carries far less risk than one that can. Ask the vendor how permissions are set for each workflow and who can change them.
Lamatic is built for this review. It supports privately hosted models, encrypts data in transit and at rest, supports SSO/SAML, and builds access controls, audit logs, model tracking and data governance into every workflow. Customers can export or delete their data. The details your information security team will want, including our SOC 2 work and third-party testing, are on our security page. Run your normal due diligence on us as you would any vendor.
How a community bank automates GLBA work
Here is a Lamatic workflow for vendor due diligence, one of the heaviest recurring GLBA tasks.
- Inputs. The vendor's completed questionnaire, SOC report, contract and any security documents, plus the bank's vendor management policy and review checklist.
- Extract. The agent reads each document and pulls out the facts the checklist asks for: data types handled, hosting location, subcontractors, encryption, incident notice terms, audit period and any exceptions in the SOC report.
- Check. It compares each answer with the bank's requirements and flags gaps, such as a SOC report that has expired, a missing complementary user entity control, or a contract with no incident notice clause.
- Draft. It drafts the vendor risk review and a list of follow-up questions for the vendor.
- Human review. The vendor manager or information security officer reviews the draft, decides the risk rating and whether to approve the vendor, and signs off.
- Audit trail. Lamatic logs the documents used, the agent's findings, the reviewer's changes and the approval, which becomes part of the evidence for the board report and examiners.
The same approach supports the annual privacy notice review and the board report. Staff questions about privacy procedures can be answered in Microsoft Teams from the bank's own policies, as Locality Bank does for policy and procedure questions. More workflows are on the bank compliance page and the banking solutions hub.
This page is a general overview, not legal advice. Confirm current requirements with counsel and your regulator.
Frequently Asked Questions
Title V requires banks to give privacy notices, offer an opt-out before sharing nonpublic personal information with nonaffiliated third parties outside the rule's exceptions, protect customer information with a written security program, and guard against pretexting.
Regulation P (12 CFR Part 1016) implements the GLBA privacy provisions for banks and credit unions. The CFPB administers it, and it includes a model privacy form.
Not always. Since a 2015 amendment, a bank can skip the annual notice if it shares information only in ways that do not trigger an opt-out right and has not changed its policies. Confirm with counsel whether your bank qualifies.
Banks follow the Interagency Guidelines Establishing Information Security Standards. Credit unions follow the NCUA's guidelines in 12 CFR Part 748. The FTC Safeguards Rule applies to non-bank financial companies.
If it accesses or processes customer information, yes. The bank must do due diligence, require safeguards by contract, and monitor the vendor.
Pretexting is obtaining customer information from a financial institution by false pretenses, such as impersonating a customer. GLBA makes it illegal, and banks are expected to train staff and authenticate callers to prevent it.
See vendor due diligence run on Lamatic
Bring a vendor questionnaire and SOC report and we will show an agent drafting the review for your team to approve.
Book a Demo