WISP for non-federally insured credit unions
Non-federally insured credit unions need a WISP when the business is covered by the FTC Safeguards Rule category non-federally insured credit union. The practical coverage trigger is that the firm operates as a credit union that is not federally insured and maintains member financial information. Member data lives in core processing, online banking, loan files, card systems, ACH and wire systems, shared-branching tools, call-center notes, and vendor portals. The WISP should map third-party core and online banking providers with contract oversight.
Key facts
- Non-federally insured credit unions should evaluate coverage under the FTC Safeguards Rule and document the factual trigger: operates as a credit union that is not federally insured and maintains member financial information.
- The data map should be vertical-specific: Member data lives in core processing, online banking, loan files, card systems, ACH and wire systems, shared-branching tools, call-center notes, and vendor portals. The WISP should map third-party core and online banking providers with contract oversight.
- Many credit unions exceed 5,000 consumers through member and former-member records. A very small institution should still document the count because 16 CFR 314.6 is limited.
Key takeaways
- Non-federally insured credit unions should evaluate coverage under the FTC Safeguards Rule and document the factual trigger: operates as a credit union that is not federally insured and maintains member financial information.
- The data map should be vertical-specific: Member data lives in core processing, online banking, loan files, card systems, ACH and wire systems, shared-branching tools, call-center notes, and vendor portals. The WISP should map third-party core and online banking providers with contract oversight.
- Many credit unions exceed 5,000 consumers through member and former-member records. A very small institution should still document the count because 16 CFR 314.6 is limited.
- Credit unions already have financial regulators. Federal insurance status affects regulator mapping; it does not make member information less sensitive or remove the need to confirm the governing safeguards regime.
Why non-federally insured credit unions are covered
Non-federally insured credit unions are covered when their business activity fits non-federally insured credit union. FTC guidance lists non-federally insured credit unions as covered financial institutions.
The coverage test is factual. For this vertical, Policywright treats the trigger as: operates as a credit union that is not federally insured and maintains member financial information. The sources block below is limited to primary-source or regulator materials so the page does not drift into unsourced compliance folklore.
The page does not invent a coverage theory beyond the cited category and factual trigger.
Where customer information lives
Member data lives in core processing, online banking, loan files, card systems, ACH and wire systems, shared-branching tools, call-center notes, and vendor portals. The WISP should map third-party core and online banking providers with contract oversight.
That data-flow map changes the WISP. A tax preparer worries about portals and e-file records; a collection agency worries about placement files, dialers, and dispute queues; an auto dealer worries about the credit application, F&I office, DMS, and lender portals.
A useful written program should name the systems, roles, vendors, access paths, retention points, and evidence records that fit the trade.
Common objection
Credit unions already have financial regulators. Federal insurance status affects regulator mapping; it does not make member information less sensitive or remove the need to confirm the governing safeguards regime.
Policywright handles that objection by writing the factual basis into the packet rather than hiding it. If coverage is unclear, the firm should preserve the question for counsel instead of turning a WISP into an unsupported legal conclusion.
Under-5,000-consumer analysis
Many credit unions exceed 5,000 consumers through member and former-member records. A very small institution should still document the count because 16 CFR 314.6 is limited.
16 CFR 314.6 exempts smaller covered firms only from 314.4(b)(1), (d)(2), (h), and (i). It does not remove the written-program duty or the need to protect customer information with reasonable administrative, technical, and physical safeguards.
A serious small-firm packet should document the count assumption and keep the fuller controls where they are operationally useful.
| Question | Vertical-specific answer | Source |
|---|---|---|
| Coverage trigger | operates as a credit union that is not federally insured and maintains member financial information | FTC Safeguards Rule business guidance |
| Customer data flow | Member data lives in core processing, online banking, loan files, card systems, ACH and wire systems, shared-branching tools, call-center notes, and vendor portals. The WISP should map third-party core and online banking providers with contract oversight. | Document in WISP data inventory |
| Common objection | Credit unions already have financial regulators. Federal insurance status affects regulator mapping; it does not make member information less sensitive or remove the need to confirm the governing safeguards regime. | FTC Safeguards Rule business guidance |
| Small-firm exception | Many credit unions exceed 5,000 consumers through member and former-member records. A very small institution should still document the count because 16 CFR 314.6 is limited. | 16 CFR 314.6 |
FAQ
Is this legal advice?
No. Policywright is a configurable template product, not a law firm and not legal advice. A qualified lawyer should review state-law reliance or breach-notification decisions.
Does a small firm still need a written plan?
Yes. The Safeguards Rule requires a written information security program for covered financial institutions, and IRS guidance tells paid tax preparers to maintain a written data security plan.
What if a control is not in place yet?
A serious WISP should not pretend. It should identify the gap, assign an owner, set a target date, and preserve a dated remediation record.
What makes non-federally insured credit unions different from tax preparers?
The data flow and objection pattern are different. Non-federally insured credit unions need a WISP that follows Member data lives in core processing, online banking, loan files, card systems, ACH and wire systems, shared-branching tools, call-center notes, and vendor portals. The WISP should map third-party core and online banking providers with contract oversight.
Does Policywright cover related non-Safeguards obligations?
No separate related obligation is claimed on this page. Policywright is focused on the Safeguards Rule policy packet and does not replace counsel.
Sources
Build a WISP for non-federally insured credit unions.
Answer plain questions and receive a source-cited policy packet tailored to the firm's systems, vendors, and gaps.
Build my plan