This page describes the data flows implemented in the current LivePulse application.
Information handled
Account access is provided by Clerk. LivePulse receives the account identifier and profile information needed to identify you in the application, such as a username or first name when available.
When you send a room message, LivePulse processes the event room identifier, your account identifier, the displayed author name, the message text, and a timestamp.
When you save an event, LivePulse stores the relationship between your account identifier and that event. Event schedules and venue information come from Ticketmaster and are not personal profile data.
How it is used
Account information is used to control access to event rooms, associate messages with their sender, and retrieve your saved events.
Connection information is processed to operate WebSocket chat and calculate the number of active connections in a room. The current frontend does not include a separate analytics or advertising SDK.
Storage and retention
Room messages are stored temporarily in Upstash Redis and are scheduled for deletion one hour after the event ends.
Account-to-event favorites are stored in Neon PostgreSQL. A favorite can be removed from the event desk or event room, and favorite records are removed when their associated event record is deleted.
Authentication sessions and account profile retention are managed through Clerk and its account controls.
Service providers
LivePulse relies on Clerk for authentication, Ticketmaster for event information, Neon for relational data, Upstash for temporary message storage, Vercel for the frontend, and Northflank for backend hosting.
These providers process information as needed to supply their part of the service and apply their own privacy terms to that processing.
Cookies and sessions
Clerk uses cookies or similar browser storage to maintain authentication sessions. LivePulse does not add a separate advertising-cookie or analytics-cookie system in the current frontend.
Your choices
You can browse event listings without signing in. You can remove saved events at any time, avoid sending room messages, and use the account controls provided by Clerk to manage authentication information.
Do not include private or sensitive information in room messages. Messages are shared with other signed-in people who enter the same event room.
Questions about this policy?
Use the project repository’s contact options for a privacy question. Do not post account details, message contents, or other personal information in a public issue.