bindro · version 2026-08-12

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

bindro Terms of Service

These terms are a contract between you and [ENTITY NAME], a [STATE OF FORMATION] company ("bindro", "we", "us"). They govern your use of bindro.io and every event page we serve — whether you are browsing, registering for an event, or buying a ticket. Using the service means you accept them. If you do not accept them, do not use the service.

If you organise events and receive payouts through bindro, you are a host, and a separate Host Agreement governs that side of the relationship. These terms are written for visitors and attendees.

Effective date: [TO BE SET ON PUBLICATION].

1. One service, many storefronts

bindro runs under twenty vertical brand presentations — the ticketing pages for a theatre look different from the pages for a climbing gym. They are all one service, run by one company, under this one set of terms. Whatever the page looks like, your legal relationship is with bindro.

2. bindro and the host: who does what

Every event on bindro belongs to a host — the organiser who created it. The split of responsibility matters, so here it is plainly:

bindro is responsible for	The host is responsible for
The platform: event pages, registration, ticketing, check-in, and your account.	The event itself: creating it, describing it honestly, and making it happen as described.
Processing your card payment as merchant of record. When you buy a ticket, your payment is made to bindro, not to the host.	Setting the ticket price, the tax settings, and the refund policy for each event.
Enforcing the refund policy you bought under, exactly as it stood when you paid (see Section 6).	Everything at the venue: safety, conduct rules, age limits, admission decisions, and what actually happens on the day.

We are not the organiser of any event. If an event is cancelled, moved, or turns out not to be what was promised, that is a matter between you and the host — but the refund protections in Section 6 apply to your purchase, and we enforce them. If the whole event is cancelled, your booking stays refundable.

3. Your account

You sign in with your phone number. We text a one-time code to that number; entering the code signs you in. That has three consequences:

Keep your phone number current. It is how you get back into your account.
Protect your phone. Anyone who can read your texts can sign in as you.
You are responsible for activity that happens under your sign-in.

Give us accurate information — your real name and a working email and phone number. If we believe an account is being misused, we can suspend it while we look into it.

4. Buying a ticket

Prices are in US dollars. The total shown at checkout is the total you pay. There are no surprise fees added after you click buy.

Item	How it works
Platform fee	2.5% + $0.99 per paid ticket. By default it is added to the ticket price and appears in the total shown to you at checkout. A host may instead choose to absorb the fee or split it with you — either way, the checkout total is final.
Free tickets	No fee. Free means free.
Taxes	Where an event charges sales tax, it is applied according to the host's tax settings for that event and shown at checkout.

Your card details never touch bindro's systems. Card payments are processed by Stripe on bindro's account, and Stripe collects your card details directly on its own secure payment pages. We see the outcome of a payment — paid, refunded, disputed — never your card number.

5. Your tickets

A ticket is personal to you. It is not a bearer instrument to duplicate or pass around.
Each ticket admits one person once.
If a ticket is refunded, it is revoked and will not admit anyone.

Some events ask registration questions or require a waiver signed electronically before you attend. Those answers and signatures are collected for the host of that event (see Section 11), and the waiver is an agreement between you and the host.

6. Refunds

Every event has a refund policy, and you see it on the event page before you buy. Hosts publish their own; if a host has not published one, the platform's default applies — refundable until the event starts. Here is our commitment: the policy you bought under is the policy that applies. The version in force when you paid is recorded with your order, and every later decision is judged against that version — a host cannot quietly tighten the rules after your purchase.

Within the policy's window, refunds are self-serve. You request the refund yourself, from your account, and it is granted automatically — no one's approval is needed. When a refund is issued, the ticket is revoked.

If your situation falls outside the policy's window, you can still ask. Your request goes from your order page to the host, is judged against the policy you bought under, and you will hear back by email.

If the whole event is cancelled, your booking remains refundable regardless of any cut-off. A cancelled event does not trap your money.

7. Chargebacks

A chargeback is when you dispute a charge with your bank instead of using the refund flow. Please try the refund flow first: if your request is within the refund policy, a self-serve refund is faster and certain.

When a chargeback is filed, the full disputed amount is debited from the host's balance and the dispute is resolved through the card network's process. Filing chargebacks to get around a refund policy you accepted at purchase is a misuse of the service and can lead to your account being closed under Section 18.

8. At the event

Conduct at events is the host's domain. The host sets and enforces the rules of the event and the venue — safety requirements, age limits, behaviour, and admission decisions. Check-in and attendance are recorded on the platform. Disputes about what happened at an event are between you and the host.

9. What you may not do

You may not use bindro to:

break the law, or attend to buy or sell anything illegal;
resell, white-label, or otherwise pass off the platform as your own;
duplicate, forge, or circumvent tickets, credentials, or check-in controls;
scrape the service, interfere with it, or probe its security;
impersonate another person or misrepresent who you are;
do anything on Stripe's prohibited business list, which is incorporated into these terms.

Hosts face further restrictions in the Host Agreement — including licensure and age controls for alcohol events and mandatory guardian-consent machinery for events aimed at minors. The full list of prohibited uses lives in our Acceptable Use Policy.

10. Text messages and email

We send two kinds of text message: one-time sign-in codes, and transactional messages about your bookings. That is all. We never send marketing texts. By signing in with your phone number you agree to receive these messages; message and data rates may apply from your carrier. Because sign-in works by text code, you cannot use an account without receiving the codes. We also send transactional email — receipts, booking confirmations, and notices about your account.

11. Your data, briefly

This is a summary; the details are in our privacy documentation, including the full retention schedule published at /privacy/retention/.

What we hold: your phone number, email, and name; your registration answers and e-signed waivers; check-in and attendance records; and payment outcomes. Never card numbers — those stay with Stripe.
Who is responsible: for your bindro account data, bindro is the controller. For registration answers collected for a host's event, the host is the controller and bindro processes the data on the host's behalf.
Sensitive answers: some verticals collect health-related or minor-related registration data. That data is encrypted at rest, excluded from AI features, and excluded from operational logs.
Who helps us run the service: a small set of providers process data for us — Stripe (payments, payouts, and identity checks), Textbelt and Twilio (text messages), Amazon Web Services SES (email), and Google (optional sign-in for hosts). The service runs on a dedicated server in an OVH datacenter serving US traffic. These providers process data to run the service — nothing else.
Your rights: access, correction, deletion, and portability — write to privacy@bindro.io. On deletion we destroy your identity (name, email, answers); financial and audit records are retained for 7 years because money disputes require them.
No ad tech: we do not sell or share personal data for advertising, and we use no third-party ad tech. The only cookie is the essential session sign-in cookie. There are no tracking cookies.

Our in-product assistant is read-only: it can look things up and file a support ticket for you, and nothing else. It never sees health-related registration data.

12. Minors

Events in youth-facing verticals require guardian consent. The guardian countersigns from their own email address — a minor cannot self-approve. If you are a guardian completing consent, you are confirming you have the authority to do so. Data about minors gets the protections described in Section 11.

13. Our content and your licence

The platform — the software, the design, the twenty brand presentations, and the content we create — belongs to bindro. Event content belongs to the host that created it.

We grant you a limited, non-exclusive, non-transferable, revocable licence to use the service to browse events, register, buy tickets, and manage your bookings. That licence does not permit copying, scraping, framing, or republishing the service or its content, and it ends if these terms end for you.

14. No warranties

The service is provided as is and as available. We work hard to keep it running, but we do not promise it will be uninterrupted or error-free. Events are created and run by hosts: we do not warrant that any event will take place, be safe, or match its description — the host is responsible for that, as Section 2 explains. Some jurisdictions do not allow certain warranty disclaimers, so parts of this section may not apply to you.

15. Limits on our liability

To the fullest extent the law allows:

We are not liable for the acts or omissions of hosts, or for anything that happens at an event.
We are not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits or lost data.
Our total liability to you for all claims is capped at the greater of the amounts you paid through the platform in the 12 months before the claim arose, or [CAP AMOUNT — COUNSEL TO CONFIRM].

Some jurisdictions do not allow certain limits on liability, so parts of this section may not apply to you. Nothing in these terms excludes liability that cannot lawfully be excluded.

16. [Arbitration and class-action waiver — counsel to decide]

[COUNSEL TO DECIDE: whether disputes are resolved by individual arbitration with a class-action waiver — including the arbitration provider, small-claims carve-out, and opt-out window — or by the courts named in Section 17. This section is intentionally a placeholder pending that decision.]

17. Governing law and venue

These terms are governed by the laws of [GOVERNING LAW — COUNSEL TO INSERT]. Subject to Section 16, disputes will be resolved in the courts of [VENUE — COUNSEL TO INSERT].

18. Ending things

You can stop using bindro at any time, and you can ask us to delete your data as described in Section 11.

We can suspend or close your account if you break these terms, break the law, or misuse the service — including ticket fraud and chargeback abuse. Where we reasonably can, we will tell you why.

Sections that by their nature should survive — including Sections 11, 13, 14, 15, 16, and 17 — survive the end of these terms.

19. Changes to these terms

We may update these terms. When we do, we will post the new version with its effective date, and for material changes we will give you notice before they take effect. Continuing to use the service after a change takes effect means you accept it. If you do not accept a change, stop using the service before it takes effect.

20. Contact

Privacy requests: privacy@bindro.io
Support: from your account — the in-product assistant can file a support ticket for you.
Legal notices: [REGISTERED ADDRESS — COUNSEL TO INSERT]

Version 2026-08-12. Related: Privacy Policy · Host Agreement · Acceptable Use Policy · Data retention schedule