Sign in

Froozy Business Terms and Conditions

Language: English · published: 7 November 2026

FROOZY BUSINESS TERMS AND CONDITIONS Document: business terms and conditions Language: English Effective date: the date of publication on the Froozy platform; for existing contracts, as provided in section 19. 1. Contracting parties 1.1. The identification and contact details of the operator of the Froozy platform appear in Appendix 4 at the end of this document. 1.2. The platform operator is referred to below as the Provider. The business using the service in the course of its business activities is the Customer. 2. Scope of the terms and subject of the service 2.1. These terms govern use of the online appointment booking and business calendar platform between the Provider and the Customer. They apply to both free and paid plans. 2.2. The Customer may be a company, sole trader or other organisation or person acting for business purposes. A Customer who is a natural person declares that they use the platform in the course of their trade or profession. This designation does not override mandatory rules applicable to the actual relationship. 2.3. Within the selected plan, the platform enables management of, in particular, the Customer's presentation page, service catalogue, locations, opening hours, bookable resources, guest requests, staff access and related notifications. The service is available through the interfaces currently published and supported. 2.4. The Customer provides the repair, personal or other actual service to the guest. The Provider neither performs that service nor is a party to the contract for it. Its price, quality, legality, performance and the agreement with the guest are the Customer's responsibility. 2.5. The platform does not collect or invoice the price payable by the guest for the Customer's service. Guests use the platform free of charge. The business's platform fee arises from a separate relationship. 2.6. The initial Hungarian offering includes general appointment booking and tyre service use. Any later new professional or payment feature becomes part of the service only after its actual introduction and separate notification. 3. Definitions and contractual documents 3.1. Business account: the interface and data set separated for the Customer. Primary user: the person designated to represent the business and manage the account's principal permissions. Staff member: a person invited by the primary user who has their own access. 3.2. Booking request: an appointment requested by a guest that still requires business approval. Confirmed booking: a request accepted by the Customer. Verification of the guest's email address does not itself constitute business approval. 3.3. Counted public request: a public guest request that has reached the state awaiting business approval through email verification or submission from an already verified guest account. The plan allowance is consumed by the number of these requests, not only by bookings subsequently accepted by the business. 3.4. Paid period: a usage entitlement associated with a specific, successfully paid plan order. Active paid period: the paid entitlement under which the Customer is using the paid plan at the relevant time. Later resumption of an entitlement placed in reserve remains part of the same purchased period. 3.5. The contract includes the version of these terms and its appendices accepted by the Customer, together with the pricing, period and plan change conditions displayed and accepted for the particular plan order. The privacy notice provides information on processing; accepting these terms is not marketing consent or general consent to data processing. 3.6. Individual order conditions govern the relevant plan, price and period; they do not implicitly override liability or data protection provisions. Earlier versions of the documents can be saved and retrieved. 3.7. These terms are based on the applicable EU legal framework. References apply within the material and personal scope of the relevant legislation. National law governing matters not regulated by EU law, and jurisdiction, are determined as provided in section 20.3. 4. Registration, representation and formation of the contract 4.1. A person authorised to represent the Customer initiates creation of the business account, providing accurate business and contact details. The primary user declares that authority when accepting these terms. A role assigned on the platform does not itself replace the legal basis for acting on behalf of the business. 4.2. Before the contract is concluded, the Provider makes the complete terms available to read, save and retrieve. The representative accepts the specific version presented by an express declaration. The separately highlighted conditions require the separate, express declaration in Appendix 2. 4.3. Before finalising registration, the registrant can check and correct the information to be submitted. The service contract is formed when the Provider confirms the business's application; access requires completion of the necessary account and email verification. The confirmation enables identification of the contract and the accepted document. 4.4. Use of an external login provider is a method of identification. It does not itself create a business, authority to represent it, a plan order or acceptance of these terms. 4.5. The language of the contract is that of the Hungarian, English or German version presented and accepted at acceptance. The other language versions do not override the language version accepted by the Customer or their mandatory rights. The Provider records the contract electronically; the Customer may request a copy of the applicable document and acceptance data at the contact address. Electronic recording does not automatically satisfy every statutory requirement for written form. 4.6. The Provider acknowledges receipt of a plan order electronically, without undue delay and, as a contractual undertaking, within 48 hours at the latest. These terms do not exclude mandatory requirements of the applicable rules transposing Articles 10–11 of Directive 2000/31/EC or the legal consequences of failure to acknowledge receipt. The 48-hour period is a contractual undertaking, not a uniform deadline prescribed by the Directive. Acknowledging receipt of an application or order does not itself confirm payment or activation of a paid plan. 4.7. If the country set in the business account is Hungary, the Customer must provide the business's valid Hungarian tax number. The Provider may query the validity of the tax number and the related data held in the register of the Hungarian National Tax and Customs Administration (name, type of taxpayer, registered office and site addresses) when the number is provided or changed and periodically thereafter. It uses the result to pre-fill registration and billing details, to reconcile the data and to apply sections 4.8–4.9. In other countries, the check published when the country is enabled applies; where an EU VAT identification number is provided, the Provider verifies it in the European Commission's VIES system. 4.8. Public bookability of the business (its public page and appearance in search, free time slots and acceptance of new booking requests) requires that the check of the tax number has been completed with a valid result. If the tax number is missing or invalid, the business does not become publicly bookable. Temporary unavailability of the authority is not an invalid result: the Provider repeats the query and may carry out a manual check where justified. If a later check shows that the tax number is no longer valid, the Provider notifies the Customer, and if the cause is not removed by the deadline stated in the notice, public bookability is suspended until the cause is removed. During suspension, existing bookings and the business interface remain available. 4.9. If the name or address in the register differs from the details provided, the Provider may carry out a review and request evidence; the difference alone does not end public bookability. The "Tax number verified" label means only that, on the date shown, the tax number was valid according to the register. It does not certify authority to represent, a professional licence or the quality of the service, and it is not continuous monitoring. When the tax number is changed, a new check takes place and the previous label ceases. Details of the data processing are set out in the Privacy Notice. 5. Access and the Customer's obligations 5.1. The Customer is responsible for the accuracy and maintenance of the service catalogue, durations, opening hours, available capacity, price indications and contact details. 5.2. Staff members work through their own user accounts. The Customer is responsible for appropriately allocating access and revoking permissions that have ended. Changes of primary user must be handled through the platform's supported procedure. 5.3. The Customer must protect login credentials and promptly report any detected unauthorised access. This obligation does not release the Provider from its own security and data protection duties. 5.4. Attacking the platform, accessing another business's or guest's data without authorisation, deceptively circumventing limits, unsolicited messaging and uploading unlawful content or data are prohibited. The Provider may take necessary, proportionate security measures and documents their reasons. 5.5. The Customer must regularly check and handle booking requests within their deadlines. Email notifications assist with checking the business calendar; they do not guarantee revenue or guest attendance. 6. The free FREE plan 6.1. The normal FREE allowance is 40 counted public requests per business per month, with one active user and one active location. The primary user counts towards the user limit. Internally entered bookings do not consume the public allowance. 6.2. Counting assigns a request to the calendar month of the time it was counted in the business's time zone. The month of the later booked service appointment is not decisive. Cancellation, rejection or expiry does not restore the allowance; rescheduling the same booking does not count as a new request. 6.3. From the first exceedance of the normal monthly allowance, that is, the 41st counted request, the FREE allowance is reduced to 20 requests per month for one calendar month. That month is calculated in the business's time zone at that time; at month ends, the corresponding last day of the following month applies. The deadline is fixed and is not recalculated following a time zone change. 6.4. Earlier requests in the month also count towards the reduced allowance of 20. A change of month and further requests above the allowance neither cancel nor extend the reduction period. When it ends, the normal monthly allowance of 40 applies again. 6.5. FREE limits do not apply during an active paid plan, but the reduction period continues to run. If the Customer returns to FREE before it ends, the monthly allowance of 20 applies for the remaining time. A later new exceedance of the normal monthly allowance may start a new reduction period. 6.6. Guests may submit requests for available capacity regardless of the allowance. Requests above the allowance appear to the business as restricted summaries; guest personal data and business management actions remain locked until a paid plan is activated through successful payment. Cancellation is an exception: the business may cancel a locked booking without changing plan or unlocking the restricted guest data. 6.7. Activation unlocks only requests that are still live. Expiry of the reduction, creation of an invoice or a payment return page alone does not unlock previously locked requests. An already accessible booking is not locked again merely because the plan expires. An expired request is not revived by later payment. 6.8. FREE use does not create an automatic payment obligation. Exceeding the allowance does not automatically order a plan or charge a payment card. 7. Paid plans, orders and fees 7.1. Appendix 1 describes the initial paid offering. The Customer may order the plan and period actually offered to that business. 7.2. Before ordering, the Customer is shown the plan content, duration, net fee, VAT, gross total, currency and activation/plan change rules. The currency of the initial Hungarian offering is HUF. Approving the order constitutes acceptance of the payment obligation displayed. 7.3. Paid usage entitlement covers a period purchased in advance. The platform activates or schedules it on the basis of a verified successful result from the payment provider. The payment provider handles card data on its own interface. 7.4. The initial offering consists of one-off period purchases; there is no automatic renewal, automatic recurring charge or paid trial. Recurring payment may be introduced later only under separately presented and expressly accepted conditions. 7.5. The Provider issues electronic invoices, which the Customer accepts as part of the contract. The invoice uses the verified billing information supplied by the business; an appropriate corrective document is issued for a correction or refund. 7.6. A period that has not been purchased or renewed does not automatically constitute an outstanding invoice debt. Without a paid entitlement, FREE rules apply. An uncertain payment result requires reconciliation; the Customer should not initiate a repeat payment for the same transaction before the result is clarified. 7.7. New prices may apply to new orders. The fee and purchased entitlement for an already paid period do not change retrospectively merely because a new price list is published. 8. Plan changes, advance purchases and expiry 8.1. When a higher plan is successfully purchased, it starts immediately on the local payment date; that day already counts towards the new plan's period. Remaining whole days of the lower plan are placed in reserve and resume after the new higher plan. There is no monetary credit for a proportional price difference. 8.2. The same or a lower plan may be purchased in advance to start after the entire chain of already paid entitlements. An immediate downgrade cannot be selected during an active period. The order displays the applicable start and end dates and the consequences of the change. 8.3. When paid entitlements run out, the business returns to FREE. This does not itself end the platform relationship or delete bookings or business data. 8.4. Where the user or location allowance is lower, access above the limit may be suspended without deletion. The primary user remains; on BUSINESS, three additional active staff members may be selected. The business interface shows the supported selection procedure and the primary user's options to change it. The primary location remains active; other locations above the limit may be suspended. 9. Booking requests and approval deadlines 9.1. A request provisionally occupies capacity from creation or the required email verification until the applicable deadline. It becomes a confirmed booking when the Customer approves it. 9.2. The specific business approval deadline appears with the request. The usual rule allows up to 24 hours, with the deadline expiring at least 12 hours before the service starts; it may therefore be shorter for an imminent appointment. The applicable deadline shown for the particular request governs. 9.3. Without approval, the request expires and releases capacity. This also applies to requests above the allowance. The business must arrange any necessary plan activation and approval within the deadline; payment does not extend the approval deadline. 9.4. Guests are informed of the booking consequences of pending approval, rejection, expiry, cancellation and acceptance. The Customer's plan or payment problem is not displayed to the guest. 10. Email communication and evidence 10.1. Email is the parties' primary communication channel. The Customer must ensure that the primary user's and designated contact's addresses are correct, accessible and checked regularly. In-platform messages and separately enabled device notifications may supplement this channel. 10.2. An email about application of an already accepted allowance, fee or access rule does not require a reply, a new acceptance click or a read receipt from the Customer. It provides information about the situation; it does not replace acceptance of a new condition. 10.3. Legal or essential service information is handled separately from optional booking notifications. The absence of a reply does not change application of an already accepted rule; the legal sufficiency of delivery must be assessed in light of the actual circumstances and applicable rules. 10.4. The Provider retains the accepted version of the terms and the acceptance declaration, necessary identification of the accepting person and represented business, the time of acceptance, and the subject, original content, recipient, timestamps, message identifier and available delivery or failure evidence for relevant notices. 10.5. Successful acceptance of an email for sending by a mail system does not necessarily establish arrival in the recipient's mailbox or reading. The Provider retains the available sending and delivery evidence; a returned non-delivery notice is not treated as proof of delivery merely because the email was previously sent. 10.6. Acceptance evidence is retained for five years after the relevant version ceases to apply; notification case evidence is retained for five years after the case closes. A justified and reviewed extension is possible for data needed for a specific legal claim. The privacy notice details the precise legal basis, processing arrangements and data subject rights. 11. Operation, support and service failures 11.1. The Provider operates the platform professionally and with due care, seeking to prevent, investigate and remedy service failures. The Customer may report a failure to info@froozy.eu, identifying the business and matter and describing the circumstances. We reply to the report within two working days in accordance with section 13.4; this reply does not mean that the failure has been remedied or that a deadline for remedying it is undertaken. Reports must not contain passwords, secret login codes or unnecessary guest data. 11.2. Unless separately agreed, there is no percentage uptime guarantee, guaranteed repair deadline or service level guaranteeing revenue. This does not exclude the obligation to provide the service, remedies for defective performance or mandatory liability. 11.3. The Provider gives reasonable advance notice of foreseeable maintenance involving material loss of use. Immediate security or repair intervention may be performed without advance notice where necessary; information on its material consequences is provided afterwards. 11.4. The Customer's equipment, internet connection, email settings and actions on a third-party interface fall within the respective party's control. Engaging an external contributor does not itself release the Provider from its own contractual obligations or processor liability. 11.5. In designing and operating the platform, the Provider takes technical and organisational precautions reasonably expected and proportionate to the nature and risks of the service to prevent, detect and counter malicious IT activities by third parties intended to disrupt or disable the service. This is not an unconditional guarantee of uninterrupted service. 11.6. If, despite the proportionate and expected precautions under section 11.5, malicious IT activity by a third party succeeds and causes an outage, the parties regard the event causing the outage as force majeure, provided that the circumstances were beyond the Provider's control, were not foreseeable when the contract was concluded and could not reasonably have been avoided or their damage prevented by the Provider. The Provider claiming exemption must prove these conditions, the precautions taken and the causal link between the malicious activity and the outage. 11.7. Where the conditions in section 11.6 are met, the Provider is exempt, to the extent legally permitted, from damages liability for non-performance actually prevented by the malicious activity, in respect of the affected obligation and for the duration of the impediment. Mandatory exceptions, particularly those in section 16, remain. 11.8. Malicious activity alone does not justify exemption. Failure to take expected protective measures, a known security deficiency reasonably capable of being remedied, or a Provider fault independent of that activity does not constitute force majeure under this clause. The Provider cannot base an exclusion on its own intentional conduct or gross negligence as defined by applicable mandatory rules. 11.9. As far as possible, the Provider informs the Customer without undue delay of the outage and its known consequences, cooperates in resolving it and continues restoration and mitigation. Referring to malicious activity does not automatically end these duties. 11.10. Force majeure does not independently exclude settlement of service fees and unperformed services, justified termination or mandatory data protection rights. The effect of the malicious activity on personal data security must be assessed separately. 12. Intellectual property and confidential information 12.1. The platform and its software, branding and documentation are the intellectual property of the Provider or the appropriate rights holder. The Customer receives a non-exclusive right of use within the contract and plan, not ownership of the platform. 12.2. Rights in business content entered by the Customer do not transfer to the Provider. Having the necessary rights, the Customer authorises its storage, display and processing to the extent needed to perform the service. 12.3. The parties use non-public business, technical and personal data only for contractual performance, legal obligations or justified enforcement of claims, and limit access to those who need it. This does not prevent lawful authority requests or exercise of data subject rights. 13. Data controllership and processing 13.1. As a rule, the Customer is controller and the Provider is processor for processing guest requests for the business's purposes. The Customer determines the purposes, legal basis, guest information and necessary data for its own service. The Provider may act as independent controller for its own account, billing, security and evidence retention purposes, as described in its own notice. 13.2. Appendix 3 is the processing agreement. Use of the service does not give general marketing permission. The general booking service cannot be ordered for special categories of data, such as health data, without a separate agreement and appropriate safeguards. 13.3. The Customer limits guest questions and notes to necessary data. The Provider supports lawful and secure processing through technical and organisational measures. 13.4. Questions about the service or contractual terms may be sent to info@froozy.eu, including matters not detailed in the terms. We reply to enquiries sent to this address within two working days of receipt; working days are those of the country where the Provider has its registered office, and an automatic acknowledgement of receipt does not count as a reply. If a substantive answer requires further investigation, this reply sets out the next steps, and we provide the substantive answer within a maximum of one month of receipt; where a shorter mandatory deadline applies, we comply with that deadline. Data protection requests are subject to the separate rules in the following section. 13.5. Data protection questions or requests to exercise rights may also be sent to gdpr@froozy.eu, without an active account, while a booking is open and even where self-service profile deletion is blocked. An obstacle to self-service deletion does not automatically result in refusal of the request. We also handle data protection requests received through our other official contact channels. Exercising a right does not depend on whether the terms address the particular matter in detail. We handle requests without undue delay and, as a rule, provide information on the action taken within one month of receipt. An automatic acknowledgement of receipt alone does not fulfil this obligation. Where necessary because of the complexity and number of requests, the deadline may be extended by up to two further months; we inform the individual of the extension and its reasons within the first month. Where a request is only partly granted or refused, we explain the reasons and the available remedies before a supervisory authority or a court. 13.6. The processing of personal data is governed by Regulation (EU) 2016/679 (GDPR) and other applicable data protection rules. Details of the processing are provided in the Privacy Notice, available separately on the platform. This reference and the opportunity to ask questions by email do not replace mandatory prior information or restrict the individual's rights. Acceptance of the terms is not a general consent to the processing of personal data. 13.7. Certain data may remain after deletion of a personal profile or closure of a business: - Booking event history: dates and times, services and status changes, to substantiate the business's booking history. When deleting a personal profile, we remove the customer's name, email address, telephone number and answers and notes containing personal information from the booking record; the internal identifier remains as the customer identifier. We treat this history as pseudonymised and do not claim that it is necessarily anonymous. - Billing and payment data and the history of related payment and tax authority communications: for settlement, accounting and tax obligations, reconciliation and the handling of legal claims. - Evidence of contractual acceptances, requests and actions taken, and previously sent emails: to demonstrate statements, information provided and the handling of matters, and to handle legal claims. - Earlier copies in backups: to enable restoration of data and the system. Earlier emails and backups may contain personal data already removed from the operational booking record. The listed purposes do not give general permission to retain all data indefinitely. The Privacy Notice specifies the controller, the particular legal basis, the retention period or the criteria for determining it, and access restrictions for each category of data; the response to an individual request also explains the data actually retained in that individual's case and the action taken. Data processed on behalf of a business are also subject to the return or deletion instruction and the data processing agreement. 13.8. Retention and data protection enquiries We process the data associated with a request according to its purpose and only to the extent necessary: – General information question: 90 days after the case is closed. – Access, erasure, rectification and other data subject rights cases: 3 years after closure, limited to the necessary evidence of handling the case. Retaining the entire correspondence and every attachment is not automatic; we remove content that is not needed for subsequent evidence. – Consumer complaint: 3 years, using the starting point and mandatory exceptions under the rules applicable to the complaint. – Invoice and the accounting, tax and payment evidence necessary for it: the mandatory period for the applicable country, document type and transaction. We take account of the mandatory rules of the invoice issuer's country and any other countries relevant to invoicing, together with each obligation's own starting point. Where several obligations apply to the same data, we apply the one that expires last. We determine the billing country from the data recorded when the invoice was issued; a later profile change does not by itself alter it. – Tax reporting authority (NAV) and payment provider communications that are not needed for an invoice: 5 years from the original event. Where the communication is invoicing evidence, the preceding point applies. – A payment case that is demonstrably unsuccessful, cancelled or expired and has never been invoiced: 5 years after closure, unless another applicable obligation or erasure restriction requires longer retention. We retain technical metadata of completed AI operations for 30 days after completion and technical receipts of viewing a reply draft for 30 days after viewing. Template-maintenance logs are retained for 365 days after the event; technical reports of completed monthly retention runs are retained for 365 days after completion. A receipt confirming erasure of an external copy is retained for at least 90 days after acknowledgement and until the associated case no longer exists. These shorter technical periods do not shorten retention of necessary case-handling evidence and do not affect pending operations, active approvals or data subject to a justified erasure restriction. We assess each category of data and its copies separately: an obligation to retain a particular document does not justify unlimited storage of other personal data that is no longer needed. A technical copy, a new status query or an AI suggestion does not restart the period. A specific dispute, authority proceeding or other applicable obligation may prevent erasure of the necessary data for a justified period that is regularly reviewed. Once the retention period has expired, we erase the data or anonymise it so that it can no longer be linked to a person in a controlled deletion process. The Privacy Notice describes the legal basis and further details for each category; you may ask for information about the data retained in your own case and the periods applied. AI used by the Provider may assist in preparing a verified information response. AI does not independently decide on the exercise of a particular data subject right, identity verification, disclosure or erasure. Only the data necessary and authorised for this purpose may be transferred to an external AI service, under the conditions stated in the Privacy Notice. 14. Liability for free use and absence of payment conditions 14.1. Subject to mandatory exceptions and section 16, the Provider excludes liability, to the extent legally permitted, for business losses resulting from use or unavailability of the free service. FREE provides no guarantee of revenue, guest numbers or business results. 14.2. Within the same limits, liability is excluded for business losses resulting from restrictions lawfully applied under these terms because the Customer exceeded an allowance, did not purchase or renew a paid period or did not successfully pay. This includes, in particular, lost revenue or profit, business interruption and financial loss from expiry of requests not handled in time. 14.3. This exclusion does not make a restriction contrary to these terms lawful or turn a service failure during an actually active paid period into a FREE event. A claim arising during a former paid period is not governed by the later return to FREE. 15. Liability limits for paid services 15.1. Subject to the limits in this section, the Provider is liable for proven direct financial damage caused by its own breach of contract, causally connected with that breach and recoverable under applicable law. The Customer takes reasonable measures necessary to prevent, avert and mitigate loss. The conditions of liability and recoverable amount are determined by applicable law and valid contractual deviations. 15.2. Subject to mandatory exceptions and to the extent legally permitted, compensation is excluded for lost revenue and profit, lost business opportunities, customer loss, business interruption and related consequential business loss. Revenue loss from a service failure falls under this rule, not only loss from a restriction for non-payment. 15.3. The damages cap for paid services is the net service fee for the affected active paid period. 15.4. The affected period is the verified paid usage entitlement arising from a specific plan order and active when the damaging event occurred. Its net fee is the platform service fee recorded in that order, excluding VAT. In the initial Hungarian offering, the cap is an amount in HUF. Resumption of a period placed in reserve does not create a new fee or damages allowance for the same purchased entitlement. 15.5. The cap applies in aggregate to legally limitable damages claims for the affected paid period, not separately per booking or damaging event. Losses with the same origin spanning multiple periods belong to the period affected at the first damaging event. Allocation to a period does not affect the exceptions in section 16. 15.6. The cap limits damages. It does not itself reduce a service fee lawfully repayable, invoice corrections or settlement of a substantiated overpayment; these arise on other grounds. No service credit or automatic period extension is due unless separately agreed. 15.7. An external provider's failure or force majeure can be assessed only in light of the actual circumstances and applicable exemption rules. The Provider does not treat every email, hosting or payment failure as automatically beyond its control. 15.8. For outages caused by malicious IT activity by a third party, the verified force majeure conditions in sections 11.5–11.10 apply. Exemption and the period-fee cap are different legal questions: the cap governs the amount of existing damages liability that can legally be limited. 16. Mandatory exceptions to liability limits 16.1. Neither the exclusions nor the financial cap in sections 14–15 limit liability for intentional breach, breach causing harm to life, physical integrity or health, or any other case that mandatory law does not permit to be limited. 16.2. The clause does not override mandatory data protection liability, duties towards authorities or the independent rights of a third party, including a guest or other data subject. The Customer cannot waive another person's claims by accepting its own terms. Article 82 of Regulation (EU) 2016/679 applies in particular to data protection compensation rights and liability. 16.3. If a liability limitation is legally inapplicable in a particular case, liability under mandatory rules applies. An application's sending status does not determine whether or to what extent liability exists. 16.4. For business contractual terms relating to data within Article 13 of Regulation (EU) 2023/2854, the prohibition of terms excluding or limiting liability for intentional conduct or gross negligence, and the fairness requirements for restrictions on remedies and liability, also apply. The period-fee cap does not override these mandatory requirements. 17. Termination and settlement of fees 17.1. The platform relationship is of indefinite duration; individual paid plan periods have a fixed term. Not renewing a plan does not itself terminate the indefinite relationship. 17.2. The Customer may request closure of the business account, return or deletion of data and resolution of guest requests by email from the primary user's verified contact address or through the platform's designated interface. Receipt of a request does not itself delete the business or cancel bookings. Closure requires express approval by an administrator of the Provider, subject to the narrow self-service exception in section 17.6. The Provider confirms the request, any matters requiring resolution, the closure date and the arrangements for data access/deletion, taking account of section 18 and mandatory data protection rules. 17.3. Voluntary early discontinuation or non-use does not itself create a refund entitlement for an already purchased period. This does not exclude settlement rights arising from the Provider's breach, lawful termination or mandatory provisions. 17.4. For a remediable breach, the Provider gives written notice of the reason and reasonable opportunities to resolve it. A serious security threat, unlawful use or an authority order may justify immediate necessary restriction. If the Provider terminates a paid period early, the fee for the unperformed part and its legal basis must be accounted for; there is no general right to retain fees without justification. 17.5. Termination does not erase invoices or legal evidence that must lawfully be retained, or unresolved claims. Further processing of other data is determined by the appropriate legal basis and purpose, not by earlier payment alone. 17.6. Without administrator approval, express confirmation of deletion of one's own account may immediately close a business if it is the applicant's only owned business not yet closed, is active and operates on an active FREE plan, and the applicant is its active primary user with no other active staff member or staff member suspended due to plan limits. The business must also never have had a paid plan entitlement or any plan order, and there must be no open booking or payment/refund requiring resolution either for the business or linked to the applicant's own account. This exceptional combined procedure also closes the personal user account. A business that returned to FREE after earlier paid use follows the administrator approval procedure even if its finances are settled. 17.7. Open bookings comprise requests awaiting email verification or business approval and confirmed bookings that have not been closed. The appointment passing is not in itself closure. Immediate deletion under section 17.6 cannot proceed while a booking is open; it may be requested again immediately after cancellation or closure and will be carried out if the other conditions are met. If online cancellation is no longer available to the guest, they must contact the business; the business may cancel the booking, including when it is locked under section 6.6. Under the administrator procedure, the request is recorded even while bookings require resolution, and closure arrangements are agreed. 17.8. The administrator procedure checks representation, resolution of open bookings and finances, the choice of data return or deletion and mandatory retention. Before approval, the request itself does not remove access. Reasons and required actions are provided for any obstacles; the request may be withdrawn until execution starts. The Provider's two designated administrators receive an email about the closure request; no such notification is sent for self-service deletion under section 17.6. Approval does not require a joint decision by both administrators. 17.9. Closing a business ends its public bookability and business access. It does not delete the separate accounts of the primary user, staff or guests, or their permissions at other businesses. A personal user account may be deleted on a separate express request under section 17.6 or 17.11. Data held as processor is handled according to the Customer's choice under Appendix 3.F and Article 28(3)(g) of the GDPR. Retaining closed booking history does not itself authorise unlimited storage of personal data. Information is provided about the categories of data lawfully retained, their purposes and retention periods. 17.10. Closing a business account and a natural person's exercise of data protection rights are separate procedures. Administrator approval, an open booking or a financial matter does not automatically postpone examination of every personal data request. Such requests are answered without undue delay and normally within one month; in the event of a lawful extension, its reason and duration are communicated within the first month. Reasons and available remedies are provided for partial fulfilment or refusal. 17.11. The primary user may separately and expressly request deletion of their own personal profile together with the administrator closure request. After the business closes, this is carried out without further administrator approval if the conditions, checked again at that time, are met: they own no other business not yet closed and have no open personal booking or related payment/refund requiring resolution. Deleting the personal profile ends all its login methods and that person's business access; it does not delete anyone else's account or another business's data. If personal profile deletion remains blocked, the business closure remains valid; separate information is provided about the obstacle and the option to request deletion again immediately after resolving it. The personal profile deletion request may be withdrawn separately until its own execution starts. Sections 17.9–17.10 continue to apply to lawfully retained data and independent data protection requests. 17.12. The Customer may separately select that deletion of the personal data of all staff associated with the business is also requested. This covers staff data, invitations and personal data copies processed within the business, including former staff; it does not delete staff members' independent personal accounts or data held at other businesses or in their capacity as guests. Business access ends on closure regardless of this selection. The administrator checks in advance which data is to be deleted and which may lawfully be retained; information is provided on fulfilment and the purposes and duration of retained exceptions. Not selecting the option does not authorise unlimited retention: the chosen data return/deletion procedure, Appendix 3 and applicable retention rules still apply. 18. Data provision and switching providers 18.1. The Customer's data can be provided in machine-readable form: business profile, locations, catalogue, opening hours, permission settings, its own booking data and their history. Other businesses' data, authentication secrets and the platform source code cannot be disclosed under this provision. 18.2. Where EU switching rules apply, the maximum notice period is two months, the transition is generally no longer than 30 calendar days, and the post-transition retrieval period is at least 30 days. The Provider assists secure transfer and continuity; deviations must be justified and permitted by the Regulation. The applicable provisions are Chapter VI, in particular Article 25, of Regulation (EU) 2023/2854. 18.3. Termination of the relationship is confirmed upon successful completion of switching or, where deletion is chosen, at the end of the applicable notice period. Exportable data is deleted at the end of the retrieval period; data required by law to be retained may remain separately stored. 18.4. The Provider charges no separate switching fee. Ordinary service performed up to that point is accounted for. A versioned service information sheet available before contracting describes the exportable data, how it is provided and any limitations, and jurisdictional information about the service infrastructure used. 19. Changes to the terms and new versions 19.1. The Provider may address legal, security, service or business changes through a new version of the terms. Earlier acceptance and its text remain unchanged. 19.2. Planned changes imposing material new obligations or liability rules on the Customer are normally notified by email at least 30 days in advance; urgent legal/security situations are assessed under applicable rules. 19.3. Any required new and separate express acceptance must be given by the business's currently authorised representative. Email delivery, silence or continued use alone does not replace a required declaration. Changes to already paid periods and consequences of not accepting a new version must be handled through lawful introduction and fee settlement procedures. 20. Complaints, disputes and final provisions 20.1. Complaints and compensation claims may be submitted to info@froozy.eu, identifying the business and matter and describing the facts and claim. We reply to the submission within two working days in accordance with section 13.4. Once necessary information is received, the Provider investigates and gives a substantive written response. Submission does not automatically constitute admission of liability or a refund. 20.2. The parties cooperate in discussions; this is not a prerequisite for mandatory authority or court remedies and does not create a separate short deadline extinguishing rights. 20.3. Applicable EU rules govern the relationship, particularly the General Data Protection Regulation (EU) 2016/679 and, within its scope, the Data Act, Regulation (EU) 2023/2854. National law applicable to contractual matters not regulated by EU law is determined by Regulation (EC) No 593/2008 (Rome I) and other applicable private international law rules; these terms make no separate choice of national law. Reference to EU law does not exclude national law or mandatory provisions applicable in this way. Jurisdiction is determined in particular by Regulation (EU) No 1215/2012 and other applicable procedural rules. The contract does not restrict proceedings by a data protection authority or another mandatorily competent body. 20.4. Invalidity of a provision affects applicability of the remainder under the conditions of applicable law. The Provider does not retrospectively and unilaterally treat an invalid clause as acceptance of a different clause. Protection against unfair terms under applicable law remains; acceptance alone does not validate a legally inapplicable liability limitation. APPENDIX 1 – INITIAL PLAN INFORMATION FREE: 40 counted public requests per month; the temporary monthly allowance of 20 under section 6; 1 active user and 1 active location. BASIC: unlimited counted public requests, 1 active user and 1 active location. BUSINESS: unlimited counted public requests, 4 active users and 1 active location. PROFESSIONAL: no plan-based numerical limit on bookings, active users or active locations. The primary user counts towards the user limit. An unlimited plan does not authorise attacks, unlawful bulk use or infringement of another business's rights. Initial Hungarian net prices, HUF, for periods of 1 / 3 / 6 / 12 months: BASIC: 2 000 / 5 000 / 8 000 / 14 000 HUF. BUSINESS: 4 000 / 10 000 / 16 000 / 28 000 HUF. PROFESSIONAL: 8 000 / 20 000 / 32 000 / 56 000 HUF. The initial offers' net fees are subject to 27% VAT. The price, tax and gross amount displayed, accepted and recorded for the specific order govern. A new price list does not alter an already paid period. This explanatory content may be versioned separately from the plans as an informational document distinct from the terms. APPENDIX 2 – HIGHLIGHTED ACCEPTANCE DECLARATION Before contracting, the Customer's representative expressly makes the following declaration: “On behalf of the business I represent, I have read and accept the precise version of the Froozy business terms presented to me. I have separately reviewed the rules on business access and request expiry following exceedance of the FREE allowance or absence of the conditions for paid use, the liability limits for free use and paid services, and the mandatory exceptions. I expressly accept that the aggregate cap on paid-service damages claims that may legally be limited is the net fee for the affected active paid period, and that I need not reply to an email about application of a rule already accepted.” The declaration is linked to clear identification of the complete terms version and highlighted part. APPENDIX 3 – DATA PROCESSING TERMS A. On the Customer's instructions as controller, the Provider stores and transmits the business's guest booking data to create, manage, notify and support bookings. Data subjects: guests and contacts. Data: name, email, telephone, requested service and appointment, necessary answers, notes, status and event history. Processing continues during the service and until closure according to lawful instructions. B. The Customer is responsible for the lawfulness of instructions, legal basis and information. The Provider acts only on documented instructions, ensures confidentiality and appropriate security, and reports instructions it identifies as unlawful. C. Data security measures include encrypted connections, separation of businesses' data, role-appropriate permissions, restricted administrator access, secure user identification, logging, and appropriate backup and recovery procedures. The versioned service information sheet records the specific measures actually provided. D. Subprocessors appear on a list disclosed before contracting, identifying name/purpose/location/jurisdiction. Under general written authorisation, advance notice of changes and a meaningful opportunity to object are provided. The Provider does not shift its statutory responsibility for the engaged processor's performance to the Customer. Third-country transfers require an appropriate legal basis and safeguards. E. The Provider reports personal data breaches without undue delay, assists with data subject requests and necessary investigations, and supports verification of processing compliance. F. At the end of the service, the Provider returns or deletes processed data according to the Customer's choice and deletes existing copies, except for storage required by law. Data retained for the Provider's own controller purposes requires a separate legal basis and information. The system's general booking retention setting cannot override lawful closure instructions. APPENDIX 4 – PROVIDER DETAILS Provider of the Froozy platform: Name: IT Resource Consulting Kft. Registered office: 2098 Pilisszentkereszt, Kossuth Lajos utca 45. Tax number: 13207379-2-13. Company registration number: 13-09-220205. Corporate website: https://itresource.hu. Platform website: https://froozy.eu. Business interface: https://business.froozy.eu. Contact, customer support and legal notices email: info@froozy.eu.

https://froozy.eu/terms/BUSINESS_PLATFORM_TERMS/versions/8?locale=en

Data protection request

You can ask for access, rectification, erasure or the exercise of another data protection right by e-mail at info@froozy.eu. You do not need to sign in: you can write without an account, while a booking is open, and even if self-service account deletion did not succeed. If you can, write from the e-mail address of your account. Do not send passwords, sign-in codes or bank card details. As a rule, we inform you of the action taken within one month.

Data protection request by e-mail