The Human Data Illusion: How to Tell Real People From Data That Only Looks Human
Bots, synthetic identities and generated profiles can look human enough that nobody questions them. Why that happens and how to check for a real person.
Key findings
- Data that looks human (a plausible name, a working email, a sensible address) is no longer evidence that a human is behind it.
- Generated and synthetic records are built to pass the checks that only test format and plausibility.
- Look for signals that take time and real life to build: phone tenure, email history, consistent device and location, and believable behaviour.
- Judge records on how well their signals hang together, not on whether each field looks valid on its own.
When does data stop proving there’s a person behind it?
What happens when data looks human enough that we stop questioning whether there’s actually a human behind it?
For years, a record with a sensible name, a valid email address and a real postcode was treated as a person. Most systems still work that way: if every field passes format and plausibility checks, the record is accepted. But producing plausible data is now cheap and easy, which means plausibility on its own has stopped being evidence.
Where do human-looking fake records come from?
- Bots and scripts that fill in forms with realistic details, often drawn from lists of real names and addresses.
- Synthetic identities stitched together from real and invented details, designed to pass identity checks.
- Stolen data from breaches, which is real by definition and so looks entirely human.
- Generated profiles that use realistic names, photos and text to build accounts at scale.
Each of these is built to pass checks that ask “does this look valid?” and almost all of them do.
What does episode 002 cover?
Episode 002, “The Human Data Illusion”, asks what happens when data looks human enough that we stop asking whether there’s actually a human behind it. It is a question that runs through every later episode, from KYC to lead generation to affiliate fraud.
Listen to the episode for the full conversation.
Why do standard checks miss it?
Most validation tests each field on its own. Is the email formatted correctly and deliverable? Is the postcode real? Is the phone number the right length? A generated or stolen record passes each test, because each field, taken alone, is fine.
What generated records struggle with is depth and consistency. Real people accumulate history slowly: a phone number kept for years, an email address used across many services, a home location that matches where they browse from. Fabricated records tend to be shallow, new or inconsistent once you look across fields instead of within them.
How do you check for a real person?
- Check phone tenure and status. A live number that has been in use for years is strong evidence of a real person. A brand-new or unreachable number is weak.
- Check email history. A long-established address with a footprint is very different from one created minutes before sign-up, or from a disposable domain.
- Compare location signals. Does the IP address fit the stated address? Is the connection coming from a data centre, VPN or proxy?
- Watch behaviour. Form fills completed in impossibly short times, identical timings across many sign-ups, or bursts of activity at odd hours point to automation.
- Look for links between records. Many accounts sharing a device, phone, email pattern or IP range usually means one operator, not many people.
- Score the whole record. Combine these signals into a single view. A real person usually has several strong signals that agree. A fake record usually has one or two good-looking fields and little behind them.
What is the bigger lesson?
The lesson of the human data illusion is to stop asking whether data looks right and start asking whether it holds together. That shift, from checking fields to checking evidence, is the thread that runs through the whole series.
See how to tell real people from human-looking data, with an example of the signals that expose a fake sign-up.
Frequently asked questions
What is a synthetic identity?
A synthetic identity is a made-up identity built from a mix of real and invented details, for example a real address combined with a fabricated name and date of birth. Because parts of it are real, it can pass checks that only look for valid, plausible data.
How can you tell if a user is real?
No single field proves it. Look at signals that are hard to fake together: a phone number that is live and has been in use for a long time, an email address with history, a device and location that fit the stated details, and behaviour that looks like a person rather than a script.
Why are fake records getting harder to spot?
Tools for generating realistic names, profiles, text and even images are now widely available, and large amounts of real personal data are available from breaches. Together they make it cheap to produce records that look entirely plausible.