Privacy should match the product.

Location

Pulse asks for your location only when you choose a location action: Use my location or Update my location in Explore, the Nearest first sort when Pulse doesn’t have your location yet, or the location button on a map. It never asks when you open the app or the page. On the web, your browser shows its own permission prompt and Pulse reads your position once for that action. On iPhone, Pulse asks for permission only while you use the app, then requests one position, accurate to about 100 meters.

Your position is used to measure how far events are from you, to list events nearest first, and to center the map on where you are. It stays in memory until you close the page or the app, and it is not saved. Pulse never sends your location to its servers or includes it in analytics. If you don’t share it, distances are measured from the center of the city you’re browsing.

When the map shows the area around you, map images for that area load from the map provider: OpenFreeMap on the web and Apple Maps on iPhone.

Private interests

Marking an event Interested stores a copy of that event’s details only in this browser or on this iPhone. Pulse does not upload, publish, or aggregate the events you mark. Removing an interest removes its copy; deleting the app or clearing browser data removes all interests kept there.

Private plan links

A plan link can contain an optional note after the URL’s # symbol. Web browsers and the iPhone app do not send that part to Pulse or Vercel as part of the page request. The iPhone app holds a draft note only while you compose and share the link. Anyone you forward the complete link to can read the note. Pulse does not store or count invite replies.

iPhone event data

The iPhone app includes a reviewed event snapshot for each city so it can open without a network connection. It may refresh the same public event feed from trypulse.city and keep the last version that passes Pulse’s identity, schedule, geography, and source checks. This cache contains public event facts and their sources, not your interests, plan notes, replies, contacts, or location. Deleting the app removes the cached feed and local interests.

Optional analytics

After you choose Allow analytics, Pulse can send a sanitized page path and a small set of interaction types to its own aggregate endpoint hosted on Cloudflare Workers. The endpoint stores only a daily count for each kind of interaction. It does not set an analytics cookie or store a user ID, IP address, browser agent, raw event history, selected event IDs, interests, plan notes, replies, contacts, or location.

Choosing No thanks, or turning on Global Privacy Control, keeps the endpoint from receiving analytics. As with any web host, the edge provider has to process connection information to deliver a request; Pulse does not add that information to its analytics database. You can reset your choice below and decide again on your next visit.

Infrastructure

The public site is hosted by Vercel, which receives the ordinary request information needed to deliver and protect the site. Events link to independent source websites with their own privacy practices.

Links to venue websites

When you open a venue’s or organizer’s own website from Pulse, the link says the visit came from Pulse, so they can see their listing being used. It says nothing about who you are. Links to ticket sellers, event calendars, and social profiles open exactly as they were published.

How event information is handled

Read how Pulse checks events, labels human picks, handles freshness, and describes incomplete coverage.