Consumer reporting agencies play a crucial role in determining access to housing, credit, and employment. Errors in their data can lead to more than just compliance issues. RentGrow's $2.25 million settlement with the FTC highlights how misconceptions about data accuracy can lead to significant legal risks.
These myths often stem from confusing technical capability with legal responsibility. Your systems might function correctly but still violate the Fair Credit Reporting Act (FCRA). Understanding this distinction can prevent enforcement actions like the one RentGrow faced.
Myth 1: Clean Data from Vendors Equals Compliance
Reality: The FCRA holds you accountable for data accuracy, regardless of the source. RentGrow received accurate data from its vendor but displayed it in a way that duplicated criminal and eviction records. This made applicants appear to have more issues than they actually did.
Under FCRA Section 607(b), you're required to ensure accuracy in how data is transformed and presented. If your processes create duplicates, you're responsible for that inaccuracy. The FTC found RentGrow knew about this issue but didn't address it until they were investigated.
What you should do: Deduplicate records before displaying them, use matching logic to prevent multiple entries for the same case, and test your data presentation for accuracy.
Myth 2: Disclose Only the Sources You Deem Important
Reality: FCRA Section 609 mandates that you disclose all sources used in a consumer report when requested. RentGrow failed to disclose Lexis-Nexis Accurint as a source for historical addresses and middle names, which were used to match records to consumers.
This omission undermines a consumer's ability to dispute inaccuracies. If they don't know which sources were used, they can't effectively challenge the data.
Your obligation: Disclose every source that contributed to the report, including those that provided matching criteria. Document your data lineage thoroughly, detailing which vendors supplied which fields and the logic applied.
Myth 3: You Can Dismiss Disputes You Consider Invalid
Reality: The FCRA doesn't allow you to dismiss disputes as "invalid" without action. RentGrow improperly categorized disputes about duplicate records as invalid, bypassing required procedures.
Section 611 requires you to conduct a reasonable reinvestigation of disputed information, review all relevant consumer information, and complete the investigation within 30 days. You can't skip these steps based on your judgment of a dispute's validity.
If disputes fall outside your normal process, it indicates a gap in your procedures. Develop a system that handles edge cases and provides substantive responses to consumers.
Myth 4: Informing Consumers Satisfies Notification Duty
Reality: RentGrow misled consumers by claiming successful disputes were communicated to landlords, while telling landlords there was no change. This violated both the FCRA and the FTC Act.
Section 611(a)(5) requires you to notify anyone who received a report with disputed information that it has been corrected. The notification must be accurate and consistent.
Ensure your dispute resolution includes verified notifications to all recipients of the original report, confirming that the updates were sent and received.
Myth 5: Compliance Means Avoiding Obvious Errors
Reality: RentGrow knew about its duplication issues but didn't address them until investigated. Awareness without action turns a technical issue into a compliance violation.
Section 607(b) demands you address known accuracy risks. If your quality assurance identifies systematic errors, fix the root cause, not just individual reports.
Monitor error patterns in your reports. Recurring disputes about the same issue indicate a procedural gap. Document what you learned, the changes made, and how you verified the fix.
Proactive Steps to Take
Integrate accuracy into your data architecture, not just your dispute process. Map data transformations from source to report generation and implement controls to prevent errors.
Create consumer-friendly disclosure documentation. Explain how you use historical addresses or name variants in matching logic.
Use dispute volume as an early warning. Investigate recurring disputes to find root causes before the FTC does. Document your findings and solutions.
Test notification workflows thoroughly. Ensure that when you modify or delete information, recipients of the original report receive accurate updates. Audit dispute resolutions monthly to confirm notifications were sent as promised.
The $2.25 million penalty RentGrow faced underscores the importance of addressing accuracy gaps proactively. The choice is whether you'll act now or wait for an investigation.
