Where the family's location data goes — the documented record

Begin with the reporting itself, because the facts need no embellishment. In December 2021, The Markup — a nonprofit newsroom specializing in technology accountability — published an investigation with a headline that did all the work: the popular family-safety app Life360 was selling precise location data on its tens of millions of users, a customer base heavy with children and families, to roughly a dozen data brokers. The location industry sources quoted described the company as one of the largest raw location-data suppliers they had seen. In April 2022, following the investigation, U.S. regulators questioned the company's practices. In 2023, a lawsuit followed, alleging among other things that the sold data could reveal visits to sensitive places — naming, in the complaint's categories, places of religious worship.

Life360 announced changes to its data practices after the reporting. The record above still happened, is still documented, and is still the single most important context for any family weighing what a location product knows. This article lays out that record, what the broker economy actually does with such data, and why this community — of all communities — should treat "where does the data go?" as the first question about any family map, including ours.

What a broker can reconstruct from "anonymous" dots

The industry's standard reassurance is that sold location data is de-identified — no names, just device IDs and coordinates. The reassurance dissolves on contact with arithmetic. A device that sleeps at one address every night and spends weekday mornings at one office is its owner; researchers have shown repeatedly that a handful of location points uniquely identifies most individuals. Once identified, the trail is a biography: the clinic visited, the lawyer consulted, the shul davened in.

Now run that reconstruction on a frum household's week and feel the temperature change. The morning minyan, daily, same address. The mikvah — with its exquisitely private timing. The yeshiva gate at seder times; the seminary dorm an ocean away; the shadchan's block on a Tuesday night; the beis din's office. A location trail that flags "places of religious worship" as a category is not flagging an abstraction here — it is a machine-readable map of a family's ruchniyus, its simchas, its tzaros, and its children's daily routes, held by companies whose entire business is selling the map onward. The general public read The Markup's investigation as a privacy story. This community should read it as a kashrus question about data: who certified where this goes?

The uncomfortable structure of "free"

The deeper lesson is structural, and it outlasts any one company. Family-safety apps sell peace of mind to the family — but a free tier serving tens of millions has to be paid for somehow, and location data is among the most monetizable exhaust a phone produces. When the product's buyer and the data's buyer are different parties, the family is not fully the customer; it is partly the inventory. That is not cynicism, it is the documented business model of the location-data economy — and it means "does the app work?" and "who does the app work for?" are separate questions, and the second one is the one a family cannot inspect from the outside.

Which is exactly why the community's oldest instinct applies. This is a society that does not publish its guest lists, that keeps simchas and struggles inside the family, that built an entire etiquette around what is and is not spoken of. That instinct is not nostalgia; it is a standard — and by that standard, a family-location product funded by reselling family locations is not a product with a privacy flaw. It is a category failure.

“The general public read it as a privacy story. Here, it is a kashrus question about data: who certified where this goes?”

kolbo.life

What "private by design" means, and how to audit for it

Against that record, read the one line the kolbo.life homepage gives KolBo Safe's data posture: "Private by design — family data stays in the family, period." Three words carry the weight: by design. Not private by policy — policies change with ownership and quarters. Not private by toggle — toggles default the other way. By design: an architectural commitment, stated as identity, by a platform whose reason to exist is that this community's standards were worth building for rather than around. It sits inside a suite whose backbone the homepage describes the same way — "KolBo Cloud is the proprietary backbone that stores it all, protected under our own security layer" (the cloud's own story is here) — infrastructure owned by the same hands that build the apps, answerable to the families it serves.

And because this library holds itself to its own rules: that homepage sentence is the claim we can quote, and we quote it exactly — this article will not invent retention windows or server diagrams the homepage doesn't state. What we can give you is the audit any family should run on any location product, ours included:

1. Find the data sentence. Not the marketing page — the stated position. If a product cannot say in one sentence where family data goes, that is the answer.
2. Ask who else is a customer. A free product with tens of millions of users is being paid for by someone. Identify them.
3. Check the record, not the promises. Search the product's name plus "data" in a serious newsroom. The Markup's Life360 series is the model of what you are looking for.
4. Prefer architecture to policy. "We promise not to" loses to "the system is built so it doesn't." By design beats by pledge.

The fuller story of what a family map built on that standard looks like — the live map, the arrival alerts named in this community's own vocabulary — is the KolBo Safe pillar, and the search-term version is the kosher Life360 alternative.

Frequently asked questions