Who's staying
where?
Heerish is a shared map for the days your attendees are in town. They open a link and add their hotel and dates. Then everyone can see who's around and who wants dinner. No app, no attendee accounts, and it's all deleted two weeks after the event.
Free up to 50 attendees. Above that you pay once per event, never monthly.
One link does the work of three tools.
You've probably run this on a WhatsApp group, a spreadsheet and a Google My Map. It holds up until message 400. Then nobody can find the hotel list, and a year later the sheet still has forty phone numbers in it.
The map
Hotels with faces on them. Lodging is always a named place: a hotel, a district, or just the city. Never a coordinate, and everyone at one hotel shows up at the same spot.
You decide how precise it may get. The default is city, and hotel level asks you to read a warning first.
The people
Everyone's card in one list. See who's in town already and who lands tomorrow.
The meetups
Anyone can propose one. Others RSVP with a tap and add it to their calendar.
Opens from a link
Attendees tap it in your newsletter or the invite email. It runs in the phone browser, so there is nothing to install.
A small tool on purpose
Heerish has no ticketing, agenda, sponsors, badges or matchmaking. Your event platform handles those. We cover the days people are in town, and the card is short: name, photo, group, dates, where you're staying. A phone number if you want.
- WhatsApp group
- Hotel spreadsheet
- Google My Map
Gone 14 days after the last day.
Every event has a purge date. When it passes, the cards, photos, meetups and roster leave our live systems within 24 hours and our backups within 30 days. You can shorten the window. In the EU and UK you can stretch it to 90 days and no further.
- Day 0 The event ends
- Day 14 Purge date
- Within 24 hours Gone from live systems
- Within 30 days Gone from backups
No attendee accounts
People get in with the event passphrase, an email link, or Google, LinkedIn or Apple. You choose per event, and nobody creates a password.
Hide and block are silent
Hiding your hotel looks the same as never sharing it. A block is instant and mutual, and nobody is notified. There is no "nearby" sort and no distance filter, and there won't be.
EU events are stored in the EU
Each event picks a region when it's created and keeps it. EU and UK events live in an EU-jurisdiction database with their photos beside them.
No trackers on attendee pages
No third-party scripts or analytics where attendees are. We count cards per event and nothing about individuals.
Pay per event.
One-off, never monthly. The organiser pays and attendees never see a price. Moderation, privacy controls, report and block are in every tier, the free one included.
Unlimited events for a year, up to 500 attendees each. For schools and programmes that run residencies all year.
Create an eventAsked before signing up.
Do attendees need an app or an account?
No. They open the event link in a phone browser and add a card. Depending on what you choose for the event, they get in with a shared passphrase, an email link, or a Google, LinkedIn or Apple sign-in. Nobody sets a password.
What happens to the data after the event?
It's deleted. The default is 14 days after the last day of the event, or 30 for events in the US region. Once the purge date passes, everything is gone from live systems within 24 hours and from backups within 30 days.
How exact is the lodging shown on the map?
A named hotel at most, and only if you allow it. You pick a ceiling per event: city, district or hotel. The default is city. Coordinates and distances between people are never shown or sent.
Does Heerish replace our event platform?
No. It has no ticketing, agenda, sponsors or badges. It sits next to whatever you use for those and covers the days people are in town.
What does it cost?
Free up to 50 attendees. €79 up to 150, €149 up to 300 and €249 up to 500, paid once per event. €990 a year covers unlimited events of up to 500 people each.
What if our event is bigger than 500?
Run one Heerish per track, cohort or side event, each with its own link, map and up to 500 people. It also keeps every map to people who have a reason to find each other. The annual plan covers as many of them as you need. If that doesn't fit your event, write to heerish@thatukrainianguy.rocks.
Who is responsible for attendee data?
You are the controller and Heerish is your processor. We store attendee data on your instructions, we don't analyse individuals, and we never email your attendees about Heerish.
Notes from the build.
How we build Heerish, and what we're learning about getting a few hundred travelling people to find each other.