UNDER THE HOOD
How Where’s Busy works.
One physical signal — the door clicker — feeds two surfaces: the operator dashboard and the consumer app. Nothing in between collects you.
THE DATA LAYER
One signal, two surfaces.
Door clicker
PHYSICAL
Aggregator
UK SERVERS · GDPR
VENUE
Dashboard
EXPLORER
App
WHAT WE CAPTURE
Every signal, sourced and labelled.
Door count (in/out)
Live from each venue’s clicker
Live capacity %
Door count divided by registered capacity
Crowd mix
Observed by door staff at the point of entry
Vibe / energy
Aggregated anonymous check-ins
Average dwell time
Estimated from in/out cadence over the night
Demand forecast
Modelled from historical patterns + weather + day-of-week
Neighbourhood benchmark
Aggregated across opted-in venues in a postcode area
WHAT WE DON’T CAPTURE
The list of things we’re uninterested in.
- × Faces — no cameras, no biometric pipeline
- × Names, emails, phone numbers from explorers
- × Locations — phones never share GPS with us
- × Demographics: age, ethnicity, income
- × Re-identification data of any kind
- × Re-sale of anything to advertisers
WHERE THE DATA LIVES
UK servers. GDPR-compliant. Deleted on request.
All data sits on UK-region infrastructure. We use AWS London for primary storage and a separate UK-only analytics provider.
Aggregate data has no individual identifier — there’s nothing for us to delete because there was nothing personal in the first place.
Operators can export their venue data and pull their account at any time during the pilot, no notice required.
WHO CAN SEE WHAT
-
Explorer (consumer app)
Aggregate signals: busy / steady / quiet, vibe band, neighbourhood activity.
-
Venue operator
Their venue’s raw counts, trend data, forecasts, neighbourhood benchmarks (anonymised).
-
Where’s Busy team
Aggregate health metrics. Never explorer behaviour. Operator data only with explicit support consent.