Information you provide
When you register, we store your name, email address, and a hashed password. Your chosen interests, neighborhoods, budget, follows, saved events, personal RSVP status, place wishlist, and digest preferences support your account and recommendations. If you join the editorial newsletter, we store your email address, optional first name, confirmation state, and delivery history. Contact submissions store the message, listing information, and any name or email you provide.
How it is used
We use this information to operate your account, personalize discovery, send account verification and password reset messages, deliver digests you enable, and review submissions. A personal RSVP records your intention in this guide; it is not sent to an external event host as a reservation.
Service providers & external sites
Hosting and email services process information needed to run the app and deliver messages. Map tiles are requested from external providers, which receive your IP address and requested map area. Ticket sites and source websites have their own policies. Sharing through your device or email opens the service you choose.
Guest discovery
Before you make an account, recent events, places, organizers, and scenes you spend time with can be kept in this browser for up to 30 days to make “more like this” suggestions. This history is not sent to TPTB, is not attached to a guest profile, and can be cleared from the For you page or your browser settings.
Analytics & bot protection
Optional Google Analytics measures browsing when you consent. Discovery events use public catalogue identifiers, scene and placement labels, and the official destination hostname. We exclude titles, searches, account names, email addresses, passwords and reset links. During the bounded member pilot, TPTB also increments daily aggregate counters for coarse steps such as setting an event intention, confirming attendance, or following a series. Those counters contain no member, session, listing, series, IP, location, search, or free-text identifier; operator reports hide totals below five. Newsletter signup records may retain coarse campaign labels such as source, medium, and campaign so we can understand how readers found the list; those labels must not contain personal information. When enabled, Google reCAPTCHA Enterprise assesses public form submissions for abuse using browser and interaction signals. It is separate from optional analytics. See Google’s Privacy Policy and Terms.
Storage & your choices
Account and newsletter records persist in our database; operational logs and backups can also contain technical or account information. Identifier-free daily pilot counters are deleted after 90 days. You can edit preferences, remove saves and follows, disable account digests, unsubscribe from the editorial newsletter, or download a copy of your account data. Account deletion requires your current password and a deliberate confirmation. It removes the live account, sessions, reset tokens, newsletter records, and uploaded avatar. Reports needed to investigate safety concerns remain without the deleted member or profile identifier, and public catalogue suggestions may remain after their contact details and private access tokens are erased. Backups may retain earlier records until they are replaced.
See Cookies for browser storage and Contact for requests. This notice will be updated as the service changes.