Plain-English terms for using Hubbaly

These terms apply to anyone using Hubbaly, including account holders, guests using hosted ticket links or guest checkout, community members, organisers, community admins, event staff, and anyone accessing public event or community surfaces.

If you use Hubbaly on behalf of an organisation, community, or event team, you are also responsible for making sure you have authority to act for that organisation in the parts of the product you control.

You must give accurate information, keep your account credentials secure, and use Hubbaly lawfully. Do not abuse the service, scrape it, interfere with normal operation, impersonate other people, or use Hubbaly to commit fraud, safety violations, or payment abuse.

You are also responsible for following the local rules, access rules, and participation rules set by the communities and events you join.

Organisers and community admins are responsible for the communities and events they run through Hubbaly. That includes event details, ticket settings, venue information, staffing, admission decisions, required forms, local policies, and on-the-ground safety and legal compliance.

Hubbaly provides the platform layer. We do not take over the organiser's responsibility for running an event, checking whether every event detail is accurate, or guaranteeing that an event will happen exactly as described.

Hubbaly provides event setup, checkout, ticket delivery, waitlist, refund, and organiser payout tooling. Payments are processed through Stripe.

Ticket prices, quantities, availability, refund settings where the product allows them, admissions decisions, and event fulfilment are controlled by the organiser. Depending on how a community's payments are set up, card statements and payment settlement may identify the organiser or community account used for that event sale rather than Hubbaly itself.

Tickets for a specific date do not have the usual 14-day cooling-off right. Unless the organiser's published policy says otherwise, attendees are not entitled to a refund simply because they change their mind, can no longer attend, or bought the wrong ticket.

This does not affect statutory rights. Where an event is cancelled, moved, rescheduled, or materially changed and the attendee does not accept the change, refund handling follows applicable consumer law, the organiser's obligations, Hubbaly's platform rules, and payment-provider requirements.

Where Hubbaly offers optional queue-based ticket return for an eligible paid ticket, that feature is a Hubbaly product option rather than a general refund right. The original buyer can request a return before or after primary ticket availability sells out, but the refund is triggered only if Hubbaly releases the place and a replacement buyer purchases a newly issued organiser ticket through the Hubbaly flow. Under the standard ticket return settlement, Hubbaly's platform fee and Stripe processing fee are retained from the refund amount unless the product explicitly shows a different organiser-funded outcome.

If Hubbaly or an authorised moderator invalidates a ticket because of a safety, abuse, fraud, or policy-enforcement decision, that ticket may be cancelled with refund or cancelled without refund. Those moderation-driven ticket outcomes can override the ordinary attendee refund path or refund cutoff where the product says they do.

Some public events allow guest checkout and hosted ticket access without a full Hubbaly account. Some events also allow ticket transfers, waitlists, or queue-based ticket return flows. These features are conditional and can be limited by event settings, timing, payment status, fraud checks, or whether a ticket has already been used, transferred, or made ineligible by policy.

Ticket returns, where enabled, are not an open peer-to-peer sales feature and are not a legal refund obligation. Buyers do not create public ticket adverts or set their own replacement price. Instead, Hubbaly can release a returned place through waitlist-first or public fallback flows and only process the original buyer's refund after a replacement purchase succeeds.

You are responsible for the content you post, upload, send, organise, or moderate through Hubbaly, including community content, event details, chat messages, photos, forms, and related materials.

We may remove content, cancel access, suspend or restrict accounts or features, or intervene in communities and events where we reasonably believe there is abuse, policy breach, unlawful use, payment risk, impersonation, fraud, or a safety or platform-integrity issue.

Moderation action can include warnings, content removal, muting, suspension, removal from a community, event bans, platform bans, and related limits on ticket purchase, transfer, check-in, messaging, or other participation features.

Deleted or removed content may still be retained in restricted review paths where reasonably necessary for investigations, dispute handling, abuse prevention, legal compliance, or enforcement.

For platform account, security, payment, support, safety, transactional communication, and product-operation processing, Hubbaly acts as data controller and explains that processing in the Privacy Policy.

For event and community data that organisers or community admins decide to collect, require, upload, or manage, those organisers and community admins act as controllers. Hubbaly may act as processor for that organiser-controlled data when we host, transmit, store, display, export, or delete it for them.

Where Hubbaly acts as processor, our Data Processing Addendum describes the documented instructions, processing scope, security commitments, assistance duties, return-or-delete rules, subprocessors, and the authorisation process that apply to that processing.

Organisers and community admins are responsible for having a lawful basis for the data they ask people to provide, for writing any event or community terms they require, and for not using Hubbaly to collect sensitive data unless they have a valid legal basis and appropriate safeguards.

If a hub uses Details to collect for reusable hub details, organisers must collect only details they genuinely need, explain the purpose to members, choose appropriate Hub Admin visibility, and not use reusable hub details as a general sensitive-data store or a substitute for event-specific waivers, consent forms, or feedback forms.

Our Privacy Policy explains how Hubbaly collects, uses, stores, shares, and deletes data across accounts, communities, tickets, media, payments, notifications, browser storage, and first-party analytics.

Read the full policy here:

Privacy Policy

We may suspend, limit, or close accounts, communities, events, or features if needed for safety, abuse prevention, legal compliance, payment risk, or platform integrity. Organisers and admins may also lose access to communities or events if their permissions are removed.

If you are banned from a community or event, you may immediately lose membership, directory visibility, event access, chat access, connection-request eligibility, ticket privileges, or other related access tied to that scope.

Users can request account deletion through the product where available, but some records may still be retained where payment, dispute, security, moderation, or backup obligations require it. We may also change, pause, or discontinue features over time.

To the extent allowed by law, Hubbaly is provided on an as-is basis. We do not promise that every event, organiser, attendee, event detail, payment, message, photo, or feature will always be accurate, lawful, safe, uninterrupted, or error-free.

To the extent allowed by law, Hubbaly is not liable for indirect or consequential loss, loss of profits, loss of revenue, loss of business, or losses caused by organisers, attendees, third-party providers, outages, misuse of the service, or events outside our reasonable control.

Nothing in these terms excludes or limits liability that cannot legally be excluded, including liability for fraud or fraudulent misrepresentation, or for death or personal injury caused by negligence.

These terms are governed by the laws of England and Wales. The courts of England and Wales will have jurisdiction, except where mandatory consumer law says otherwise.

Hubbaly is a product built by Chicken House Labs Ltd, trading as Hubbaly, registered in England and Wales under company number 17081220. Its registered office is Suite RA01, 195-197 Wood Street, London E17 3NU.

For privacy questions, legal notices tied to these terms, or other policy questions, contact privacy@hubbaly.com.