Privacy
Updated 26 October 2026. This describes what runs today.
localhum is the guide at localhum.app to what is on at a neighbourhood's bars, breweries, galleries and venues, built from what each venue publishes itself. It is run by its founder in San Diego, California. There is no account to create, no advertising and no analytics script. We do not sell personal information and never have.
What localhum keeps about visitors
One cookie. The neighbourhood you last looked at, so the home page opens there. It holds nothing else, lasts a year, and goes when you clear it.
Your searches. The words you search for are sent to our search service to answer them. They are not stored with anything that says who searched.
Server logs. Address, page, time and browser, as any web server records, kept a few days to keep the site running and to limit abuse.
What localhum keeps about people who write to us
When you add a venue, claim a page or report a problem, we keep what you typed: the venue, your email address, your name if you gave it, and your note. We use it only to reply and to act on the request, and keep it while the venue is listed so a later request about it can be checked against it. A scrambled form of your network address is kept for an hour, to limit repeat submissions.
What localhum keeps about venues
What the venue has published about what is on: its website, its flyers and its public posts, read again every few days, and attributed to the venue. Nothing about any private person.
Not running today. When it is turned on, this is what it will do, and this page will say so.
Public posts. Where a venue announces what is on through a public Instagram professional account, localhum reads that account's public posts through Instagram's API, the way it reads the venue's website. It keeps the caption, image address, link and date of posts about what is on, attributed to the venue. It reads no private account, no followers, no messages and no insights, and never posts to any account.
A connected account. If a venue connects its own Instagram account to localhum, the access token Instagram issues is kept only to read that account's posts. Disconnecting removes the token and everything read through it.
Who processes it for us
Cloudflare hosts the site, its database and its logs, and routes mail to and from hello@localhum.app.
Model providers (OpenAI through Cloudflare's AI Gateway, and models Cloudflare runs) read venue websites and posts to build listings, and read search queries to answer them. They receive the venue's published text and the words searched for, nothing about who searched.
Meta, only for the Instagram section above, once it runs.
None of them may use this data for their own purposes.
Your rights
You can ask what we hold about you or your venue, have it corrected, or have it deleted. Under California law you can also ask whether personal information is sold or shared: it is not.
Deleting your data
Email hello@localhum.app from the address you used with us, or name the venue or Instagram account, and say what you want removed. Within 14 days we delete a request you sent and our replies to it; if you run the venue, stop reading its website or Instagram account and remove its listings; and remove a connected Instagram account's token and everything read through it. You get a reply saying what was removed. We keep only what the law requires us to keep, and say so if that applies.
Changes
When this page changes, its date changes with it. A change in what we keep or who processes it is noted on the home page for a month.
Contact
hello@localhum.app