General Terms and Conditions (GTC)

General Terms and Conditions (GTC)

1. Introductory provisions

1.1. These General Terms and Conditions (GTC) govern the conditions for using the multi-tenant appointment-booking software service named MeetPly, accessible through a browser and through programmatic interfaces (the Service), between the Provider and the Subscriber.

1.2. By ordering the Service, by completing registration, or by actually using the Service, the Subscriber accepts all terms of these GTC.

1.3. Two legally separate legal relationships. Sections 1–17 and 22–23 of these GTC set out the content of the subscription agreement between the Provider and the Subscriber. Sections 18–21, by contrast, contain the conditions applicable to the End User for the use of the booking interface. Section 22 (Force majeure) and Section 23 (Final provisions) — the applicable law, partial invalidity, notices and the entire agreement clause — apply to the subscription relationship; to the End User, the amendment rule under Section 21.3 and the provisions expressly designated in Sections 18–21 apply.

1.4. Sections 18–21 do not make the End User a party to the subscription agreement, and do not create a contract between the End User and the Provider for the service that is the subject of the appointment; that contract is concluded exclusively between the End User and the Subscriber (Section 18.2).

2. Provider details

The Provider obtains hosting and server services through the infrastructure of Hetzner Online GmbH. The details of personal data processing are set out in the separate Privacy Notice.

3. Definitions

• Service: the multi-tenant appointment-booking software operated by the Provider, accessible through a browser and through programmatic interfaces, provided as a service (SaaS).
• Subscriber: the business association, sole trader, other legal person, organisation without legal personality, foundation, association, ecclesiastical legal person, public body, budgetary organ or local government that subscribes to the Service and uses it to make appointments bookable for its own clients, within the scope of its professional, business, organisational or public-duty activity (Section 4.5).
• Workspace: the data area belonging to the Subscriber, separated from the data of other subscribers, together with the user accounts, calendars, resources, services and bookings belonging to it.
• Calendar: the booking unit within the Workspace, with its own public identifier (slug), its own resources, services and rules. Access and role may also differ per calendar.
• Resource: the person or capacity to which the appointment is tied (e.g. a hairdresser, a trainer, a treatment room).
• User Account: the login identifier within the Workspace, tied to an e-mail address. Its roles are: owner (owner), admin (administrator), staff (staff member).
• End User: the natural person who books an appointment on the Subscriber's booking interface, or cancels their booking.
• Plan: the pricing and limit tiers announced by the Provider (Solo, Studio, Multi, Team).
• Trial Period: the free period under Section 7, available without providing a payment card.
• Non-Entitled State: the state under Section 7.3 (expiry of the Trial Period without a paid subscription) and under Section 15.9 (the data-retention grace period following termination of the agreement), in which the administration interface is readable and data export works, but no modifying operation can be performed, and the Service is not available to End Users either (public booking page, embedded interface and other channels).
• Locking: the reversible state under Section 8.3, in which a Calendar cannot be booked publicly and its settings cannot be modified, but it is not deleted and does not lose any data.
• Payment Provider: Stripe (see Section 6.3). Invoicing Partner: Számlázz.hu (KBOSS.hu Kft.) (see Section 6.4).
• Programmatic Interface: the versioned REST API (/api/v1) and the MCP interface of the Service, with API-key authentication.
• Integration Client: the third-party system (e.g. a messaging/chatbot platform or the Subscriber's own system) that uses the Service through the Programmatic Interface.
• Availability Target: the availability target value per calendar month under Section 10.1, to which the service credit under Section 10.3 attaches as the exclusive remedy.
• Supplementary Terms: terms published by the Provider for specific functions or fields of use, which become part of the agreement pursuant to Section 23.4.

These GTC do not use the concept of consumer under point 3 of Section 8:1(1) of the Civil Code, because the Service is not available to consumers pursuant to Section 4.5. This does not affect the provisions of Section 2(a) of Act CLV of 1997 on Consumer Protection (Fgytv.) concerning the conciliation board; those are governed by Section 16.3.

4. Subject matter of the Service

4.1. The Provider provides the Service "as is", with its functionality as it exists from time to time, within the limits of the Plan chosen by the Subscriber. The Service includes:

• the management of calendars, resources, work schedules, exceptions (holidays, closures), services and booking rules;
• the automatic calculation of bookable appointments and the recording of bookings, for both individual (single-participant) and group (multi-participant) sessions;
• a public booking page for every published calendar;
• an embeddable booking interface (widget) for the Subscriber's own website;
• a calendar subscription (ICS) feed for the calendar client of the Subscriber and its staff;
• programmatic interfaces: a versioned REST API (/api/v1) and an MCP interface, with API-key authentication;
• automatic transactional e-mails (confirmation, cancellation, reminder);
• the cancellation of bookings by means of a single-use cancellation link sent to the End User, valid for a definite period.

The functional content of the Service from time to time is determined by the plan description published on the https://meetply.com website and by the administration interface. No function of the Service is tied to a Plan: the Plans differ exclusively in the limits set out in Section 8.

4.2. Settlement of the consideration for the appointment. As a general rule, the End User and the Subscriber settle the consideration for the appointment between themselves, outside the Service (Section 18.5). The Service may — per calendar or per service, according to the Subscriber's setting and independently of the Plan (Sections 4.1 and 8.1) — allow the Subscriber to attach online payment to the booking (e.g. a deposit, a cancellation fee or payment of the full consideration at the time of booking) through the Payment Provider under Section 6.3; making this available qualifies as a functional extension under Section 4.3 and therefore does not in itself require an amendment of these GTC. The activation of online payment, its amount and the conditions applicable to refunds and cancellations depend on the Subscriber's decision and fall within its sphere of responsibility under Section 18.4; in this respect the Provider ensures only the technical execution of the payment.

4.3. Continuous development of the Service. The Service is a continuously developed software service with a changing feature set. The Provider is entitled to extend the Service with new functions and to develop its existing functions. Making a new function available does not in itself qualify as an amendment under Section 14.2, provided that it does not adversely affect the Subscriber's existing rights and that its use depends on the Subscriber's decision. The discontinuation, material restriction or making chargeable of an existing material function is governed by Section 14.2. This Section does not affect the sub-processor notification procedure under the DPA, nor the Provider's information obligation under Article 13 of the GDPR.

4.4. What the Provider does not provide. The Provider does not provide the service that the appointment is for and does not participate in its performance; it does not check the content, lawfulness, quality or price of the Subscriber's service. The Service determines the bookable appointments — irrespective of the interface or channel used (e.g. public booking page, widget, programmatic interface, messaging/chat-based integration) — exclusively on the basis of computational rules: the availability and conflict check, as well as the recording of the booking itself, is never the decision of a language model or artificial intelligence, but the deterministic logic of the booking core under Section 4.1. If a channel — whether the Provider's or that of an Integration Client — uses artificial intelligence or a language model for communication with the End User, this affects only the communication layer; it does not influence the substantive conditions or the validity of the booking, and does not qualify as content provided by the Provider. Such an Integration Client — including another messaging/chatbot platform using artificial intelligence — may initiate a booking exclusively through the Programmatic Interface under Section 3 (the MCP server), by way of a separate connection established with the Provider; without this it cannot access the Service.

4.5. The Service is not for consumer purposes. The design, functions and business model of the Service are aimed exclusively at supporting professional, business, organisational or public-duty activity. The Provider neither offers nor provides the Service to consumers. By the declaration under Section 5.4, the Subscriber concludes the agreement within the scope of its profession, self-employed occupation or business activity, and therefore does not qualify as a consumer (point 3 of Section 8:1(1) of the Civil Code), and the right of withdrawal/termination under Government Decree No. 45/2014 (II. 26.) on the detailed rules of contracts between consumers and undertakings does not apply.

4.6. Presumption. If the Subscriber does not provide complete organisational data during registration, the Provider shall regard the order as having been placed by the Subscriber within the scope of its activity under Section 4.5, on behalf of the organisation it represents, with appropriate powers of representation. The Provider has no obligation to examine the substantive truth of the declaration under Section 5.4: beyond the formal check of the registration data under Section 5.3, the Provider is not obliged to examine whether the Subscriber is in fact acting within the scope of its profession, self-employed occupation or business activity — the Provider has no means to do so, and responsibility for the correctness of the declaration lies with the Subscriber (Section 4.7).

4.7. Rebuttal of the presumption. If it subsequently turns out that the Subscriber used the Service as a consumer despite Section 4.5:

• a) in the case of a good-faith misclassification, the Provider may terminate the agreement with immediate effect and shall refund the fee for the unused period on a pro rata basis;
• b) if the declaration under Section 5.4 was knowingly untrue, this qualifies as a material breach of contract (Section 15.5) and no refund is due.

Neither case affects the rights to which a consumer is entitled by operation of law.

4.8. Territorial scope. The Service is currently available to Subscribers established in the Member States of the European Union; in the case of a sole trader or another Subscriber without a registered seat, the place of establishment is to be determined according to the place of registration or, failing that, the place where the activity is carried out. The Provider is entitled to extend geographical availability to further countries; it publishes the conditions for this by amending these GTC.

5. Conclusion of the agreement, registration, user accounts

5.1. In order to use the Service, the Subscriber must register on the https://meetply.com website, providing accurate data, either directly or through a third-party identification service. The Subscriber is responsible for the accuracy of the data provided and for keeping it up to date.

5.2. Conclusion of the agreement and proof of acceptance. The agreement is concluded electronically, for an indefinite term, during registration, when the person acting on behalf of the Subscriber expressly accepts these GTC on the registration form (by ticking a checkbox) and submits the registration. The actual use of the Service is tied to the prepaid billing period (month or year) under the chosen Plan, which renews by automatic charge under Section 6.2 until the Subscriber terminates the agreement pursuant to Section 15. The agreement does not qualify as a contract put in writing and is not filed by the Provider.

5.3. Data content of the registration. The Subscriber is obliged to provide: (a) the name and registered seat of the organisation; (b) its tax number and EU VAT number, if any; (c) at least one registration identifier (company registration number, sole trader registration number, court or ecclesiastical registration number, public-body register identifier or other official registration number); (d) the name and contact details of the natural person acting on its behalf.

The Provider is entitled to verify this data — including the verification of the EU VAT number in the Union database — and to refuse registration or suspend the account if the data is incomplete, untrue or unverifiable. The Provider may refuse registration if the applicant is a natural person holding only a tax number (private individual with a tax number, primary producer) and is unable to provide the identifier under point (c).

5.4. Declaration. During registration, the Subscriber declares by a separate, active act that it uses the Service within the scope of its activity under Section 4.5; the person carrying out the registration also warrants that they are entitled to accept these GTC and to conclude the agreement on behalf of the Subscriber. The Provider logs the declaration and the time of it.

5.5. Access credentials, API keys, ICS links. The Subscriber is responsible for the confidential handling of the login credentials belonging to its accounts, for keeping the set of users up to date (for revoking the access of a departed staff member), and for all activity carried out with its accounts. The same applies to the API keys and ICS links belonging to the Workspace: whoever holds them can access data within the scope associated with the key, and they must therefore not be shared with third parties; in the event of compromise, the Subscriber is obliged to replace (rotate) them without delay in the interface.

5.6. Suspension. The Provider is entitled to suspend the account or the Workspace if its use infringes legislation, infringes the right of a third party, endangers the security or operation of the Service, or in the event of payment delay under Section 6.5.

6. Fees and payment terms

6.1. Pricing. The use of the Service takes place in accordance with the pricing in force from time to time, published on the https://meetply.com website. The published prices are net prices; value added tax under the VAT rules of the country of the Subscriber's registered seat is added to them. If the Subscriber is an undertaking established in a Member State of the European Union holding a valid EU VAT number and the conditions for reverse charge are met, the Provider issues the invoice with 0% VAT, with self-assessment by the Subscriber. These GTC govern the conditions for using the Service and do not set out the specific amounts of the pricing; the names of the Plans and the differences in limits between them are set out in Section 8.

6.2. Billing cycle. The Subscriber may choose between a monthly and an annual cycle. The fee is due in advance at the beginning of the cycle and renews automatically at the end of the cycle by charging the payment instrument registered with the Payment Provider, unless the Subscriber cancels the subscription pursuant to Section 15.

6.3. Method of payment. Payment of the fee is made by payment card, on the payment interface of the Payment Provider, by automatic charge. The Subscriber provides its payment data directly on the interface of the Payment Provider; the Provider does not see, store or process payment card data.

6.4. Invoicing. The Provider issues and retains an electronic invoice for every successful charge, through the system of the Invoicing Partner, and makes it available to the Subscriber's billing e-mail address and in a form accessible in the interface of the Service.

6.5. Payment delay. In the event of an unsuccessful card charge, the Provider grants a 10-day grace period to settle the payment. If the charge is unsuccessful during the grace period as well, the Provider may suspend the Workspace pursuant to Section 5.6: the public booking page, the embedded interface and other channels available to End Users become unavailable, whereas the administration interface and data export remain accessible, and the suspension may be lifted at any time by subsequently settling the payment. If the payment delay persists despite the written notice under Section 15.5, the Provider may terminate the agreement with immediate effect; in such a case, the retention and deletion rules under Section 15.9 apply to the Workspace data. This risk is borne by the Subscriber.

6.6. Fee modification. The fee remains unchanged for an already paid subscription period (Section 14.5). The Provider may modify the pricing — as regards the Subscriber's existing subscription — at most once per calendar year, with effect from 1 March; it notifies the Subscriber thereof pursuant to Section 14.2, at least 30 days before entry into force, electronically and in the interface of the Service.

Entry into force on 1 March relates to the pricing. For the Subscriber, the modified fee applies from its next renewal (Section 6.2). The Subscriber accepts the modified fee by renewing; if it does not accept it, it may terminate the agreement with effect from the date of renewal.

This Section does not restrict the Provider in setting the pricing for new subscriptions not yet concluded.

The following do not qualify as a fee modification under this Section: a fee reduction; the introduction of a promotional or discounted fee; the expiry of a promotional or discounted fee upon the lapse of its announced duration, if the Provider published the duration of the discount when it was taken up; and furthermore the effect on the gross price of a change in the tax rate based on legislation — in particular a change in the rate of value added tax — which does not affect the net fee under Section 6.1.

7. Trial Period

7.1. The Trial Period. Upon the creation of the Workspace, the Subscriber receives a 14 calendar day free Trial Period, without providing a payment card: the Provider does not initiate an automatic charge at the end of the Trial Period and does not issue an invoice for it.

7.2. Limits of the Trial Period. The Trial Period runs with the limits of the Studio Plan (Section 8); all functions of the Service are available during it as well.

7.3. Consequence of the expiry of the Trial Period. If no paid subscription is created during the 14 days of the Trial Period, the Workspace enters the Non-Entitled State upon the lapse of the last day of the Trial Period (Section 3): the public booking page, the embedded interface and other channels available to End Users become unavailable, whereas the administration interface and the data export under Section 15.6 remain accessible for a further 30 calendar days. The Provider notifies the Subscriber electronically of the onset of the Non-Entitled State and of the expected date of deletion.

Upon the lapse of the 30 calendar days, the Provider permanently deletes all data of the Workspace. The only exceptions to deletion are data which the Provider is required by law to retain (in particular accounting and tax documents) or the retention of which is necessary for the enforcement of claims (Section 15.9). This 30-day period is not cumulative with the grace period under Section 15.9. This risk is borne by the Subscriber.

A paid subscription created at any time during the Trial Period or during the 30 calendar day period restores the Workspace without any restriction.

7.4. One-time availability. The Trial Period may be used once per Workspace; the Provider may refuse it if the same undertaking creates a new Workspace solely for the purpose of using it again.

8. Plans, limits and the Locking of a Calendar

8.1. The Subscriber may obtain information about the Plans and their limits (Calendar, Resource, User Account) at any time on the https://meetply.com website; the fees are set out in the pricing under Section 6.1. There is no functional difference between the Plans, they differ exclusively in their limits (Section 4.1). The fee and conditions of the Team Plan are the subject of an individual agreement, which does not raise the absolute liability cap under Section 13.1(4).

8.2. If the Subscriber were to reach one of the limits (e.g. by creating a new calendar, resource or user account), the operation is rejected until it switches to a larger Plan; this does not affect existing data.

8.3. Locking of a Calendar. If the Subscriber switches to a Plan with lower limits — or its Plan is reduced due to an intervention at the Payment Provider — and the number of calendars in the Workspace consequently exceeds the new limit, it must select which calendars are to remain active; the rest enter the locked state (in the absence of a selection, the ones created earliest remain active). A locked calendar cannot be booked publicly, but its data is retained and remains accessible in the administration interface; locking — unlike deletion or archiving — may be lifted at any time (by upgrading the Plan or by locking another calendar), whereupon the calendar becomes available again with unchanged content, at the same web address.

8.4. An upgrade of the Plan takes effect immediately, with pro rata settlement by the Payment Provider.

9. Rights and obligations of the Subscriber

9.1. The Subscriber is entitled to use the Service within the framework of the chosen Plan, in accordance with these GTC.

9.2. Lawful use and legal basis. The Subscriber warrants that it has an appropriate legal basis in respect of the data entered into the Service and that it uses the Service lawfully.

9.3. Own information obligation. The Subscriber is obliged to provide information, in its own name and as controller, to its own clients (End Users) about the processing of their data, including the fact that the Provider participates as processor in the processing of the booking data (see Section 17). The Subscriber is obliged to ensure the legal compliance of its own digital interface (its own privacy notice, cookie notice, terms and conditions).

9.4. Prohibited use. The Subscriber may not use the Service:

• a) for sending unsolicited messages;
• b) for reverse engineering the Service, circumventing access restrictions, or attempting to access the data of another subscriber;
• c) for automated load testing without the Provider's prior written permission;
• d) for reselling the Service without the Provider's prior written consent;
• e) for displaying content that infringes legislation or the right of a third party.

9.5. Displayed content. The Subscriber is responsible for the content it displays in the calendar, in a service name, in a description or in any other freely editable text field. The Subscriber acknowledges that a service name may in itself convey sensitive information about the End User; the choice of names is the Subscriber's decision as controller.

9.6. Correctness of data entry. The Subscriber is responsible for the correctness and currency of the data it provides (work schedule, exceptions, service duration, buffer, booking rules, e-mail addresses), and for checking it before going live and regularly during use.

9.7. A breach of this Section qualifies as a material breach of contract and entitles the Provider to the indemnification claim under Section 13.9, as well as to the immediate suspension under Section 5.6 and to termination with immediate effect under Section 15.5.

10. Rights and obligations of the Provider; availability and support

10.1. Availability Target. The Provider sets an availability target of 99.0% for the availability of the Service per calendar month, which it calculates on the basis of the data of its own monitoring system, in proportion to the total number of minutes in the month. Continuous outages of less than five minutes are disregarded. The Provider makes the measurement data accessible upon the Subscriber's written request.

10.2. Maintenance. The Provider may suspend the Service for maintenance purposes. Where possible, it provides advance information about planned maintenance on the website and/or in the administration interface; the absence of such information does not affect the right to carry out maintenance. Extraordinary maintenance may be carried out without prior information in the event of a security incident, the prevention of data loss or a statutory obligation.

10.3. Service credit — exclusive remedy. If the Service did not reach the Availability Target in a calendar month, the Subscriber is entitled to a service credit upon written request submitted within 30 days of the end of the month, specifying the period concerned and the fault experienced; in the case of an incomplete request, the Provider may request that the deficiencies be remedied. The amount of the service credit is the part of the subscription fee for the month concerned that is proportionate to the duration of the outage, based on the Provider's measurement data, which the Provider deducts from the fee for the next billing period; no cash payment is due. The annual total of the service credits may not exceed one month's subscription fee; unused service credit is forfeited upon termination of the agreement and cannot be claimed during a payment delay. No service credit is due during the Trial Period or in the case of free use.

If the Service did not reach the target in two consecutive months, the Subscriber may terminate with immediate effect within 30 days of the end of the second month; in such a case the Provider refunds on a pro rata basis the prepaid fee attributable to the unused period.

The service credit, and the right of termination and refund, are the Subscriber's sole and exclusive remedy for failure to reach the Availability Target; no other claim — including a claim for damages — may be asserted on that basis, except within the scope of Section 13.4.

10.4. Causes outside the Provider's sphere of responsibility. An outage does not fall within the Provider's sphere of responsibility — and is not included in the calculation of the service credit under Section 10.3 — if it is caused by:

• a) maintenance under Section 10.2;
• b) a fault of the Subscriber's device, network, configuration or access credentials, or a modification carried out by the Subscriber;
• c) faulty configuration of the Workspace, the Calendar or the Service by the Subscriber (Section 9.6);
• d) the malfunction, restriction or cessation of a third-party service, including the hosting, payment, invoicing and e-mail providers, as well as the Integration Client;
• e) lawful suspension of the Service (payment delay, breach of the GTC, security incident, statutory obligation);
• f) force majeure under Section 22;
• g) a DDoS or other malicious attack;
• h) an intervention requested or approved by the Subscriber;
• i) the outage of a supplementary function provided in beta, on an experimental basis or free of charge.

10.5. Fault reporting and support. Faults may be reported at support@meetply.com. The Provider processes reports on business days; the Provider does not undertake a specific response time. If the Provider undertakes a response time in the future, it will publish it in the procedure under Section 14.2.

10.6. Subcontractors, contributors. The Provider uses contributors to provide the Service, for whose activities it is liable as if it had acted itself. The list of processors participating in the processing of personal data from time to time is set out in the Privacy Notice, and the set of sub-processors processing the personal data of End Users is set out in the annex to the DPA, including in particular:

• Hetzner Online GmbH (Germany) — hosting and operating infrastructure;
• Stripe Payments Europe, Limited and its affiliates — subscription management and payment;
• KBOSS.hu Kft. (Számlázz.hu) (Hungary) — invoice issuance;
• Mailjet SAS (France; member of the Sinch AB group) — delivery of transactional e-mails.

The Provider gives at least 30 days' advance notice of any material modification of the list.

10.7. Updates, maintaining conformity. The Provider provides the Service with the skill and care reasonably expected in the industry and, during the subscription, provides the updates necessary to maintain conformity, including security updates. The updates do not require the notification procedure under Section 14, because they do not change but maintain that to which the Subscriber is entitled.

10.8. Reference. The Provider is entitled to name the Subscriber and use its logo as a reference, unless the Subscriber prohibits this in writing.

11. Intellectual property; embedding and programmatic interfaces

11.1. Intellectual property in the Service. The Service, its source code, interface, design, visual identity and documentation, as well as the MeetPly name and logo, are the exclusive intellectual property of the Provider (or its licensors). The Subscriber acquires a non-exclusive, non-transferable right of use, limited to use in accordance with the agreement, for the use of the Service for the term of the agreement, exclusively in accordance with these GTC.

11.2. The website. Pursuant to Section 1(1) of Act LXXVI of 1999 on Copyright (Szjt.), the meetply.com website qualifies as a copyrighted work, and therefore every part of it is protected by copyright. Pursuant to Section 16(1) of the Szjt., it is prohibited to use without permission the graphic and software solutions, photographs, texts and computer program works found on the website, or to use any application by means of which the website may be modified. Material may be taken from the website — even with the Provider's written consent — only with a reference to the website and an indication of the source. The rightholder is: SolvePly Kft.

11.3. Embedding. The Subscriber may place the embeddable booking interface on its own website; embedding is limited to the domains recorded in the embedding allowlist of the Service. The Subscriber is responsible for the lawfulness of its own website, including the information and consent management relating to the cookies and trackers placed on its own website.

11.4. Programmatic interfaces. An API key is required to use the programmatic interfaces (REST API, MCP). The Provider operates the interfaces with reasonable usage limits (rate limits) and may restrict abusive use. The Subscriber, or the integration partner engaged by it, is responsible for bookings created through the programmatic interface, and for the Integration Client having informed the End User appropriately and having obtained the necessary legal basis (see Sections 13.7 and 18.6).

11.5. The Subscriber's content. The data and content entered into the Service by the Subscriber (calendar and service names, descriptions, logo, booking rules, the data of the Workspace) remain the property of the Subscriber. The Provider acquires in respect of them only a non-exclusive right of use necessary for providing the Service, for the term of the agreement.

12. Confidentiality

12.1. The parties treat as confidential the non-public information relating to the business activity of the other party that comes to their knowledge during the performance of the agreement (Confidential Information), and use it exclusively to the extent necessary for the performance of the agreement.

12.2. The parties do not disclose the Confidential Information to third parties without the prior consent of the other party, except in the case of a statutory or official obligation. It does not qualify as disclosure if the Provider transfers the Confidential Information to the contributors under Section 10.6, to the extent necessary for the provision of the Service.

12.3. Data which is already publicly available at the time of disclosure, which was published by the party concerned itself, or which the other party lawfully obtained from a third party, does not qualify as Confidential Information.

12.4. The Provider's employees and contributors are bound by a contractual confidentiality obligation.

12.5. The confidentiality obligation survives the termination of the agreement for 3 years.

13. Liability

13.1. Caps

(1) General cap. The Provider's liability is limited on an aggregate basis: as against the given Subscriber, in any 12-month period — for all damage-causing events taken together, irrespective of the legal basis of the claim — it may not exceed the sum of the net subscription fees actually paid to the Provider by the Subscriber in the 12 months preceding the damage-causing event. In the case of a shorter contractual term, the actual term is decisive.

(2) What counts as a paid subscription fee. Subscription fee actually paid means exclusively the regular basic subscription fee under the chosen Plan. It does not include one-off setup or other one-off fees, default interest and collection costs, nor revenue arising from a partner or reseller programme. The service credit under Section 10.3 counts towards the general cap.

(3) Free period. If, at the time when the damage-causing event occurs, the Subscriber is using the Service free of charge — during the Trial Period, during the 30-day period under Section 7.3, during the grace period under Section 6.5, for testing purposes or by virtue of an individual discount — the general cap is replaced by an amount corresponding to six months' fee of the Provider's lowest-priced publicly announced Plan from time to time.

(4) Absolute cap. The Provider's total liability as against the given Subscriber in any 12-month period — irrespective of the above caps and of the amount of the fees paid — may in no case exceed an amount corresponding to 12 months' fee of the Provider's highest-priced publicly announced Plan from time to time. This cap is not raised in the case of a subscription agreed individually at a price that is not publicly announced (Team Plan) either.

13.2. Application of the caps

(1) The caps under Section 13.1 are not cumulative. The same event cannot fall under two caps at the same time; if more than one could apply, the higher one applies, but only once.

(2) Requirement of proven damage. The caps are exclusively upper limits: they do not in themselves create any payment obligation, and do not mean any automatic or lump-sum payment. A precondition of compensation is that the Subscriber proves its actual, quantifiable damage and the causal link; the Provider is obliged to compensate only the proven amount.

13.3. Exclusion of indirect and consequential damage

The Provider — to the extent permitted by law — is not liable for the following damage, irrespective of the legal basis of the claim, and even if it knew or should have known of the possibility of the damage: indirect damage; consequential (incidental) damage; lost profit and revenue; lost business opportunity, loss of revenue due to a contract not concluded or an appointment not taking place; failure to achieve expected savings; damage resulting from business interruption and the cost of a substitute solution; consequential damage resulting from data loss, data corruption or data restoration, including the irrecoverability of booking data automatically deleted or anonymised under the DPA upon the expiry of the retention period set for the Calendar; damage resulting from harm to reputation or business goodwill; any contractual penalty or other undertaking assumed by the Subscriber towards a third party, including its End User.

The damage excluded here is excluded before the application of the caps under Section 13.1, i.e. it is not included in them and cannot be asserted within them either.

13.4. Exceptions to the limitation of liability

Sections 13.1–13.3 do not apply to (a) damage caused by the Provider intentionally or by gross negligence; (b) damage caused by a breach of contract harming human life, physical integrity or health; (c) damage falling within the scope of liability that cannot be excluded or limited by law. Everything else, including damage caused by slight negligence, falls within the scope of Sections 13.1–13.3.

13.5. The service that the appointment is for

(1) The Provider provides a software service. It is not liable for claims arising from the legal relationship between the Subscriber and the End User, for an appointment not taking place, for the End User's failure to appear, for delay, or for the content, quality, pricing and lawfulness of the Subscriber's service.

(2) The organisation of the Subscriber's service, the design of the cancellation and no-show rules and their enforcement towards the End User are exclusively the task and responsibility of the Subscriber.

13.6. The Subscriber's data entry and content

(1) The Provider is not liable for consequences arising from incorrect data provided by the Subscriber (e.g. an erroneous work schedule, an incorrect e-mail address, a mistyped service duration, an incorrectly configured buffer or booking rule), including incorrectly advertised or missing available appointments and notifications sent to an incorrect address.

(2) The Provider is not liable for damage arising from the content displayed by the Subscriber, including the case under Section 9.5, where a service name or description in itself conveys sensitive information about the End User.

(3) If the Subscriber fails to comply with its checking obligation under Section 9.6, and the damage arose in connection with that or its extent increased for that reason, the parties bear the damage in proportion to their responsibility, pursuant to Section 6:525 of the Civil Code.

(4) The Provider's own system failure. The exclusion under paragraphs (1)–(2) does not apply — and liability is governed by the general regime of Sections 13.1–13.2 — to a fault arising from a culpable failure of the Provider's own system, in particular from a software error, a malfunction, or the incorrect processing, corruption or erroneous transmission of data provided by the Subscriber.

13.7. Bookings arriving through an integration channel

(1) An appointment may also be booked through the programmatic interface, from an Integration Client (for example a messaging platform). In such a case, the Integration Client transfers the End User's name, e-mail address and telephone number to the Service, accompanied by a short-lived, digitally signed identity assertion.

(2) In this case, the operator of the Integration Client, or the Subscriber, is responsible for informing the End User and for ensuring the necessary legal basis; the Provider processes the transferred data as the Subscriber's processor.

(3) The Provider does not warrant the correctness, completeness and timeliness of the data transferred by the Integration Client, and is not liable for the operation, malfunction or cessation of the Integration Client. The secure handling of the API keys and of the keys producing the identity assertion, the narrowing of their scope of authorisation to the necessary and sufficient extent, and their periodic replacement are the Subscriber's responsibility (Section 5.5). On this channel, proof of acceptance of Sections 18–21 is not necessarily created in the Service (see Section 18.6).

13.8. Data loss, backups

The Provider makes regular backups. It is recommended that the Subscriber, in its own interest, regularly export its own data by the means under Section 15.6. Consequential damage resulting from data loss is governed by Section 13.3.

13.9. The Subscriber's indemnification obligation

(1) The Subscriber is obliged to fully indemnify and hold harmless the Provider in respect of any claim, demand, damage, fine and cost (including reasonable legal representation costs) asserted by a third party (including its End Users and clients) or enforced by an authority, which arises from:

• a) data or content entered into the Service by the Subscriber, including service names and descriptions (Section 9.5), as well as claims based on infringement of intellectual property rights;
• b) breach of the Subscriber's data entry, configuration or checking obligation (Section 9.6);
• c) breach of the Subscriber's obligations as controller — such as informing End Users and ensuring the legal basis (Sections 9.3 and 17);
• d) the use and configuration of the Integration Client and the bookings carried out through it (Sections 11.4 and 13.7);
• e) inappropriate handling of user accounts, API keys and ICS links (Section 5.5);
• f) prohibited use under Section 9.4;
• g) the legal relationship created between the Subscriber and the End User for the service that the appointment is for (Section 13.5);
• h) any other breach of these GTC.

(2) This obligation also exists if the claim is asserted directly against the Provider; in such a case the Subscriber is obliged to reimburse the Provider's well-founded damage and costs. The Provider is obliged to inform the Subscriber of the claim without delay and to give it the opportunity to participate in the defence; the Provider shall not settle the claim by way of a settlement agreement imposing an obligation or an admission on the Subscriber without the Subscriber's prior written consent.

(3) Privity of contract. This Section governs the internal reimbursement relationship between the parties and does not preclude the End User or another third party from asserting its claim directly against the Provider under the law. Nor does it affect the statutory allocation of liability towards the data subject under Article 82 of the GDPR.

(4) Limits. The indemnification does not extend to that part of the claim which arises from the Provider's liability under Section 13.4 or from a culpable failure of its own system under Section 13.6(4). In such a case the parties bear the damage in proportion to their responsibility. The purpose of this limitation is to keep the stipulation in line with Section 6:152 of the Civil Code.

13.10. Notification of claims, limitation, consolidation of claims

(1) The Subscriber is obliged to notify its claim in writing — specifying the underlying facts and the extent of the damage — within 30 days of becoming aware, or of having been able to become aware, of the underlying circumstance. In the event of failure to notify or of delayed notification, the Provider is released to the extent that this led to an increase in the damage or to the frustration of mitigation or of proof.

(2) Pursuant to Section 6:22(3) of the Civil Code, the parties agree that the Subscriber's claims arising in connection with these GTC or with the provision of the Service become time-barred within 12 months of the occurrence of the conduct or event leading to the damage.

(3) Consolidation of claims. The Subscriber is obliged to submit all of its claims arising from the same or connected facts as a single, consolidated claim. Damage arising from the same circumstances — including the damage of the Subscriber, its affiliates, End Users and clients, as well as damage affecting several Calendars or Workspaces of the Subscriber — qualifies as a single claim for the purposes of these GTC. A claim may not be split in such a way as to achieve multiple application of the caps.

(4) Paragraphs (1)–(2) of this Section do not apply within the scope of Section 13.4.

13.11. Nature and survival of the limitations

(1) The exclusions and limitations under this Section 13 apply irrespective of the legal basis of the claim, and also where a limited remedy has failed of its essential purpose.

(2) The exclusions and limitations survive the termination of the agreement.

(3) The parties record that the allocation of risk under this Section reflects a mutually accepted, reasonable allocation of risk taken into account in setting the pricing and adjusted to the nature of the Service and the level of the consideration.

(4) If any provision of this Section proves to be invalid, this does not affect the validity of the remaining provisions, and it is replaced by a valid provision closest to the parties' original intention.

14. Amendment of the GTC and the pricing

14.1. The Provider is entitled to amend these GTC and the pricing unilaterally. Amendment takes place exclusively by issuing a new version; the Provider does not subsequently modify the text of a published version.

14.2. Notification. The Provider notifies the Subscriber of an amendment that adversely affects the Subscriber — in particular an increase of the fee, a narrowing of the Plan limits, the discontinuation of a material function or a narrowing of liability — at least 30 days before entry into force, electronically (to the e-mail address provided at registration) and in the interface of the Service.

14.3. This procedure does not apply to updates and security updates serving the maintenance of conformity under Section 10.7, or to making new functions available under Section 4.3.

14.4. Acceptance or rejection of the amendment. If the Subscriber does not accept the amendment, it may terminate the agreement until the entry into force of the amendment; in such a case, the unused, prepaid fee is refunded on a pro rata basis. Further use after the entry into force of the amendment qualifies as acceptance of the amendment.

14.5. A modification of the fee does not affect the current, already paid billing cycle. Section 6.6 lays down further limits binding on the Provider as to the frequency of fee modification, the date of its entry into force and the exceptions to it.

15. Termination of the agreement, notice, data export

15.1. Cancellation by the Subscriber. The Subscriber may cancel the subscription at any time, without giving reasons and without a notice period, on the self-service interface provided by the Payment Provider and accessible in the billing interface of the Service.

15.2. Effect of cancellation. Cancellation takes effect at the end of the current billing cycle: the Service remains entitled without change until the end of the paid cycle, after which the Workspace enters the Non-Entitled State under Section 15.9. The Provider does not initiate any further charge at the end of the cycle. This rule does not affect the Subscriber's right under Section 15.7 to have the agreement terminate within two months at the latest.

15.3. Refund. The fee for the Service is the consideration for a prepaid service for a definite period. The fee for a billing cycle that has already started is not refunded on a pro rata basis, except where:

• a) the Provider terminates the agreement pursuant to Section 15.4, or on the basis of Section 4.7 a), for a reason not attributable to a breach of contract by the Subscriber — in which case the Provider refunds the fee attributable to the unused period on a pro rata basis;
• b) the Subscriber terminates pursuant to Section 14.4, due to rejection of an amendment;
• c) the Subscriber is entitled to a service credit under Section 10.3;
• d) the Provider carries out the transfer of contract under Section 23.3 and the Subscriber does not accept it;
• e) legislation provides otherwise.

15.4. Ordinary termination by the Provider. The Provider may terminate the agreement with 30 (thirty) days' notice, without giving reasons; in such a case it refunds the unused, prepaid fee on a pro rata basis.

15.5. Termination with immediate effect. The Provider may terminate the agreement with immediate effect if the Subscriber commits a material breach of contract, in particular if it uses the Service in a manner infringing legislation or the right of a third party, endangers the security or operation of the Service, fails to settle its payment delay within 30 days despite a written notice, breaches its obligations under Section 9, or made an untrue declaration under Section 4.7 b). In such a case the Provider may also suspend the Service instead of or prior to termination (Section 5.6).

15.6. Data export and switching providers. The Subscriber is entitled to export its own data. This includes in particular: the settings of the Workspace and the Calendars; the resources, work schedules and exceptions; the services and booking rules; the bookings and the related participant data; the register of user accounts and roles; the notification log; the billing and subscription data, as well as the invoices issued. The list is illustrative and extends to any other digital asset that qualifies as the Subscriber's own data.

During the term of the agreement, the Provider provides data export at any time, free of charge, in the administration interface, in a structured, commonly used, machine-readable format (typically JSON, and CSV for tabular data), as well as through the calendar feed (ICS). Data export also remains available during the 30-day period under Section 7.3, until deletion, and throughout the entire duration of the suspension under Section 6.5.

This provision relates to the Subscriber's own data. The deletion or return of the End Users' personal data upon termination of the agreement is governed by the DPA, since in respect of that data the Subscriber is the controller (Section 17.1).

15.7. Switching conditions (Data Act). The Provider does not charge a fee for data export and for switching providers, and makes available — in documentation-based form — the information relating to the structure and format of the exported data; this does not extend to bespoke migration development. No notice period attaches to cancellation under Section 15.1: the Subscriber may initiate cancellation at any time, with immediate effect, and the data export under Section 15.6 remains fully available both before the cancellation is initiated and during the grace period under Section 15.9.

Two months at the latest. By way of derogation from the main rule under Section 15.2, the agreement — upon the Subscriber's express request to that effect — terminates no later than two months from the communication of the notice of termination, even if the paid billing period is longer than that (annual cycle). In such a case the Provider refunds on a pro rata basis the prepaid fee attributable to the unused period. The purpose of this provision is to ensure that switching providers can in all cases be completed within the maximum two-month termination cap under Article 25 of Regulation (EU) 2023/2854 (Data Act). The Subscriber may notify this request at the contact details under Section 16.1 or in the administration interface.

15.8. Cancellation during the Trial Period. If the Subscriber cancels the Workspace during the Trial Period — still before any payment of a fee — the Provider deletes its data without delay after the cancellation is finalised; in such a case neither the grace period under Section 15.9 nor the 30 calendar day period under Section 7.3 applies.

The reason for this is the Subscriber's express declaration aimed at terminating the Workspace. The 30-day period under Section 7.3 protects the Subscriber who merely let the Trial Period lapse passively, and for whom the data loss is therefore unintended; whereas for a Subscriber who expressly initiates cancellation, further data retention would be contrary both to its own declaration and to the principle of data minimisation. Cancellation is therefore irreversible: once deletion has taken place, the Workspace — unlike in the period under Section 7.3 — cannot be restored even by creating a paid subscription.

The Subscriber may make use of the free data export option under Section 15.6 at any time before the cancellation is finalised. The deletion of the End Users' personal data is governed by the DPA.

15.9. Data processing after termination of the agreement. Following termination, the Provider retains the Workspace data and keeps it retrievable for a grace period of 30 days, so that the Subscriber may extract it pursuant to Section 15.6, after which it deletes the data permanently. During the grace period the Workspace is in the Non-Entitled State: the administration interface is readable and data export works, no modifying operation can be performed, and the Service is not available to End Users either (public booking page, embedded interface and other channels). The risk of this — and of the consequences that may arise towards End Users as a result — is borne by the Subscriber. Exceptions to deletion are data which the Provider is required by law to retain (in particular accounting and tax documents) or the retention of which is necessary for the enforcement of claims. The details of the processing are set out in the Privacy Notice and the DPA.

16. Complaint handling and dispute resolution

16.1. Complaint handling. The Subscriber may submit its complaint relating to the Service electronically:

• Website: https://meetply.com
• E-mail: info@meetply.com

The Provider investigates the complaint and answers it on the merits within 30 days at the latest; in the event of rejection it gives reasons for its decision.

16.2. Data protection complaint. In the case of a complaint relating to the processing of personal data, the data subject may turn to the Hungarian National Authority for Data Protection and Freedom of Information (NAIH) (1055 Budapest, Falk Miksa utca 9-11.; mailing address: 1363 Budapest, Pf. 9.; ugyfelszolgalat@naih.hu; www.naih.hu), or to a court. Details are set out in the Privacy Notice.

16.3. Conciliation board procedure. Although the Subscriber is not a consumer pursuant to Section 4.5, Section 2(a) of the Fgytv. also regards as a consumer, for the purposes of applying the conciliation board rules, a civil society organisation, ecclesiastical legal person, condominium, housing cooperative and micro, small and medium-sized enterprise acting outside the scope of its economic activity; such a Subscriber may turn to a conciliation board. The competent body is the one at the Subscriber's registered seat or, failing that, at the Provider's registered seat; in an online, cross-border dispute, exclusively the board operating alongside the Budapest Chamber of Commerce and Industry. The Provider fulfils its cooperation obligation under the Fgytv. but does not make a general declaration of submission. The availability of the procedure does not affect the caps and exclusions under Section 13.

In the absence of a general declaration of submission, the decision of the conciliation board qualifies as a recommendation with regard to the Provider. This does not affect the Subscriber's statutory right to initiate the procedure.

16.4. Court proceedings. For the decision of disputes that cannot be settled by negotiation, the parties stipulate the exclusive competence of the Hungarian district court (járásbíróság) or, depending on the value of the subject matter of the action, the regional court (törvényszék) having competence at the Provider's registered seat. This stipulation applies uniformly to the parties' disputes, with the exception of the possibility of the conciliation board procedure under Section 16.3.

If the Subscriber were nonetheless to qualify as a consumer pursuant to Section 4.7, the mandatory rules on jurisdiction and competence applicable to it prevail; in that case the stipulation of exclusive competence does not apply, and the Provider may bring its action exclusively before the courts of the Member State of the consumer's domicile [Article 18(2) of Regulation (EU) No 1215/2012].

17. Data processing — data protection roles and the DPA

17.1. The booking data: the Subscriber is the controller. In respect of the booking data of End Users (name, e-mail address, telephone number, the comment written for the booking, the data of the booking), the Subscriber is the controller and the Provider is the processor, which processes this data exclusively in accordance with the Subscriber's instructions, for the purpose of providing the Service.

17.2. The DPA forms part of the GTC. The details of this legal relationship — with the mandatory content under Article 28 of the GDPR — are set out in the Data Processing Agreement (DPA), which forms an inseparable part of these GTC and is available at https://meetply.com/jogi/dpa. By accepting the GTC, the Subscriber also accepts the DPA, without a separate checkbox. In the event of a conflict — in matters concerning the processing of personal data — the provisions of the DPA prevail.

17.3. The Provider's own processing activities. In respect of the Provider's own processing activities (the Subscriber's user accounts, subscription and billing data, operational and security logs, proof of acceptance of the legal documents, support requests), the Provider is the controller; these are covered by the separate Privacy Notice, which likewise forms an inseparable annex to these GTC: https://meetply.com/jogi/adatkezeles

17.4. Cookies are governed by the separate Cookie Notice: https://meetply.com/jogi/cookie

18. Conditions for the use of the booking interface (End Users) — scope and the contracting parties

Sections 18–21 apply to the natural person who books an appointment on the public booking page or embedded booking interface of a provider (the Subscriber). By starting to use the booking interface, or by submitting the booking, the End User accepts the conditions of Sections 18–21. This part does not make the End User a party to the subscription agreement under Sections 1–17 (Sections 1.3–1.4).

18.1. Operator of the booking interface. The booking interface is operated by the Provider, with the details under Section 2.

18.2. With whom does the End User contract? The service that is the subject of the appointment is provided not by the Provider but by the provider indicated on the booking page (the Subscriber). The contract relating to the appointment is concluded exclusively between the End User and the Subscriber.

18.3. The extent of the Provider's liability towards the End User. The Provider's liability is limited to the operation of the booking interface: to displaying the available appointments, recording the booking, sending the confirmation and reminder e-mails, and providing the technical possibility of cancellation.

18.4. What the Subscriber is responsible for. The Subscriber is responsible for the duration and pricing of the appointment, for the content of the service, and for its own rules on lateness, no-shows and cancellation — including any cancellation fee. If the Subscriber applies its own terms and conditions, those apply alongside these Sections 18–21.

18.5. Booking is free of charge — as a general rule. As a general rule, no payment, deposit or cancellation fee can be made in the interface of the Service at the time of booking; the End User pays the consideration directly to the Subscriber, outside the Service (Section 4.2). If the Subscriber uses the online payment option of the Service under Section 4.2, a different rule applies to the given calendar or service — the booking interface clearly indicates this before the booking.

18.6. Bookings arriving through an integration channel. An appointment may also be booked from another system — for example from a messaging (chatbot) interface or another Integration Client, through the programmatic interface. In such a case, the calling system transfers the End User's name, e-mail address and telephone number to the Service. In this case, the operator of the calling system, or the Subscriber, is responsible for providing information and for ensuring the necessary legal basis; the Provider processes the transferred data as the Subscriber's processor. On this channel, proof of acceptance of these conditions is not necessarily created in the Service (see Section 13.7).

19. The booking process, confirmation, cancellation

19.1. Creation of the booking. The booking is created by submitting the service and appointment selected on the booking interface and the data provided (name, e-mail address, telephone number, optional comment). The Service confirms the booking by e-mail.

19.2. Holding the appointment. The displayed appointment may still be booked by someone else until the booking is submitted; the Service holds the selected appointment for a short time, but only the confirmation makes the booking final. If the appointment is already taken at the moment the booking is submitted, the Service informs the End User of this and asks them to choose another appointment.

19.3. The cancellation link. The confirmation e-mail contains a single-use cancellation link, valid for 30 days from dispatch. For security reasons, cancellation by name and e-mail address — without the link — is not possible. If the link has been lost or has expired, the End User can make arrangements directly with the provider (the Subscriber).

19.4. Correctness of the data provided. The End User is responsible for the correctness of the data they provide. In the event of an incorrect e-mail address or telephone number, the confirmation, the reminder and the cancellation link will not reach them.

19.5. The comment field. The End User should write only the information necessary for the booking in the comment field. The field is freely editable; please do not write in it any data relating to health or other particularly sensitive circumstances if it is not necessary for arranging the appointment.

20. Prohibited use of the booking interface

20.1. It is prohibited to use the booking interface in a manner involving untrue data, automated tools or the unjustified tying up of booking capacity, or which disrupts the operation of the interface. The Provider is entitled to restrict or reject abusive bookings and requests.

21. Data processing on the booking interface; amendment of the End User conditions

21.1. Who is the controller? In respect of the data provided during the booking, the controller is the provider indicated on the booking page (the Subscriber), and the Provider is its processor (Section 17.1). The End User may enforce its requests relating to the data processing (access, erasure, rectification) primarily with the Subscriber; the Provider forwards a request submitted directly to it to the Subscriber without undue delay and informs the End User thereof.

21.2. The Provider's own processing activities. The Provider's own processing activities (operation of the interface, operational security, abuse prevention) are covered by the Privacy Notice, and cookies by the Cookie Notice: https://meetply.com/jogi/adatkezeles · https://meetply.com/jogi/cookie

21.3. Amendment of the End User conditions. The Provider may amend Sections 18–21 by issuing a new version. When a booking is submitted, the version displayed and referenced on the booking interface is always decisive, and the Service records which version the End User accepted and when. On two channels this proof is not created: (a) on the integration (programmatic) channel under Section 18.6, where the booking is created by an external system, and (b) where the booking is recorded by the Subscriber or its staff member in the administration interface — in which case the End User does not use the booking interface and therefore does not accept these Sections 18–21; the Subscriber, as controller, is responsible for informing them (Sections 9.3 and 17.1).

22. Force majeure

22.1. Force majeure means any extraordinary event occurring after the conclusion of the agreement which renders its performance impossible, which the parties did not foresee at the time of concluding the agreement, which cannot be averted by reasonable measures, and which is not attributable to the culpable conduct of either party. Such an event may in particular be: a natural disaster, fire, flood, epidemic, quarantine restriction, war, revolution, act of terrorism, state of emergency, official measure, strike, nationwide electronic communications or energy supply outage, server attack, hacker attack, unauthorised server access, as well as an unavoidable outage of the hosting or network provider used by the Provider.

22.2. In the event of force majeure, neither party is liable for the failure to perform or the delayed performance of an obligation set out in the agreement.

22.3. An attack or unsolicited messaging that is attributable to the Subscriber's negligence, or that results from a breach of these GTC by the Subscriber, does not qualify as force majeure.

23. Final provisions

23.1. Applicable law. The agreement is governed by Hungarian law, within the framework of the Union conflict-of-laws rules. Matters not regulated in these GTC are governed by Hungarian law, with particular regard to the following:

• Act V of 2013 — on the Civil Code (Ptk.);
• Act CLV of 1997 — on Consumer Protection (Fgytv.);
• Act C of 2000 — on Accounting (Számv. tv.);
• Act CVIII of 2001 — on Electronic Commerce Services and Certain Issues of Information Society Services (Ektv.);
• Act CXII of 2011 — on the Right of Informational Self-Determination and on Freedom of Information (Infotv.);
• Act XLVIII of 2008 — on the Basic Requirements and Certain Restrictions of Commercial Advertising Activity (Grt.);
• Act LXXVI of 1999 — on Copyright (Szjt.).

23.2. Negotiation. The parties primarily attempt to settle their disputes arising from these GTC amicably, by way of negotiation (see Section 16).

23.3. Legal succession and transfer of contract. By accepting these GTC, the Subscriber gives its prior consent to the Provider transferring its rights and obligations arising from this agreement in their entirety (Section 6:208 of the Civil Code), or to those passing to its legal successor in the event of transformation, merger, demerger or the transfer of an economic unit (line of business), provided that (a) the transferee assumes all of the Provider's obligations under these GTC and the DPA with unchanged content; (b) the transfer does not result in an adverse change of the contractual terms for the Subscriber; (c) the Provider informs the Subscriber of the transfer at least 30 days in advance, by a notice sent to the e-mail address provided at registration, stating the transferee's name, registered seat, company registration number and tax number.

Upon the transfer, the processor relationship under the DPA also passes to the transferee; the Provider expressly informs the Subscriber, as controller, of this in the notice. If the Subscriber does not accept the transfer, it may terminate the agreement with immediate effect, free of charge, from the receipt of the notice until the entry into force of the transfer; in such a case the Provider refunds on a pro rata basis the prepaid fee attributable to the unused period (Section 15.3 d)).

The Subscriber may transfer its rights and obligations arising from this agreement only with the Provider's prior written consent.

23.4. Supplementary Terms. The Provider may publish supplementary terms for specific functions or fields of use, which become part of the agreement upon the Subscriber's express, logged acceptance. The supplementary terms may, within their own subject matter, deviate from these GTC; in the event of a deviation — exclusively within the subject matter concerned — the supplementary terms prevail. This Section does not affect the precedence of the DPA under Section 17.2 in data protection matters.

23.5. Partial invalidity. If any provision of the GTC is invalid or unenforceable, this does not affect the validity of the remaining provisions; the invalid provision is replaced by a valid provision closest to the parties' original intention.

23.6. Notices. The Provider sends its declarations addressed to the Subscriber to the e-mail address provided by the Subscriber, or through the interface of the Service; these qualify as being in writing. The Subscriber sends its declarations addressed to the Provider to the electronic mail address under Section 2.

23.7. Entire agreement clause. These GTC — together with the DPA, the Privacy Notice, the Cookie Notice, their annexes and the supplementary terms under Section 23.4 — constitute the entire content of the agreement between the parties concerning the use of the Service.

23.8. Governing language. These GTC were drafted in Hungarian, and the Hungarian-language version is the authoritative text. The Provider also publishes these GTC in English and in German; those versions are provided for information purposes only, to assist Subscribers and End Users who do not speak Hungarian, and do not create any independent contractual content. In the event of any discrepancy or difference of interpretation between the Hungarian version and a translation, the Hungarian version prevails.