Mosaic is a privacy-engineered marketplace for location data. App publishers monetize signals through an SDK that strips PII before egress. Brands and analysts consume the result — pre-aggregated, auditable, risk-free for everyone in the chain.
Drop our SDK into your app. We hash identifiers on-device, aggregate inside our perimeter, and pay you on the cleared revenue. Your users keep their privacy. Your team keeps its weekends.
Query foot traffic, audience reach, and competitive share through one API. Every result is pre-aggregated and ships with panel composition and confidence intervals — so legal signs off and analysts trust the answer.
The SDK collects opt-in location events inside the publisher's app. Identifiers are k-hashed on-device. No raw device IDs ever leave the phone.
Hashed events land in Mosaic. We bucket them into H3 hex cells, audience segments, and category counts before anything is queryable.
Identifier graphs are dropped, opt-out is propagated within 24h, and every aggregate carries panel composition and a confidence interval.
Buyers query the result through SDK, REST, or SQL. The smallest unit they ever receive is a cell, segment, or count — never a path, never a person.
Hourly visit counts, dwell time, and trade-area shape for any place or chain in the country. Refresh on the hour, not next quarter.
Most location SDKs collect first, ask later. Mosaic inverts that: identifiers are hashed before they leave the device, and only aggregates are eligible for payout. You ship one library; we handle the legal posture.
ATT-compliant prompt, GDPR + CCPA notice, and a user-facing audit screen — themed to your app, not a generic modal.
k-anonymous hashing happens before any payload is composed. No raw MAID or location string ever crosses the wire.
Per-aggregate accounting. You can reconcile your statement against the rolled-up cells we sold.
Open changelog, signed releases, and a public threat model. We document what we drop, not just what we keep.
Most location feeds were built on raw device records, then patched with policy. Mosaic was built the other way around: we ship aggregates because that's all we ever held — on either side of the marketplace.
“The first location vendor we've onboarded without a 90-day legal review. The aggregated pipeline did the talking.”
“We replaced two SDKs with Mosaic and our App Review escalations dropped to zero. Revenue went up.”
“Hourly trade-area refresh changed how we open stores. We see lift before the second weekend, not the next quarter.”
Suppliers integrate the publisher SDK to capture opt-in signals. Buyers hit the same model from a typed SDK, REST, or their warehouse. Every response carries panel composition and a confidence interval — so you can show your work.
// Buyer: foot traffic for a trade area, last 7 days
import { Mosaic } from "@mosaic/sdk";
const mosaic = new Mosaic({ apiKey: process.env.MOSAIC_KEY });
const result = await mosaic.visits.aggregate({
place: "poi_8a3f9c",
window: "7d",
grain: "hour",
grid: { h3: 10 },
});
return result.cells; // [{ h3, visits, ci_low, ci_high }]We can't sell what we never had. The pipeline drops identifiers on the supplier side, aggregates inside our perimeter, and ships counts to the buyer — never paths.
Read the privacy whitepaperTell us whether you're sourcing the data or using it. We'll route you to the right team and the smallest, cleanest version of the answer.