Back to marketplace ↗

PRIVACY · TRANSPARENCY · CONTROL

Privacy
Notice.

A plain-language explanation of what we collect, why we need it and the choices available to you.

Effective
18 October 2026
Controller
UOL Marketplace
Contact
support@uolmarketplace.com
01

Who we are

UOL Marketplace is an independent student ticket-resale marketplace founded and operated by Akshat Kashyap as a sole trader. It is built for verified students at six London universities to list, offer, buy and sell tickets for student nights.

For UK data-protection purposes, UOL Marketplace determines how and why personal information handled through the Service is used and acts as the data controller. Privacy questions can be sent to support@uolmarketplace.com.

02

Information we collect

Account and verification

University email, university, display name, password hash, verification and password-reset records, account dates, the timestamp of your 18+ confirmation and security status. We do not collect a date of birth for ordinary account creation and never store a readable copy of your password.

Marketplace activity

Listings, selected event and tier, price, face value, offers, orders, payment status, seller profile statistics, ratings, reports, written evidence, optional supporting images or videos, file metadata and moderation decisions.

Ticket files

The uploaded PDF, file hashes, extracted event and tier indicators, structural fingerprints, barcode hashes, scan results and warnings. A ticket may also contain the original buyer's name or other information printed by the issuer.

Payments and payouts

Stripe customer, checkout, payment, connected-account, application-fee and payout identifiers; a temporary two-minute reservation timestamp; transaction status; payout eligibility and request timestamps; and limited processing or error records. Stripe receives card, identity and bank-account details directly; UOL Marketplace does not store full card or bank-account credentials.

Technical, communications and aggregate analytics

Session identifiers, essential cookie data, request and security information, messages sent through support, transactional-email delivery status, and aggregate counts and averages derived from account, listing and transaction records. These may include sign-ups by university, live listings, completed orders, venue demand, average sold prices, purchase day and time patterns, ticket-tier demand, repeat-buyer share and refund or report rates.

We obtain most information directly from you. Public event title, venue, dates, organiser, description, age restriction, last-entry time, address and entry requirements may also be retrieved from Fatsoma so users can see relevant event rules before listing, offering or buying. Transaction status comes from service providers such as Stripe.

03

How we use information

  • create, verify and secure accounts;
  • publish listings and display seller profiles;
  • check that a PDF appears to match the selected event and ticket tier;
  • detect duplicate, malicious or suspicious uploads;
  • process checkout, controlled ticket delivery, reports, refunds and seller payouts;
  • send verification codes, receipts, accepted-offer alerts and security messages;
  • moderate the marketplace, enforce our Terms, prevent fraud and comply with law;
  • produce restricted, aggregate operational statistics such as total sign-ups, university mix, live listings, completed orders, venue and ticket-tier demand, sold-price averages, purchase timing, repeat-buyer share and service health rates; and
  • diagnose faults and improve the reliability and usability of the Service.

Seller release timing is applied automatically from order and event records: the Service checks whether 24 hours have passed since the recorded event start and whether an open report, reversal or compliance hold exists. If the order is eligible, it requests the net bank payout from the seller's connected Stripe account. This rule does not analyse personal characteristics or make an admission or refund decision; disputed orders remain subject to human review.

We do not use ticket contents to build advertising profiles. We do not send marketing unless you have been given a clear choice where required.

04

Lawful bases

Contract

To create and manage your account, provide listings and offers, process orders, deliver a purchased ticket and administer payouts.

Legitimate interests

To protect users, prevent fraud and duplicate tickets, secure the Service, moderate activity, resolve disputes, improve reliability and understand aggregate service adoption using existing operational records—after considering necessity, users' rights and their reasonable expectations.

Legal obligation

To keep required financial records, respond to lawful requests and meet consumer, payment, tax or crime-prevention duties.

Consent

For optional marketing or non-essential tracking if either is introduced. Consent may be withdrawn at any time without affecting earlier lawful processing.

Some information is required to provide the Service. Without a supported university email we cannot verify an account; without transaction and ticket information we cannot list, deliver or protect an order.

05

Sharing and processors

We share only what is reasonably necessary with:

  • Cloudflare, for website delivery, database, private ticket-file storage and the scheduled settlement check;
  • Stripe, for checkout, fraud tools, identity checks, connected seller accounts, transfers and bank payouts;
  • Resend, for verification and service emails;
  • Cloudmersive, where enabled, for malware, document and barcode analysis;
  • professional advisers, insurers, auditors or prospective business transferees under confidentiality; and
  • courts, regulators, payment partners, law enforcement or event organisers where disclosure is required by law or reasonably necessary to investigate fraud or a ticket complaint.

Stripe processes purchases in the platform payment flow. After the protection window and release checks, UOL Marketplace transfers eligible net seller proceeds to the seller's connected Stripe account; Stripe then handles onward bank payout. Stripe determines balance availability and bank-arrival timing. A connected account's first payout may take approximately 7–14 days after its first successful payment while Stripe completes its initial availability and verification process. Later timing may still be affected by weekends, bank holidays, reviews and the receiving bank.

Buyers see the seller's display name, university, join date, completed sales and rating. We do not display a user's university email or payment details to another user.

Some providers may process information outside the UK. Where required, transfers are covered by an adequacy decision, recognised contractual safeguards or another lawful transfer mechanism. You may ask us for more information about applicable safeguards.

06

Security and ticket PDFs

We use encrypted connections, hashed passwords, hashed session tokens, restricted private storage, access controls, duplicate hashes, rate limits and payment-provider security controls. Ticket PDFs are not publicly addressable. After payment, the fulfilment copy is released only to the authorised buyer.

Automated checks are the default. They examine file structure, embedded content, malware indicators, event name and date matches, conflicting tier wording, duplicate fingerprints and hashed barcode identifiers. A safe PDF is held for restricted manual review when its event name or date does not match, when it clearly names a different tier from the seller's selection, when another signal appears unusual, or when the barcode scanner cannot reach a reliable result. Missing or unclear tier wording and venue wording do not by themselves prevent automatic approval because issuer PDFs may omit or abbreviate them. Immediate automated rejection is reserved for an invalid or unsafe file, a confirmed duplicate, or a PDF that at least two successful scanner passes confirm has no readable barcode or QR code. Users may contact support if they believe a decision was wrong. We do not use solely automated processing to make decisions that produce legal or similarly significant effects.

Manual checks, complaint decisions and refunds are handled through the restricted admin portal. Only authorised administrators can preview a ticket awaiting a manual decision, and each preview is recorded. There is no administrative download control. When the decision is saved, that temporary review object is deleted and review access ends. If approved, a separate sealed fulfilment object remains because it must be delivered to a future buyer. After a sale, an administrator may preview the exact PDF delivered to the buyer only while a buyer report is open and only to decide that report; each preview and decision is recorded. Resolving the report closes that access.

A buyer may optionally attach relevant images or short videos to a report. Supported files are checked by their actual file signature, restricted by type, number and size, stored in private object storage and served only through an authenticated owner-only review route while the report is open. Users should not upload unrelated people, full payment details or other material they do not have the right to share.

The restricted analytics portal receives grouped counts, rates and averages only. It does not return names, emails, IP addresses or device identifiers and does not provide a user-level drill-down. University, sign-up, venue, ticket-tier, price and purchase-timing statistics are derived from records already needed to operate accounts, listings and orders; they are not generated through third-party behavioural tracking.

No internet service is completely secure. If you believe your account or ticket has been exposed, contact us immediately and change any reused password elsewhere.

07

Retention

  • Email-verification and password-reset codes are designed to expire after 10 minutes.
  • Standard login sessions are designed to expire after seven days and may be revoked earlier. Administrator sessions also require a recent email security code and expire after 12 hours.
  • An unfinished checkout reserves a ticket for up to two minutes. When the hold expires, the Stripe checkout is expired and the pending marketplace order is deleted when the release is processed; limited provider and security logs may remain for fraud prevention, troubleshooting and legal compliance.
  • A rejected ticket file is deleted when the rejection is saved. For a manually approved listing, the temporary review object is deleted immediately after the decision and replaced by a sealed fulfilment object that administrators cannot browse through the review queue. An unsold ticket PDF is automatically removed 30 days after its event where there is no order or legal hold.
  • The sealed fulfilment PDF and scan record are kept only while needed to advertise and deliver the ticket, operate the event reporting window, resolve an open report, respond to a payment chargeback or complete a necessary fraud investigation. The exact delivered PDF may be viewed by an authorised administrator only during an open buyer report. When an order is complete and there is no open report or legal hold, the automated retention process removes the ticket PDF after 180 days from the event; transaction records may be retained separately.
  • Images and videos attached to a report remain available while the report is open and are removed by the automated retention process 180 days after resolution, unless a legal hold, chargeback or regulator request requires longer retention.
  • Transaction, payout, complaint, access-log and accounting records may normally be retained for up to six years after the relevant transaction or resolution where needed for legal claims, tax, accounting, accountability and fraud prevention.
  • Account information is kept while the account is active and afterwards only for the period needed to close transactions, meet legal duties and prevent repeat abuse.

We review retention by purpose and delete or anonymise information when it is no longer reasonably needed. A legal hold, active dispute or regulator request may require longer retention.

08

Your rights

Depending on the circumstances, you may have the right to access personal information, correct it, ask for erasure, restrict processing, receive portable information, object to processing and withdraw consent. These rights are not absolute—for example, we may need to retain order records where the law requires it or a dispute remains open.

A signed-in user can select Delete account on the account page and confirm the request with their password. Deletion is paused while a payment, payout, dispute, reservation or ticket check is still open. Once completed, the profile, sign-in credentials, sessions, open offers, unsold listings and their PDFs are removed or anonymised. Completed transaction, payout, fraud-prevention, dispute and accounting records may remain for the retention periods above, but are no longer attached to an active public profile.

YOUR RIGHT TO OBJECT

You may object to processing based on legitimate interests. Tell us why the processing affects you; we will stop unless we have compelling lawful grounds or need the information for legal claims. You may always object to direct marketing.

Send requests from your verified email to support@uolmarketplace.com. We may ask for proportionate information to confirm identity and normally respond within one month.

09

Cookies

UOL Marketplace currently uses an essential uol_session cookie to keep verified users signed in and protect authenticated actions. It is HTTP-only, secure, uses SameSite controls and is designed to expire after seven days, or 12 hours for an administrator session. Because it is strictly necessary to provide account access, it does not require optional-cookie consent.

We do not currently use advertising or analytics cookies. The internal analytics portal derives aggregate statistics from existing operational database records. If optional analytics or marketing technologies are introduced, we will update this notice and request consent where required before setting them.

10

Age requirement

The Service is for people aged 18 or over and is not directed at children. A university email does not establish age. New users must separately confirm that they are at least 18, and we record when that confirmation was made. We do not normally collect a date of birth. If you believe a child has provided information, contact support so we can investigate and delete it where appropriate.

11

Contact and complaints

Start by contacting support@uolmarketplace.com with the subject “Privacy”. Include the verified account email and enough information to understand the request, but never send a password, one-time code or full payment details.

If you remain unhappy, you have the right to complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint ↗. We would appreciate the opportunity to address the concern first.

Instagram is suitable for general questions only. Send privacy and account requests by email.