Back to matches

RIGA FC FAN TRAVEL

Personal data processing

Version dated 3 October 2026

This policy covers all Riga FC Fan Travel destinations, travel and individual service requests, tickets, supporter registration, your account and related correspondence. It applies to Pafos, Kaunas, Banja Luka and new destinations published on this website.

For data enquiries and to exercise your rightsinfo@gtr.lv

1. Who is responsible

The data controller is Gulliver Travel, travel agency / tour operator, registration No. 40003935619. Address: Blaumaņa iela 16/18, Riga, LV-1011, Latvia. Email: info@gtr.lv. Phone: +371 22306472.

This policy describes processing by Gulliver Travel. Airlines, hotels, insurers and match organisers may act as independent controllers for the data they need to provide their own services.

2. Data collected and its sources

For Cyprus trips, an agent may record the Fan ID and each traveller’s first and last name, date of birth, passport or ID card type and number, and phone number received from the customer. These details are stored with the request to organise the chosen services and are available to authorised agents and the applicant in their account after sign-in. Document numbers are not included in email notifications. The last editor and edit time are recorded; the request retention period also applies to these details.

An agent may upload ticket files to your Cyprus application. They are accessible to the applicant after sign-in and to authorised agents; a service email is sent when files are uploaded. To follow up on ticket delivery, we record the number and time of your requests to open and download each file. These records do not prove that a file was read or saved on your device. For flight confirmations and itinerary programmes we also record each traveller’s document open requests and clicks on the Print / Save as PDF button. A click does not prove that a PDF was saved. Files and these records follow the retention period of the relevant application.

At the customer’s request, an agent may enter a request received by email. Its source, the agent and entry time are recorded; website form confirmation is not recorded on the customer’s behalf. The request becomes available in the account after the same email is verified with a one-time code.

After buying tickets for the Kaunas match, the account holder or agent enters each supporter’s sector, row and seat. It is linked to the registered supporter for identification and matching to their stadium seat. It is available to the account holder and authorised agents, included in the list for the match organiser, and retained for the same period as the registration.

You provide data through website forms and contact with your travel agent. Website requests require your first name, last name, verified email, phone, destination and selected services with quantities. Preferences, hotel city and category are recorded where relevant. Kaunas match registration collects each of up to 50 supporters’ first and last names, date of birth, passport or ID card type and number, and phone number. The website request is linked to the submitter’s verified email. The document number is used to check registration and identify the supporter; no document copy is required.

Accounts store a verified email, creation date and linked requests. Requests record the time you confirm the form, review status and agent actions. Sign-in and abuse prevention use one-time codes, session data and hashed email/IP identifiers. Codes and session tokens are stored as hashes in the database. The hosting service may also process technical request logs.

Website forms do not accept passport copies or payment card details. If your chosen service requires additional passport data, your agent will separately explain what is needed, who receives it and how to send it. Do not enter medical or other sensitive information in the free-text field. If you provide someone else’s data, tell them about this policy and ensure you are entitled to act on their behalf.

3. Purposes and legal bases

Requests, bookings and travel correspondence: processing is necessary for steps you request before entering a contract and to deliver agreed services (GDPR Article 6(1)(b)). Without mandatory contact details we cannot process your request; additional preferences are optional.

An account is created and used at your request for sign-in and handling requests; the necessary processing of your email is based on providing this service (Article 6(1)(b)). You may request account deletion. Existing bookings and data that must be retained on another basis are considered separately. If consent is needed for a new optional purpose (Article 6(1)(a)), we will request it separately.

Supporter identification, registration checks, website protection and abuse prevention relate to legitimate interests in match safety and a secure service (Article 6(1)(f)), taking supporters’ rights and interests into account. An organiser’s or UEFA’s requirements are not, by themselves, described as a statutory obligation. Where specific data is required by law, Article 6(1)(c) applies and the basis is communicated for that operation.

The request-form checkbox confirms that you have read this policy and that your details are accurate. It is not marketing consent. These forms do not subscribe you to advertising emails.

4. Who may receive data

Authorised Gulliver Travel staff have access. A request notification is sent to the agent’s work email. Document numbers are available to authorised agents and the relevant applicant after sign-in; they are not included in notifications or supporter emails.

To the extent needed for your chosen service, data may be shared with an airline, hotel, carrier, insurer, ticket seller, Riga FC, the host club, stadium or match organiser. For the away section this may include a registered supporter list containing names, dates of birth, document types and numbers, and phone numbers. Hotel or insurance information is not shared with the match organiser merely because it appears in your request.

The website uses OpenAI Sites and Cloudflare infrastructure for hosting and the request database, and Resend for sign-in codes, notifications and ticket purchase code emails. These services process data needed for their functions. Data is provided to public authorities where an applicable lawful basis exists.

5. Processing outside the EEA

Some technical suppliers and travel service providers may be outside the European Economic Area. Do not assume that all website data is stored only in the EU. Resend identifies the United States as its primary processing location and provides international transfer mechanisms, including Standard Contractual Clauses, in its data processing agreement.

For bookings outside the EEA, the recipient and country depend on the service selected. Before such a transfer, your agent must provide the necessary information about the recipient and applicable transfer basis. You can ask Gulliver Travel at info@gtr.lv about safeguards and how to obtain a copy.

6. Retention and deletion

The general retention rule for this project’s requests and registration lists is no longer than six months after the relevant match or the end of the trip, unless there is a separate basis to retain some documents longer. Current form deadlines are: Pafos travel requests - 23 April 2027; Kaunas match registration - 26 May 2027. For new destinations, a specific deadline is set on the same basis when data collection opens.

Your verified email and account record are retained while the account is used to provide the service, or until a justified deletion request. Request history has its own retention periods and must not remain indefinitely with the account. Sign-in codes are valid for 10 minutes and sessions for up to 7 days; these are access validity periods, not promises about deletion of all technical logs.

Gulliver Travel is responsible for deleting or anonymising data after its retention period, including working copies, exports and emails. Deleting a database record does not itself erase copies in mailboxes or held by recipients. Contract, accounting and dispute documents may be retained separately to the extent and for the period required by law or the defence of rights. On request, we will explain which data is retained, why and how the period is determined.

7. Cookies and security

Sign-in uses necessary cookies: __Host-riga_login (up to 10 minutes) and __Host-riga_session (up to 7 days). They verify sign-in and associate requests with your account. Hosting may use additional technical cookies for its own authentication and protection. The site does not load visit analytics services or advertising pixels.

Access to requests is restricted: users see their own requests, while agents pass a separate access check. Sign-in codes have expiry and attempt limits. HTTPS sign-in cookies use Secure, HttpOnly and SameSite. These measures reduce risk but do not guarantee absolute security. Do not share sign-in codes.

8. Your rights and how to contact us

Where provided by the GDPR, you may access and obtain a copy of your data, correct errors, request erasure or restricted processing, object to processing based on legitimate interests and receive data in a portable format. You can withdraw consent without affecting the lawfulness of processing before withdrawal.

Email info@gtr.lv from your account email, stating your request and booking reference if available. We may ask for proportionate identity verification to avoid disclosing data to others. We normally respond within one month; where a lawful extension applies, we will explain it and the reasons within the first month.

You may complain to Datu valsts inspekcija: Elijas iela 17, Rīga, LV-1050, Latvia; pasts@dvi.gov.lv; www.dvi.gov.lv, or another competent supervisory authority.

9. Review and policy changes

Ticket purchase codes are sent after an agent reviews the registration. The service does not use profiling or decisions based solely on automated processing that have legal or similarly significant effects on a supporter. Automatic price calculations and email delivery assist with processing requests.

The current version is published here. If purposes, recipients or processing conditions change materially, information must be provided before the new processing; where fresh consent is required, it is requested separately.