WISP for account servicers
Account servicers need a WISP when the business is covered by the FTC Safeguards Rule category account servicer. The practical coverage trigger is that the firm services consumer credit accounts, payment accounts, or loan portfolios for another entity. Servicing data lives in boarding files, account platforms, payment systems, call-center tools, correspondence queues, dispute workflows, vendor portals, and investor or client reports. The WISP should identify data received from the owner and data generated by servicing activity.
Key facts
- Account servicers should evaluate coverage under the FTC Safeguards Rule and document the factual trigger: services consumer credit accounts, payment accounts, or loan portfolios for another entity.
- The data map should be vertical-specific: Servicing data lives in boarding files, account platforms, payment systems, call-center tools, correspondence queues, dispute workflows, vendor portals, and investor or client reports. The WISP should identify data received from the owner and data generated by servicing activity.
- Servicers frequently exceed the threshold because one client file can contain thousands of accounts. If a niche servicer is below it, the exception remains narrow.
Key takeaways
- Account servicers should evaluate coverage under the FTC Safeguards Rule and document the factual trigger: services consumer credit accounts, payment accounts, or loan portfolios for another entity.
- The data map should be vertical-specific: Servicing data lives in boarding files, account platforms, payment systems, call-center tools, correspondence queues, dispute workflows, vendor portals, and investor or client reports. The WISP should identify data received from the owner and data generated by servicing activity.
- Servicers frequently exceed the threshold because one client file can contain thousands of accounts. If a niche servicer is below it, the exception remains narrow.
- We are only the servicer. Servicing is exactly the point: the servicer maintains customer information and must safeguard the systems, vendors, and users that handle it.
Why account servicers are covered
Account servicers are covered when their business activity fits account servicer. FTC guidance lists account servicers among the financial institutions covered by the Safeguards Rule.
The coverage test is factual. For this vertical, Policywright treats the trigger as: services consumer credit accounts, payment accounts, or loan portfolios for another entity. 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
Servicing data lives in boarding files, account platforms, payment systems, call-center tools, correspondence queues, dispute workflows, vendor portals, and investor or client reports. The WISP should identify data received from the owner and data generated by servicing activity.
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
We are only the servicer. Servicing is exactly the point: the servicer maintains customer information and must safeguard the systems, vendors, and users that handle it.
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
Servicers frequently exceed the threshold because one client file can contain thousands of accounts. If a niche servicer is below it, the exception remains narrow.
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 | services consumer credit accounts, payment accounts, or loan portfolios for another entity | FTC Safeguards Rule business guidance |
| Customer data flow | Servicing data lives in boarding files, account platforms, payment systems, call-center tools, correspondence queues, dispute workflows, vendor portals, and investor or client reports. The WISP should identify data received from the owner and data generated by servicing activity. | Document in WISP data inventory |
| Common objection | We are only the servicer. Servicing is exactly the point: the servicer maintains customer information and must safeguard the systems, vendors, and users that handle it. | FTC Safeguards Rule business guidance |
| Small-firm exception | Servicers frequently exceed the threshold because one client file can contain thousands of accounts. If a niche servicer is below it, the exception remains narrow. | 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 account servicers different from tax preparers?
The data flow and objection pattern are different. Account servicers need a WISP that follows Servicing data lives in boarding files, account platforms, payment systems, call-center tools, correspondence queues, dispute workflows, vendor portals, and investor or client reports. The WISP should identify data received from the owner and data generated by servicing activity.
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 account servicers.
Answer plain questions and receive a source-cited policy packet tailored to the firm's systems, vendors, and gaps.
Build my plan