Sign in

Privacy Notice

Language: English · published: 31 October 2026

Effective date: date of publication on the Froozy platform. The controller’s identity and contact details are set out in section 13; this notice refers to the controller as the “Operator” or “Froozy”. 1. Scope of this notice This notice applies to the processing of personal data in connection with Froozy's web and mobile applications. It covers, in particular, appointment booking as a guest; guest, business and administrator accounts; use of the platform by businesses and their staff; sign-in through an external provider; ordering and paying for platform plans; invoicing; notifications; customer support; and security-related processing. 2. Roles in connection with appointment bookings As a general rule, the business identified on the booking page determines the purposes of processing the guest information submitted for a particular appointment. For this processing, the business is the controller and Froozy acts as a processor, providing the technical appointment-booking system on the business's documented instructions. The business is responsible for its own privacy notice concerning its services, customer relationship and any additional processing it performs. Froozy acts as an independent controller for platform accounts, subscriptions, payments, invoicing, platform security, prevention of abuse, service operation and compliance with its own legal obligations. 3. Processing activities 3.1. Operation of the website and platform Data processed: IP address; date, time and technical details of requests; browser and device data; requested page or API operation; errors; security and access events; and shortened or hashed technical identifiers. Purposes: providing an available and secure service, troubleshooting, and detecting and preventing abuse. Legal basis: the Operator's legitimate interest in protecting and operating the service, Article 6(1)(f) GDPR. Retention: application logs and general abuse events are normally retained for 30 days from the event. Recognising repeated attacks is a separate purpose: security-lock history is retained for 365 days from imposition and at least until the active lock expires; the technical marker coordinating repeated locks is retained for 366 days from last use. Audits of administrator access to financial data are retained for 365 days from access. Necessary evidence of an incident or specific legal claim may be retained with restricted access for the applicable period, with a recorded reason and regular review. These are not retention periods for all personal data. 3.1.1. IP-based country detection The guest website uses the request's IP address and a local DB-IP Lite country database to determine the visitor's approximate country. The purposes are to select the default country-specific price list and indicate when Froozy is not yet available in that country. This is not precise geolocation, and the country can be overridden manually. We do not save the IP address or the country-detection result for this operation. The database runs locally: there is no external lookup for each visitor, and DB-IP does not receive the visitor's data. General operational and security logs are subject to the separate rules in section 3.1. Legal basis: the Operator's legitimate interest in providing country-specific service and pricing information, Article 6(1)(f) GDPR. The operation does not use analytics or advertising cookies, is not linked to an account and is not a condition for booking online. The data is processed solely within the Operator's own service environment. You may object to processing based on legitimate interests as described in section 10. 3.1.2. Log of notices about countries where the service is not yet available When the guest website displays the notice that Froozy is not yet available in a country, the Operator records the country shown in the notice, the browser language and the time of display. We do not save the IP address in this record, or link an account or visitor identifier to it. A random technical notice identifier prevents resubmission of the same notice and is not a visitor-profile identifier. We use the IP address only in server memory while processing the request to limit repeated notices within a day. The temporary fingerprint uses a random key replaced daily; the key and fingerprints are replaced at the UTC day boundary and are lost on restart. They are not written to the country-notice database. The separate rules in section 3.1 apply to general operational and security logs. Purposes: planning the service's expansion by country based on the number and language of displayed notices, and limiting repeated notices. The log does not constitute registration or a notification subscription, and is not used to create individual advertising profiles. Legal basis: the Operator's legitimate interest in planning service expansion and maintaining reliable statistics, Article 6(1)(f) GDPR. You may also object to this processing as described in section 10. The country, browser language and event time remain in the statistical records and are used for totals by country and language. Only the Operator's authorised platform administrators may access the detailed log within the Operator's own service environment. DB-IP and other country-database providers do not receive visitor data from this log either. 3.1.3. Aggregate business statistics The Operator produces aggregate counts from system data about accounts, businesses and bookings to operate, plan and improve the service. The statistics counter stores hourly counts, event types, countries and platform business categories; it does not store person, account, business or booking identifiers, IP addresses, browser data or monetary amounts. The legal basis for creating the aggregates is the Operator's legitimate interest in these purposes, Article 6(1)(f) GDPR. The aggregate results without identifiers may remain after the source data is deleted. The counter does not use cookies, local storage or visitor tracking; the report is available only to authorised platform administrators. 3.2. Account registration and management Data processed: email address, display name, preferred language, securely hashed password, email-verification status, account status and roles, session and token data, business memberships and an optional device name. Purposes: registration, authentication, account and permission management, maintenance of sessions and account security. Legal basis: taking steps to enter into and performing a contract, Article 6(1)(b) GDPR; for security processing, the Operator's legitimate interests, Article 6(1)(f) GDPR. Retention: for the lifetime of the account and thereafter for as long as required for legal claims or mandatory retention. Account deletion revokes sessions and removes sign-in credentials, but booking and invoice data that must be retained by law or for another lawful purpose may not be erased immediately. Account deletion can also permanently close the sole FREE business with only its owner as an active member, provided it has no open bookings, plan-order or non-FREE entitlement history, or unresolved payments. The closed business disappears from public pages; memberships become inactive and pending invitations are revoked. Closure does not delete retained booking or accounting history and does not initiate an automatic refund or restoration period. The retention of bookings detailed below and the applicable country- and record-specific invoicing obligations apply independently of account deletion. The account’s external sign-in identities and sessions are removed. 3.3. Sign-in through an external provider Users may choose Google, Apple, Facebook or another external sign-in provider enabled in the interface. Data processed: provider name, provider-specific user identifier, email address verified by the provider, email-verification status, in some cases name and private-relay-email status, and the dates of linking and last sign-in. Froozy does not store the password used with the external provider. Authorization codes and provider tokens are used only to complete the authentication process. Purpose and legal basis: providing the selected sign-in method and performing the contract, Article 6(1)(b) GDPR. The external provider is an independent controller for processing performed through its own interface. Users may use Froozy's password-based sign-in where it is available for their account. 3.4. Appointment booking Data processed may include the guest's name, email address and telephone number; selected business, location and service; appointment time; answers to booking questions; notes; booking status and event history; technical data relating to email confirmation and private management links; and, for registered guests, the link to their account. Purposes: requesting, confirming, accepting or rejecting, rescheduling, cancelling and completing an appointment, and sending related notifications. Legal basis: steps taken before entering into, or performance of, a contract between the guest and the selected business, Article 6(1)(b) GDPR. Froozy acts as the business's processor for this processing. Retention: five years from the later of the scheduled end of the appointment and the date on which the booking entered its final status. Personal fields are then erased or irreversibly anonymised. Non-personal statistical data may be retained for a separately documented purpose. Froozy does not request special-category data such as health information. Users should not enter such information in free-text fields unless the business expressly requests it and has an appropriate legal basis. Personal account erasure or approved business closure may remove the booking's direct personal fields, answers, notes and management tokens before that period ends. We treat the business event history retained with an internal customer identifier as pseudonymised data; the identifier alone does not establish irreversible anonymity. Necessary financial and case-handling evidence has its own retention rules. 3.5. Business accounts and staff Data processed: names and email addresses of contacts, business roles, membership and invitation information, staff activity, permission and change history, business profile information and location contact details. Purposes: operating the business through the platform, managing permissions, enabling collaboration and applying plan limits. Legal basis: performance of a contract, Article 6(1)(b) GDPR; for security and permission audits, the Operator's legitimate interests, Article 6(1)(f) GDPR. 3.6. Plan purchases, payment and invoicing Data processed: details of the purchasing business and contact person, billing name, address and tax number, plan, amount, currency and order details, payment transaction identifiers and status, invoices and related accounting documents. Payment-card details are processed on the SimplePay payment interface and are not stored by Froozy. Froozy receives the payment result and the technical identifiers associated with the transaction. Legal basis: performance of a contract for ordering and payment, Article 6(1)(b) GDPR; compliance with legal obligations for invoicing and accounting retention, Article 6(1)(c) GDPR. Retention: invoices and necessary accounting, tax and payment evidence are retained according to the applicable country, record and transaction rules. We consider the issuer’s obligations and any other rules that actually apply, each with its own starting event; the latest applicable expiry governs the same data. Details are set out in section 3.8. Information about SimplePay's own processing is available at https://simplepay.hu/adatkezelesi-tajekoztatok/. 3.7. Notifications and customer support Froozy may send transactional emails, in-app system messages and, where separately enabled, push notifications. These may concern account activation and password reset, booking confirmation, modification or cancellation, appointment reminders, staff invitations, payment, plan and invoice events, and security or service information. Legal basis: performance of a contract, Article 6(1)(b) GDPR; for security-related communications, the Operator's legitimate interests, Article 6(1)(f) GDPR. Seasonal tyre-change reminders are a separate, optional service: the relevant business may send at most two such emails per year based on the guest's separate consent, which is not selected in advance. The business is the controller and Froozy the processor for this purpose. Data includes the email address and its hash, business and related booking or account identifiers, the consent text version and time, withdrawal and technical delivery status. The legal basis is consent under Article 6(1)(a) GDPR. Booking is possible without consent. Consent can be withdrawn at any time through the email's unsubscribe link; this does not cancel the booking or affect earlier lawful messages. Withdrawal stops further reminders and removes the active booking/account link. Necessary evidence of a declaration or message is retained only to the extent and for the period needed for a substantiated claim; individual information can be requested from the business or Froozy. Accepting the terms, reading the notice or granting device push or location permission does not replace this separate consent. Transactional notifications may also involve recipient details, message content, delivery status and timestamps in the email queue and message centre. Sent emails and backup copies may contain personal data already erased from the operational profile. Access is restricted to authorised persons for necessary contractual, financial or case-handling evidence; the period for each category follows section 3.8 and the purpose of the particular case. Sent status indicates handover to the email delivery system, not that the recipient read the message. 3.8. Retention and data protection enquiries For GDPR case handling, the Operator acts as an independent controller. It processes contact details, the necessary content and attachments of enquiries and replies, timestamps, status and information needed to evidence the handling; for abuse prevention it may also use technical sender data or its hash for a short period. The purposes are to answer enquiries, fulfil data subject rights and mandatory complaint-handling duties, and retain necessary evidence of action taken. General service-related handling relies on Article 6(1)(b) GDPR; mandatory rights and complaint handling on point (c); necessary evidence retention and proportionate abuse prevention on legitimate interests under point (f), to which the data subject may object where the conditions apply. Only authorised case handlers may access a case. Administrators receive a notification without the enquiry’s content. You may send privacy questions and data subject requests to gdpr@froozy.eu. We respond without undue delay and, as a rule, within one month of receiving the request. Where the General Data Protection Regulation (GDPR) permits a justified extension, we inform you of the extension and its reasons within the original month. An acknowledgement of receipt does not by itself mean that the request has been substantively fulfilled. 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. 3.9. Profiles, images, location data and consequences of providing data Business profiles, premises addresses, contact details, service descriptions and uploaded images help display the business and select a service. Content supplied for publication may appear on the public profile. Froozy processes it to perform the platform contract and, for personal content supplied by the business, on that business's instructions. Retention lasts while the profile's purpose continues or until a lawful erasure or closure instruction; separately necessary evidence and backup copies under section 3.10 may remain. Address search and map location may transmit the entered address fragment, place identifier or coordinates to Google Places/geocoding to identify the selected place and check its country. If the interface uses the device's current location, separate device permission is requested. Where supported, a manually entered address or place can be used if permission is refused. Location permission is not marketing consent; location data is not used for continuous movement tracking. An enquiry about an unsupported country may involve a country code, time, source and technical network data for service planning and abuse prevention on the basis of legitimate interests; the raw IP address has separate, short retention and is not included in public country statistics. Required fields are marked when data is collected. Without data necessary for the contract, booking or invoicing, that operation cannot be completed. Omitting optional data, images, seasonal consent or device permission does not become a general reason to exclude someone from the service. Where a business records guest data indirectly, it must also provide the information applicable to its own processing and the source of the data; Froozy's notice does not replace it. 3.10. Backups and recovery Regular full backups may include invoices, attached records and email evidence still stored. Managed database backups are retained for 35 days from the original snapshot; downloading does not restart the period. Encrypted server and local copies are inventoried and access is restricted. Controlled cleanup removes expired copies; if the local computer is off, cleanup occurs at the next available run and the copy cannot meanwhile be used for ordinary operational processing. The separate database change log is retained for 30 days. A separately protected journal containing minimal internal identifiers and executed operations ensures that erasure and restrictions remain effective after recovery. It may also contain personal data; its purpose is to prevent erased data and old access from reappearing. Necessary journal entries remain while they protect recovery of a retained backup. A completed entry older than 35 days can be removed only after verified retirement of the earlier backups and copies. An old backup is first restored in isolation; current erasures, expiries and access revocations must be applied and checked before ordinary traffic resumes. A restored system cannot accept user traffic if the journal is missing or invalid. 3.11. AI-assisted reply preparation If separately enabled, Froozy may use Google Gemini text assistance to prepare an informational data protection reply. Setting an API key does not itself enable transmission of substantive case data. Before external processing, we check the provider contract, permitted data use, storage and safeguards for any third-country access. Only data necessary and authorised for that purpose may be transmitted; passwords, sign-in tokens, full email archives and unnecessary attachments may not. The service does not make business or legal decisions for the person: it does not independently decide identification, disclosure, erasure or the substantive assessment of a request. Necessary case data follows the legal basis of the underlying case; section 3.8 describes the purpose and retention of technical records. A person may request information about the particular provider, data transmitted and safeguards. 4. Sources of personal data Personal data are usually provided directly by the data subject. Data may also be received from a business that records a booking on the data subject's behalf, an external sign-in provider, SimplePay, or the technical operation of the user's device or browser. Where a business records a booking, that business is responsible for having an appropriate legal basis and providing the required information before disclosing personal data. 5. Recipients and processors Personal data may be made available, to the extent necessary for their tasks, to authorised staff of the business concerned by the booking; hosting and infrastructure providers; email-delivery providers; SimplePay; Google Analytics as described in section 7.1; OpenAI where separate consent is given as described in section 7.2; Google Places/geocoding for address and location search; the external sign-in provider selected by the user; Google Firebase, Apple Push Notification Service or browser push infrastructure where push notifications are enabled; the Operator's accountant, legal advisers or auditors; and competent public authorities and courts where required by law. Processors may process personal data only on documented instructions and subject to confidentiality and data-security obligations. 6. Transfers outside the European Economic Area Some external sign-in, analytics, push or infrastructure providers may process personal data outside the European Economic Area. Such transfers take place only where an appropriate safeguard under the GDPR applies, such as an adequacy decision of the European Commission or standard contractual clauses. Information about the applicable safeguard and how to obtain a copy may be requested at info@froozy.eu. 7. Cookies and browser storage Froozy may use cookies or similar browser-storage technologies that are strictly necessary for providing the service, for example to maintain sessions and security, temporarily store OAuth state and PKCE data, or remember the selected language or interface settings. 7.1. Audience measurement (Google Analytics) The Operator uses Google Analytics 4, in two separate Google Analytics properties, to measure use of the production guest website froozy.eu and of the production business portal business.froozy.eu. The purpose is to understand and improve the website and booking process on the guest website, and the usability of the portal on the business portal. The Operator is an independent controller for this purpose; its details are in section 13. This service does not measure the administration interface, native applications, or test and development environments. On both sites, the Google Analytics code loads on every page view, using Google's consent mode (Consent Mode). Before you make a choice, following refusal and after withdrawal, all Google storage is denied: we set no analytics cookies and use no persistent visitor or session identifier. In this state Google receives cookieless signals without identifiers (for example, that a page was opened or that an action listed below took place). The legal basis for these is the Operator's legitimate interest under Article 6(1)(f) GDPR: understanding and improving use of the service in aggregate, including allowing Google to produce aggregated estimates (modelling) for traffic without consent. We use analytics cookies and the related random identifiers only with your voluntary, prior consent; the legal basis for this is Article 6(1)(a) GDPR. The two sites ask for and store the choice separately; consent given or refused on one site does not apply to the other. The booking widget embedded in other websites does not ask for consent, so only cookieless signals without identifiers are sent there. Booking, the business portal and the basic service functions remain available without consent. Accepting the terms or reading this notice does not replace this separate choice. Data processed on both sites: a cleaned page path and title, referral and campaign information, interface language, device and browser information, approximate geographical location, and the times of page views and actions. After consent, random cookie and session identifiers are added; cookieless signals contain no such identifier, at most a random value that changes with each page load. Google also receives an IP address in the network request; according to Google, GA4 does not log or store IP addresses. This does not mean that data are sent without an IP address or that all measurement data are anonymous from the outset. On the guest website, we measure business and service search terms and filters, the public name or code of the selected business, location and service, booking steps, time of day, quantity, successful or unsuccessful outcomes and error codes, signed-in status and sign-in method, as well as actions such as language changes, adding to a calendar and using contact buttons. On the business portal, the page title is the general name of the screen (for example “Calendar”), and the page path contains only the names of parameters instead of identifiers. We measure the sign-in and registration method and outcome, the business type and country, the selected plan, term and net price, the outcome of orders and payments, the action, result and count of booking handling (for example acceptance, rejection or cancellation) and whether a reason was given for a rejection, basic attributes of bookings recorded by the business (for example quantity and whether an email address was given), the role and outcome of team-member invitations, language changes and error codes. As user attributes we record the signed-in status, the role in the active business and that business's plan. Names, email addresses, telephone numbers, vehicle registration numbers, notes, answers to booking questions, account or booking identifiers, passwords, and sign-in, confirmation, management or invitation tokens must not be sent for measurement. In addition, on the business portal, the names of the business, its locations and services, the identifiers of the business, orders, invoices and invitations, guests' data, the text of rejection reasons and the text of the customer search are not measured either. Page and referral information must be generated without these data; permitted campaign and search fields must not be used to transmit them either. We do not send the complete, unfiltered URL or its fragment. Google signals, advertising storage, user data for advertising, remarketing and ad personalisation are not enabled in either state. The analytics processor is Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland); Google LLC and subprocessors may also be involved in providing the service. Processing or access outside the EEA, including in the United States, may occur. Where applicable, Google relies on the EU–US Data Privacy Framework and the related adequacy decision; for other relevant transfers it relies on European Commission-approved standard contractual clauses and necessary supplementary safeguards. We use the service only under the applicable processing and transfer terms. Information about the specific safeguard and a copy may be requested at gdpr@froozy.eu. Google's privacy notice: https://policies.google.com/privacy ; processing on partner sites: https://policies.google.com/technologies/partner-sites . After consent, on the guest website the _ga and _ga_<id> cookies, and on the business portal the bw_ga and bw_ga_<id> cookies bound to business.froozy.eu only, distinguish visitors and sessions; measurement on the business portal does not use the guest website's cookies. Without consent, no such cookies are set. Their default lifetime is two years and may be renewed on use; the browser may limit this. We set user-level and event-level retention in both GA properties to no more than 14 months, without resetting the user retention period on new activity. Google removes expired data in its monthly deletion cycle. This setting does not govern retention of standard aggregated reports; aggregated statistics that can no longer be linked to an individual may remain available for longer. You may consent using the audience-measurement banner's “Accept” button or refuse using “Reject”. You may change your choice at any time through “Cookie settings” in the footer of the guest website or in the account menu of the business portal. Withdrawal deletes that site's analytics cookies, and from then on only cookieless signals without identifiers are sent there; it does not affect the lawfulness of earlier processing. You may object to the signals based on legitimate interest as described in section 10. As they cannot be linked to an individual, you can also prevent them in your browser, for example with the Google Analytics opt-out browser add-on (https://tools.google.com/dlpage/gaoptout) or a content blocker. Rights regarding data already sent to Google may be exercised as described in sections 10–11. The choice, its time and text version are stored separately for each site in the tr.analyticsConsent entry of that browser; the choice is valid for no more than one year, after which we ask again. The backend does not keep a separate consent log for this analytics choice. 7.2. Advertising measurement with the OpenAI Conversions API If the Operator enables this feature, separate, voluntary consent for “Advertising measurement (OpenAI)” may be requested on the froozy.eu guest site, including the blog, and the business.froozy.eu business portal. Our purpose is to measure business registrations arising from Froozy advertisements in ChatGPT and assess our advertising performance. Froozy is an independent controller for this purpose. Our legal basis is consent under Article 6(1)(a) GDPR. This choice is independent of consent to Google Analytics and acceptance of the terms; refusal or withdrawal does not prevent registration or use of the service. This measurement does not cover the native applications. The oppref in an advertising landing URL is an opaque click/attribution reference provided by OpenAI. We remove it from the browser address bar; before consent it remains, at most, in the current browser page's memory, is not written to persistent storage and is not sent to OpenAI. Refusal or leaving the page discards this temporary value. The oppref and event references may be pseudonymous online identifiers; we do not automatically treat them as anonymous data. After explicit acceptance, the first-party cookie tr_openai_ads stores the affirmative consent state, a random consentId, its time, the consent-text version and, where available, the original oppref. The cookie belongs to the froozy.eu parent domain and the / path, with Secure and SameSite=Lax settings, and is used jointly by the guest site and business portal. It lasts for at most 30 days from the original consent; another ad visit does not extend this period. The browser may impose shorter limits. If the cookie cannot be stored, is absent, invalid or expired, we do not create a new measurement event. With valid consent, when a new business registration is successfully saved in the database, the Froozy server may send a registration_completed event to OpenAI. The event contains a random identifier that remains unchanged on retry, the actual registration time, the web source designation, the registration-page URL without query parameters or fragment, and the customer_action type designation. The original oppref is included only where available; a registration without an oppref may also be reported with consent. Email activation of the registration is not a separate conversion. A general registration response for an existing account, or a failed registration rolled back in the database, does not create a new event. This integration does not disclose a name, email address or its hash, telephone number, address, user IP address or user agent, account, business, booking or invoice identifier, free text, guest data or special-category data. We do not load the OpenAI Measurement Pixel in the browser or send a parallel registration Pixel event, and do not use automatic or advanced customer-identifier matching. Transmission is from the server, so the network connection's technical data relates to the Froozy server. The advertising-measurement consent identifier is not sent to OpenAI. Under the public OpenAI Ad Tools DPA, the recipient for EEA and Swiss data is OpenAI Ireland Limited (1st Floor, The Liffey Trust Centre, 117–126 Sheriff Street Upper, Dublin 1, D01 YC43, Ireland). Under the Conversion Terms the parties normally act as independent controllers; OpenAI acts as a processor for Restricted Processing as defined in the agreement. Froozy does not automatically classify the disclosure as processing on its behalf merely because of a technical setting. OpenAI may use the permitted data for advertising measurement, operation and improvement under its conversion terms and link it with advertising information available in its own systems. Froozy sends every event with opt_out: true to restrict user-level personalisation. This does not replace consent or exclude every other processing activity by the provider. OpenAI explains its own purposes, retention criteria and the rights exercisable with it at https://openai.com/policies/eu-privacy-policy/ ; requests can be submitted at https://privacy.openai.com/ . Conversion Terms: https://openai.com/policies/conversion-terms/ ; Ad Tools DPA: https://openai.com/policies/ad-tools-dpa/ . Processing or access outside the EEA, including in the United States, may occur. Under the Ad Tools DPA, OpenAI Ireland Limited uses a valid data-protection mechanism for such onward transfers. Where applicable, an adequacy decision, or otherwise appropriate safeguards such as standard contractual clauses and necessary supplementary measures, may support the transfer; consent alone does not replace them. Information about the applicable safeguard and a copy can be requested at gdpr@froozy.eu or privacy@openai.com. OpenAI's own retention is separate from Froozy's technical periods below. Froozy manages the event needed for transmission in a durable delivery queue. Following temporary failures it makes at most 12 transmission attempts in total, preserving the original event identifier and time, for at most 7 days after the event occurred. A provider failure does not make registration fail. The oppref is removed from the queue after successful transmission, permanent failure or withdrawal; a still-pending event stops permanently no later than the 7-day limit. The full event record is deleted in the cleanup cycle after 31 days from registration. The necessary internal consent and withdrawal reference remains for 31 days from its creation and, where events are linked to it, at least until the last such event is deleted, so withdrawal and replay protection can be enforced. Backup copies and the minimal deletion/withdrawal journal follow the separate rules in section 3.10; restoring a backup must not revive a withdrawn transmission. On refusal, the origin-specific localStorage entry tr.openAiAdsConsent retains the negative choice, its time and text version for at most 1 year, without an oppref. If network failure or a limit delays server acknowledgement of withdrawal, the localStorage queue tr.openAiAdsWithdrawals contains only the withdrawal consentId and technical retry details, for at most 31 days and with at most 10 entries. Each entry is removed after successful acknowledgement. The local refusal takes effect immediately while acknowledgement is pending. Consent can be given and withdrawn for the separate OpenAI purpose in “Cookie settings”, available in the guest-site footer and business-portal menu. Withdrawal removes the shared cookie, so permission for new events ends on both interfaces, and the server stops the affected pending transmissions after acknowledgement. A network request already in flight cannot be recalled; rights regarding data lawfully disclosed earlier can be exercised as described in sections 10–11 and with OpenAI. Before consent or upon refusal, we do not send events to OpenAI for this purpose. 8. Data security Froozy uses measures designed to protect personal data, including encrypted HTTPS connections; non-reversible password hashing; role- and business-based access controls; separation of business data; restricted and logged administrative access; hashed storage of sign-in and email tokens where possible; prohibition of logging passwords, complete tokens or external-provider secrets; backups; and incident-management procedures. 9. Automated decision-making Froozy does not carry out solely automated decision-making or profiling that produces legal effects or similarly significantly affects a data subject. The system may automatically check booking capacity, permissions, plan limits, deadlines or conflicts. These checks implement the technical and contractual rules of the service. 10. Your rights You may request information about and access to your personal data, correction of inaccurate data, erasure, restriction of processing and, where the relevant conditions apply, receipt of your data in a portable format. You may object to processing based on legitimate interests and may withdraw consent at any time where processing is based on consent. Withdrawal does not affect the lawfulness of processing carried out before the withdrawal. We normally respond within one month. Where necessary because of the complexity or number of requests, this period may be extended by a further two months. We will inform you of an extension and its reasons within the first month. Requests may be submitted to gdpr@froozy.eu. Where there are reasonable doubts about the requester's identity, the Operator may request only the additional information necessary to confirm identity. 11. Complaints and judicial remedies If you believe that the processing of your personal data infringes the GDPR, you have the right under Article 77 GDPR to lodge a complaint with a competent data protection supervisory authority. You may contact, in particular, the supervisory authority in the EEA country of your habitual residence, your place of work or the place of the alleged infringement. An up-to-date list and contact details of the data protection supervisory authorities in the European Economic Area are available at https://www.edpb.europa.eu/about-edpb/our-members_en. The European Data Protection Board itself is not a supervisory authority and does not handle individual complaints. You also have the right to an effective judicial remedy under Article 79 GDPR. Where permitted by the GDPR, proceedings may be brought before the courts of the country in which the controller has an establishment or in which you habitually reside. Before lodging a complaint, you may contact us at info@froozy.eu so that we can attempt to resolve your request. Contacting us first is voluntary and does not limit your right to complain to a supervisory authority or seek judicial relief. 12. Changes to this notice Froozy assigns a version number and effective date to each published version of this notice. Where a change is material, affected users will be informed in a manner appropriate to the nature of the change. 13. Controller The Froozy platform is operated by: - Name: IT Resource Consulting Kft. - Registered office: 2098 Pilisszentkereszt, Kossuth Lajos utca 45, Hungary - Tax number: 13207379-2-13 - Website: https://itresource.eu - Email: info@froozy.eu Hereinafter referred to as the “Operator” or “Froozy”.

https://froozy.eu/terms/PRIVACY_POLICY/versions/12?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