Privacy Policy

• Account data: name, email address, profile image, account identifier, and authentication information supplied by Clerk.
• Eligibility data: date of birth when needed for an age-restricted event.
• Ticket and event data: registrations, attendee contact details, quantity, confirmation codes, event content, organizer identity, scans, refunds, and operational records.
• Payment and payout data: Stripe payment references and organizer payout information. Stripe collects card details directly; Happenster does not store full payment-card numbers.
• Support data: messages, attachments or evidence you submit, and contact details needed to respond.
• Legal acceptance data: the Terms and Privacy versions accepted during organizer publication, acceptance time, and account identifier.

Our servers and security controls process request timestamps, requested routes, response status, IP addresses or IP-derived rate-limit keys, user-agent and browser information, account identifiers when signed in, and security events such as repeated failures, suspected automation, or attempts to bypass access controls.

We use this information to authenticate requests, apply rate limits, diagnose failures, investigate fraud or scraping, protect users and organizers, enforce our Terms, and preserve evidence of serious incidents. We do not use these logs for targeted advertising.

• Provide accounts, event listings, ticket purchases, refunds, check-in, and support.
• Show relevant age-restricted events and remember eligibility information.
• Send confirmations, receipts, event updates, and organizer announcements.
• Operate organizer analytics and event-day tools.
• Distribute organizer-approved event content to selected providers and channels.
• Moderate content, prevent abuse, secure the platform, and enforce our Terms.
• Maintain acceptance records and comply with legal obligations.

We do not sell personal information or use it for targeted advertising.

Organizers receive attendee information needed to run their events. Door staff receive limited ticket information needed for authorized check-in. Public event information may appear in search results, social previews, approved embeds, and external providers selected by an organizer.

Service providers process information for Happenster under their own privacy terms, including Clerk for authentication, Stripe for payments, Resend for transactional email, hosting and database providers for platform operation, and event providers such as Eventbrite or Ticket Tailor when an organizer connects and uses those channels. Ticketmaster also supplies public event catalogue data; Happenster links or imports that provider-owned material as described in the event listing.

We may disclose information when reasonably necessary to comply with law, protect rights or safety, investigate misuse, or complete a merger, financing, acquisition, or sale involving Happenster, subject to appropriate safeguards.

Account and organizer information is generally retained while an account is active. Ticket, payment-reference, acceptance, distribution, and audit records may be retained longer when needed for transactions, disputes, tax or accounting obligations, platform integrity, or legal claims.

Routine server and anti-abuse logs are normally retained for up to 90 days. Records tied to a security incident, suspected fraud, scraping investigation, or legal obligation may be retained longer while reasonably needed. Support history may be retained for up to two years so we can handle follow-up requests.

Backups and provider systems may take additional time to delete information. We will refine and verify these periods with counsel before production publication.

Depending on where you live, you may have rights to access, correct, delete, receive, or object to certain uses of your personal information. You can update profile information in Happenster or submit a request through the Help Desk.

We may need to verify your identity and may retain information that is required for completed transactions, fraud prevention, legal compliance, or the rights of others. Authorized agents should provide proof that they may act for the person concerned.

We use access controls, authenticated sessions, encrypted network transport, restricted server access, and provider security features intended to protect information. Clerk handles passwords and session credentials, and Stripe handles payment-card data. No internet service can guarantee absolute security.

We identify each policy version by its effective date. For material changes, we may use email or in-app notice and request acknowledgment or assent where appropriate. Organizer publication records store the policy version acknowledged at that time.

Submit privacy questions or rights requests through the Help Desk. Include enough detail to identify the account and request, but do not send passwords, payment-card numbers, or other secrets.