The Hidden Inputs Behind a Match
This chapter examines the identifiers behind RentGrow’s alleged matching process: historical addresses, names, middle names, initials, application information, credit data, and public records. The key judgment is whether an identifier merely helps a screening company find a possible record or actually establishes that the record belongs to the applicant. That distinction matters because broader data can improve discovery while also making a report harder for the applicant to inspect and correct.
A tenant-screening report may not begin with a complete identifier. An application may omit a middle name. A court record may use an old address. A public record may contain only limited information about the person involved. A company that searched only the most obvious fields could miss a record that belongs to the applicant. But a company that treats every matching name or address as proof could attach another person’s history to the wrong report. The value and risk of enrichment arise from the same fact: it adds information that was not visible in the original application alone.
Why a screening company uses more than a name
The complaint alleges that RentGrow obtained address-history and name information from LexisNexis’s Accurint database. It says RentGrow used that information to locate additional addresses and supplement missing middle names or initials for applicants. The alleged purpose was practical. Public records may contain limited identifiers, so an address history or a fuller name can help a vendor decide which records to search and which person a record may describe.
This is different from saying that Accurint proved the identity of an applicant. An identifier can narrow a search without resolving it. An address may have been shared by several people. A middle name may be common or recorded differently. A historical address may connect an applicant to a jurisdiction where a case was filed, but it does not by itself establish that the applicant was the person in that case. The matching question is therefore cumulative: how do the available identifiers fit together, and what alternatives remain plausible?
The complaint alleges that RentGrow provided the Accurint information to third-party vendors. Those vendors allegedly combined it with the applicant’s application information and credit-report information, searched for criminal and eviction records, and returned records for inclusion in a Tenant Screening Report. The alleged process makes the report a chain of inferences. An address helps identify a jurisdiction or search path; a name helps compare a candidate record; other information may support or weaken the connection. The retained materials do not disclose the exact matching formula, confidence threshold, or internal software used by RentGrow, so those details should not be invented.
The distinction between a search key and an identity proof becomes especially important when information moves through more than one organization. RentGrow may use one data source to expand the search, a vendor may use the expanded identifiers to retrieve candidates, and RentGrow may then receive a record whose original search rationale is not obvious from the returned text. Agreement among systems can show that they repeated the same association; it does not automatically show that the association is correct. A reliable match requires enough independent information and context to separate the applicant from other people who share a name, an address, or a similar history.
The risk is also asymmetric.