{"id":5379,"date":"2024-04-22T13:48:06","date_gmt":"2024-04-22T13:48:06","guid":{"rendered":"https:\/\/wp.hellopay.hu\/?page_id=5379"},"modified":"2024-10-15T11:52:13","modified_gmt":"2024-10-15T11:52:13","slug":"cookie","status":"publish","type":"page","link":"https:\/\/hellopay.hu\/en\/cookie\/","title":{"rendered":"Cookie policy"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

COOKIE INFORMATION (\"COOKIE\")<\/b><\/p>

About data management with cookies used on HelloPay website and HelloPay app<\/strong><\/p>

\u00a0<\/p>

A HelloPay Information Technology and Services Private Limited Company<\/strong> (registered office: 1037Budapest, Montevideo utca 10.; company registration number: 01-10-048364, registrar: F\u0151v\u00e1rosi T\u00f6rv\u00e9nysz\u00e9k C\u00e9gb\u00edr\u00f3s\u00e1ga; tax number: 25155781-2-41, represented by Norbert Varga, CEO, e-mail address: dpo@hellopay.hu<\/a>; hereafter: HelloPay<\/strong> or Data Controller<\/strong>) hereby informs the data subjects about the processing of data relating to cookies (\"cookies\") used during the use and enjoyment of the HelloPay website and HelloPay application in accordance with Regulation 2016\/679 of the European Parliament and of the Council on the General Data Protection Regulation (hereinafter: GDPR<\/strong>) in line with.<\/p>

\u00a0<\/p>

HelloPay may unilaterally amend this Cookie Notice at any time. This Cookie Notice is published on the HelloPay website and is also available in the HelloPay app. This Cookie Policy shall enter into force upon its publication.<\/p>

\u00a0<\/p>

  1. General information on how the cookies work<\/strong><\/li><\/ol>

    We use cookies and other various programs (hereinafter collectively referred to as \"cookies\") on the HelloPay website and HelloPay application in order to learn about users' needs and behaviour with the HelloPay website and HelloPay application and to use them to improve the HelloPay website and application, to compile anonymous statistics about visits to and use of the HelloPay website and application, and to send users targeted advertising messages.<\/p>

    \u00a0<\/p>

    A cookie is a small text file consisting of letters and numbers in the source code of a website, which the website uses to send information to the user's browsing device or browser and to access the data stored by the cookie on the user's browsing device.<\/p>

    \u00a0<\/p>

    1. What personal data do we process, for how long, what we use it for and under what authority?<\/strong><\/li><\/ol>

      The legal bases for our processing are:<\/p>

      \u00a0<\/p>

      1. the voluntary informed consent of the user to the processing of personal data pursuant to Article (1)(a) of the GDPR (hereinafter: Contribution<\/strong>);<\/li>
      2. the processing is necessary for the purposes of the legitimate interests pursued by the controller or a third party pursuant to Article (1)(f) of the GDPR (hereinafter: legitimate interest<\/strong>).<\/li><\/ol>

        The table below shows the purpose, legal basis, retention period and type of each cookie, broken down by cookie.<\/p>

        \u00a0<\/p>

        The cookies used on the HelloPay website and app are divided into three main categories:<\/p>

        \u00a0<\/p>

        1. Cookies required for the HelloPay website and app to work<\/strong>: without them, the HelloPay website and application will not function at all or not function as intended, these cookies are necessary for the HelloPay website and application to run. If the User blocks these cookies in his browser, the HelloPay website and application will not function properly.<\/li><\/ol>

          COOKIE NAME<\/strong><\/p><\/td>

          PURPOSE OF THE COOKIE, SCOPE OF DATA COLLECTED<\/strong><\/p><\/td>

          DURATION OF PROCESSING<\/strong><\/p><\/td>

          YOUR OWN OR A THIRD PARTY'S CAKE<\/strong><\/p><\/td><\/tr>

          \u00a0<\/p>

          \u00a0<\/p>

          grs_gdpr<\/p><\/td>

          A cookie created by the GDPR management plugin that stores the permissions accepted in a given browser, such as whether the user has consented to the placement of cookies.<\/p><\/td>

          \u00a0<\/p>

          \u00a0<\/p>

          1 year<\/p><\/td>

          \u00a0<\/p>

          \u00a0<\/p>

          My<\/p><\/td><\/tr>

          wordpress_test_cooki e<\/p><\/td>

          Checks whether the user's browser allows cookies to be set.<\/p><\/td>

          Until the end of the user session<\/p><\/td>

          \u00a0<\/p>

          My<\/p><\/td><\/tr>

          wp-settings-{time}-<\/p>

          {UID}<\/p><\/td>

          Required for customising the user interface.<\/p><\/td>

          1 year<\/p><\/td>

          My<\/p><\/td><\/tr>

          wp-settings-{UID}<\/p><\/td>

          Required for customising the user interface.<\/p><\/td>

          1 year<\/p><\/td>

          My<\/p><\/td><\/tr><\/tbody><\/table>

          HelloPay processes the cookies that are strictly necessary for the operation of the HelloPay website and app on the basis of Legitimate Interest pursuant to Article 6(1)(f) of the GDPR.<\/p>

          HelloPay's legitimate interest: it is in HelloPay's legitimate business interest that the HelloPay website and application function as intended and that the HelloPay website and application can be displayed to users. This requires the use of the cookies indicated above and the processing of personal data collected by them.<\/p>

          \u00a0<\/p>

          In the case of processing based on legitimate interest, the data subject may object at any time to the<\/strong><\/p>

          data processing, in which case the Service Provider will no longer process your data.<\/strong><\/p>

          A full copy of the balancing of interests test on data processing based on legitimate interests is available to data subjects on request. The request should be made to the above e-mail address.<\/strong><\/p>

          1. Cookies for analytical and statistical purposes<\/strong>: these cookies allow HelloPay to measure visitor traffic to the HelloPay website and app, and to understand which products and activities are more popular than others. These cookies can be blocked by the User's browser or used by the User: https:\\tools.google.com\/dlpage\/gaoptout.<\/a> HelloPay uses the data collected by these cookies to optimize and improve the HelloPay website and application.<\/li><\/ol>

            COOKIE NAME<\/strong><\/p><\/td>

            PURPOSE OF THE COOKIE, SCOPE OF DATA COLLECTED<\/strong><\/p><\/td>

            DURATION OF PROCESSING<\/strong><\/p><\/td>

            YOUR OWN OR A THIRD PARTY'S CAKE<\/strong><\/p><\/td><\/tr>

            _ga<\/p><\/td>

            A unique identifier that is used to generate web traffic statistics based on the user's browsing<\/p><\/td>

            2 years<\/p><\/td>

            \u00a0<\/p>

            \u00a0<\/p>

            \u00a0<\/p>

            Third party (Google)<\/p><\/td><\/tr>

            _gid<\/p><\/td>

            A unique identifier that is used to generate web traffic statistics based on the user's browsing<\/p><\/td>

            1 day<\/p><\/td><\/tr>

            AnalyticsSyncHistory<\/p><\/td>

            For individual users, to record the time of synchronisation with the LinkedIn analytics (\"lms_analytics\") cookie if the previous and current browsing of the website take place in the same country<\/p><\/td>

            30 days<\/p><\/td>

            Third party (LinkedIn)<\/p><\/td><\/tr>

            _clck<\/p><\/td>

            Unique identifier used by the user to browse<\/p><\/td>

            1 year<\/p><\/td>

            Third party (Microsoft)<\/p><\/td><\/tr><\/tbody><\/table>

            COOKIE NAME<\/p><\/td>

            PURPOSE OF THE COOKIE, SCOPE OF DATA COLLECTED<\/p><\/td>

            DURATION OF PROCESSING<\/p><\/td>

            YOUR OWN OR A THIRD PARTY'S CAKE<\/p><\/td><\/tr>

            \u00a0<\/td>

            to generate web traffic statistics<\/p><\/td>

            		\u00a0<\/td>\u00a0<\/td><\/tr>

            _clsk<\/p><\/td>

            A unique identifier for a user session that allows linking user activities during a specific visit to a website for website\/application development purposes.<\/p><\/td>

            24 hours<\/p><\/td><\/tr>

            _clsid<\/p><\/td>

            A unique identifier for a user session that allows linking user activities during a specific visit to a website for website\/application development purposes.<\/p><\/td>

            Until the end of the user session<\/p><\/td><\/tr><\/tbody><\/table>

            HelloPay processes this data on the basis of consent pursuant to Article 6(1)(a) of the GDPR.<\/p>

            In the case of consent-based processing, the data subject may withdraw his or her consent at any time.<\/strong><\/p>

            1. Cookies for marketing and remarketing purposes: these cookies are set for marketing, advertising and promotional activities in order to allow HelloPay to track users' interests and to display relevant ads on the HelloPay website and app. Based on the data collected by these cookies, user profiles are created about users based on their browsing and app usage patterns. If the user does not allow these cookies, they will not receive targeted ads in the future. Data collected through the use of these cookies<\/li><\/ol>

              for the purpose of direct marketing segmentation for the publication of targeted advertising. In addition, in order to ensure that users only receive ads that match their interests and are relevant to them, HelloPay uses the automatically collected data to segment and group users and advertising recipients.<\/p>

              \u00a0<\/p>

              COOKIE NAME<\/strong><\/p><\/td>

              PURPOSE OF THE COOKIE, SCOPE OF DATA COLLECTED<\/strong><\/p><\/td>

              DURATION OF PROCESSING<\/strong><\/p><\/td>

              YOUR OWN OR A THIRD PARTY'S CAKE<\/strong><\/p><\/td><\/tr>

              HSID<\/p><\/td>

              Detecting and preventing fraud when using Google Ads<\/p><\/td>

              2 years<\/p><\/td>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              Third party (Google)<\/p><\/td><\/tr>

              SID<\/p><\/td>

              Detecting and preventing fraud when using Google Ads<\/p><\/td>

              2 years<\/p><\/td><\/tr>

              \u00a0 <\/u>Secure-1PSID<\/p><\/td>

              Create a profile of the user's interests to display personalised Google ads<\/p><\/td>

              2 years<\/p><\/td><\/tr>

              \u00a0 <\/u>Secure-3PSID<\/p><\/td>

              Create a profile of the user's interests to display personalised Google ads<\/p><\/td>

              2 years<\/p><\/td><\/tr>

              SAPISID<\/p><\/td>

              Create a profile of the user's interests to display personalised Google ads<\/p><\/td>

              2 years<\/p><\/td><\/tr>

              \u00a0 <\/u>Secure-3PAPISID2 years<\/p><\/td>

              Create a profile of the user's interests to display personalised Google ads<\/p><\/td>

              2 years<\/p><\/td><\/tr><\/tbody><\/table>

              COOKIE NAME<\/strong><\/p><\/td>

              PURPOSE OF THE COOKIE, SCOPE OF DATA COLLECTED<\/strong><\/p><\/td>

              DURATION OF PROCESSING<\/strong><\/p><\/td>

              YOUR OWN OR A THIRD PARTY'S CAKE<\/strong><\/p><\/td><\/tr>

              \u00a0 <\/u>Secure-1PAPISID2 years<\/p><\/td>

              Create a profile of the user's interests to display personalised Google ads<\/p><\/td>

              2 years<\/p><\/td>

              		\u00a0<\/td><\/tr>

              \u00a0 <\/u>Secure-3PSIDCC 2 years<\/p><\/td>

              Create a profile of the user's interests to display personalised Google ads<\/p><\/td>

              2 years<\/p><\/td><\/tr>

              \u00a0 <\/u>Secure-ENID<\/p><\/td>

              Create a profile of the user's interests to display personalised Google ads<\/p><\/td>

              13 months<\/p><\/td><\/tr>

              bcookie<\/p><\/td>

              Identification of the user's browsing device at LinkedIn login to detect and prevent fraud<\/p><\/td>

              2 years<\/p><\/td>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              Third party (LinkedIn)<\/p><\/td><\/tr>

              UserMatchHistory<\/p><\/td>

              Sync custom ad IDs to ads on LinkedIn.<\/p><\/td>

              30 days<\/p><\/td><\/tr>

              _guid<\/p><\/td>

              Unique identification of the browsing browser\/device on which the user is logged in to LinkedIn while browsing, to prevent abuse on LinkedIn<\/p><\/td>

              90 days<\/p><\/td><\/tr><\/tbody><\/table>

              COOKIE NAME<\/strong><\/p><\/td>

              PURPOSE OF THE COOKIE, SCOPE OF DATA COLLECTED<\/strong><\/p><\/td>

              DURATION OF PROCESSING<\/strong><\/p><\/td>

              YOUR OWN OR A THIRD PARTY'S CAKE<\/strong><\/p><\/td><\/tr>

              \u00a0<\/td>

              detection and diagnostic purposes.<\/p><\/td>

              		\u00a0<\/td>\u00a0<\/td><\/tr>

              lms_ads<\/p><\/td>

              Identify registered LinkedIn users for LinkedIn ads on the website<\/p><\/td>

              30 days<\/p><\/td><\/tr>

              lms_analytics<\/p><\/td>

              Identify registered LinkedIn users for LinkedIn ads on the website<\/p><\/td>

              30 days<\/p><\/td><\/tr>

              li_sugr<\/p><\/td>

              LinkedIn Insights web is used to establish the identity of the user on a probabilistic basis<\/p><\/td>

              90 days<\/p><\/td><\/tr>

              _fbp<\/p><\/td>

              A cookie used by Facebook to identify the user and the browser, linked to the web traffic statistics generated by the user and assigned to the Facebook profile.<\/p><\/td>

              3 months<\/p><\/td>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              Third party (Facebook)<\/p><\/td><\/tr>

              fr<\/p><\/td>

              A cookie used by Facebook to identify the user and the browser, to track the web traffic generated by the user, and to<\/p><\/td>

              \u00a0<\/p>

              3 months<\/p><\/td><\/tr><\/tbody><\/table>

              COOKIE NAME<\/strong><\/p><\/td>

              PURPOSE OF THE COOKIE, SCOPE OF DATA COLLECTED<\/strong><\/p><\/td>

              DURATION OF PROCESSING<\/strong><\/p><\/td>

              YOUR OWN OR A THIRD PARTY'S CAKE<\/strong><\/p><\/td><\/tr>

              \u00a0<\/td>

              is linked to statistics that you associate with your Facebook profile.<\/p><\/td>

              		\u00a0<\/td>\u00a0<\/td><\/tr>

              \u00a0<\/p>

              \u00a0<\/p>

              tr<\/p><\/td>

              A cookie used by Facebook to identify the user and the browser, linked to the web traffic statistics generated by the user and assigned to the Facebook profile.<\/p><\/td>

              \u00a0<\/p>

              Until the end of the user session<\/p><\/td><\/tr>

              _hjSessionUser<\/em>{site_id}<\/p><\/td>

              User identification with unique ID, tracking data within the same website.<\/p><\/td>

              365 days<\/p><\/td>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              \u00a0<\/p>

              Third party (Hotjar)<\/p><\/td><\/tr>

              \u00a0<\/p>

              \u00a0<\/p>

              hjSession<\/em>{site_id}<\/p><\/td>

              \u00a0<\/p>

              \u00a0<\/p>

              Store current session data.<\/p><\/td>

              30 minutes, if the user session is longer, until the end of the user session<\/p><\/td><\/tr>

              _hjClosedSurveyInvites<\/p><\/td>

              Interaction with a Survey invitation module.<\/p><\/td>

              365 days<\/p><\/td><\/tr>

              _hjDonePolls<\/p><\/td>

              An on-site Survey completed by a user.<\/p><\/td>

              365 days<\/p><\/td><\/tr>

              _hjMinimizedPolls<\/p><\/td>

              An on-site survey minimised by a user.<\/p><\/td>

              365 days<\/p><\/td><\/tr><\/tbody><\/table>

              COOKIE NAME<\/strong><\/p><\/td>

              PURPOSE OF THE COOKIE, SCOPE OF DATA COLLECTED<\/strong><\/p><\/td>

              DURATION OF PROCESSING<\/strong><\/p><\/td>

              YOUR OWN OR A THIRD PARTY'S CAKE<\/strong><\/p><\/td><\/tr>

              _hjShownFeedbackMes sage<\/p><\/td>

              Feedback widget minimized or filled in by a user.<\/p><\/td>

              1 day<\/p><\/td>

              		\u00a0<\/td><\/tr>

              \u00a0<\/p>

              _hjLocalStorageTest<\/p><\/td>

              Controls whether Hotjar can use the local memory \/ storage of the device used for browsing.<\/p><\/td>

              Until end of user session (deleted immediately after creation)<\/p><\/td><\/tr><\/tbody><\/table>

              HelloPay processes these cookies on the basis of consent in accordance with Article 6(1)(a) of the GDPR.<\/strong><\/p>

              \u00a0<\/p>

              In the case of consent-based data processing, the data subject can withdraw his or her consent at any time in the browser settings, in which case HelloPay will not use the cookie in question and will no longer collect or process data with it.<\/strong><\/p>

              \u00a0<\/p>

              1. Data transfers to third countries<\/strong><\/li><\/ol>

                HelloPay transfers personal data collected by cookies to the following third countries outside the EEA (European Economic Area) in connection with the processing of the cookies listed in section 2 above:<\/p>

                \u00a0<\/p>

                1. Cookies placed by Google LLC (\"Google\")<\/strong>: Google is a company based in the United States. The United States does not provide the level of protection required under Chapter V of the EU General Data Protection Regulation 2016\/679 (\"GDPR\") for data protection within the EEA, as ruled by the Court of Justice of the European Union in its judgment C-311\/18 (Schrems II) of 16 July. Google uses the Data Privacy Framework (\"DPF\") certificate established between the European Union and the United States by the European Commission's Data Protection Compliance Decision adopted on 10 July 2023 pursuant to Article 45 of the GDPR to provide adequate safeguards for its data transfers outside the EEA. More information on this is available at the following links: https:\/\/www.dataprivacyframework.gov\/list<\/a> and https:\/\/policies.google.com\/privacy\/frameworks?hl=en-US.<\/a><\/li><\/ol>

                  Google data:<\/p>