A new spin on my slow baking location intelligence data union (https://wherelabs.info).
This week I’m thinking about whether it makes sense to provide a location history ‘vault’, designed to let users expose their location history to LLM’s as context.
This week I’m thinking about whether it makes sense to provide a location history ‘vault’, designed to let users expose their location history to LLM’s as context.
Still slowly working away on my location intelligence data union..
I’ve spent a while understanding what sort of market would make it viable. I think it does actually work if you can square: 10K participants per major metro area, revenue of about 2.9M per metro area (so say, 5K monthly recurring with about 50 customers).
At that point you could pay data union participants about $5 a week to share their location data with you.
From talking to some previous data union folks, the major challenges are paying out (my target is much higher than any union managed), and people dropping out over time.
My bet is that these are both solvable things by selling data products rather than just bundles of data, and the data source being very passive.
I’m also interested in the idea that such a union should act more like a union than previous efforts in this space, by actively defending members’ data from brokers.
I’ve been working more on the unit economics of my data union/trust idea (https://wherelabs.info/).
What I’m trying to understand is whether it is viable to pay people ~$5 per week for sharing their location data and demographics based on a 90% share of revenue from sales of data products built on that data. (But without ever selling or exposing individual level data).
I’m still slowly working on a location intelligence data union (https://wherelabs.info) - the idea is people install an app and agree in a very upfront way to have their location tracked over time.
The union monetises this by selling privacy preserving aggregates (think ‘where is everyone in London right now’, or ‘where did people commute from?’), and acts on behalf of union members to stop data brokers selling their location data.
this is a really fascinating idea. I'm reading it as, instead of seeing my individual identity in a location dataset, it will see -DataUnionMember- with no unique identifier? When two members are in the same place at the same time, you don't know which one went in which direction?
The question of who can de-identify or unmask the data is there, but I could see the capability being required for gov, military, and police, and then as a premium service to customers.
I think at least initially the ‘product’ is datasets which don’t show individuals. You could of course build out a future direction which is differentially private.
More or less my initial approach to this is you take a grid, and you show movements/density on that grid. If necessary you coarsen the grid to avoid reidentification of individuals, and ultimately to get a good picture of the population given the biased sample which is the union membership, you need a statistical model on top which also helps from a privacy perspective.
State actors demanding individual location history is definitely an issue. I have a few possible approaches in mind to defend against that.
I built an app for iOS and android recently with a combination of Claude, and cursor. I started off by drawing Claude a picture of what I wanted the app to look like, and telling it to give me the skeleton of an iOS app. (It did a surprisingly good job)
Then I switched to cursor and iterated with it on making it work. Once I had the iOS app running, I got cursor to create an android app that looked and functioned the same.
Super interesting experience - took a couple of days of iterating here and there, helped to have them in git repos for when cursor went too far off piste.
Both apps work, they look pretty much like my original picture.. and the code is absolute trash. I don’t know swift, or particularly kotlin, but the code is horrendous. If you wanted to take them any further, you’d rewrite it from scratch.
This was. Rating combinations of Claude 3.7, 4.0 thinking, Gemini 2.5, and chatgpt 4. (Switching between agents when one was getting stuck.)
Observationally, they all had a much harder time with android and rarely produced anything that didn’t need fixing to build.
Great for rapid prototyping in a stack I don’t know, but 100% tech debt.
I’m playing around with the idea of a location intelligence data union. I work in an adjacent space, and it drives me crazy that there’s all this data about humans moving around that could make a huge positive difference in the world but it doesn’t, because ‘good’ actors won’t touch the shadily data broked data.
I figure the solution is to pay people for their location data, and be up front and transparent about collecting it.
Flowminder | Southampton, UK | Full time/part time | Remote (UK) | Full stack software engineer (frontend bias) | python/react | 52000
Still looking for someone to join my small but wily team of engineers and help me build a new, open source (https://github.com/Flowminder/flowkit-ui and https://github.com/Flowminder/flowkit-ui-backend), data platform for the humanitarian and development sector. (There's lots of other interesting and impactful things to get your teeth into as well, but the role is primarily for this project to start with).
Flowminder is a pioneering, internationally operating non-profit organisation that supports disaster relief and development efforts through several products including the analysis of data gained from mobile phones and household surveys in ethical, privacy and security preserving manners.
We use things like:
React, Linux, Mapbox, Deck.gl, Python, FastAPI, Docker, make, PostgreSQL/MySQL, Terraform, CircleCI, Github, GCP, OpenAPI, Auth0
I can also promise you no stupid interview process - you, me, and a couple of the engineers have a chat about you, us, and things you have worked on and the kind of work you’d do with us. If you’ve got a GitHub/bitbucket/gitlab/whatever that’s great, and we’ll look at it, but not everyone’s work is public, and not everyone develops as a hobby, and those things are entirely reasonable as well!
Flowminder | Southampton, UK | Full time/part time | Remote (UK) | Full stack software engineer (frontend bias) | python/react
I'm looking for someone to join my small but wily team of engineers and help me build a new, open source (https://github.com/Flowminder/flowkit-ui and https://github.com/Flowminder/flowkit-ui-backend), data platform for the humanitarian and development sector. (There's lots of other interesting and impactful things to get your teeth into as well, but the role is primarily for this project to start with).
Flowminder is a pioneering, internationally operating non-profit organisation that supports disaster relief and development efforts through several products including the analysis of data gained from mobile phones and household surveys in privacy and security preserving manners.
We are now looking for an Infrastructure Engineer with excellent communication skills to facilitate and (depending on experience) drive and lead the expansion of our small but worldwide infrastructure and product installations in cooperation with key technology partners.
We use terraform, docker, linux, python, Postgres, airflow, GCP and anything else that gets the job done. Our infrastructure sits in mobile phone operators' data centres in interesting places around the world, and we use it to help people.
We value autonomy, a drive to make stuff better, and being curious.
