Effective from 18.02. 2021
The Real-Deal Hungary Korlátolt Felelősségű Társaság provides an internet service that provides helps for a lessor and a lessee in the concusion in the conclusion of a lease agreement, for exercising their rights under a lease and the fulfillment of their obligations.
The regulation is regularly updated to continuously comply with the applicable national and European Union legislation.
Name: Real-Deal Hungary Korlátolt Felelősségű Társaság
Seat: 7726 Véménd, Zrínyi u. 58.
Address: 7726 Véménd, Zrínyi u. 58.
Court of Registry: Pécsi Törvényszék Cégbírósága
Company registration number: 02-09-084505
Tax number: 25971358-2-02
Representative: Ballók Attila ügyvezető
Phone number: +36 20 800 4010
Person responsible for the data processing activity: Ballók Attila
No data protection officer had been appointed at the Controller.
The Controller hires a Processor to facilitate its data processing activities.
The Controller shall endeavor to use a Processor who or which provides adequate guarantees for implematation of appropriate technical and organizational measures to ensure compliance with the requirements of data processing set out in the GDPR Regulation and to implement appropriate technical and organizational measures to protect the rights of the Data Subjects.
The Controller hires the following Processors:
1) Name: Isobar Budapest Zrt.
Seat: 1027 Budapest, Kacsa u. 15-23.
Company registration number: 01-10-044680
Tax number: 12740088-2-41
2) Name: Amazon Web Services Emea Société Á Responsabilité Limitée
Seat: 38 Avenue John F. Kennedy, L-1855 Luxembourg
3) Name: The Rocket Science Group, LLC
Seat: 675 Ponce de Leon Ave NE, Suite 5000, Atlanta, GA 30308 USA
4) Name: Hotjar Ltd
Seat: Level 2
St Julians Business Centre,
3, Elia Zammit Street
St Julians STJ 3155, Malta, Europe
5) Name: tawk.to.inc
Seat: 187 East Warm Springs Rd, SB298
Las Vegas, NV, 89119
6) Name: Usersnap Gmbh
Seat: Industriezeile 35, 4020 Linz, Austria
7) Name: INNOVATIVE GROUP Kereskedelmi és Szolgáltató Korlátolt Felelősségű Társaság
Seat: 9400 Sopron, Bem u. 3.
Company registration number: 08-09-016137
Tax number: 14261150-2-08
The Controller follows the principals in accordance with Article 5 of the GDPR, that the processing of „the personal data” shall be
The Controller shall be responsible for, and shall comply with the above principles (‘accountability’).
The strictly necessary data for the use of Albee is marked as required data in order to make it clear to the Data Subject which information is required to use Albee.
Optional data: gender, nickname, profile picture, bank account number, phone number
The Data Subject gives his/her consent to the Data Controller by entering (typing) his/her personal data via Albee in the interface created for this purpose.
The Data Subject shall acknowledge, that it is not possible to register on Albee, and the provision of the service shall not start on Albee without his/her consent.
With regard to the data, the legal basis for data processing as follows:
The Data Subject can subscribe to the newsletter by entering their personal data and clicking on the „Subscribe newsletter” button.
The Data Subject aknowledges that it is not possible to subcribe to the newsletter without his or her consent.
The Data Subject is entitled to withdraw his or her consent to the sending of the newsletter at any time by clicking on the unsubscribe button at the bottom of the newsletter.
With the withdrawal of the Data Subject’s the personal data of the Data Subject shall not be processed any longer for the purpose of sending a newsletter.
In the eventof claim inforcement of the other party of the lease agreement (lessor-lessee) arising in connection with his or her personal data, the Data Subject is liable, the Controller excludes its liability in this respect.
The third parties can get to know Albee by invitation.
In the course of enforcing a claim created by third parties in connection with their personal data, the Data Subject is liable, the Controller excludes its liability in this case
What are cookies? A cookie is a small text file that your device saves when you use Albee. Your device stores the cookie for a specied period of time. This allows certain data and settings (such as language, font size and other display settings) to be “memorized” for a specified period of time.
The following cookies are used on Albee:
Name of the cookie
strictly necessary cookies
It stores cookie settings set by the user, namely those cookies which were granted before.
It measures the number of the visitors, the duration of the visit, the navigation and other visited websites.
The PHPSESSID cookie is part of the PHP’s native version, which enables websites to store a unique sequence. It settles a user routine on the website and transfers status information through a temporary cookie, which is usually called routine-cookies. Since the PHPSESSID cookie does not have timed expiration, it ceases with the closure of the browser.
It saves the URL settings.
It enables real time two-way event-based communication.
The name of the cookie is connected to the Google Universal Analytics. The cookie assigns a unique value for every visited page and updates it.
The name of the cookie is connected to the Google Universal Analytics, according to the documentation, its task is to improve the query scale to restrict the data collection of the most visited pages.
The name of the cookie is connected to the Google Universal Analytics – which is a significant update of the Google’s most used analityc service. The cookie is used to distinguish the individuel users with a randomly generated user-identification number. This appears at every page drawdown on a certain website and it calculates the data of the visitors, routines and campaignes for the website’s analytic reports. The cookie expires after 2 years by default.
The name of the cookie is connected to the Google DoubleClick service and it is for retargeting, optimalisation and reporting.
IDE, DSID, FLC, AID, TAID, exchange_uid
The name of the cookie is connected to the Google DoubleClick service. These cookies have marketing purposes, they help to customize the advertistments.
The use of necessary cookies is vital for the proper operation of Albee, so in this case, the legal basis is Article 6. (1) b) of the GDPR regulation.
B.2.) Application of the Hotjar program
What is the hotjar program for? The hotjar program helps the Controller to collect feedback from the Albee’s visitors / users and to monitor the custom of Albee’s visitors /users according to the followings:
Hotjar-cookie, which is loaded when a visitor interacts with a pop-up widow of a survey invitation. It secures that the same invitation would not appear again, if it had been shown previously.
Hotjar-cookie, which is loaded when the visitor sends the feedback with the help of „Feedback Poll” widget. It secures, that the same voting would not appear again, if it had been filled previously.
Hotjar-cookie, which is loaded when the visitor closes the “Feedback Poll” widget. It secures, that the widget would stay closed, when the visitor navigates in yous website.
Hotjar-cookie, which is loaded when the visitor closes or fills the feedback. It happens as if the visitor navigates to anouther site, the feedback window would be loaded in closted status.
Hotjar-cookie, which is loaded, when the user arrives on the same page with the Hotjar-script .This Hotjar is for the safekeeping of the user identifier, which is typical for the certain website in the browser. This secures, that the habit of the latter visit of the same website could be assigned to the same user identifier.
It is updated, when the setting of the user begins and when the data would be sent through the WebSocket (when the user executes the procedure set by the Hotjar).
When the Hotjar script ran down, we try to determine the most frequent cookie access route instead of the page’s hostname. This allows that the cookies could be shared between the subdomains (in certain cases). Until it is successfully determined, we try to store the _hjTLDTest cookie at alternative URL subtexts. After this controll, the cookie would be deleted.
The user attributes sent via Hotjar Identify API are stored in cashe memory during the routine in case of getting to know when had the attribute had changed and if any update is necessary.
This cookie stores the user attributes, which are sent via the Hotjar Identify API, when the user is not in the pattern. These attributes are saved only whent the user interacts with a Hotjar Feedback instrument.
This cookie is for controlling if the Hotjar Tracking Script is allowed to use local storage. If it is allowed, 1 value is set in the cookie.
This cookie is set, that it would notify the Hotjar if the user is in the pattern used for producing channels.
This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
This cookie is for identifying the user’s first page visiting routine. This is a true/false value, which is set by the cookie. This cookie is set by the application as a randomly generated identifier for the anonym users.
This cookie is set by the Google Analytics to gain information from the advertistment’s clicks and stores it in the user’s cookie to make the conversations assignable outside the target page.
The Data Subject gives consent with visiting Albee that a hotjar programm would be applicable in Albee
B.3.) Application of Facebook Pixel
What is Facebook Pixel? According to the official definition of Facebook, it is an analytical instrument which can measure the effectiveness of the advertisment activity and gives information on the actions of the Data Subject in Albee.
In Albee, the following Facebook cookies are applicable:
It stores encrypted Facebook and browser ID.
Facebook uses it for determining the appearance order of the advertisment products, for example for real time bids from third party’s advertiser.
This cookie distincts the two routines provided in different moments by the same user.
The c_user cookie contains the currently logged user’s user identification.
The aim of the datr cookie is to identify that browser, which is used for connecting to Facebook, independently from the logged user. This cookie has a key role in the Facebook’s security and website-integrity function.
It stores encrypted Facebook and browser ID.
This cookie is for showing the user’s chat status.
The Facebook uses it for improving the friend suggestions.
Facebook uses advertistment cookies for analysing the social campaigns, establishing troubleshooting campaigns in accordance with establishing campaign, establishing cumulative public groups in the websites of the campaigns and for targeting the outsider activity tendences.
It stores the site’s resolution.
The Facebook cookie is for maintaining the routine. It operates with the c_user cookie to certify the identity on Facebook.
This cookie contains the browser’s last logged user’s editing scope.
It is for optimalising the website’s capacity for the advertisers.
This cookies are used by Facebook for supporting the sharing and the integration of the Facbook services.
The Data Subject gives consent with visiting Albee that cookies would be applicable in Albee
B.4.) Application of Tawk.to program
What the tawk.to program is for? With the application of the tawk.to program, the Data Subject can use a chat window in order to connect the Controller.
In Albee, the following tawk.to cookies are applicable:
Expiration Time (HU)
This cookie identifies the user to connect the chats in case of producing better services. The cookie is stored for 6 months.
This cookie enables the identification of the user to optimalise chat-box functions.
This cookie is used for collecting information ont he user’s interactions with the chat function of the website.
It is necessary for the operation of the chat-box function.
The Tawk.to is our live chat service. The cookies are used for identifying anonymously the user’s usual location and for continuing the chat when returns.
By using the chat function, the Data Subject consents to the use of “cookies” on Albee.
B.5.) Application of Usersnap program
What is Usersnap program for? With the application of Usersnap program at Albee, the Data Subject can notify the Controller on the errors noticed while using Albee on the error notification platform (named Hibabejelentés).
In Albee, the following Usersnap cookies are applicable:
Expiration Time (HU)
The Data Subject consents to the use of “cookies” on Albee by indicating the errors detected on Albee in the Error Reporting interface.
The Controller will no longer store the data in the event of termination of the reason or purpose of the data processing. Data processing is terminated by the deletion of the data by the Controller.
With regard to data for which the legal basis is the following:
The Data Subject is entitled in relation to its personal data processed by the Controller to
Right of access: The Data Subject shall have the right to obtain from the Controller confirmation as to whether or not personal data concerning him or her are being processed, and, where that is the case, access to the personal data and the following information.
Right of rectification: The Data Subject shall have the right to obtain from the Controller the rectification and completion of inaccurate personal data concerning him or her.
Right to restriction of processing: The Controller, upon request of the Data Subject, restricts the data process if the accuracy, the pertinence or the completeness of the personal data is contested by the Data Subject, and the accuracy, pertinence or competeness of the Processed data cannot be certified without doubt, during the time until the doubt is clarified, or in case of the deletion of the data could be needed, but if according to the written declaration of the Data Subject or the available information at the Controller, it is reasonably assumable, that the deletion of data would harm the Data Subject’s until the existence of the legal interests underlying the deletion. Upon request of the Data Subject, the Controller restricts the Data process if the Controller no longer needs the personal data for the purposes of the processing, but they are required by the Data Subject for the establishment, exercise or defence of legal claims; or the Data Subject has objected to processing pending the verification whether the legitimate grounds of the Controller override those of the Data Subject. Where processing has been restricted, such personal data shall, with the exception of storage, only be processed with the Data Subject’s consent or for the establishment, exercise or defence of legal claims or for the protection of the rights of another natural or legal person or for reasons of important public interest of the Union or of a Member State. A Data Subject who has obtained restriction of processing shall be informed by the Controller before the restriction of processing is eliminated.
Right to erasure/right to beeing forgotten: The Controller shall delete the personel data of the Data Subject without delay if the Data process is unlawful, especially if the Data process harms the principals determined in Article 4 of the Info. Act, its aim had been terminated, or the Data process is not necessary for reaching the aim of the data process, or the time period determined in laws, international agreements or a binding legal act of the European Union had been expired, or its legal basis had been terminated and there is no other legal basis of the Data process. The Controller shall delete the personel data of the Data Subject without delay if the Consent of the Data Subject had been withdrawn or if the Data Subject requests the deletion or if the deletion of the data had been ordered by laws, any binding legal act of the EU, the Authority or the court, or the time period determined in Section 19 (1) b)-d) of the Info. Act had been expired.
Right to data portability: The Data Subject shall have the right to request the direct transfer of his or her personel data between controllers.
The Data Subject shall have the right to object against the data process of his or her personel data.
The Controller shall consider the request submitted by the Data Subject regarding his or her rights to be enforced as soon as possible but not later then 25 (twenty-five) days following the submission, and inform the Data Subject on its decision in written form, or in electronic form, if the request had been submitted by the Data Subject in electronic form.
The Data Subject is entitled to contact the Hungarian National Auhtority for Data Protection and Freedom of Information with any request (address: 1125 Budapest, Szilágyi Erzsébet fasor 22/c; post office: 1530 Budapest, Pf. 5.; electronic contact: firstname.lastname@example.org; phone: + 36 1 391-1400; telefax: + 36 1 391 1410; address of homepage: http://naih.hu; hereinafter refferred to as: „Authority”).
The Data Subject may seek judicial remedy against the Controller if, in his or her opinion, the Controller or a processor entrusted by or acting on his or her behalf processed his or her personal data with violation of the provisions on the processing of personal data stipulated in law or in a binding legal act of the European Union. The Data Subject may bring the action before the regional court having territorial jurisdiction over his domicile or place of residence, according to his choice. (Section 23 (1), (3) of Info. Act)
The Controller shall have appropriate technical and organisational measures in force to provide protecion against unathorized use, disclosure or access.
If the personal data breach is likely to involve a high risk to the rights and freedoms of natural persons, the Controller shall notify the Data Subject of the personal data breach without undue delay.
In the notification provided to the Data Subject, the Controller shall clearly and intelligibly describe the nature of the personal data breach and communicate the names and contact details of other contact persons providing further information; describe the likely consequences of the personal data breach; the measures taken or planned by the Controller to remedy the personal data breach, including, where appropriate, measures to mitigate any adverse consequences arising from the personal data breach.
The Controller shall not inform the Data Subject, if any of the following conditions emerge:
If the Controller has not yet notified the Data Subject of the personal data breach, the supervisory Authority, after considering whether the personal data breach is likely to involve a high risk, shall order the information of the Data Subject thereof, or impose one of the conditions referred to in points (a), (b) or (c). fulfillment.
Reporting a personal data breach to the Authority: The breach of personal data shall be notified by the Controller to the competent supervisory authority pursuant to Article 55 of the GDPR Regulation without undue delay and, if possible, no later than 72 (seventy-two) hours after becoming aware of the breach of personal data, unless the personal data breach would not result any risks for the rights and freedoms of the natural persons. If the notification is not made within 72 (seventy-two) hours, the Controller shall also enclose the reasons for the delay.
Real-Deal Hungary Korlátolt Felelősségű Társaság