Updated 5 September 2026
Who is responsible
Patchworks AI Consulting Ltd operates Season Ticket Sharing and is the controller of the personal information described here. Registered in England and Wales, company number 16144699. Registered office: 14 David Mews, London, United Kingdom, W1U 6EQ.
For support or privacy requests, contact tickets@patchworks.ai.
What we use and why
| Information | Purpose |
|---|---|
| Email, sign-in identifiers and display name | Let you sign in, receive invitations and appear in your group. |
| Membership, role and seat ownership | Control group access and record season-seat entitlements. |
| Match requests, allocations and seating preferences | Coordinate attendance and apply your group’s allocation rules. |
| Extra-seat offers, notes, terms and decisions | Record gift, cash, credit or swap arrangements and their fulfilment. |
| Notification choices and device push token | Send the app alerts you enable. |
| Security events and technical diagnostics | Protect accounts, preserve record integrity and investigate faults. |
| Support emails and information you include | Answer questions and resolve problems. |
Most information comes from you. Your organiser or another group member may supply your invitation email, seat ownership and information about a shared arrangement. Apple supplies sign-in identifiers if you choose Sign in with Apple.
We use account and group information to perform our contract with you and provide the service you request. We rely on our legitimate interests in securing the service, supporting users and maintaining accurate shared records for security, support and related audit processing. We also use information when needed to meet legal obligations. Optional alerts are under your control in Account and iPhone Settings.
You need an email address and sign-in identifier to hold an account. You can browse this website without an account. Match preferences and extra-seat arrangements are optional; without them, the app cannot coordinate those requests for you.
Who can see it
Your group sees information according to membership and role. Organisers manage invitations, seats and allocations; people involved in an extra-seat arrangement can see its relevant terms and status. Only share notes that are appropriate for those people to read.
Supabase provides app authentication, sign-in email delivery and database hosting. Apple provides optional sign-in and push notifications. Google Workspace handles our support mailbox. Cloudflare hosts and protects this website. These providers process the information needed for their services. We may disclose information when required by law or to deal with abuse and protect users.
Where information is processed
The app’s primary Supabase database is hosted in London. Our providers also operate internationally, including in the United States, so this does not mean all processing stays in the UK. Provider data-processing terms describe applicable international-transfer mechanisms, including standard contractual clauses and the UK addendum where required. You can read the Supabase data-processing terms and Cloudflare data-processing terms, or contact us for information about safeguards applicable to your data.
What we do not collect
The app does not track you across other companies’ apps or websites, sell data, serve advertising, collect precise location, access contacts, process payment credentials, or store ticket PDFs, QR codes or barcodes. Cash, credit and swap terms are records of arrangements: the app does not transfer money or deliver tickets.
Retention and account deletion
Your active account remains until you delete it. Group records remain with the group’s history, including across seasons. There is no automatic end-of-season purge. When deciding whether a historical, security or support record still needs to be kept, we consider whether the group still uses it, whether an arrangement or issue is unresolved, whether it is needed to investigate misuse, and any applicable legal obligation. Contact us to request review or erasure of retained information.
Leaving a group ends that membership. Account deletion removes your active authentication account and notification registrations across groups. Direct account links are removed or detached and display names are replaced in retained shared records. Historical membership references, audit records and group notes may remain; people who know the group’s history may still recognise an arrangement. Deletion therefore does not guarantee that every historical record becomes anonymous.
Signing out disables notification delivery for the relevant device; it is not the same as account deletion. Before deleting an account that owns a group, transfer ownership or archive the group. Open Account and choose Delete Account. See account-deletion help for the additional Apple Settings step if Apple authorisation cannot be revoked automatically.
Your rights
Depending on the circumstances, you can request access, correction, erasure, restriction or a portable copy of your information. Contact tickets@patchworks.ai; we may need to verify your identity.
You can object to processing based on legitimate interests. Explain your circumstances so we can consider your request.
You can complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint. You can also contact the supervisory authority where you live if applicable.
Allocation rules
The app can apply your group’s rules to seat requests and ownership information. These results help organise a group’s match attendance; they do not transfer a ticket. Ask your organiser to explain a result or review an allocation.
This website and invitations
This website includes no analytics, advertising, external fonts or tracking cookies. Cloudflare receives technical request information, such as IP addresses and requested pages, to deliver content and provide security. We do not enable application request logs or analytics.
An invitation page reads the code locally in your browser and includes it in the app link only when you choose to open it. The website does not check membership or accept the invitation. Avoid sharing private invitation links publicly. Never include passwords, sign-in links, invitation tokens or ticket barcodes in a support email.
Changes to this notice
We update this page when the service or its use of information changes. The date above shows the latest update.