What a panel actually stores about your device
Every time you open a survey panel, whether it is a browser tab or a phone app, the panel is quietly logging a pile of information about the device you are using. That starts before the first question. Most of that data has nothing to do with the survey itself. It exists to answer two questions the panel cares about far more than your opinions: are you a real, unique person, and which quotas can we slot you into. Understanding what gets collected explains a lot about why you get screened out, why your account sometimes gets flagged, and why the same person on two different devices can get wildly different invite volumes.
The IP address is the anchor
The first thing any panel sees is your IP address. It does more work than people assume. Panels use it to resolve a rough geolocation, usually down to city or postal region depending on your ISP, and that location gets checked against whatever you entered as your address during signup. If the two do not roughly match, you either get excluded from location-based studies or your account gets a mismatch flag that a fraud model will weigh later.
IP also carries a reputation. Data brokers and panels alike maintain lists of IP ranges associated with data centers, VPN exit nodes, and mobile carrier NAT pools. Residential IPs from a home ISP score as “clean.” Anything that looks like a hosting provider or a known VPN range gets treated with suspicion, because that is the exact signature of someone running automated accounts. This is also why switching networks a lot, like connecting from a different city’s cafe wifi every few days, can quietly reduce the number of invites you get even without anything ever going wrong on your end. No one is accusing you of anything. The system weights consistency, and inconsistency lowers the weight.
Browser and device fingerprinting
Beyond the IP, your browser exposes a fingerprint: user agent string, screen resolution, installed fonts, timezone, language setting, whether cookies and local storage are enabled, GPU rendering quirks, and dozens of smaller signals. None of these alone identifies you, but combined they narrow a device down to a small pool. Sometimes a pool of one. This is standard web fingerprinting technology, the same kind used across advertising and fraud prevention generally, not something panels invented.
Panels use this fingerprint for two things. First, deduplication: if the same fingerprint shows up under two different account emails, that is a strong signal of one person running multiple accounts, which most panels’ terms explicitly prohibit. Second, consistency checking: if your fingerprint reports one timezone but your stated location is somewhere else entirely, or if your browser locale is set to a language that does not match your country, that mismatch gets logged. You can see your own fingerprint and how unique it is using free tools built for exactly this, like amiunique.org or whatismybrowser.com. It is worth doing once, purely so you understand what the panel is actually looking at.
Cookies and local storage do the remembering
Fingerprinting identifies a device in the moment; cookies and local storage let a panel recognize it again later without re-fingerprinting from scratch. A panel typically drops a first-party cookie plus, in many cases, a tracking pixel or script from a third-party fraud vendor. Those tools remember your device across sessions. Sometimes they remember it across different panels too, when those panels share the same anti-fraud vendor, which is more common than most respondents realize. A handful of fraud-prevention companies supply the backend for a large share of the panel industry, so your “clean” or “flagged” status is not always siloed to one company’s database.
Clearing cookies does not erase you. The fingerprint and IP history are still there on the vendor’s side, tied together the next time you log back in. This matters if you are trying to figure out why a fresh account on the same laptop got flagged immediately: the device history followed you.
Mobile apps collect more
If you take surveys through a mobile app rather than a browser, the data footprint gets bigger. Apps can request an advertising ID (IDFA on iOS, GAID on Android), which is a persistent identifier meant for ad targeting but reused heavily for fraud detection. Some apps also request GPS location rather than relying on IP-based geolocation, which is far more precise and much harder to have drift from your stated address. Depending on permissions granted, an app can also see device model, OS version, and installed app list signals through SDK-level checks, which feed into device-reputation scoring the same way IP ranges do.
None of this is a secret conspiracy. It is written, in dry legal language, into the privacy policy of basically every panel you have ever signed up for. Reading one of those policies once is more informative than any forum thread about “how panels really work,” because it tells you, in the panel’s own words, exactly what categories of data they collect and which third parties they share it with.
How this actually affects your qualification rate
Here is the part that connects device data to money. Panels build screener logic on top of this data before you ever see a question. If your device profile suggests you are in a location, income bracket, or demographic that a client is not buying responses from, you get screened out immediately, sometimes within seconds. It costs you nothing. It pays you nothing either. If your device profile looks inconsistent, whether that is a VPN IP paired with a home-country profile, or a fingerprint that has shown up under a different account, you may get routed into fewer studies overall or your account gets held for manual review before payouts process.
This is also why running surveys through a work laptop shared with other family members, or through a shared office network with many other respondents on it, tends to reduce invite volume over time. The device and IP have a mixed history now, and mixed history reads as risk to a scoring model even when every individual using it is legitimate.
What you can actually check yourself
You cannot see a panel’s internal fraud score, and no honest source will tell you it exists to be gamed. But you can check its inputs. Confirm your browser’s reported timezone and language match your actual location. Check whether your IP resolves to your real city using any IP lookup tool, since a mismatch there is often caused by a VPN, a work proxy, or a mobile carrier’s NAT gateway rather than anything you did on purpose. Keep your account’s stated address current if you move. None of this requires special software; it just requires knowing what the panel is looking at and making sure your own setup is not accidentally sending contradictory signals.
The honest summary
Panels collect device data for the same reason any ad-supported or client-billed business does: to verify who is real, prevent duplicate payouts, and slot people into quotas efficiently. Punishing you is beside the point, and so is your convenience. That indifference explains a lot of the screen-out frustration that gets blamed on bad luck. Survey income is inconsistent by nature, and no amount of device tuning changes the fact that most panels pay modestly for the time involved. Knowing what your device reports just means fewer confusing rejections and a clearer sense of why your account behaves the way it does.
For more breakdowns of how panels actually set pay, screen-outs, and account rules, head back to the Survey Farm home page.