Industries
Banking: what your operating records are worth to AI research
A bank's unit of work is the loan or account case its staff move from request to decision. The workflow can be useful for research. Account numbers, customer lists and nonpublic customer details stay out. Being a bank is not eligibility. The fit check decides.
Up to $150K · $0 cost · 3 days
| Fact | Detail |
|---|---|
| Unit of work | loan or account case |
| First exclusion | account numbers |
| First rule | Part 314 of Title 16 implements sections 501 and 505(b)(2) of the Gramm-Leach-Bliley Act. It sets standards for developing, implementing, and maintaining reasonable administrative, technical, and physical safeguards to protect the security, confidentiality, and integrity of customer information. eCFR |
| Second rule | The Safeguards Rule applies to the handling of customer information by financial institutions over which the Federal Trade Commission has jurisdiction. Institutions subject to the Commission's enforcement authority are those that are not otherwise subject to the enforcement authority of another regulator under section 505 of the Gramm-Leach-Bliley Act, 15 U.S.C. 6805. eCFR |
What Banking operating records look like
Banking operating records are the loan or account case staff move from request to decision, and they are not the customer's account number.
Taking a credit request records the channel, the checklist, and the handoff into review. Moving a case through review records the steps, the exception, and the decision. The customer's profile, the account number, and the list of depositors are not the workflow. The case history, with those fields removed, is.
Other sectors are grouped under company data licensing by industry.
The license itself is explained in how to sell company data to AI companies.
Workflows in Banking that AI research can learn from
Taking a credit request, moving the loan or account case through review, and servicing it after the decision are three separate trails.
- taking a credit request
- moving a case through review
- servicing the account after the decision
Servicing the account after the decision shows disputes, covenants, and the next review date as events, not as a customer file. The full case matters because the decision alone hides the exception path.
For a related sector's records, read insurance company data for AI research or fintech company data for AI research.
Systems Banking companies usually run
Mail, the CRM, and chat are where a loan or account case leaves a staff trail, beside the core banking platform that has no system write-up.
Microsoft 365 holds the credit memo and the committee pack. Salesforce holds the pipeline stage. Slack holds the internal question on an exception. The core banking platform holds the ledger and is named only as plain text.
| System | Category | Why it holds this sector's work |
|---|---|---|
| Microsoft 365 | Email and collaboration | Credit memos and committee packs sit in mail and documents. |
| Salesforce | CRM and sales | The pipeline stage of a credit request sits in the CRM. |
| Slack | Chat | Exception questions between credit staff sit in chat. |
| core banking platform | Industry system | Balances, account records, and the ledger sit in the core banking platform. |
What a Banking license leaves out
Account numbers and customer lists and nonpublic customer details stay out of a license, even when they sit on the loan or account case.
- account numbers
- customer lists and nonpublic customer details
Account numbers identify the product the customer holds. Customer lists and nonpublic customer details include balances, contact records, and anything the customer gave the bank about their finances. Those stay out. The step sequence can remain.
The details that never leave any company are listed in what is never shared.
Rules cited for Banking records
Each note on a loan or account case quotes a public source about financial privacy, and none of them says a license meets that source.
The Safeguards Rule in the Code of Federal Regulations is the public rule for customer information at a financial institution under the Federal Trade Commission's jurisdiction. It does not say a de-identified case file satisfies those duties.
| Rule | What the source says | Source |
|---|---|---|
| 16 CFR 314.1(a) — Purpose of the Safeguards Rule | Part 314 of Title 16 implements sections 501 and 505(b)(2) of the Gramm-Leach-Bliley Act. It sets standards for developing, implementing, and maintaining reasonable administrative, technical, and physical safeguards to protect the security, confidentiality, and integrity of customer information. | eCFR |
| 16 CFR 314.1(b) — Scope of the Safeguards Rule | The Safeguards Rule applies to the handling of customer information by financial institutions over which the Federal Trade Commission has jurisdiction. Institutions subject to the Commission's enforcement authority are those that are not otherwise subject to the enforcement authority of another regulator under section 505 of the Gramm-Leach-Bliley Act, 15 U.S.C. 6805. | eCFR |
| 16 CFR 314.2(d) — Customer information | Customer information means any record containing nonpublic personal information about a customer of a financial institution, in paper, electronic, or other form, that is handled or maintained by or on behalf of that institution or its affiliates. | eCFR |
| 16 CFR 314.2(h) — Financial institution | A financial institution, for the Safeguards Rule, is an institution whose business is an activity that is financial in nature, or incidental to such activities, as described in section 4(k) of the Bank Holding Company Act of 1956, 12 U.S.C. 1843(k). An institution significantly engaged in those activities is a financial institution. | eCFR |
| 16 CFR 314.2(l) — Nonpublic personal information | Nonpublic personal information means personally identifiable financial information, and any list, description, or other grouping of consumers (and publicly available information pertaining to them) that is derived using personally identifiable financial information that is not publicly available. | eCFR |
| 16 CFR 314.3(a) — Information security program | A financial institution subject to the Safeguards Rule shall develop, implement, and maintain a comprehensive written information security program with administrative, technical, and physical safeguards appropriate to its size and complexity, the nature and scope of its activities, and the sensitivity of the customer information at issue. | eCFR |
Wind-down specifics for Banking
When a bank winds down a book, the staff trail on the loan or account case is the operational record, not a customer list.
A sale of a loan book is a different transaction from a license of the staff workflow. Keep the case chronology. Leave the customer list and the account numbers out.
- Keep the case chronology if you discuss the workflow.
- Leave the customer list and the account numbers out.
- A loan-book sale is a different transaction from a workflow license.
General information only. This is not legal, tax or financial advice.
Related
- Industries
What operating records look like by sector, and what is left out.
- How to sell company data
How to sell or license company data to AI companies, and which route fits.
- What's shared
Which records can be licensed, which details never leave, and what you approve.
- Eligibility
Staff, records, daily-use systems, and the right to license, plus a checker.
- Estimate
US payout bands by staff at peak, and the estimator that uses them.
- Insurance
Claims handling, with claimant identity left out.
- Fintech
Payment and credit decisions, with card numbers left out.
Questions about banking company data for AI research
Which account numbers and customer lists never leave a bank in a license?
Account numbers never leave a bank in a license, and neither do customer lists and nonpublic customer details. Balances, contact records, and what the customer told the bank about their finances stay out. The unit of work that can remain is the loan or account case: the steps from the credit request through review to the decision. The customer's profile is not that case history.
Is the loan case the record, or is it the customer's profile?
The record is the loan or account case, not the customer's profile. Taking a credit request, moving a case through review, and servicing the account after the decision are the trails. The decision alone hides the exception path, so the case chronology is the part worth describing. Account numbers stay on the core banking platform and out of any copy you discuss.
Where do bank workflow records usually sit among the systems Vetrix already documents?
Credit memos and committee packs usually sit in Microsoft 365. The pipeline stage of a credit request sits in Salesforce. Exception questions between credit staff sit in Slack. The core banking platform holds the ledger and is named only as plain text, because it has no deletion write-up. List the tools staff actually open, and leave the customer list out of the export.
Does holding a banking charter replace the staff and records tests?
No. Holding a banking charter does not replace the staff and records tests. Being a bank is not eligibility. The fit check decides. A loan or account case can be useful as workflow history only after account numbers and nonpublic customer details are removed. The charter does not change that removal, and it does not set a payout.
Sources
- eCFR. 16 CFR 314.1(a) — Purpose of the Safeguards Rule. Checked 2026-11-04
- eCFR. 16 CFR 314.2(d) — Customer information. Checked 2026-11-04
- eCFR. 16 CFR 314.3(a) — Information security program. Checked 2026-11-04