bindro · version 2026-08-12

Draft prepared [2026-08-12] — pending review by counsel; [bracketed items] are for counsel to complete.

Host Agreement

This is the agreement between you — the person or organisation running events on bindro.io (we call you the host, or organiser) — and bindro, operated by [ENTITY NAME], a [STATE OF FORMATION] company. You accept it when you create a host account. It covers how you sell, how you get paid, what you're responsible for, and how we handle your attendees' data. The data-processing terms in section 9 are part of this agreement; you don't need to sign a separate DPA.

We've written this in plain English on purpose. It's still a contract. If you don't agree with it, don't sell on bindro.

1. Who we are, and who you are

bindro is a self-serve ticketing and registration platform. We present it under twenty vertical brands — one for yoga and fitness teachers, one for breweries, one for museums, and so on. Those are presentations of one service. Whichever brand page you signed up through, you have one account, one legal relationship, and it's this one.

Three kinds of people use bindro:

Hosts (you): you create events, sell tickets or take registrations, and receive payouts.
Attendees (your buyers): they purchase tickets or register for your events.
Visitors: they browse event pages.

At launch, host onboarding is US-only. Your currency is USD, derived from your country.

2. Your event is yours

We provide the platform. You run the event, and you are responsible for it. Specifically:

Accuracy. Your event listing — description, dates, venue, what's included, the refund policy you publish — must be true. Attendees buy on the strength of what you write.
Delivery. You must run the event you sold. If you can't, you deal with the consequences, including refunds.
Safety. The safety of your event, venue, and activities is your responsibility.
Licences and permits. If your event needs a licence — an alcohol licence, an activity permit, professional accreditation, anything — you must hold it. Alcohol events additionally require age controls (see section 11).
Taxes. Taxes on your sales are yours to determine, collect where required, and remit. We are not your tax advisor.

The ticket is a contract between you and your attendee. We handle the payment side of it (section 4), but we are not the organiser of your event and we don't take on your obligations to your attendees.

3. Our fee

Free is free. Free tickets and free events carry no platform fee.

For paid orders, our fee is 2.5% + $0.99 per paid order: 2.5% of the order subtotal (after discounts, excluding tax), plus $0.99 charged once per order — once per order, however many tickets are in it.

You choose, per event, who pays the fee:

Fee mode	What happens
Attendee pays (default)	The fee is added to the buyer's total at checkout. Your ticket price is what you keep.
You absorb it	The buyer pays the ticket price only. The fee comes out of your proceeds.
Split	The fee is divided between you and the buyer as evenly as cents allow.

Whichever mode you choose, the checkout shows the buyer exactly what they're paying and why. There is no monthly fee, no setup fee, and no listing fee.

4. How payment collection works

For card payments, bindro is the merchant of record. Charges are processed by Stripe on bindro's account. That means the payment transaction runs through us, and disputes about the payment come to us first — but the event contract stays between you and your attendee (section 2).

Card data never touches bindro's systems. Stripe collects card numbers in its own embedded payment fields and pages. We see payment outcomes — paid, refunded, disputed — never card numbers.

5. Payouts

We pay you after your event completes. Your payout is released two days (T+2) after your last session ends. We never pay advances against future ticket sales. Ever. That rule is part of how we keep attendee money safe, and it has no exceptions.

Before your first payout

Before we can send you money, you must complete Stripe Connect Express onboarding. Stripe — not bindro — collects your identity details and bank account and verifies them. By accepting this agreement you also agree to the Stripe Connected Account Agreement, which is incorporated into this agreement; you'll be asked to accept it during Stripe onboarding, and you must, or we cannot pay you.

Onboarding is required before your first payout, never before your first sale. You can publish an event and start selling right away, and complete Stripe onboarding while sales come in.

Reserves

Some verticals carry more refund and dispute risk than others, so we hold a rolling reserve in some of them: a percentage of your net proceeds, between 0% and 13.5% depending on your vertical, held back from your payout and returned to you on a schedule — between 90 and 180 days after the payout it was withheld from, depending on the vertical. Low-risk verticals have a 0% reserve and the full balance releases at T+2.

Your exact reserve percentage and return schedule are disclosed in the product before your first sale. You'll never discover a reserve after the fact.

6. Refunds

You publish a refund policy for each event. The platform then enforces the policy you published: attendees can claim refunds themselves, without asking you or us, whenever their request falls inside your published policy. The policy you show buyers is the policy that gets applied — you can't publish a generous policy and apply a stingy one.

Refunds are paid from your balance. When a refund is issued, the refunded amount is debited from your host balance (or creates a debt if your balance can't cover it — section 8).

On a full refund, everything is returned to the buyer, including our platform fee — the sale is reversed exactly. On a partial refund, the refunded portion goes back to the buyer and our fee stays earned. Stripe's card-processing fee is not returned to bindro when a refund is issued; that is a cost of the payment system, and we tell you about it here so the money flow has no surprises.

7. Chargebacks

A chargeback is when a buyer disputes a charge with their card issuer instead of using your refund policy. When that happens, the card network takes the full disputed amount back regardless of what anyone thinks of the dispute.

You bear chargebacks. The full disputed amount is debited from your host balance. Chargebacks are also a risk signal: a pattern of them can lead to payout holds while we assess what's happening (section 12).

The best defence against chargebacks is a clear listing, a fair published refund policy, and delivering the event you sold — the platform's self-serve refunds exist so buyers have an easier path than calling their bank.

8. If your balance goes negative

If refunds, chargebacks, or other debits exceed what's in your balance, your balance goes negative and you owe us the difference. We may recover it from your future payouts, and if there aren't any, you must pay us the amount owed promptly on request. This obligation survives closing your account.

9. Your attendees' data: processing terms

This section is the data-processing agreement between us. It applies whenever we handle personal data about your attendees on your behalf.

9.1 Who is responsible for what

For attendee registration data collected on your behalf — names, registration answers, waivers, check-in records for your events — you are the controller (the "business" under California law) and bindro is your processor (your "service provider").
For platform account data — your own host account, and the account attendees hold with bindro itself — bindro is the controller. Our privacy policy covers that.

9.2 What we process

Phone numbers (used for one-time sign-in codes) and email addresses
Names
Per-event registration answers you configure — which in some verticals can include health-class data and data about minors
Waiver e-signatures
Check-in and attendance records
Payment outcomes (paid, refunded, disputed) — never card numbers, which only Stripe holds

Bank details exist only at Stripe. Card data never enters our systems.

9.3 Our commitments as your processor

We process attendee data only on your instructions, given through how you configure and use the platform, and only as needed to run the service — never for our own purposes.
We keep it confidential and limit access to people who need it to run the service.
We protect it: each host's data lives in its own isolated database; health-class and minor-class registration answers are encrypted at rest, excluded from AI features, and excluded from operational logs; a tamper-evident audit log records administrative actions; and card data is out of scope entirely because it never reaches us.
We maintain a written incident-response plan with notification deadlines. If a breach affects your attendees' data, we will notify you without undue delay so you can meet your own legal obligations.
We help you honour attendee rights requests — access, correction, deletion, portability — with the platform's built-in tools, and via privacy@bindro.io where a tool doesn't cover it.
We use only the sub-processors listed below (section 9.4), and they are bound to protections consistent with this section.
When you leave, we return and then delete your attendees' data as described in section 10.

9.4 Sub-processors

These are the services we use to run the platform. This list is incorporated into this agreement; if it changes, that is a change to this agreement and section 16 applies.

Sub-processor	What it does
Stripe	Card payments, Connect payouts, host identity verification, bank details
Textbelt	SMS delivery (one-time codes, booking messages)
Twilio	SMS delivery (secondary route)
Amazon Web Services (SES)	Email delivery
Google	Optional sign-in to the host console
OVH	Datacenter hosting our dedicated server (serving US traffic)

9.5 Sensitive data and minors

Some verticals collect registration answers that touch health (a medical-conditions question at a fitness class) or concern minors (a child's registration for a youth programme). These get extra protection: encryption at rest, exclusion from AI features, exclusion from operational logs.

Youth-facing verticals include a guardian consent flow: the guardian countersigns from their own email address. If your event is aimed at minors, you must use it (section 11).

The platform's AI assistant is read-only, can only file support tickets, and never sees health-class data.

9.6 Your duties as controller

Because you are the controller of your attendees' registration data, you must:

Have a lawful basis for collecting what you collect, and collect only what your event actually needs
Tell your attendees how you use their data (your own privacy notice)
Honour their rights requests under the laws that apply to you — which may include the GDPR or UK GDPR if you have European attendees, and the CCPA/CPRA for California
Not use attendee data pulled from the platform for purposes your attendees wouldn't expect

9.7 What we never do with attendee data

We do not sell it or share it for advertising. There is no third-party ad tech on the platform.
We use essential cookies only — a session sign-in cookie. No tracking cookies.
SMS is for one-time sign-in codes and transactional booking messages only. No marketing SMS — not from us, and the platform gives you no way to send any. (Message and data rates may apply to recipients.)

10. Leaving: your export, and what happens to the data

You can close your account at any time. Before you do, you can export your data — your events, attendee lists, registration answers, and financial records — using the platform's export tools, so you leave with what's yours.

After you leave, deletion works by tombstoning: identity data (names, emails, registration answers) is destroyed, while financial and audit records are retained for 7 years, because money disputes — refunds, chargebacks, tax questions — outlive accounts, and we're required to be able to answer them. The full retention schedule is public at /privacy/retention/.

11. Acceptable use and event standards

You may not use bindro for:

Illegal events or goods. If the event or what it sells is unlawful where it happens, it can't be on bindro.
Reselling the platform. Your account is for your events, not for offering bindro to others as your own service.
Alcohol events without proper licensure and age controls. If alcohol is served or sold, you need the licence and you need age verification at the door.
Events targeting minors without the required consent machinery. If your event is aimed at minors, the guardian consent flow (section 9.5) is mandatory, not optional.
Anything on Stripe's prohibited and restricted businesses list, which is incorporated into this agreement — because Stripe processes the payments, their rules bind us both.

Beyond the prohibited list, the standard is simple: describe your event honestly, deliver what you sold, and treat your attendees the way you'd want a platform to make you treat them. The general platform terms of service also apply to your use of the site.

12. Suspension and termination

You can stop using bindro whenever you like. Obligations that arose while you sold here survive: refunds under your published policies, chargebacks, and any negative balance (section 8).

We can suspend or terminate your account:

With notice, if you breach this agreement and don't fix it after we tell you.
Immediately, for fraud, illegal activity, or serious risk — including patterns of chargebacks or refund abuse that put attendee money in danger, or anything that violates section 11.

If we suspend or terminate you, sales stop. Funds in your balance may be held while open disputes resolve and reserves run their disclosed schedule; what remains after refunds, chargebacks, and reserves is paid out to you. Section 10 governs your export and the data.

13. The platform will change

We improve the platform continuously — features will be added, changed, and occasionally removed. If a change materially reduces what your account can do, we'll tell you before it lands. We are not liable for changes to features, but your published events and the money owed on them are always honoured under the rules that applied when the tickets were sold.

14. Liability

Plainly: we're responsible for running the platform well and paying you what you're owed. We're not responsible for your event.

What we don't cover. Neither of us is liable to the other for indirect or consequential losses — lost profits, lost goodwill, lost data (beyond our data commitments in section 9) — arising from this agreement.
Cap. Our total liability to you under this agreement is capped at the platform fees we earned from your sales in the 12 months before the claim arose. This cap does not apply to money we hold that is owed to you as payouts — that isn't "liability," it's your money, and we owe it to you in full under section 5.
Your indemnity. If a third party — an attendee, a venue, a regulator — brings a claim against bindro arising from your event, your listing content, your failure to hold a required licence, or your tax obligations, you will defend us and cover the losses. Your event is yours (section 2), including when it goes wrong.
Nothing here limits liability that the law does not allow to be limited, including for fraud or wilful misconduct.

15. Governing law and disputes

This agreement is governed by the laws of [GOVERNING LAW STATE — COUNSEL TO INSERT], and disputes will be resolved in [VENUE — COUNSEL TO INSERT].

[ARBITRATION — COUNSEL TO DECIDE: whether disputes go to binding arbitration, on what terms, and whether to include a class-action waiver; insert the full clause or strike this placeholder.]

16. Changes to this agreement

We can change this agreement, and we'll do it in the open: we'll give you notice before changes take effect, and material changes require you to re-accept the agreement before you continue selling. We won't change the deal on you silently. The current version always lives at /legal/host-agreement/.

17. How to reach us

Privacy and data rights: privacy@bindro.io
Support: through your host console, which files a ticket to a human
Notices to you: we send them to your account email; keep it current

By creating a host account you accept this agreement, and you confirm you have the authority to bind the organisation you're signing up for.

Version 2026-08-12. Related: Terms of Service · Privacy Policy · Acceptable Use Policy · Data retention schedule