People search is not a background check

If the output would be used like a consumer report, stop. That is the whole method. Public-web people search — a name, a confirm step, a sourced page — is conversation prep. A background check is a regulated product sold for eligibility decisions. They share a noun ("the person") and almost nothing else. Mixing them is how teams create legal exposure and still walk into the wrong meeting.

OneSearch is not a consumer reporting agency (CRA). It is not FCRA-compliant. It does not produce consumer reports. This page is a working classification method, not legal advice. For the product policy, read FCRA and legal use. If your facts are specific, talk to qualified counsel. Do not treat a search box as a substitute.

The line in one sentence

Use public-web research to prepare a conversation. Use a CRA — with disclosure, authorization, and adverse-action process where the law requires it — to decide whether someone is eligible to be hired, housed, lent to, or insured. If you cannot say which of those two jobs you are doing, you are not ready to open a tab.

The Fair Credit Reporting Act (FCRA) is a U.S. statute that regulates consumer reporting agencies and the use of consumer reports. It is not a vibe and it is not optional because the data "was already on Google." A consumer report is defined by who assembled it and what it is used for, not by whether a fact also appears on a public page. General information is on the FTC Fair Credit Reporting Act page and the CFPB credit reports overview. This guide will not restate the statute as if it were a product FAQ.

What a consumer report is for

A CRA sells a product designed to be used in eligibility decisions: employment screening, tenant screening, credit underwriting, insurance underwriting, and related uses that the statute covers. That product comes with process — permissible purpose, notices, accuracy duties, dispute rights, adverse-action steps. You buy it because the decision is regulated, not because you wanted a richer biography.

What belongs in that lane: criminal-record products sold for hiring or housing; credit files; tenant reports; driving records used as a screen; any packet your HR or risk team treats as the official file that can produce a no. Do not copy those categories out of a search engine into the same file as if you had bought a screen. If you need the category, you need the vendor and the process.

People directories that sell contact attributes, age, relatives, and address history are a different failure mode: they invite you to treat aggregator fields as facts and then quietly use them in a decision. Compare the jobs in OneSearch vs people directories. Using that output to deny a job, a lease, credit, or insurance as if it were a screen is still the wrong lane. When in doubt, ask counsel — not this page.

What public-web research is for

Public-web research answers: who is this person among the public identities that share the name, what have they said or shipped on open pages, and what should I ask in the room? The output is a sourced brief you can open. Typical uses: meeting preparation, outreach tone, quoting a public talk, booking a source, checking whether a speaker bio matches the person on the invite. Recruiting outreach sits here only when it is conversation prep — not a hire/no-hire file. See people search for recruiting.

The method is the same as research someone before a meeting: inventory what you already have, confirm the person, extract a few dated facts with URLs, write a short note, stop. You do not collect criminal, credit, tenant, or insurance data. You do not bypass logins. You do not put the note into an official eligibility file. If the web is quiet, the brief stays thin. Silence is not a negative screen. It is the absence of public pages.

Confirmation is still a gate. A background-check vendor identifies a person with identifiers you are authorized to collect. A public-web brief identifies a person with a unique public artifact — a talk, a team page, a byline. If two Alex Chens still fit, you do not merge them, and you do not treat the collision as "no record found." That sentence is a screening sentence. You are not screening. You are unconfirmed. The method for the collision is confirm the right person.

The decision tree

Ask one question before you type the name: will this inform hiring, tenant, credit, or insurance eligibility? If yes, stop. Use a compliant screening process. If no — conversation prep only — you may read public pages, confirm the person, and keep citations. You still do not paste an unverified summary into an official file as if it were a screen. Use the tree; it is a teaching control, not a legal determination.

Two follow-up questions catch the cases people lie to themselves about. If the public pages are unflattering, will that change a regulated yes/no? If the note can travel into a hiring packet, a landlord folder, or an underwriting file, it is not a meeting brief anymore. Delete the workflow. Use the CRA. Do the notices.

"We only use it as one signal" is not a safe middle. Either the output is being used like a consumer report or it is not. If you need a signal of that kind, you need a CRA. Public pages can inform how you talk to someone you have already decided to meet. They cannot become the rejection memo.

Hiring, tenant, credit, insurance

These four words are the red cell on the boundary diagram. They are not metaphors.

• Hiring and promotion.Offer, reject, or advance someone because of what a people-search brief said — including "the web was quiet" or "we found a lookalike with a problem" — is an eligibility use. Recruiter prep before a coffee chat is not, as long as the note cannot become the reason. The moment you score candidates from public-web notes, you have left prep.
• Tenant and rental.Deciding who gets a lease from a search is tenant screening. Looking up a property manager you are about to meet, to ask about a public talk they gave on housing policy, is prep. Looking up an applicant to see if you "get a bad feeling" is a screen you are not authorized to invent.
• Credit and lending. Public-web research does not tell you whether someone pays their debts. Do not pretend a thin LinkedIn page is a credit signal. This guide will not help you build a collection process.
• Insurance. Underwriting from a people-search brief is the red cell. Reading a public lecture by an actuary you are meeting is the green cell.

Other uses that are out of scope even when they are not those four words: harassment, stalking, discrimination, and any attempt to get non-public records through a search box. If you need a criminal history for a lawful purpose, you use the process that purpose requires. You do not Google harder.

Worked example: Alex Chen

Two versions of the same name. Only one is legal-use safe as public-web research.

Prep (green).You are a recruiter. Priya referred "Alex Chen, the SF engineer who spoke on latency last year." You have a coffee chat booked. You will not decide an offer from this note. You run the meeting method: confirm the SF engineer against the NYC quant and the Austin founder, open the talk, write one question about p99. The note lives in your personal prep doc. It is not copied into the ATS as a "screen." If you later make an offer, your company runs its CRA process — disclosure, authorization, the vendor you already have. The brief does not go in that packet. Outcome: you do not quote the Austin podcast. You ask a question the SF engineer can recognize as their work.

Eligibility (red).Same referral. No coffee chat. A hiring manager says "just look them up and tell me if there's anything concerning." You search, you find a news mention of a different Alex Chen, you write "possible issue — see article" in the req, and the manager kills the pipeline. That is a screening decision built on a collision and a non-CRA product. You have briefed the wrong person and used the output like a consumer report. Stop. Do not finish the note. Do not send the article. Say: we do not use public-web search as a screen; if we need a screen, we use the CRA; if we want a conversation, we book the conversation and confirm the person first.

The failure mode inside the green version: you confirm the right Alex, then paste the brief into the official candidate file "for context." Context that can produce a no is eligibility. Keep prep on your side of the table.

Worked example: Maria Garcia

You are a founder. Two meetings land in the same week. Both involve a Maria Garcia. The name is high-collision. The statute does not care that you are a small company.

Prep (green). Maria Garcia is a possible advisor. Intro email: former VP of operations at a Miami logistics company, trade podcast last quarter on port delays. You confirm her against a journalist in Madrid and a school-board member in Texas using the podcast show notes and a conference badge photo. You write a six-line note and one question about warehouse buffer. You will not run a background check yourself because she might later join a board. If a board seat later requires a screen, that is a later process with a CRA and counsel. Today is a conversation. Thin is fine. See the meeting method if you want the twelve-minute clock.

Eligibility (red).A different Maria Garcia applied to rent the in-law unit behind your house. You type her name into a people-search product or Google, you skim a directory for "relatives and age," you decide she "seems messy," and you tell her the unit is taken. That is tenant screening you invented. OneSearch must not be used for it. Google must not be used for it as if it were a report. A people directory is not a CRA. If you screen tenants, you use a tenant-screening process that is actually built for that decision, and you follow the notices that process requires. This page will not walk you through that process. It will only tell you to get out of the search box.

A third version people miss: you reuse the advisor note when a candidate named Maria Garcia applies for an ops role six months later. The candidate is a different person. Reusing a brief across a name is how you screen without a CRA. Confirm again or do not use the note.

What teams get wrong

• "It's public, so we can use it for anything." Public is a source constraint, not a use license. The FCRA cares about use. Your employment counsel cares about use. A public talk is still a public talk if you quote it in a meeting. It is not a license to reject a candidate.
• "We're just being thorough." Thoroughness in the red cell is a CRA plus process. Thoroughness in the green cell is one unique artifact and three dated URLs. Extra tabs past that are usually a hunt for something you should not be deciding from.
• "The ATS needs a dump." A sourced meeting note is not improved by being pasted into a system of record. If a field does not have a compliant purpose, it does not get the brief.
• "Quiet web means they're hiding." No. Quiet web means few indexed pages. Engineers on dark profiles, operators in industries that do not blog, people who changed names — they are not a negative report. Treat silence as silence.
• Merging lookalikes into a risk story.The NYC Alex Chen's faculty-page controversy is not a fact about the SF engineer. A collision is not a character signal. Confirm or stop.
• Using a directory when you wanted a brief.Age, relatives, and a phone are not answers to "what should I ask in the room?" They are answers to a question you should not be asking in this lane.

Keep citations attached

The practical control that keeps prep from rotting into a screen is the URL. Every line you might speak or share has to carry the original page and a date. If you cannot open the page, the line dies. If the page is a lookalike, the line dies. If someone asks "how do you know?" you send the link, not a paraphrase. Paraphrases are how a talk about latency becomes "they struggle with reliability" in a hiring Slack.

Do not strip sources when you paste into Slack. Do not summarize a brief as "seems solid" or "seems off." Those sentences have no URL and they travel like a report. Send the confirm line, the talk, and the question. If they want a yes/no on eligibility, that is not this document.

Verification is its own method when a claim has to hold up in the room. Open the page. Check the date. Check the name collision. See verify a people-research claim if you are about to speak a fact you have not opened.

What OneSearch is and is not

OneSearch is a private public-web people brief: name, confirm, sourced page, follow-ups. It is not a background check, not a CRA, not FCRA-compliant, and not a contact database. It does not buy consumer files or notify the subject. If a fact is not on an open page, it will not appear. Thin beats invented.

Confirm first. Cite everything. Stay in prep. When the decision is regulated, leave. The same boundary is in FCRA and legal use and the terms. To request removal, use opt out.

OneSearch will not certify that your workflow is lawful. If you need a written opinion, that is counsel. If you need a screen, that is a CRA. If you need to walk into a meeting without inventing the first five minutes, that is this lane.

This is not legal advice

This guide classifies jobs so you do not use the wrong tool. It is not a legal opinion and not a complete statement of the FCRA. Employment, housing, credit, and insurance law vary by jurisdiction and by what you did with the output. The FTC and CFPB pages linked above are starting points, not a substitute for counsel.

If someone asked you to "just make sure they're clean," say no, name the CRA process you do have, and do not open the search. If you have a calendar hold and you want one sourced question, you are in the green cell — confirm the person, keep the URLs, leave eligibility alone.