This notice explains how we handle personal data when you use TM360-Tickets. It covers:
- Clubs — grounds, clubs, leagues and others who license the platform.
- Ticket buyers and attendees — people who buy or are issued tickets through an club’s shop.
- My Tickets wallet users — people who store tickets in the TM360° My Tickets wallet.
1. Who we are
TM360-Tickets is software licensed by TM360 Limited (trading as TM360°), tm360.uk. We provide the ticket shop software and the My Tickets wallet.
We are not the ticket seller for fixtures listed by clubs. Ticket money is taken by the club through their own Stripe account. We do not receive, hold or pay out ticket funds.
Privacy contact: hello@tm360.uk
2. Who is the controller?
This depends on the data.
Club accounts
For your club account, billing, support and how you use the platform, TM360° is the controller.
Fixture orders (shop)
For the ticket sale itself — what you bought, for which fixture, at what price — the club named on the fixture page is the controller. They sell the ticket. TM360° is their processor for hosting the shop, checkout hand-off to Stripe, ticket delivery into the wallet, scanning and club support.
My Tickets wallet
If you create or use a My Tickets wallet, TM360° is the controller of the wallet account and of:
- your name
- your email address
- your contact telephone number, if you provide one
Those details belong to the wallet relationship with TM360°. We use them to give you a single place to hold tickets, receive ticket and service messages, and recover access.
A ticket sitting in My Tickets may therefore be linked to two controllers:
- TM360° for the wallet identity (name, email, phone)
- the club for the fixture order
Payments
Card and wallet payments are handled by Stripe for the club. Stripe has its own privacy notice. We do not store full card numbers.
Website enquiries
If you only browse tm360.uk or send a sales enquiry, TM360° is the controller of that enquiry.
3. Data we use
Clubs
- Name, organisation, role, email, phone
- Login details and security fixtures
- Fixture listings, ticket types, pricing, capacity
- Licence type (Member / Fixture / Season), invoices, usage fees
- Stripe connected-account identifiers (not ticket payouts)
- Support messages
- Device, browser and approximate location used to access the dashboard
My Tickets wallet (TM360° as controller)
- Name
- Email address
- Contact telephone number, if populated
- Wallet login / authentication data
- Tickets stored in the wallet and related display data (fixture name, date, ticket type, barcode / QR)
- Device data needed to keep the wallet secure
- Preferences (for example notifications)
If name, email or phone is not populated in the wallet, we do not treat a wallet profile as complete. Checkout may still collect those fields for the club’s order.
Ticket buyers — fixture order (club as controller; we process it)
- Order details, ticket type, quantity, face value, discounts
- Fixture, ground and entry data
- Delivery details if the club collects them
- Marketing preferences the club asks for
- Scan / entry timestamps if the club uses scanning
- Limited technical data (IP, device, checkout errors) needed to run checkout securely
Special category data
We do not seek health or accessibility data as a standard field. If an club adds a custom question (for example access requirements), they are the controller of that answer and must have a lawful basis. We only store it as part of their form responses.
4. Why we use it
Clubs — TM360° as controller
| Purpose | Lawful basis |
|---|---|
| Create and run your account | Contract |
| Provide the shop, scanning and support | Contract |
| Charge licence and usage fees | Contract / legitimate interests |
| Security, fraud prevention, abuse | Legitimate interests / legal obligation |
| Improve the product (aggregated or limited analytics) | Legitimate interests |
| Service messages, outages, material term changes | Contract / legal obligation |
| Optional product news | Consent, or legitimate interests with opt-out |
My Tickets wallet — TM360° as controller
| Purpose | Lawful basis |
|---|---|
| Create and maintain your wallet | Contract |
| Show tickets you have been issued | Contract |
| Use name, email and phone (if provided) to identify you, send ticket and service messages, and recover the wallet | Contract |
| Security and fraud prevention | Legitimate interests / legal obligation |
| Optional wallet / product news from TM360° | Consent, or legitimate interests with opt-out |
We do not sell wallet contact details.
We do not give clubs a marketing list of all My Tickets users. An club only receives the buyer data for their fixture, as controller of that order.
Fixture orders — club as controller
| Purpose | Typical lawful basis (club) |
|---|---|
| Sell and deliver the ticket | Contract |
| Identify you at the door | Contract / legitimate interests |
| Refunds, postponement, cancellation | Contract / legal obligation |
| Fixture operations and safety | Legitimate interests / legal obligation |
| Club marketing | Consent, or soft opt-in where the law allows |
5. Where wallet data comes from
Name, email and phone in My Tickets may be:
- entered by you when you create or update the wallet
- captured at checkout and written into the wallet if you use or create My Tickets at purchase
- updated by you later in wallet settings
You can correct wallet name, email and phone in My Tickets. Changing wallet details does not automatically change the name on a ticket already issued for an club’s fixture; that order stays with the club unless they agree a change.
6. Who we share data with
- The club of an fixture you bought — order and ticket data they need to run that fixture. Not your full wallet history with other clubs.
- Stripe — payment for the club.
- Hosting, email, SMS and support providers we use to run TM360-Tickets and My Tickets, under contract.
- Professional advisers and authorities where the law requires it.
- A buyer of our business, if we ever transfer the platform, under the same kind of protections.
We do not sell personal data.
7. International transfers
If a supplier stores data outside the UK, we use a lawful transfer tool (UK adequacy or UK IDTA / addendum) where required.
8. How long we keep it
- Club accounts and invoices: life of the account plus up to 6 years for tax and contract records.
- My Tickets wallet profile (name, email, phone): while the wallet is open, then a short period after closure unless we must keep it for security or legal reasons.
- Tickets in the wallet: while useful for entry and a reasonable period after the fixture (typically up to 2 years unless the club’s records require longer processing).
- Fixture orders: retained for the club as their processor for the period they instruct, or our default of 2 years after the fixture if they set none.
You can ask us to close a My Tickets wallet. Closing the wallet does not delete the club’s order record for fixtures you already bought.
9. Your rights
UK GDPR rights: access, correction, deletion, restriction, objection, portability, and withdrawal of consent where we rely on it.
- Wallet name, email and phone — request these from TM360° (we are the controller).
- A specific ticket purchase, refund or fixture communication — request these from the club first (they are the controller). We will help them if needed.
You may complain to the Information Commissioner’s Office: ico.org.uk.
10. Children
TM360-Tickets is not aimed at children creating their own wallet. If an club sells tickets for an under-18 fixture, they must collect only what they need and comply with the law. A parent or guardian should manage a wallet used for a child’s ticket.
11. Cookies and similar tech
We use essential cookies to run login, checkout and the wallet. Analytics or marketing cookies, if used, are described in a cookie banner and can be refused where they are not essential.
12. How to contact us
My Tickets wallet / TM360° platform: hello@tm360.uk
A ticket, refund or fixture: the club named on the ticket and fixture page.
TM360 Limited (trading as TM360°) · tm360.uk