Event Registration & Ticketing
Tito
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Team Tito Limited · ti.to
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Tito at a glance
- Vendor
- Team Tito Limited
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Default not stated; pages mention Ireland and the EU source, captured 29 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates Tito 2.5/5, the mean of 6 judges. Tito, an event management and ticketing platform from Team Tito Limited of Dublin, lands mid-field; persona-weighted totals span 4.3 to 5.6. how scores are made
- As of
- Vendor pages captured 29 Oct 2026 to 1 Nov 2026; evaluated by the panel 30 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Tito, an event management and ticketing platform from Team Tito Limited of Dublin, lands mid-field; persona-weighted totals span 4.3 to 5.6. Its strongest ground is sovereignty at 5–6, with attendee data ownership, check-in and onsite, and payments and fees each at 4–6. Organisers are the data controller with Tito as processor; attendee data exports as CSV, XLSX, API and webhooks. Check-in apps for web, iOS, Android and Badgy scan QR codes from ticket email, PDF or Apple Wallet with automatic multi-device sync and duplicate-scan warnings. Paid tickets run through the organiser's own Stripe or PayPal gateway, sending funds directly to the organiser's bank. The weak spot is invoicing and tax, the only category topping out at 4: beyond EU VAT guidance, we found no public information on invoices in the organiser's name, business-buyer VAT IDs, credit notes or a named accounting export. Shop and registration at 4–5 rests on a two-line embeddable widget, with no public information on waiting lists or seating plans. Score spreads bring no flagged disagreement — judges differ in needs, not readings.
Speaks for it
- Attendee data belongs to the organiser as data controller with Tito as processor, exportable as CSV, XLSX, API and webhooks, with mail blasts to attendees from inside the product
- Paid tickets run through the organiser's own Stripe or PayPal gateway across 139 currencies, which sends funds directly to the organiser's bank account so the platform never holds or delays money
- Check-in apps ship for web, iOS, Android and Badgy, scanning QR codes from ticket email, PDF or Apple Wallet with automatic multi-device sync and duplicate-scan warnings
- Team Tito Limited is registered in Ireland with company number 566334 and VAT number IE3384527RH published, and personal data is stored and processed on Amazon Web Services in Ireland within the EEA
- The pricing page publishes a 3% per-ticket fee capped at €25 for tickets above €833.33, with free events at no charge and no credit card required to start
Held against it
- We found no public information on invoices issued in the organiser's name with consecutive numbers, business-buyer VAT IDs, credit notes or a named accounting-system export
- We found no public information on waiting lists, capacity quotas, seating plans or group bookings for the shop
- We found no public information on refunds, chargebacks, or whether fees can be passed on to the buyer
- Check-in sync is documented to work only while a data connection is available, and the web-based check-in app is stated not to support QR scanning
- The captured third-party provider list is cut off mid-way, Intercom — a US-headquartered provider — sits in the support and messaging chain alongside Google Analytics cookies with no stated safeguard, and no ISO 27001 or SOC 2 certification is stated
Best for
- You sell tickets from your own website and want a checkout you can embed with two lines of code and style with your own CSS
- You want ticket revenue sent directly to your bank account through your own Stripe or PayPal gateway
- You run a multi-device door operation and need QR check-in from ticket email, PDF or Apple Wallet with time-stamped exports
- You want an Irish-registered vendor that stores and processes personal data on Amazon Web Services in Ireland within the EEA
Avoid if
- Your venue has unreliable connectivity, since check-in sync is documented to work only while a data connection is available
- Your compliance policy rules out US-headquartered providers, since Intercom sits in the support and messaging chain here
- You need attendee data deleted automatically after each event, since data is retained while the account is active with deletion only on request
The scores
| Criterion | Panel median |
|---|---|
| Ticket shop, checkout & registration | 2.5 of 5 |
| Payments, payouts, fees & refunds | 2.5 of 5 |
| VAT, invoices & accounting handoff | 2 of 5 |
| Check-in, badges & on-site sales | 2.5 of 5 |
| Attendee data & the customer relationship | 3 of 5 |
| European sovereignty | 3 of 5 |
Ticket shop, checkout & registration
Show reasoningHide reasoning
How this is scored
How a ticket or a registration is sold: ticket types and categories, member and early-bird prices, discount codes, bundles and add-ons, a shop embeddable on the organiser's own website or under its own domain, custom questions per ticket and per attendee, group and company bookings, capacity limits and waiting lists, reserved seating with a seating plan, recurring dates and course series, several languages, and an accessible mobile checkout.
0 — Not a ticketing or registration tool; tickets cannot be sold and registrations cannot be taken in the product.
3 — An event page on the platform with a few ticket types and a fixed sign-up form; embedding, custom questions, capacity rules or seating are basic or not described.
5 — Several ticket types with prices, quotas and sale periods, discount codes, custom questions per attendee, a shop embeddable on the organiser's website as a widget or link, capacity limits with a waiting list, and a checkout that works on a phone.
8 — A white-label shop under the organiser's own domain and design, reserved seating with a seating-plan editor, add-ons and bundles, group and company bookings with several attendees per order, conditional questions, member prices by code or login, recurring dates and course series, several languages, and the checkout's accessibility stated.
10 — A shop that fits any event: multi-event and season tickets, timed entry and seat holds, a checkout that the organiser can extend (API, custom fields synced to a CRM), an accessibility conformance statement (WCAG level named), and the conversion and drop-off of the checkout reported to the organiser.
The Conference Organiser
The widget embeds our registration form into the association's own site with two lines of code and custom CSS, with dedicated guides for WordPress and similar platforms, and the demo shows several priced ticket types plus discount codes created through the admin API. But we found no public information on quotas and sale periods, waiting lists for our twenty-seat workshops, member prices by code, or group bookings where an assistant registers three colleagues in one order, so this lands partway up the scale. 1 2 5
The Venue Promoter
The widget is the strong part for a club: two lines of code embed the full checkout on our own site with our own CSS, the checkout opens in an overlay without leaving the page, and there are dedicated guides for common site builders. Several priced ticket types appear (a discounted Student ticket among them), the admin API creates discount codes, and a student-ID prompt at ticket assignment hints at per-ticket questions. We found no public information on capacity limits with waiting lists, seating plans, several languages, or the checkout's accessibility. 1 2 5
The Course Provider
The embeddable widget is well documented — two lines of code put my course checkout on my own site, styleable with my own CSS, with guides for WordPress and Squarespace — and the examples show several ticket types at different prices, a discounted student ticket with an ID question, and discount codes via the API. For my eight-week courses I need waiting lists that refill a cancelled seat, quotas and recurring dates, and I found no public information on any of those, nor on checkout languages or accessibility. 1 2 5
The Revenue Accountant
The embeddable widget is documented in real depth — two lines of code, full checkout in an overlay, custom CSS, a single-button pop-up and guides for WordPress, Weebly and Squarespace — and ticket types with distinct prices plus discount codes are evidenced, with the developer API able to create events, tickets and codes. But I found no public information on capacity limits and waiting lists, custom questions per attendee, seating plans, member or early-bird prices, or checkout accessibility, which keeps this just above the basic level. 1 2 5
The Data Protection Officer
The JavaScript widget embeds the full checkout into the organiser's own website with two lines of code and custom styling, and the captured pages show several priced ticket types plus discount codes created through the admin API. We found no public information on capacity limits, waiting lists, seating plans, group bookings or the checkout's accessibility. 1 2 5
The Skeptic
Three ticket types with prices, a discounted student tier carrying an ID-number question, and discount codes creatable through the admin API are shown, and a two-line widget embeds the checkout into the organiser's own site with custom CSS and a platform-guided install. We found no public information on quotas, waiting lists, sale periods, seating plans or checkout accessibility, so this is a solid mid-level shop, not a full one. 1 2 5
Payments, payouts, fees & refunds
Show reasoningHide reasoning
How this is scored
How the money moves: payment methods offered to buyers (cards, PayPal, SEPA direct debit, invoice, local methods), whether the organiser connects its own payment account or the platform collects as merchant of record, when the revenue is paid out (continuously, before the event, or after it), the per-ticket and payment fees and whether they can be passed on to the buyer, refunds of single tickets and of a cancelled event, ticket transfer and resale, and chargebacks.
0 — No payment of any kind; the product only collects free registrations.
3 — Online card payment through the platform; payout timing, fee model, refunds or buyer-paid fees are basic or not described.
5 — Several payment methods including cards and PayPal or SEPA, the fee per ticket stated with the option to pass it to the buyer, the payout schedule stated, and refunds of single orders and of a cancelled event issued from the product.
8 — A choice between the organiser's own payment account (Stripe, PayPal, Mollie or similar) and platform collection, payouts before the event stated with their conditions, invoice and bank transfer for business buyers, partial refunds and refund policies set per event, ticket transfer or resale by buyers, and chargeback handling explained.
10 — Full control of the money: the merchant of record named for each set-up, payout timing and any reserve held published, every fee itemised per order, refunds, transfers and resale with the organiser's rules enforced, and the cancellation process for an event documented end to end.
The Conference Organiser
Paid tickets run through our own gateway — Stripe or PayPal, 139 currencies — and the pages state funds are sent directly to our bank account by the gateway, so the platform can never hold or delay our money. The fee is stated as 3% Per Ticket capped at €25 above €833.33 and gateway fees shown as 2.9% + 30¢ with US Stripe pricing as the example; we found no public information on refunds, ticket transfer, chargebacks, or whether fees can be passed to the buyer. 6 7
The Venue Promoter
The money route suits a club that needs the ticket cash before the night: you connect your own payment gateway (Stripe or PayPal, 139 currencies) and the pricing page says funds "are sent directly to your bank account by your chosen payment gateway", with Tito never holding or delaying money. The fee is "3% Per Ticket", capped at "€25" for tickets above "€833.33", with gateway fees shown as "2.9% + 30¢" (a US Stripe example). We found no public information on refunds of single orders or of a cancelled event, on adding the fee to the buyer's price, or on chargeback handling. 6 7
The Course Provider
The money model is unusually clear: I connect my own Stripe or PayPal gateway, the fee is 3% per ticket capped at €25, and the gateway sends funds directly to my bank so the platform never holds my course fees. I found no public information on how refunds of a single booking or a cancelled course are issued, whether the fee can be passed to the buyer, or how chargebacks are handled. 6 7
The Revenue Accountant
The money path is unusually clean for my books: the organiser connects their own Stripe or PayPal gateway, 139 currencies are supported, funds go straight to the organiser's bank with Tito never holding or delaying money, and the payment processing fee is shown as 2.9% + 30¢ with US Stripe pricing named as the example. But I found no public information on refunds of single orders or a cancelled event, passing fees on to the buyer, invoice or bank transfer payment for business buyers, or chargeback handling. 6 7
The Data Protection Officer
Paid tickets run through a gateway the organiser connects, with Stripe and PayPal named, and funds are sent directly to the organiser's bank account by the gateway, so the platform holds no money; the per-ticket fee is published with a cap. We found no public information on refunds, ticket transfer, chargebacks, or whether fees can be passed to the buyer. 6 7
The Skeptic
Paid tickets run through the organiser's own gateway — Stripe or PayPal — and the pricing page states funds are sent directly to the organiser's bank account by that gateway, so Tito can never hold or delay the money, which is exactly the payout answer I look for. What the captured pages do not show is refund handling, chargebacks, or whether the per-ticket fee can be passed to the buyer, so the money story is only half documented. 6 7
VAT, invoices & accounting handoff
Show reasoningHide reasoning
How this is scored
How ticket revenue reaches the books correctly: the VAT rate set per ticket or product (reduced rates for concerts and culture, exemptions for education and seminars), gross and net prices shown, invoices to buyers in the organiser's name with consecutive numbers, business buyers with company name and VAT ID, reverse charge for cross-border events, cancellation invoices and credit notes, the platform's own fee invoice, e-invoicing, and exports to DATEV or named accounting systems.
0 — No receipts or invoices; the organiser has to produce every invoice outside the product.
3 — An order confirmation or simple receipt per booking; VAT rates, invoices in the organiser's name, business buyers or accounting exports are basic or not described.
5 — VAT rate configurable per ticket, invoices generated in the organiser's name with its tax details and consecutive numbers, company name and address captured for business buyers, cancellation invoices on refund, and a sales export as CSV or to at least one named accounting system.
8 — Several VAT rates in one order, net prices for business buyers, VAT IDs validated and reverse charge applied, e-invoices (XRechnung or ZUGFeRD) for public and business buyers, a DATEV export with booking data, the platform's fee invoice separated from ticket revenue, and whether the platform sells as agent or in its own name stated.
10 — Tax handled per country: VAT rules for events in several EU countries documented with the place of supply, invoices and credit notes stated as compliant with national invoice law, a reconciliation of payouts, fees and ticket revenue per event, and a GoBD-compliant archive or audit export.
The Conference Organiser
The EU VAT guidance is genuinely useful — place of supply where the event takes place, and why reverse charge does not apply to event admissions — and the demo tickets show gross prices marked Inc. VAT @23%. But we found no public information on invoices issued in our name with consecutive numbers, business buyers with company name and VAT ID, e-invoicing, or an export to a named accounting system, which is precisely what our accounts payable department will ask about. 3 5 6
The Venue Promoter
Example tickets display gross prices with their rate ("$99.99 Inc. VAT @23%"), a help article sets out the place-of-supply rules for event admissions — VAT at the rate where the event takes place, with reverse charge not applying to admissions — and orders can be exported as CSV. We found no public information on invoices issued in the organiser's name, credit notes, business-buyer VAT IDs, or exports to named accounting systems. 3 5 6
The Course Provider
The EU VAT guidance is genuinely useful for my mix of exempt teaching and taxable workshops, covering place-of-supply for event admissions, the exemption note and reverse charge for exhibitor services, and example tickets carry an inclusive rate such as Inc. VAT @23%. I found no public information on invoices in my own name with consecutive numbers, business buyers' VAT IDs, credit notes, or an export to a named accounting system such as DATEV. 3 5 6
The Revenue Accountant
VAT rates appear on tickets with gross display (the examples all show Inc. VAT @23%), the place-of-supply guidance is genuinely useful — VAT at the rate of the country where the event takes place, reverse charge not applying to admissions but applying to expo booth and advertising services — and sales reporting exports as CSV. But I found no public information on invoices in the organiser's name with consecutive numbers, company and VAT ID capture for business buyers, credit notes on refund, a fee invoice kept apart from ticket revenue, or any DATEV or named accounting handoff. 3 5 6
The Data Protection Officer
Ticket examples show VAT set per ticket with gross prices ('Inc. VAT @23%'), the EU VAT help article explains place-of-supply rules for admissions and reverse charge for expo services, and sales data exports as CSV. We found no public information on invoices issued in the organiser's name with consecutive numbers, VAT ID capture for business buyers, credit notes, or exports to a named accounting system. 3 5 6
The Skeptic
Ticket prices are shown as Inc. VAT at 23%, a help article works through EU place-of-supply rules for event admissions including that the reverse charge does not apply to admissions, and orders and expenditure export as CSV. We found no public information on invoices in the organiser's name with consecutive numbers, business-buyer VAT IDs, credit notes or any named accounting-system export — the parts that actually feed the books. 3 5 6
Check-in, badges & on-site sales
Show reasoningHide reasoning
How this is scored
What happens at the door: a check-in app that scans tickets on phones or scanners, offline scanning and several devices at once, entrances and time slots, check-in lists by name, badge printing with attendee data and QR code, box office and on-site sales with card terminals, walk-in registration, session and room check-in at conferences, attendance certificates, and live attendance figures.
0 — No check-in; tickets cannot be validated at the event.
3 — Tickets with a QR code and a guest list to tick off by hand or in a simple app; offline use, several devices, badges or on-site sales are basic or not described.
5 — A free check-in app for iOS and Android that scans tickets on several devices at once, works offline and syncs, a searchable guest list, and live check-in numbers in the dashboard.
8 — Badge printing with attendee data and QR codes, access rules per entrance, session or day, box office sales on site with a named card terminal, walk-in registration, dedicated scanner hardware supported or rented, and attendance certificates for courses.
10 — On-site operations at scale: self-service kiosks or turnstile integration, session check-in feeding continuing-education credits, cashless or on-site payments reconciled with online sales, and the hardware, offline limits and failover documented.
The Conference Organiser
Four check-in versions — web, iOS, Android and Badgy — scan the QR code from the ticket email, PDF or Apple Wallet or search attendees by name, sync across multiple devices, warn on duplicate scans and support a bluetooth barcode scanner, with multiple lists per day or ticket type that would suit our two-day format. We found no public information on badge printing with attendee data, box office sales with card terminals, attendance certificates for continuing-education points, or live check-in figures; offline operation is only implied by the manual sync button, and the web version is stated not to scan QR codes. 4 5
The Venue Promoter
For the door: iOS and Android apps scan the QR code from the ticket email, PDF or Apple Wallet or find the attendee by search, several devices sync automatically with the admin panel, duplicate scans raise a warning, and a Bluetooth barcode scanner is supported. Multiple lists per day or ticket type, a secret staff link that needs no login and expires with the list, and an export of checked-in attendees with their check-in times cover a two-volunteer door well. The pages describe sync happening "as long as there is an available data connection", and we found no public information on whether scanning works with no signal, on badge printing, box-office card sales, walk-in registration, or live attendance figures. 4 5
The Course Provider
Check-in is well documented: iOS and Android apps, search by name or QR scan from ticket email, PDF or Apple Wallet, several devices syncing to my admin panel, Bluetooth scanner support, duplicate warnings, and timed exports of who checked in when. The documented sync only works while a data connection is available, and I found no public information on offline scanning, live attendance figures, badge printing, box office sales or attendance certificates for my courses. 4
The Revenue Accountant
Four check-in versions — web, iOS, Android and Badgy — cover QR scanning from the ticket email, PDF or Apple Wallet plus name search, sync automatically across multiple devices, warn on duplicate scans, accept a bluetooth barcode scanner, and support multiple lists per day or ticket type with time-stamped exports of who checked in. But I found no public information on badge printing, box office or on-site card sales, walk-in registration, entrance or time-slot access rules, live attendance figures, or offline scanning. 4
The Data Protection Officer
The check-in app ships as web, iOS, Android and Badgy versions, scans QR codes from ticket email, PDF or Apple Wallet, syncs across several devices, and supports Bluetooth scanners with duplicate-scan warnings and spreadsheet exports including check-in times. We found no public information on offline operation, box office sales on site, attendance certificates or live door figures; badge printing appears only as a private beta sign-up. 4 5
The Skeptic
Check-in is unusually well documented: iOS, Android and web apps plus a Badgy version, QR scanning from the ticket email, PDF or Apple Wallet, name search, lists per day and per ticket type, automatic multi-device sync, a Bluetooth barcode scanner, duplicate-scan warnings and spreadsheet exports with check-in times. We found no public information on badge printing, box-office sales, card terminals, walk-in registration or offline behaviour, and the web version is stated not to support QR scanning. 4 5
Attendee data & the customer relationship
Show reasoningHide reasoning
How this is scored
Who the ticket buyer belongs to: whether the organiser is the controller of attendee data and the platform its processor, or the platform a controller in its own right; whether buyers must create an account on the platform; whether the platform markets other events to the organiser's buyers or lists the event on its own marketplace; consent for the organiser's newsletter collected in the checkout; messages to attendees; attendee data exportable at any time; and deletion and anonymisation after the event.
0 — The organiser receives no attendee data at all; the platform keeps the buyer relationship entirely.
3 — A guest list visible to the organiser; who is controller, the platform's own marketing to buyers, export or deletion are basic or not described.
5 — Attendee data exportable by the organiser at any time, the organiser named as controller with a data processing agreement offered, buyers able to book without a platform account, newsletter consent for the organiser collectable in the checkout, and messages to attendees from the product.
8 — A white-label set-up in which buyers see only the organiser, the platform stated not to market other events to the organiser's buyers (or the opt-out explained), the platform's marketplace listing optional, deletion and anonymisation of attendee data after the event configurable, and attendee data synced to a named CRM or via API and webhooks.
10 — The organiser owns the relationship and can prove it: the controller and processor roles documented for every data flow, no platform account or platform marketing by default, retention set per event and enforced, and a complete export of orders, attendees and answers that a successor tool can import.
The Conference Organiser
The roles are documented plainly: the organiser is the data controller for attendee data with the platform acting as processor, attendee data is exportable at any time as CSV, XLSX, webhooks or through the read/write API, messages can be sent to attendees from inside the product, and personal data is deleted on request. We found no public information on whether buyers can register without a platform account, newsletter consent collected in the checkout, or whether the platform markets other events to our attendees. 5 6 7 8
The Venue Promoter
The roles are stated plainly: for anyone who registers a ticket the platform acts as processor on behalf of the organiser, and attendee data goes out at any time via CSV, XLSX, webhooks or the API. Mail blasts to attendees can be sent from inside the product, so the club can keep mailing its own buyers — my headline need. We found no public information on whether buyers need a platform account, on newsletter consent collected in the checkout, on a data processing agreement being offered, or on whether the platform markets other events to our buyers. 6 7 8
The Course Provider
The roles are stated outright — I am the data controller for my attendees and the platform is the processor — and attendee data is exportable as spreadsheets, by webhook and by API, with mail blasts to attendees from inside the product. I found no public information on whether students can book without a platform account, on collecting my newsletter consent in the checkout, or on an explicit data processing agreement being offered, though a GDPR compliance page and third-party list are published. 1 5 7 8
The Revenue Accountant
The roles are stated plainly — for attendee data Tito acts as processor on the organiser's behalf — and organisers can export via CSV and XLSX, webhooks and API, send mail blasts to attendees in the product, capture a consent statement at order and ticket assignment, and publish a per-event data protection page. But I found no public information on a data processing agreement being offered, whether buyers can book without a platform account, platform marketing to the organiser's buyers, or configurable deletion and anonymisation after the event beyond deletion on request. 7 8 6
The Data Protection Officer
The privacy terms state plainly that Tito acts as processor for attendee data on behalf of the organiser as controller, and attendee data can leave via CSV and XLSX exports, the API and webhooks, with mail blasts to attendees and a per-event public data protection page. We found no public information on platform marketing to the organiser's buyers, an optional marketplace listing, booking without a platform account, or newsletter consent collected in checkout. 5 7 8
The Skeptic
The roles are stated outright — organisers are the data controller and Tito the processor for attendee data — with export via CSV, XLSX, API and webhooks and mail blasts to attendees from inside the product, so the relationship looks genuinely the organiser's. But data is retained as long as the account is active with deletion only on request, and we found no public information on per-event retention or anonymisation settings, on whether buyers must create platform accounts, on marketplace listing, or on platform marketing to an organiser's buyers — precisely the points where I have been burned before. 6 7 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where attendee, order and payment data are hosted, and who the subprocessors are (hosting, payment providers, email delivery, analytics, support). Independently sourced by the sovereignty pipeline; attendee lists show who goes where and when, and a conference list holds names, employers and dietary or accessibility answers, so the whole chain counts, not only the database.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (payments, email, analytics, support) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, a self-hosted or on-premises option or data export and deletion documented, and certifications published with their scope rather than implied.
The Conference Organiser
The contracting entity is Team Tito Limited of Dublin, with company number and Irish VAT number published, all data-hosting services run on Amazon Web Services in Ireland, and personal data is stored and processed in the EEA; the third-party list is published and names AWS and Intercom, though the captured list appears cut off and Intercom is a US-headquartered provider. A published security policy, penetration tests every two years with interim tests every six months, and breach notification to affected individuals are stated; we found no public information on a published data processing agreement or ISO 27001 and SOC 2 certifications. 6 7 8
The Venue Promoter
The contracting entity is Team Tito Limited in Dublin, registered in Ireland with company and VAT numbers, all data-storing services are hosted by Amazon Web Services in Ireland, and personal data is processed in the EEA, with a published third-party services list. Intercom — flagged as a US-headquartered provider — handles support and messaging, Google Analytics cookies are set, and the captured provider list is cut off, so parts of the chain run outside the EU without a stated safeguard. We found no public information on security certifications or a published data processing agreement. 6 7 8
The Course Provider
The contracting entity is Team Tito Limited, registered in Ireland with a Dublin address, company number and VAT number published, and all data-hosting services run on Amazon Web Services in Ireland within the EEA. The chain runs partly through non-EU providers without a stated safeguard — Intercom, a US-headquartered provider, handles support and messaging and Google Analytics cookies measure visitors — and the third-party list I read appears cut off, with no ISO 27001 or SOC 2 certification stated. 6 7 8
The Revenue Accountant
Team Tito Limited is registered in Dublin with company number and Irish VAT number published, all data-storing services run on Amazon Web Services in Ireland, the EEA is named for storage, and a third-party services list is published. But the support and messaging chain runs through US-headquartered Intercom alongside Google Analytics cookies without a stated safeguard, the provider list is cut off in the capture, and I found no public information on a data processing agreement or ISO 27001/SOC 2 certification — penetration testing every two years with interim tests every six months is described instead. 6 7 8
The Data Protection Officer
Contracting entity Team Tito Limited is registered in Dublin with an Irish VAT number, personal data is stored in the EEA on Amazon Web Services in Ireland, and subprocessors are named (AWS for storage, the US-headquartered Intercom for support and messaging) with a published third-parties list, breach notification and a stated penetration-test cadence. We found no public information on ISO 27001 or SOC 2 certifications, and no stated safeguard for the US provider in the chain. 6 7 8
The Skeptic
Team Tito Limited is an Irish company with published company and VAT numbers, services sit on Amazon Web Services in Ireland within the EEA, and a third-party list, security policy and regular penetration tests are published. The captured provider list is cut off mid-way, already shows Intercom for support alongside Google Analytics cookies, and no ISO 27001 or SOC 2 certification is stated, so parts of the chain run through US providers without a stated safeguard and the full chain is not visible. 6 7 8
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether an organiser can compute the real cost of an event from public pages alone: the fee per ticket or per registration (fixed, percentage or both), payment processing fees, whether fees are charged to the organiser or added to the buyer's price, free events, subscriptions or credit packs, payout and refund fees, add-ons (seating, white label, badges, box office), hardware rental, minimums and term, and VAT on the fees.
0 — No public prices at all; every organiser is a sales call.
3 — A starting price or "free for free events" exists, but the fee for paid tickets, payment fees or who pays them is unclear.
5 — The fee per ticket and the payment processing fees are public with the main inclusions, but at least one commonly needed piece (refund fees, white label, seating, box office, hardware) is unpriced or "on request".
8 — Every fee published with its rule (per ticket, percentage, cap), the share paid by buyer and organiser stated, add-ons and hardware priced, payout and refund fees listed, and VAT treatment of the fees stated.
10 — Complete price computability: the cost of an event derivable for a given ticket price, ticket count and payment mix, with every add-on, hardware, support and payout fee and the cancellation and data-return terms published.
The Conference Organiser
The pricing page gets me close to a real cost for the congress: 3% Per Ticket with the cap worked through as a flat €25 above €833.33, 2.5% for charity and non-profit organisations, free events Free, gateway fees at 2.9% + 30¢ with US Stripe pricing as the example, fees quoted excluding VAT, and a fee calculator giving a net-profit estimate with Stripe. What stops full computability is that we found no public information on whether the fee is charged to the organiser or the buyer, refund or payout fees, or pricing for add-ons such as the Badgy integration. 6
The Venue Promoter
From the pricing page alone I can cost most of a night: "Tito Fees 3% Per Ticket", a charity and community rate of "2.5%" on application, the per-ticket fee capped at "€25" above "€833.33", free events free, no credit card to start, gateway fees of "2.9% + 30¢" as a US Stripe example with PayPal available, fees quoted excluding VAT, and a calculator that estimates net profit with Stripe. What I still cannot compute is my real question for a twelve-euro ticket: we found no public information on whether the fee can be shifted onto the buyer's price, on refund fees, or on add-on and hardware pricing. 1 6
The Course Provider
The pricing page is honest and mostly computable: 3% per ticket with the cap set at €25 above €833.33, a 2.5% rate for charities, free events free, gateway fees shown by example at 2.9% + 30¢ for US Stripe, fees quoted excluding VAT, and even a fee calculator with a net profit estimate. What I could not find is whether the fee falls on me or my students, and prices for refund handling, white label or any hardware. 6
The Revenue Accountant
The 3% per-ticket fee is published with its rule and cap — €25 above €833.33 — alongside a 2.5% rate for charity, community and non-profit organisations, free events free, a no-credit-card trial, fees quoted excluding VAT with local VAT applying, and a calculator estimating net profit and the fee breakdown with Stripe, which lets me price most events from public pages alone. But I found no public information on whether fees can be passed to the buyer, refund fees, or pricing for add-ons and hardware, so the full cost of an event is not computable. 6
The Data Protection Officer
The pricing page publishes the '3% Per Ticket' fee with a '€25' cap and a worked example, a 2.5% charity rate, free events at no charge, a Stripe transaction-fee example of '2.9% + 30¢', fees 'quoted excluding VAT', and a profit calculator. We found no public information on refund fees, add-on and hardware pricing, or whether fees are charged to the organiser or added to the buyer's price. 6
The Skeptic
Public and clear: a 3% per-ticket fee capped at €25 on paid plans for tickets above €833.33, a 2.5% charity rate, free events at no charge, a Stripe example of 2.9% + 30¢, the statement that fees are quoted excluding VAT, and even a profit calculator with a fee breakdown. Not stated: whether the organiser or the buyer pays the fee, refund fees, and prices for extras such as Badgy, which sits in private beta — so the real cost of an event cannot be computed from these pages alone. 1 5 6
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Tito
Is Tito European?
Yes. whats-best.ai classifies Tito as EU-Made.
Where does Tito store data?
The default storage location for customer data is not stated on the vendor’s pages as of 1 Nov 2026. The vendor’s pages mention Ireland and the EU as hosting locations, per the vendor’s page captured 29 Oct 2026.
Does Tito have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to Tito?
As of 3 Nov 2026, the panel rates pretix (3/5), Converia (3/5) and doo (3/5) highest among the other 13 Event Registration & Ticketing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is pretix (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Tito alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 6 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage ti.to Checked 29 Oct 2026 Details →
- 2 Help article (embeddable widget) help.tito.io Checked 29 Oct 2026 Details →
- 3 Help article (VAT in the EU) help.tito.io Checked 29 Oct 2026 Details →
- 4 Help article (check-in) help.tito.io Checked 29 Oct 2026 Details →
- 5 Developer documentation ti.to Checked 29 Oct 2026 Details →
- 6 Pricing page ti.to Checked 29 Oct 2026 Details →
- 7 Privacy policy ti.to Checked 29 Oct 2026 Details →
- 8 Data protection / gdpr page help.tito.io Checked 29 Oct 2026 Details →
- 9 Terms of service — found from the homepage ti.to Checked 1 Nov 2026 Details →