Privacy Policy

Pamber is designed for live B2B and workplace events. In the context of global data protection laws (including GDPR and CCPA):

• The Event Host (or their organization) is the Data Controller for attendee data generated during their events. They decide the purpose of the event and the questions asked.
• For event-specific attendee data, Pamber acts as the Data Processor, handling information strictly on behalf of the Host.
• For account management, platform analytics, and security operations, Pamber acts as the Data Controller.

We practice strict data minimization. We collect only what is technically necessary to operate live events and maintain system security:

Technical Data (Automatically upon visiting)

IP addresses and browser types logged by our CDN (Cloudflare) and database infrastructure (Supabase) strictly for security, DDoS protection, and session management.

Session Aliases (When joining an event)

To display participant names on votes, Q&A, and leaderboards. Real names are not required.

Event Inputs (During active sessions)

Vote selections, Q&A questions, upvotes, and quiz answers to render live results for the Host.

Host Account Data (Upon account creation)

Email addresses and authentication tokens to securely associate events with the Host.

We use collected data solely to:

• Deliver real-time polling, Q&A, and event mechanics.
• Provide Hosts with aggregated event analytics.
• Ensure platform stability and security.

We absolutely do not:

• Sell personal data to third parties.
• Use participant data for advertising, marketing, or profiling.
• Track users across multiple unrelated events.

Aggregated Analytics: We generate and retain strictly anonymized, aggregated usage metrics (such as total participant counts and event durations) to analyze system performance. This telemetry data cannot be linked to any individual user, host, or specific event content.

Sandbox / Instant Events

All event content (including aliases, Q&A text, and votes) is deleted immediately when the Host ends the session. We retain only de-identified, aggregated statistical counts for system telemetry.

Live / Hosted Events

Retained until manually deleted by the Host. We periodically review and purge inactive event data, typically within 30 days of event conclusion.

Host Account Data

Retained while the account is active, and deleted upon account termination.

Pamber is built on Lovable Cloud and utilizes Supabase for database infrastructure. Data is securely stored and processed in Singapore (Asia Pacific).

For our enterprise clients located in the European Economic Area (EEA), United Kingdom, or other regulated jurisdictions, data transfers are governed by Standard Contractual Clauses (SCCs) and our Data Processing Addendum (DPA), executed upon request with the Event Host.

We rely on vetted infrastructure providers to operate Pamber securely. We do not authorize these providers to use your data for their own purposes:

Lovable

Application hosting and cloud backend (United States)

Supabase

Database and real-time infrastructure (Singapore via Lovable Cloud)

Cloudflare

CDN, edge network, and security (Global)

We use essential HTML5 Local Storage mechanisms and session cookies required for real-time WebSocket connectivity and Host authentication. We do not use third-party tracking pixels, marketing cookies, or cross-site tracking scripts.

Because Pamber prioritizes privacy, participants join events using unverified aliases. Consequently, we cannot cryptographically verify identity based solely on an anonymous alias.

Participants

To request access to or deletion of specific event data, please contact the Event Host directly, as they are the Data Controller.

Hosts

You may manually delete your event data at any time via your dashboard, or contact us to execute your rights under applicable laws (e.g., GDPR, CCPA).

Pamber is an enterprise tool intended for use by adults in professional, corporate, or educational settings. We do not knowingly collect data from minors.

We employ strict architectural security measures, including HTTPS/TLS encryption in transit, Row-Level Security (RLS) policies at the database layer, and column-level access blocking for authentication tokens.

For privacy questions, DPA execution, or compliance inquiries:

Email: privacy@pamber.live