Privacy Policy

Based on the current implementation, PartyUp may process:

• account information and Google authentication information
• username, avatar, and profile information
• guest and session identifiers used for guest Match access
• room creation, participation, presence, queue, host, and attendee information
• room messages, announcements, livestream, and other user-generated content
• Match sessions, Match queue activity, Keep in Touch choices, and mutual Connections
• Following and follower relationships
• room/event location fields such as venue name, latitude, and longitude when provided for location-based rooms
• room analytics events and technical/session information needed to operate the service

PartyUp uses information to operate live rooms, Match, livestreaming, messaging, guest access, Connections, Following, room presence, host tools, and account/session state.

PartyUp also uses information to support safety, moderation, reliability, product debugging, and usage understanding where analytics are implemented.

The current web implementation uses Supabase for database, authentication, storage, realtime, and serverless functions; LiveKit for live audio/video room connectivity; Google authentication for sign-in; and Next.js font loading that fetches Google-hosted font resources at build/runtime depending on environment.

PartyUp does not control those providers' independent privacy practices. If PartyUp is deployed on an external hosting provider, that provider may also process technical information needed to serve the site.

PartyUp may create an anonymous or pseudonymous session identity so a guest can use certain features. Where supported, a guest can later sign in and associate relevant PartyUp history, including eligible Match and Connection history, with an account.

Mutual Keep in Touch can create a persistent PartyUp Connection. The product includes functionality to remove Connections.

Room content, messages, livestream participation, profile information, and room activity may be visible to other people in the relevant room or social context according to how each feature works.

Retention depends on operational, product, safety, and legal needs. The current code does not define a single fixed retention period for all PartyUp data.

Message reports preserve the reported text, display name, account and room identifiers, selected reason, optional reporter context, and moderation result. Safety evidence may be retained after the visible message, room, or associated account is removed.

PartyUp uses reasonable safeguards for the current product, including backend access controls and session-based authentication patterns, but no internet service can guarantee absolute security.

Current choices include signing in or out, using guest Match where available, following or unfollowing profiles, removing Connections, leaving rooms, and managing rooms when you are the host.

For privacy questions, use the Contact page.

This is an MVP privacy policy drafted from the current implementation and should receive formal legal review before broad commercial launch.