1. Who this policy covers
StubJoy is an event ticketing and operations platform operated by Bellu Development LLC. Our services currently serve the United States. This policy covers our website, organizer dashboard, hosted ticket sites, APIs and staff applications, including StubJoy Staff. Contact us at support@stubjoy.com with questions or requests.
Event organizers decide how to run their events and use attendee information. We process ticketing and event operations information on their behalf. We also use information for our own account administration, security and service operations. An organizer’s own privacy notice applies to its independent use of your information, including any marketing it conducts.
2. Information we collect
Account and team information includes names, email addresses, authentication records, organization details, staff invitations, roles and event assignments. Information you provide may also include event and venue details, vendor contact details, support messages and uploaded content.
Ticketing information includes purchaser and attendee details supplied at checkout or at the door, selected tickets and arrival times, order amounts, fees, payment status, ticket identifiers, check-in activity and benefit redemptions. When an event requires an agreement, we store the accepted text, completed fields and acceptance timestamp linked to the order.
Technical information includes IP addresses, browser or device information, authentication sessions, request logs and error diagnostics. Event analytics may record visitor and session identifiers, referring sites, campaign parameters, pages viewed, ticket selections and checkout activity, and may associate that activity with an order.
Stripe processes online payments and connected-account onboarding. StubJoy receives payment identifiers, transaction status and related order information; full card details are entered through Stripe’s payment interfaces. Staff applications request camera access for QR scanning and use device storage for authentication and preferences.
3. How we use information
We use information to create and secure accounts, publish events, process orders, deliver tickets and transactional messages, record agreements, support check-in and redemption, administer payments and refunds, provide event reports, answer support requests and diagnose service failures.
We also use information to prevent abuse, investigate unauthorized activity, meet legal obligations and establish or defend legal claims. Organizers receive attendance, sales and traffic reports for their events. Any additional use must be consistent with the applicable notice and law.
5. Retention, security and location
We are working toward implementing the retention schedule below. Automated deletion, anonymization and backup expiry under this schedule are not yet fully implemented. These periods are targets and do not currently guarantee when a record will be deleted; information may remain longer while implementation is pending. Contact support@stubjoy.com to request deletion. We will update this notice when the schedule is operational.
Our target is to retain organizer and staff account information while the account is active and delete unnecessary profile information within 30 days of account closure. Signing out or uninstalling an app does not close your account or delete server records.
Our target is to retain attendee details, check-in activity and benefit redemption records for 2 years after the event, then delete or anonymize them. The target for necessary accounting records is 7 years after the relevant tax year, with only the transaction details needed for that purpose retained for the longer period.
Our targets are 90 days for identifiable visitor and checkout analytics, followed by deletion or aggregation without identifiable information; 30 days for routine logs and error diagnostics; 90 days for security audit logs; and 2 years after resolution for support conversations.
Our target is a rolling 35-day backup expiry schedule. Information deleted from active systems may remain in backups until those backups expire. If a backup is restored, applicable deletions must be reapplied.
Organizers are responsible for establishing a documented retention schedule for signed waivers and agreement evidence with their insurer or legal counsel, taking account of applicable claim deadlines and requirements involving minors. Contact support@stubjoy.com to coordinate an organizer-specific schedule. We do not apply a universal waiver deletion deadline; these records are handled separately from ordinary attendee profiles and may be retained for an active dispute or preservation requirement.
We may retain relevant records longer where required by a specific legal obligation, an active dispute or a preservation requirement. These exceptions apply to the records needed for that purpose. Organizer instructions and applicable privacy rights may require earlier deletion where no overriding retention obligation applies.
We use safeguards designed to protect information, but no system can guarantee complete security. Protect your credentials and restrict staff access. Providers may process information outside your home jurisdiction. We are verifying processing and backup locations with our providers and do not currently represent that all information remains in the United States. Any international transfer safeguards required by applicable law must be verified for the relevant providers before relying on those arrangements.
6. Your choices and privacy requests
Contact support@stubjoy.com to request access, correction or deletion of your information or account. For information managed by an organizer, contact that organizer using the event page or order confirmation; we can help route requests. We may need to verify your identity and retain records where required by law or necessary to resolve transactions and disputes.
Depending on your location and the laws that apply, you may have rights to obtain a copy of information, restrict or object to processing, withdraw consent, request portability, opt out of certain uses or appeal a denied request. You may also complain to your privacy regulator. We will handle applicable rights without unlawful discrimination. Send requests and appeals to support@stubjoy.com. Please identify the account or event involved and describe your request; do not email passwords or full payment-card details. Our goal is to acknowledge requests within five business days and respond within the deadlines required by applicable law. If we deny a request, we will explain the reason and how to seek a review where applicable. We coordinate with organizers when they control the requested information.
Browser settings can remove or block cookies and local storage, though some features may stop working. Our Cookies Policy describes these technologies. Our planned approach is to disable optional visitor analytics when Do Not Track or Global Privacy Control is present while keeping authentication and checkout available. This behavior has not yet been verified across every deployed site, so these signals should not currently be relied on to disable all analytics. Contact support@stubjoy.com to exercise applicable privacy rights.
7. Children’s information
Organizer account holders and ticket purchasers must be at least 18 and legally able to enter a contract. Minors may attend events that permit them; an adult must purchase their tickets and a parent or legal guardian must complete any required guardian agreements. Staff under 18 may use organizer-authorized access with appropriate parent or guardian permission and supervision. Organizers and purchasers should provide only the information about minors needed for the event. Our services are not directed to children under 13. If you believe a child provided information improperly, contact support@stubjoy.com so we can investigate and address it.
8. Changes and contact
We will post updates on this page with an effective date and provide additional notice when required by law. Questions about this policy may be sent to support@stubjoy.com. Our business contact is Andrew Bellucci (andrew@bellu.dev).