Since 2018
Privacy-safe enterprise data
VOSB & SDVOSB
U.S. Veteran-Owned, Service-Disabled
SCC Transfers
EU/UK/CH per privacy policy
GDPR · CCPA · CPRA
Consent-first data sourcing
Core products
Most location programs start with POI + geofencing quality and then layer in a mobility panel for visitation and origin/destination reads.
Post‑FTC diligence
- Sensitive categories: confirm exclusions and enforcement posture for healthcare/worship/schools.
- Panel sizing: request DUAs by geo (DMA/polygon) and refresh cadence.
- POI fidelity: polygons vs centroids, same-address disambiguation, brand hierarchy.
Related solutions
Key POI resources
Mobility resources
Try before you buy
Use the free tools to sanity-check POI coverage and the shape of the signal before requesting a scoped sample.
What “good” looks like (POI + mobility)
Location programs are easiest to buy when you separate POI truth (what the place is) from mobility signal (who visited, when, and how often). This section is the checklist buyers use to avoid false visits, panel drift, and compliance surprises.
POI requirements
- Polygons: tenant-level where it matters (urban/malls/mixed-use).
- Brand hierarchy: franchise/DBA mapping that rolls up correctly.
- NAICS/category tags: consistent taxonomy for reproducible analytics.
Mobility panel questions
- DUA by geo: monthly actives in your exact DMA/polygon.
- Accuracy floors: filters for low-accuracy pings and spoofing artifacts.
- Visit rules: dwell thresholds and venue-category handling.
Post‑FTC diligence
- Explicit sensitive-category exclusions (healthcare/worship/schools).
- Written permitted-use boundaries and downstream sharing rules.
- Opt-out/delete propagation expectations for derived datasets.
Related buying guides
Keep procurement citations clean by using the right hub for the question you’re answering.
Vendor comparisons
Use these pages to anchor the evaluation to panel density, POI quality, and post-FTC compliance artifacts.
Frequently asked questions about location intelligence procurement
What is the difference between POI data and a mobility panel?
POI data defines place truth: polygons, brands, NAICS, open/close metadata. Mobility panels measure visitation and movement with privacy-safe aggregation. Geofencing and foot-traffic analytics usually require both; POI-only or panel-only evaluations often miss fidelity issues.
What polygon quality questions should procurement ask?
Request examples in dense retail strips, not just record counts. Ask about centroid fallbacks, same-address disambiguation, brand hierarchy, and how often boundaries change. The /poi-data page and point-of-interest data guide list concrete tests.
How does post-FTC location enforcement affect buyers?
Procurement should confirm sensitive-location exclusions, permitted use, consent chains, retention, and deletion SLAs. GSDSI documents governance in sourcing methodology and the FTC location enforcement resource linked from this hub.
How do I validate panel density for my markets?
Ask for daily unique devices by geography, polygon, and time window with minimum-cohort floors disclosed. Use /free-tools to request a sized coverage or foot-traffic sample, then scope a production sample for your exact polygons.
Are healthcare facilities or schools included in mobility feeds?
Sensitive location categories are excluded from GSDSI mobility products licensed to commercial buyers. Confirm category lists and any state-specific exclusions in the order form before blending POI and panel data.
What is the fastest path to evaluate location intelligence?
Start with /poi-data and Global Mobility Location Data product pages, request a chain- or MSA-scoped sample through /free-tools. The location intelligence resources cluster covers pricing and provider comparison criteria.
