TERMS AND CONDITIONS OF USE OF THE “JUDU” APP

CHAPTER I.
GENERAL PROVISIONS

1. The “JUDU” app (hereinafter referred to as the App) is the official mobile platform managed by ME “Susisiekimo paslaugos” (hereinafter referred to as the Company), intended for using the services administered by the Company and other services related to urban mobility.

2. In the App, the App user may:

2.1. purchase a ticket for local (urban) regular bus, trolleybus and regular passenger boat services (hereinafter referred to as a Passenger Ticket / ticket);

2.2. pay the local fee for the use of designated paid parking spaces for motor vehicles in the City of Vilnius (hereinafter referred to as the Local Fee);

2.3. pay for vehicle parking services in parking facilities operated by Municipal Enterprise “Susisiekimo paslaugos” that are regulated by barriers (hereinafter referred to as Closed Parking Facilities), and in parking facilities without barriers regulating entry (hereinafter referred to as Open Parking Facilities) (hereinafter collectively referred to as Parking Facilities);

2.4. pay an unpaid parking local fee according to the relevant notice received from the Company regarding an unpaid local fee for vehicle parking (to pay the “Yellow Slip”);

2.5. use other App options or functionalities, where they are activated and available to a specific App user or service (e.g. public transport route planning, viewing timetables, real-time public transport data, receiving relevant traffic and public transport notifications, etc.).

2.6. The Company has the right to expand, change or discontinue the provision of individual App functions or services by informing App users in the App or by other means provided for in these Rules.

3. These terms and conditions of use of the “JUDU” app (hereinafter referred to as the Rules) establish the procedure for using the App, the terms of use of the services provided in the App, the rights and obligations of App users and the Company, limits of liability, conditions for data processing and other relations related to the use of the App.

4. The Rules are binding on each App user. By using the App, the App user confirms that they have read these Rules, agree to the conditions set out herein and undertake to comply with them.

5. The Rules may be amended unilaterally taking into account requirements established by legal acts, changes in software functionality or other unforeseen circumstances that may affect the functioning of the App, by notifying about the amendments in the App no later than 10 (ten) calendar days before they enter into force, except where it is impossible to provide prior notice of the amendments and the amendments must enter into force immediately due to legal, security, technical or other objective reasons. If the user does not agree with the amendments, they have the right to stop using the App and to acquire and use the Company’s services by other alternative means. If the App user continues to use the App after amendments to the provisions of the Rules, they shall be deemed to have agreed to all amendments to the Rules.

6. The Company, at its discretion and without prior notice, has the right to temporarily restrict or prohibit the App user from using the App for an indefinite period if the App user violates these Rules or legal acts, provides incorrect data, uses the App for unlawful purposes, attempts to disrupt the operation of the App or related systems, or where there is a justified risk of fraud, a security breach or unlawful use of payments. The user shall be informed of the restriction or prohibition on using the App in the App and/or through other contacts known to the Company, except where such notification could harm security, an investigation or the rights of other persons, or is impossible due to other objective reasons.

CHAPTER II.
INTELLECTUAL PROPERTY AND COPYRIGHT

7. The developer and controller of the App is Municipal Enterprise “Susisiekimo paslaugos” (address: Laisvės pr. 10A, 04215 Vilnius, company code: 124644360, tel.: (0 5) 210 70 50, e-mail: [email protected], www.judu.lt).

8. The App, as a computer program, its software (source) code, structure, organisation, interfaces (APIs), architecture, data models and App documentation are objects of copyright protected under the Law on Copyright and Related Rights of the Republic of Lithuania and Directive 2009/24/EC of the European Parliament and of the Council of 23 April 2009 on the legal protection of computer programs, and the author’s, intellectual property and economic rights thereto belong exclusively to the Company. The Company also owns the copyright to the graphic design of the user interface (UI/UX), iconography, audio and visual elements to the extent that such elements are protected under applicable legal acts. The data collected in the App and the contents of the database, including ticket price lists, route timetables, parking facility maps, geographic and graphic data and other structured datasets, belong to the Company.

9. The name of the App, the logo, the “Judu” trademark and other marks used in the App belong to the Company and are protected in accordance with the procedure established in the Law on Trademarks of the Republic of Lithuania and other legal acts.

10. The Company grants the user a non-exclusive, personal and non-transferable right to download, install and use the App for its direct purpose, i.e. to use the services administered by the Company and other services related to mobility in the City of Vilnius. The user agrees not to use the App, its content and the data contained in the App for other purposes that are incompatible with the purpose specified in this clause of the Rules, including for commercial purposes and for the creation of derivative products, and not to use substantial parts of the App database content in a way that would infringe the legitimate interests of the database owner, i.e. the Company, and/or be contrary to the normal use of the database.

11. The Company, at its discretion and without prior notice, has the right to:

11.1. change the design of the App or other information used;

11.2. change, discontinue or offer new Services and functionalities;

11.3. change the ticket activation conditions in the App, including the ticket activation duration.

12. In accordance with the procedure established by legal acts, upon changing ticket prices, the Local Fee or the Parking Fee and/or the conditions for their application, and after informing App users thereof before the deadline specified in Clause 5 of the Rules, to change the ticket price, the amount of the Local Fee or Parking Fee and/or payment conditions.

CHAPTER III.
LIABILITY AND LIMITATION OF LIABILITY

13. Operation of the App:

13.1. The Company makes reasonable organisational and technical efforts to ensure that the App functions properly and securely and is accessible to App users; however, it does not undertake to ensure uninterrupted, continuous or entirely error-free operation of the App.

13.2. The Company does not guarantee that:

13.2.1. the App will operate continuously, without disruptions or technical malfunctions;

13.2.2. the App will be free of software, technical or other errors;

13.2.3. all App functionalities, services or parts thereof will be available at all times or at a specific time desired by the App user;

13.2.4. the App will in all cases meet the individual expectations, needs or specific purposes of use of the App user;

13.2.5. the App will be compatible with all devices, operating systems, software or versions thereof used by the App user.

13.3. The Company has the right to temporarily restrict, suspend or terminate the operation of the entire App or individual functions thereof if this is necessary due to:

13.3.1. scheduled or unscheduled technical maintenance work;

13.3.2. updating, modernisation or testing of the App, information systems or infrastructure;

13.3.3. technical, software, communication or electricity supply disruptions;

13.3.4. cyber incidents, security threats or the aim to ensure the security of the App and App users’ data;

13.3.5. disruptions in the operation of systems, platforms or services managed by third parties;

13.3.6. compliance with lawful instructions of state authorities or requirements of legal acts;

13.3.7. force majeure circumstances;

13.3.8. other objective circumstances that the Company could not reasonably foresee or control.

13.4. Where possible, the Company informs App users in advance about planned restrictions on the operation of the App or technical maintenance work in the App, on the website or by other means of communication chosen by the Company. However, prior notification is not mandatory where the restrictions arise due to emergencies, security incidents or other circumstances beyond the Company’s control.

13.5. Temporary unavailability of the App, unavailability of individual functions or operational disruptions shall not in themselves be considered a breach of the Company’s contractual obligations if they arise due to the circumstances specified in this Chapter.

14. Limitation of liability:

14.1. The Company shall be liable only for losses that arise due to the Company’s intent or gross negligence, except where mandatory legal provisions establish different liability.

14.2. To the extent permitted by applicable legal acts, the Company shall not be liable for:

14.2.1. the operation, availability or security of payment, authentication or other electronic services provided by third parties;

14.2.2. disruptions in the activities of mobile network operators, internet service providers, cloud service providers or other electronic communications service providers;

14.2.3. the operation of systems, platforms or information resources managed by partners or other third parties;

14.2.4. the inaccuracy, incompleteness or incorrectness of data provided by the App user;

14.2.5. damage arising from improper use of the App, use not in accordance with its intended purpose or use not complying with these Rules;

14.2.6. the non-operation or improper operation of the App due to failures of the hardware or software of the App user’s device, improper configuration, uninstalled updates, viruses or other malware;

14.2.7. data lost by the App user if such data are lost for reasons beyond the Company’s control;

14.2.8. indirect losses, loss of income, loss of business opportunities or other indirect consequences, except where such liability arises under mandatory legal provisions.

14.2.9. due to the limitations of GPS technology used in the App user’s device, the quality of communication, device settings, characteristics of the location or other circumstances beyond the Company’s control, the automatic location detection function of the App may be inaccurate, operate improperly or temporarily not operate. Before submitting an order or using any service provided in the App, the App user must check the data automatically determined or selected in the App and make sure that they are correct. The Company shall not be liable for an improperly provided service, losses or other adverse consequences for the App user arising from inaccurate location detection of the App user’s device or from the user’s failure to check automatically determined or selected data, except where such liability arises under mandatory provisions of legal acts.

15. The App user is responsible for:

15.1. the security of the login means, devices and account data used by them;

15.2. the correctness and relevance of the data provided in the App;

15.3. using the App in compliance with these Rules and applicable legal acts.

16. If the App contains links to third-party websites, systems or services, the Company shall not be liable for their content, operation, security, privacy practices or the quality of services provided therein.

17. Force majeure:

17.1. The parties shall be released from liability for the full or partial non-performance or improper performance of their obligations if this was caused by force majeure circumstances.

17.2. Force majeure circumstances shall be deemed to include circumstances that a party could not control, reasonably foresee at the time of conclusion of the contract or avoid the consequences of, including, but not limited to, natural disasters, military actions, riots, epidemics or pandemics, decisions of state authorities, electricity or communications infrastructure disruptions, large-scale cyber incidents and other events of a similar nature.

17.3. A party that is unable to perform its obligations due to force majeure circumstances must inform the other party within a reasonable period about the occurrence of such circumstances and, where possible, their expected duration. The legal consequences and assessment of force majeure circumstances shall be determined in accordance with the Civil Code of the Republic of Lithuania and other applicable legal acts.

CHAPTER IV.
LOGIN TO THE APP

18. A person registering as an App user is identified using the e-mail address provided by the user, to which a link for creating a unique password is sent.

19. The App user may log in to the App by:

19.1. entering their e-mail address and password;

19.2. using the “Google” or “Apple” login interface.

20. After logging in to the App by the methods specified in Clause 19 of the Rules, the App user may activate biometric login in the App settings. It should be noted that the App does not collect, store or otherwise process the App user’s biometric data. Biometric login is carried out using authentication tools provided by the device operating system (iOS or Android), and biometric data are stored exclusively on the App user’s device.

21. The App user’s account is a shared account with the self-service website https://judu.lt/savitarna (hereinafter referred to as the JUDU user account).

22. The App user undertakes to use the App service personally and to ensure the security of their login data so that third parties do not learn the password or PIN code. The App user must ensure that third parties do not have access to their mobile phone. Until proper notice is submitted to the Company about possible unlawful use of the account or App, the App user shall be liable for actions performed using their account, login data or mobile device if such actions were performed due to the App user’s fault, negligence and/or failure to comply with these Rules.

23. The Company, at its discretion and without prior notice, has the right to temporarily restrict or prohibit the App user from using the App for an indefinite period if the App user violates these Rules or legal acts, provides incorrect data, uses the App for unlawful purposes, attempts to disrupt the operation of the App or related systems, or where there is a justified risk of fraud, a security breach or unlawful use of payments. The user shall be informed of the restriction or prohibition on using the App in the App and/or through other contacts known to the Company, except where such notification could harm security, an investigation or the rights of other persons, or is impossible due to other objective reasons.

24. The Company processes App users’ personal data in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data and repealing Directive 95/46/EC (General Data Protection Regulation) (hereinafter referred to as the GDPR), as well as other applicable European Union and Republic of Lithuania legal acts and the Company’s rules.

CHAPTER V.
PRIVACY PROVISIONS

25. The Company processes the App user’s personal data in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data and repealing Directive 95/46/EC (General Data Protection Regulation) (hereinafter referred to as the GDPR), as well as other applicable European Union and Republic of Lithuania legal acts and the Company’s rules.

26. These Rules and privacy provisions provide information only about personal data collected and processed while using the App. More detailed information about other relevant personal data processing conditions of the Company is available in the Privacy Policy published on the JUDU.lt website and in the documents published in the “Personal Data Protection” section.

27. When you use the App functionalities and the services provided therein, your personal data are processed for the purposes and under the conditions specified below:

27.1. For the purpose of selling goods and services in the Company’s website self-service environment and in the App, refunding overpayments and money for returned goods, debt management, administering the use of public transport tickets (JUDU / Vilniečio Card) and performing other related obligations, we collect the following data about you: the service recipient’s name, surname, personal identification number, e-mail address, residential address, telephone number, password, country, city, street and house/apartment number, VAT code, activity certificate number, JUDU / Vilniečio Card number, card validity start date, purchase order data (order date, order confirmation time, payer’s name and surname, order number, payment amount, payment method, bank card number (last four digits), bank card token, token issuer, card network (Visa, Mastercard, etc.), bank account number (if payment is not made by bank card) and date of transfer), public transport ticket (JUDU / Vilniečio Card) usage data (name, surname, e-mail address, JUDU / Vilniečio Card number, card validity start date, ticket ID, ticket price, ticket usage history). Legal bases for processing: Article 6(1)(b) of the GDPR (processing is necessary for the performance of a contract), Article 6(1)(c) of the GDPR (processing is necessary for compliance with a legal obligation to which the controller is subject), Article 6(1)(e) of the GDPR (performance of tasks carried out in the public interest or in the exercise of official authority);

27.2. For the purpose of paying the Local Fee for the use of paid vehicle parking spaces established by the Council of Vilnius City Municipality using mobile network operator services or mobile device applications (the App), we collect the following data about you: the service recipient’s telephone number, telephone device number, name, surname, fee payment notification number, vehicle type, fee amount, payment duration, order creation time, payment start and end time, control check time, order number, location data (area), operator, payment method and payment time, parking zone code and number, vehicle registration number, violation photographs, bank card number (last four digits), e-mail address, mobile network operator. Legal bases for processing: Article 6(1)(b) of the GDPR (processing is necessary for the performance of a contract), Article 6(1)(e) of the GDPR (performance of tasks carried out in the public interest or in the exercise of official authority);

27.3. For the purpose of concluding and performing the carriage contract with passengers who use the App, we collect the following data: telephone number, information about tickets purchased (duration, price), statuses of held tickets, ticket activation time, ticket identification numbers, mobile network operator, order number, telephone device number, passenger control check time, name, surname, e-mail address, VAT invoice number, payment card type, the first six and last four digits of the bank card number, bank account number, payment time, user activity data. Legal basis for processing: Article 6(1)(b) of the GDPR (processing is necessary for the performance of a contract); Article 6(1)(e) of the GDPR (performance of tasks carried out in the public interest or in the exercise of official authority);

27.4. For the purpose of planning the fastest route using the App, we collect location data. Location data are processed only for the purpose of planning the fastest route and are not stored (when used in the public transport section). Legal basis for processing: Article 6(1)(a) of the GDPR (consent of the data subject);

27.5. For the purpose of providing information about the Company’s services and asking for opinions (direct marketing), we collect the following data: the data subject’s e-mail address (for providing information about the services provided), while the personal data of survey participants (when asking for their opinions) are usually not collected. In the case of individual surveys, residential addresses, names of workplaces and other data necessary to achieve the purposes of the survey may be collected. Legal basis for processing: Article 6(1)(a) of the GDPR (consent of the data subject);

27.6. When carrying out personalised advertising on social networks (“Facebook”, “Instagram”, “LinkedIn”) and digital channels (“Google”), we collect your e-mail address. Legal basis for processing: Article 6(1)(a) of the GDPR (consent of the data subject);

27.7. For the purpose of sending notifications to vehicle keepers who voluntarily register on the Company’s self-service portal or in the App and indicate an electronic notification method about the possibility to pay the daily local fee in the amount specified in Sub-clause 11.5 of the Regulations on the Local Fee for the Use of Paid Parking Spaces Established by the Council, approved by Resolution No. 1-127 of the Vilnius City Municipal Council of 13 July 2011, we collect the following data: name, surname, vehicle registration certificate number, vehicle registration number, e-mail address. Legal basis for processing: Article 6(1)(e) of the GDPR (performance of tasks carried out in the public interest or in the exercise of official authority);

27.8. For the purpose of short-term parking of a vehicle in parking facilities administered by the Company, we collect the following data: vehicle type: passenger car, electric vehicle, motorcycle/moped, bus/truck, trailer car, two-wheeled vehicle, bus; vehicle registration number, telephone number, telephone device number, name, surname, e-mail address, VAT invoice number, order creation time, order number, amount paid, period for which payment was made, mobile network operator, payment method, payment time, parking control check time (in the case of Open Parking Facilities), payment card type, bank card number (last 4 digits), parking facility address/name. Legal basis for processing: Article 6(1)(b) of the GDPR (processing is necessary for the performance of a contract);

27.9. For the purpose of carrying out financial operations, account management, accounting, fulfilment of tax obligations and debt management, we collect the following data: name, surname, personal identification number, position, business licence / individual activity certificate number, workplace, signature, e-mail address, telephone number, address, electronic and other communication, where a legal entity is represented – the name and contacts of the legal entity, relationship with the represented person, data contained in the authorisation, contents of public procurement proposals, declarations and contracts, account number, financial, credit or payment institution, data specified in the payment order, VAT payer code (if the person is a VAT payer), data contained in payment documents and declarations, debt information. Legal bases for processing: Article 6(1)(c) of the GDPR (processing is necessary for compliance with a legal obligation to which the controller is subject), Article 6(1)(f) of the GDPR (processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party);

27.10. For the purpose of registration in the App, we collect the following data: e-mail address, name, surname and password. These data are necessary for creating an account and providing the App services. If you wish to receive an invoice for a company, we also collect the company name, address and VAT payer code. Legal basis – Article 6(1)(b) of the GDPR (performance of a contract).

27.11. For the purpose of logging in to the App with a “Google” account, through the “Google” authentication (OAuth) service, we may receive the following data: name, surname, e-mail address and unique Google account identifier. Profile photo data may be technically accessible through the “Google” authentication service; however, the App does not collect, store or process them and does not use them for any purposes. Legal basis – Article 6(1)(b) of the GDPR (performance of a contract).

27.12. For the purpose of logging in to the App with an “Apple” account, through the “Sign in with Apple” authentication service, we may receive the following data: name, surname, e-mail address or a private (pseudonymised) e-mail address provided by “Apple”, and a unique Apple user identifier. The e-mail address is used only for account creation and authentication in the App. The App does not process any additional Apple account data. Legal basis – Article 6(1)(b) of the GDPR (performance of a contract).

28. Please note that payments for the services provided are collected using payment service providers (when paying by bank/credit card) and/or mobile network operators (when paying through the mobile network operator’s invoice).

29. When registering and/or logging in to the App using authentication solutions of other systems (e.g. Google, Apple or others), the App user’s name, surname and/or title and e-mail address are received from the respective data controllers.

30. When a bank or credit card is added (“saved”) in the App, it is first checked, i.e. authorised, to ensure that the card is valid and suitable for use. If this check is successful, you are given the option to pay for services:

30.1. After placing the desired tickets in the cart and confirming the purchase, the payment is automatically charged to the added card.

30.2. When choosing card payment for parking in fee zones and Open Parking Facilities, after starting a parking session the fee is automatically charged to the added card at established intervals.

30.3. In Closed Parking Facilities, payment from the added card is charged only after payment is initiated before leaving the parking facility. After payment, it is necessary to leave the parking facility within 15 minutes; if you do not leave, a new parking session will begin.

30.4. Your additional confirmation or separate consent is no longer requested for each payment.

30.5. It should be noted that the App uses a direct payment charging solution (“plugin”), under which the data of your added (“saved”) card (e.g. card number, expiry date, security code) are transferred to the payment service provider only at the time of initiating a specific payment. For this reason, the Company does not process these card data in its systems – it does not receive, see or store them. The Company receives only information related to the completed payment transaction, including transaction data and limited information about the card used for payment, which is necessary for transaction identification and confirmation of payment for the service.

31. We inform you that, in order to pay for tickets in the App by electronic banking, you will need to authorise the payment. During this process, you will be redirected to your online bank and asked to log in using the chosen authentication tool (e.g. “Smart-ID”, mobile signature, code generator or another method applied by the bank). Electronic banking may be used to pay only for tickets. This payment method is not available for parking services. Also, when making payment for parking in this way, your bank may additionally ask you to confirm the payment transaction using one of the authentication methods it offers. It should be noted that the App uses a direct bank payment solution (“plugin”), under which the data of your added (“saved”) bank account (e.g. account number, identification codes, personal identification information) are transferred to the payment service provider only at the time of initiating a specific payment. For this reason, the Company does not receive, process or store these data in its systems. The Company receives only information related to the completed payment transaction, including transaction data and limited information about the bank account used, which is necessary for payment identification and confirmation of payment for the service. The added payment card is automatically removed from the account after 4 years from the date it was added. If the card expires earlier than 4 years, it remains visible in the account, but it can be used for payment only until the card expiry date. Attempting to pay with an expired card will result in the payment being declined.

32. We receive personal data directly from the App user when they register or log in to their account in the App (including when authentication solutions of other providers are used, e.g. Google, Apple or others). Data are also received when the App user orders the services provided or uses the App functionality.

33. The App is permitted to determine the user’s telephone number and, with the App user’s consent, to obtain the user’s location using the Global Positioning System (GPS), in order to display the App user’s location on the map, thereby enabling the App user to see the nearest public transport stop or parking zone, etc., and also to plan the fastest route (however, location data are not stored). When the App operates using a mobile internet connection, the App uses packet data, which are charged according to the tariffs of the user’s mobile network operator.

34. For the App to obtain and use GPS data, the App user may choose one of several location sharing options: “allow once”, “allow while using the App” or “do not allow” (depending on the operating system of the mobile device, the displayed consent text may differ). The App user may at any time withdraw consent for the App to obtain and use the user’s GPS data in the settings of the mobile device operating system by selecting the location sharing options specified above in this clause. Refusing or withdrawing permission does not prevent the use of the App; however, as a result, functionalities that require the App user’s location to be determined, such as selecting the nearest stops, parking zones or routes, may not operate or may be restricted.

35. The privacy provisions specify all categories of personal data that we may process when providing the App services. However, we note that not all of these data are mandatory – certain personal data are collected only depending on the data subject’s choice and initiated actions. For example, certain data may be provided only in cases where the data subject wishes to receive an invoice. If such a need is not expressed, the respective data are not collected or processed. Thus, the specific data processed depend on the App functionalities chosen by the data subject and the scope of services used.

36. A purchased Passenger Ticket and a paid Local Fee/Parking Fee paid using the App are linked to its user’s account.

37. The App user is responsible for the authenticity of the data provided.

38. Detailed information about the conditions for processing and/or storing personal data collected in the App is provided in the Privacy and Cookie Policy and/or Personal Data Processing Rules published on the website www.judu.lt.

39. Rights of data subjects and their exercise:

39.1. You have the right to request that the Company allow you to access your personal data being processed, request that they be corrected and/or deleted, and/or restrict the processing of such data, and/or the right to object to data processing, as well as the right to data portability.

39.2. To exercise your rights, you may contact the Company by e-mail at [email protected]. If the matter cannot be resolved with the Company, you may contact the State Data Protection Inspectorate ([email protected]), which is responsible for the supervision and control of legal acts regulating personal data protection.

39.3. If you have any questions or complaints regarding the processing of your personal data, you may contact the Company by e-mail at [email protected].

CHAPTER VI.
USE OF ANALYTICAL TOOLS

40. The App collects and processes certain data about users and their devices. For the purposes of ensuring the operation of the App, security and error analysis, technical error and crash data, device information (device model, operating system, app version) and other diagnostic data necessary to ensure the stability of the App are processed. These data are processed in order to ensure the security and stability of the App and to promptly identify and eliminate technical errors. For analytics and App improvement purposes, data on the user’s interaction with the App may be processed, such as screen views, clicks, navigation in the App, session information and data on the use of functions. These data are used to understand how the App is used, identify usage problems and improve the App user experience. For analytics purposes, an internal pseudonymous user identifier, “User ID”, may also be used, enabling sessions of the same user to be linked and long-term use of the App to be analysed. This identifier does not directly identify the App user by itself; however, it may be linked to the user’s account in the App systems. The “User ID” is not used for personalised advertising or for tracking users in other apps or websites.

41. Results of service use (e.g. ticket purchases, activations, payments, parking sessions and other operations) may be recorded in Backend systems in order to ensure data accuracy, reliability and to avoid data duplication.

42. In certain cases, the App may transfer additional contextual information to Backend systems where this is necessary for the provision of the service (e.g. selection of an applicable discount).

43. Third-party services used for data processing:

43.1. Google Firebase (including Firebase Crashlytics);

43.2. Microsoft Clarity;

43.3. Meta Platforms SDK.

44. Meta SDK is used for personalised advertising only after obtaining the App user’s explicit and freely given consent in the App. Consent may be withdrawn at any time in the App settings.

45. Technical error, crash and security data necessary for the operation of the App are processed on the basis of legitimate interest, in order to ensure stable and secure operation of the App.

46. Other analytical data are used for analysis of the App’s operation, use and quality.

47. Meta SDK data are processed only after obtaining the App user’s consent.

48. Analytics reports are prepared using summarised (aggregated) data. The activity of an individual App user is not analysed.

CHAPTER VII
DIRECT MARKETING AND PERSONALISED ADVERTISING

49. Direct marketing is carried out under the following conditions:

49.1. The Company may use the App user’s contact data (e.g. e-mail address) for the Company to send the App user direct marketing communications about the Company’s services, news, offers, surveys or other information related to the Company’s activities.

49.2. Direct marketing communications may be sent by e-mail or through other communication channels provided by the App user only where there is a legal basis for doing so, including the App user’s consent or another legitimate interest, where permitted under applicable legal acts.

49.3. The App user has the right to opt out of direct marketing communications at any time. Opting out is possible by clicking the relevant link in each e-mail or by contacting the Company using the indicated contacts. Opting out will not affect the App user’s ability to use the Company’s services.

50. Personalised advertising is carried out under the following conditions:

50.1. Third-party tools, including the “Meta” software development kit (Meta SDK), may be used in the App to display personalised advertising, measure advertising effectiveness and analyse app usage behaviour.

50.2. Based on the App user’s consent (where required by applicable legal acts), the Company may collect and process information about the App user’s activity in the App, including interaction with content, so that the Company can provide advertising that is more relevant to the App user both on the Company’s platforms and on third-party platforms (e.g. “Meta” platforms).

50.3. Data used for personalised advertising may be transferred to third-party service providers, such as “Meta”, in accordance with their privacy policies and our data protection requirements.

50.4. The App user may at any time restrict or withdraw consent to personalised advertising by changing the privacy settings on their device or by contacting the Company. In certain cases, this may reduce the relevance of the advertising displayed, but the functionality of the App will remain unchanged.

51. Surveys are carried out under the following conditions:

51.1. The Company may invite the App user to participate in surveys about the Company’s services, functionality or the App user experience. Surveys may be sent by e-mail or presented in the App.

51.2. Participation in surveys is voluntary. The answers provided by the App user are used to improve our services, analyse the needs of App users and improve the functionality of the App.

CHAPTER VIII.
PAYMENT, ACTIVATION AND REFUND PROCEDURES

Procedure for purchasing, paying for and activating a Passenger Ticket.
Ticket return and transfer

52. The types and prices of Passenger Tickets are established by a decision of the Vilnius City Municipal Council. Public transport fare discounts are established in the Law on Public Passenger Transport Fare Discounts of the Republic of Lithuania and in decisions of the Vilnius City Municipal Council. The procedure for using public transport, the rights and obligations of the carrier, driver and passengers, liability, and the procedure for passenger, carrier and public transport control are established by the Rules for the Carriage of Passengers and Luggage on Public Transport of Vilnius City Municipality approved by a decision of the Vilnius City Municipal Council (current version).

53. Information about prices and applicable discounts is provided on the website www.judu.lt and in the App.

54. Tickets may be purchased in the App using payment cards (Visa, Mastercard) or via your electronic banking.

55. The App user undertakes to pay, at their own expense, fees related to the purchase and activation of a ticket (for example, the payment transfer fee set by a bank or another payment intermediary).

56. The App user must purchase the Passenger Ticket before boarding the public transport vehicle.

57. The App user must ensure that their ticket is properly activated. If the ticket cannot be properly activated, the App user must purchase a ticket by other means.

58. When activating a ticket in the App, a 15-second ticket activation duration applies, which the App user must take into account so that the ticket is activated properly and on time. The ticket is not valid until the activation duration has expired.

59. An activated ticket in the App is linked to the unique telephone device on which the ticket was activated and will not be displayed on other devices on which the same account is used.

60. The App user is responsible for the correct selection of the ticket type and discount (fare concession) type, justification of the right to a transport discount, ticket activation (taking into account the ticket activation duration), proper presentation of the ticket to passenger control and other data entered and selected.

61. Several identical or different types of Passenger Tickets may be purchased and activated on one phone at the same time. The purchaser is responsible for selecting and activating the correct types of tickets.

62. In the App, the App user may view information about ticket purchases and activations and receive a VAT invoice.

63. A non-activated (unused) ticket may be returned within 14 (fourteen) calendar days from the date of ticket purchase by logging in to the customer self-service website at https://judu.lt/isigytu-bilietu-ir-e-pinigines-lesu-grazinimas. The money for the returned ticket shall be transferred within 30 (thirty) calendar days from completion of the return procedure to the same bank account from which payment for the ticket was made.

64. In the App system, the user may transfer the desired non-activated ticket(s) from one account to another. A ticket(s) may be transferred only once. A transferred ticket(s), even if non-activated, cannot be returned. The Company assumes no liability if the user transfers a ticket(s) to an incorrect JUDU user account or transfers an incorrect type of ticket to another JUDU user account.

65. In the App system, the user may transfer the desired activated ticket(s) from one unique telephone device to another (without changing the JUDU user account), but not more often than once every 7 days, calculated from the moment of the last successful transfer of an activated ticket.

66. The user account held in the m.Ticket app and the tickets contained therein are transferred to the App (the JUDU user account) automatically after identifying the telephone number used to log in to m.Ticket or after adding in the App the telephone number used to create the m.Ticket account. Only the first linked m.Ticket user account and the tickets contained therein may be transferred to the App in this way.

Procedure for payment of the Local Fee

67. Local Fee zones, fee amounts, discounts, payment procedure and other information on the use of paid vehicle parking spaces are regulated by the Regulations on the Local Fee for the Use of Paid Parking Spaces Established by the Council, as approved by the Vilnius City Municipal Council.

68. Payment of the Parking Fee in a Local Fee zone, where payment is made using a mobile network operator’s service or a bank card, is carried out from the telephone account or bank account from which it was ordered.

69. The App user undertakes to pay, at their own expense, fees related to payment of the Local Fee (e.g. the App service fee set by their mobile network operator or by the App user’s payment institution servicing the payment card). Additional terms and conditions applied by the third-party payment service provider may also apply to the payment method; therefore, before choosing a payment method, the App user should review and assess these terms and conditions. It should be noted that payment through a mobile network operator is available only for parking services; this payment method applies only to parking services and cannot be used to pay for public transport tickets.

70. The App user must ensure that their account contains a sufficient balance to pay the Local Fee. If the App user’s account does not contain sufficient funds to pay the Local Fee, payment of the Local Fee is automatically terminated. Payment of the Local Fee may be terminated only from the same telephone device from which the Local Fee was paid.

71. In the App, the App user may choose one of the following Local Fee payment management modes:

71.1. to stop payment of the Local Fee themselves in each case (“I will stop it myself”) – the App user decides, on their own initiative and at their discretion, when to stop payment of the Local Fee and stops the payment themselves;

71.2. to set automatic payment of the Local Fee for a selected period – payment of the Local Fee is automatically terminated upon expiry of the paid period or time interval pre-set by the user in the App.

72. Where the App user selects the mode specified in Sub-clause 71.1 of the Rules in the App, the following rules apply:

72.1. payment of the Local Fee is not terminated automatically (neither at the end of the day, nor at the end of a 24-hour period, nor at the end of any other period);

72.2. payment of the Local Fee is terminated and ends in the following cases:

72.2.1. if the App user stops payment of the Local Fee themselves in the App;

72.2.2. upon expiry of the seven-calendar-day automatic validity period of the Local Fee, calculated from the date of activation of Local Fee payment.

72.3. The Local Fee is calculated only for actual paid periods, as defined in the Regulations on the Local Fee for the Use of Paid Parking Spaces Established by the Council and approved by the Vilnius City Municipal Council. During a free period (for example, at night, on weekends or during other periods established by the municipality), the fee is not calculated; however, the Local Fee payment session (calculation of the Local Fee) remains active and is not terminated until the Local Fee payment session is terminated or expires.

73. The App uses a consolidated Local Fee collection time; therefore, when paying the Local Fee, it is necessary to make sure whether the Local Fee is collected at that time in the zone in which the vehicle is parked. The Local Fee collection time is indicated by road signs and information boards; therefore, when paying the Local Fee, the driver (keeper) of the vehicle must follow the road signs and information boards.

74. The paid Local Fee does not ensure or reserve a parking space for the vehicle. The paid Local Fee also does not grant the right to park the vehicle in the area of validity of prohibitory road signs or otherwise fail to comply with the Road Traffic Rules.

75. The start of Local Fee payment is considered to be the moment when the vehicle keeper or driver receives positive confirmation in the App that payment of the Local Fee has been successfully started. The vehicle keeper or driver must start payment of the Local Fee and receive such confirmation without leaving the vehicle, unless otherwise established in applicable legal acts. A notification about the end of the paid vehicle parking time for the selected zone on that day or about termination of Local Fee payment is provided to the App user after the service is stopped or payment is terminated.

76. The App user is responsible for the proper and correct payment of the Local Fee, selection and termination of the Local Fee zone and paid vehicle parking time, entry of the registration number and other entered and selected data, as well as for the internet connection required to use the App. If the App user does not receive confirmation that payment of the Local Fee has been successfully started, sees an error message in the App or has reasonable doubts as to whether payment of the Local Fee has been started, they must pay the Local Fee by another available method and contact the Company using the contacts specified in the App or on the website. Initiating payment in the App alone is not considered proper payment of the Local Fee if the App user has not received confirmation of successful commencement of payment.

Procedure for payment of the Parking Fee

77. The App may be used to pay the Parking Fee in Parking Facilities in Vilnius that are specified on the Company’s website www.judu.lt and in the App.

78. The procedure and methods for paying the Parking Fee and/or other information on the use of Parking Facilities are provided on the website www.judu.lt and in the Parking Facility Rules specified below (hereinafter referred to as the Parking Facility Rules):

78.1. the Rules for the Use of Vehicle Parking Facilities Operated by ME “Susisiekimo paslaugos” (or another legal act replacing them), which are published on the website www.judu.lt;

78.2. the Rules for the Use of Vehicle Parking Facilities without a Barrier of ME “Susisiekimo paslaugos” approved by the Director of ME “Susisiekimo paslaugos” (or another legal act replacing them), which are published on the website www.judu.lt;

79. The Parking Fee rates are published in the Parking Facilities, on the Company’s website www.judu.lt and in the App.

80. Payment of the Parking Fee in Open Parking Facilities, where payment is made using a mobile network operator’s service or a bank card, is carried out from the telephone account or bank account from which it was ordered.

81. The App user undertakes to pay, at their own expense, fees related to payment of the Parking Fee (e.g. the App service fee set by their mobile network operator or by the App user’s payment institution servicing the payment card). Additional terms and conditions applied by the third-party payment service provider may also apply to the payment method; therefore, before choosing a payment method, the App user should review the terms and conditions of the selected payment method.

82. The App user must ensure that their account contains a sufficient balance to pay the Parking Fee. If the App user’s account does not contain sufficient funds, the person must pay the unpaid Parking Fee in accordance with the procedure established in the Parking Facility Rules – at an automatic payment machine, etc. In Closed Parking Facilities, after payment is made, 15 free minutes are granted to leave the parking facility.

83. In Open Parking Facilities, the Parking Fee is paid immediately after parking the vehicle in the parking space. In Closed Parking Facilities, the Parking Fee starts to be calculated automatically (the service is deemed ordered) when the vehicle registration number is read at the barrier and the vehicle enters the Parking Facility after the barrier opens.

84. An order for a specific vehicle left in a Closed Parking Facility is visible and can be managed (stopped/paid) from all telephone devices (with the App installed) that (whose App user account) were linked to the vehicle registration number. For personal data security purposes, all the aforementioned telephone devices (in the App) indicate that the order is being carried out in a Parking Facility, without specifying which one. The linking of the App user account to a specific vehicle registration number occurs when the vehicle registration number is entered in the App. To remove the linking of the App user account to a specific vehicle registration number, the vehicle registration number must be deleted on the telephone device (in the App).

85. The App user is responsible for ensuring that the vehicle registration numbers entered in their account are current and used lawfully. If the App user no longer uses the vehicle or no longer has the right to pay for parking services related to it, they must remove that vehicle registration number from the App. The Company shall not be liable for the consequences suffered by the App user when the Parking Fee is paid or the parking service is provided because the App user did not remove an outdated vehicle registration number from their account, except where such consequences arose due to the Company’s fault or disruptions in the operation of the App.

86. After stopping the service (by pressing the “Stop” button in the App and sliding “Stop service”), the App user of the specific telephone device is warned by a separate notification in the App whether they really wish to stop the parking service and pay the Parking Fee. If the App user of the specific telephone device confirms their decision to stop the parking service after the above-mentioned notification, they are responsible for paying the Parking Fee and the Parking Fee is charged to this App user. The Parking Fee may be paid not only using the App, but also at an automatic payment machine in the Parking Facility, if such an option is available.

87. The App user may download an invoice in the App for the Parking Fee when paid by bank card, except where the Parking Fee is paid using a mobile network operator’s service or where a notice regarding an unpaid local fee for vehicle parking, called the “Yellow Slip”, is paid. In such cases, an invoice is not generated in the App.

CHAPTER IX.
DELETION OF THE APP ACCOUNT

88. The App user has the right to submit a request to delete their App account.

89. The account deletion request shall be completed no later than within 3 (three) working days from submission of the request.

90. When deleting the App account, only data related to the App are deleted or irreversibly unlinked from the account, including, but not limited to:

90.1. name and surname;

90.2. App login data;

90.3. payment cards added in the App;

90.4. invoice details;

90.5. usage history stored in the App;

90.6. vehicle registration numbers added in the App;

90.7. linking of the telephone number to the App account;

90.8. other App settings and data related to the use of the App.

91. The data are deleted or anonymised (unlinked from the account) in such a way that they can no longer be linked to a specific App user.

92. If the App user logged in to the App using a previously created website self-service account, deletion of the App account does not affect the website self-service account.

93. The website self-service account and the data stored therein are not deleted.

94. When logging in to the App again using the same website self-service account, a new App account is created without the App data previously stored therein. In such a case, the previously added payment cards, invoice data and App usage history will no longer be present in the App.

95. If the website self-service account contains linked vehicles or other data, they may be automatically displayed in the App after login.

96. The App account deletion function is not intended for:

96.1. deleting an account linked to a telephone number;

96.2. deleting a website self-service account;

96.3. deleting parking permits linked to a specific vehicle registration number;

96.4. removing the data of a JUDU / Vilnietis Card added in the website self-service environment.

97. Deletion of these data or accounts is carried out under a separate procedure:

97.1. a request to delete an account linked to a telephone number must be submitted by e-mail to [email protected];

97.2. a website self-service account is deleted by logging in to the website self-service environment, selecting “User settings” and then selecting “Delete account”;

97.3. for deletion of parking permits linked to a specific registration number, contact [email protected] by e-mail;

97.4. for removal of the data of a JUDU / Vilnietis Card added in the website self-service environment, contact [email protected] by e-mail.

98. The App account cannot be deleted if the account contains active, valid or unused services.

99. Before submitting an account deletion request, the App user must:

99.1. complete all active parking sessions;

99.2. use or transfer the tickets they hold to another account.

100. If the App user wishes to remove tickets from the account, they must contact [email protected] by e-mail.

CHAPTER X
FINAL PROVISIONS

101. The Rules are approved and may be amended by an order of the Company’s Director.

102. The Rules and amendments thereto shall enter into force from the date of their publication in the App or on the Company’s website.

103. All disputes, disagreements or claims arising from these Rules, the use of the App or related legal relations shall first be resolved by negotiation. In case of questions or claims, the user may contact the Company using the contact details specified in the Rules, in the App or on the Company’s website.

104. The Rules, use of the App and relations arising therefrom shall be governed by the law of the Republic of Lithuania, except where mandatory legal provisions establish otherwise.

Thank you for signing up!

Do you really want to delete your account?