General Terms and Conditions (Terms of Service)

[PRODUCT NAME] salon software service (SaaS) for salons

DRAFT for legal review. Version 0.1, 2026-10-02. English translation of Általános Szerződési Feltételek. Not final, not legal advice, not to be published or put to customers before legal review. If the two texts differ, the Hungarian text prevails. [FOR THE LAWYER: ...] is the English form of the Hungarian [JOGÁSZNAK: ...] marker: an open question or missing data. The full list of open questions, the assumptions and the statement-to-code table are in the README. The text reflects the code state of 2026-10-02 (main a71f768) and the owner's decisions of 2026-10-02 (D2, D3, D4, D5, D9, D10). The product name and domain are not decided yet (D1), hence the [PRODUCT NAME] and [DOMAIN] placeholders.

1. The parties, scope and definitions

1.1. Provider (the "Operator"): [FOR THE LAWYER: the Operator's company name, registered office, company registration number, tax number, representative, e-mail and postal address. The owner fills these in; the same issuer data is also needed in the platform's Settings, Billing section, without which no invoice can be issued.]

1.2. Subscriber: the business (salon) pursuing an economic or professional activity that registers for the [PRODUCT NAME] service, on whose behalf the registering person acts. [FOR THE LAWYER: whether the contract may be concluded with businesses only; treatment of sole traders and persons who qualify as consumers; how consumer rules (for example the right of withdrawal) are excluded. Registration does not currently ask for a tax number or business status.]

1.3. Service: the [PRODUCT NAME] web-based booking and salon-management software, with the Subscriber's public booking page, the related notifications and add-on features, to the extent of the applicable Plan.

1.4. Definitions. User: a staff member or agent of the Subscriber for whom the Subscriber creates an account. Guest: a customer of the Subscriber who books on the Subscriber's booking page or whose data the Subscriber records. Plan: the paid or free variant of the Service (Annex 1). Calendar: the booking calendar of one active provider (staff member) linked to a calendar; usage under the Plans is measured on this. Place: one premises of the Subscriber. Booking page: the Subscriber's public online booking interface for Guests.

1.5. Content of the contract. The contract is concluded by the Subscriber's registration and consists of: these Terms with Annex 1 (Plans and fees), the Data Processing Agreement (Data Processing Agreement), and, for information, the Operator's Privacy Notice as controller and its Cookie Policy. [FOR THE LAWYER: the technical manner of acceptance and its provability. The registration form asks for acceptance with a mandatory checkbox and records, per document, the accepted version, the time and the accepting staff member; a later version change is re-accepted by the salon owner in the admin area. The final text must say which version binds and how the fact of acceptance is retained.]

1.6. Territory. The Service is currently aimed at salons in Hungary, invoiced in forints. [FOR THE LAWYER: the later launch in Slovakia and Romania (euro, RON, locally translated terms, mandatory local rules and governing law). This draft contains only the Hungarian and English versions.]

2. The Service

2.1. Scope. The Service includes the online calendar and booking entry, the public Booking page (in Hungarian and English), the guest register, management of services, working hours and resources, e-mail and (credit-based) SMS notifications, and Plan-dependent add-on features (for example online deposit, packages, coupons, campaigns, the cash register module, inventory, reports, digital declarations). The current range of features is set out in Annex 1 and the Operator's current plan description. [FOR THE LAWYER: the plan content is currently a proposal (docs/14-arazas-es-csomagok.md, chapter 3); the owner's approval and the development (feature gating) are still pending; the final terms must follow what is actually live.]

2.2. The Operator's role. The Operator is a technical service provider. It is not a party to the service contract between the Subscriber and the Guest, does not provide payment services, does not issue invoices or receipts on the Subscriber's behalf without the Subscriber's knowledge, and is not responsible for the quality of the Subscriber's services. The cash register module and similar functions are internal record-keeping aids. [FOR THE LAWYER: whether it can be stated that the cash register module is not a fiscal cash register or invoicing software; the bookkeeping questions on documents (in particular the receipt for online deposits) are open; the cash register module is switched off for operation abroad.]

2.3. Services connected by the Subscriber. The Subscriber may connect third-party services with its own accounts (for example card payments: SimplePay, Barion; invoicing: Számlázz.hu, Billingo; newsletters: Mailchimp; calendar: Google Calendar; measurement tags: Meta, Google, TikTok). Those contracts arise between the Subscriber and the third party; the Subscriber is responsible for legal and contractual compliance, and the availability of the Service may depend on them. The Operator transmits data to connected services on the Subscriber's instruction.

2.4. Development. The Operator may develop and change the Service. It notifies the Subscriber in advance of the removal of a material function of the Plan. [FOR THE LAWYER: the notice period and the Subscriber's rights on a material reduction.]

3. Registration and account

3.1. Process. Registration requires: e-mail address, password, the registrant's name, the salon's name and identifier (the part in the Booking page address), the salon's public telephone number and trade. The salon is created only after the confirmation link received by e-mail is opened; the link is valid for 24 hours. The trial period (clause 5) starts upon confirmation.

3.2. Data and authority. The Subscriber declares that the data provided is true and that the registrant is authorised to conclude the contract on its behalf. The Subscriber keeps its data up to date.

3.3. Protecting access. A password must be at least 10 characters and its strength is checked (simple passwords that can be derived from the salon's name or e-mail address are rejected). The Subscriber is responsible for keeping credentials secret. The Operator recommends the optional two-step verification (authenticator app) available to Users. The Subscriber notifies the Operator without delay of any suspected unauthorised access.

3.4. Users. The Subscriber is responsible for its Users' activity, for configuring permissions (roles, capabilities) appropriately, and for Users using the Service in line with the law and these Terms. The Plan's Calendar limit applies when accounts are assigned.

3.5. Identifier. The Subscriber's identifier appears in the Booking page address and may only be a free, non-reserved name. The Operator may withdraw or require the change of an identifier that infringes third-party rights or is misleading. [FOR THE LAWYER: conditions of withdrawal.]

3.6. Support access. A designated Operator employee may enter the Subscriber's account only for support or troubleshooting, with a mandatory stated reason, a time limit (by default 30 minutes, at most 120 minutes) and a non-dismissible indicator visible in the Subscriber's interface. The Operator logs the start of such access, and its end as well if it ends by exit, sign-out or termination by the Subscriber; access that ends when its time limit expires has no separate closing log row (the time of expiry is logged at the start). The log for the Subscriber's account can be retrieved through the system's programming interface (API) by signing in as a staff member entitled to change the settings (by default an administrator); there is no screen for it in the Subscriber's interface today. The marking of individual operations performed in support access in the log is partial (Data Processing Agreement, Annex 2, item 14). Support access to a cancelled salon is not possible. [FOR THE LAWYER: whether the text addressed to the Subscriber may say that the log can be retrieved when there is no screen in the interface; or whether the sentences on the log and the marking should be left out until the Subscriber-side interface and the complete marking exist (README H17).]

4. Plans and fees

4.1. Plans. The Operator offers the following Plans (details in Annex 1): Free, Standard and Pro. Fees are net prices, monthly, in forints.

4.2. Free plan. Price: HUF 0. Contents: 1 provider (1 Calendar), 1 Place, at most 50 bookings per calendar month. Extra Calendars cannot be purchased with the Free plan; more Calendars require a paid Plan. [FOR THE LAWYER: owner's confirmation that extra Calendars are excluded (proposal in docs/14, chapter 9, item 1); the exact meaning of "booking" for the limit (online only or also those entered at the desk; whether cancelled and no-show bookings count; the time zone of the month boundary: the salon's or Hungarian time); the text must follow the development's actual counting.] The Operator gives no response time for the Free plan (knowledge-base type support).

4.3. Paid Plans. Standard: HUF 1,990 per month. Pro: HUF 4,990 per month. In every paid Plan 1 Calendar is part of the monthly fee; each further Calendar costs HUF 990 per month. Prices are net; value added tax is added as required by the law in force. [FOR THE LAWYER: the Operator's VAT status and the rate; the platform default is 27%; for foreign (EU) customers, reverse charge and tax-number validation if the Operator accepts foreign Subscribers.]

4.4. SMS credit. SMS notifications consume prepaid credit; without credit no SMS is sent. The price, the method of top-up and the expiry of credit apply as notified separately. [FOR THE LAWYER: the owner decides; none of these are defined today; crediting is currently a manual Operator action; self-service purchase is a later package.]

4.5. Individual and founder fees. The Operator may grant the Subscriber individual terms in writing (for example a founder fee, a discount or an individual monthly fee); during their term the fee and content under that agreement apply. [FOR THE LAWYER: the owner decides; subscribers existing at launch keep their current effective fee and today's functions (D2); the exact group and the expiry of the discount.]

4.6. Changes to fees. The Operator may change fees and Plan contents. It notifies the Subscriber at least [30] days before the change takes effect by e-mail and in the interface. Until the change takes effect the Subscriber may terminate the contract without giving reasons or switch to another Plan. [FOR THE LAWYER: the notice period; admissibility and limits of unilateral amendment in a business contract; a cap on the change; narrowing the Free plan's content.]

5. Trial period and fall-back to the Free plan

5.1. Trial. A new Subscriber receives a 14-day trial with the full feature set, without providing a bank card. The trial runs from the creation of the salon (confirmation of registration). [FOR THE LAWYER: the owner decides; the code currently counts the 14 days from creation; starting at activation (docs/14, 6.3) is not decided.]

5.2. Fall-back. If the Subscriber has not chosen a paid Plan by the end of the trial, the account automatically moves to the Free plan. On that basis the account does not become write-protected, and no data is deleted.

5.3. Free plan limits after fall-back. Calendars beyond the Free plan's limit remain and stay visible, but a new booking can only be made on the first Calendar until the Subscriber switches to a paid Plan. If the number of bookings in a calendar month reaches 50, a further booking cannot be made and an informational message is shown; bookings already recorded remain untouched. [FOR THE LAWYER: the owner decides; whether the limit applies to online bookings by the Guest or also to those entered at the desk; the wording shown to the Guest.] Switching to a paid Plan removes the limits.

5.4. Changing Plan. The Subscriber may change Plan at any time. The change takes effect immediately. A switch to a lower Plan is only possible if the number of active Calendars does not exceed the target Plan's limit. [FOR THE LAWYER: the owner decides; fee settlement for a mid-month change. The system currently does no pro-rata settlement; at invoicing the current subscription decides.]

6. Invoicing and payment

6.1. Monthly invoicing in advance. The Operator invoices the fee of the paid Plan and of extra Calendars monthly in advance. [FOR THE LAWYER: the owner decides; the invoicing day and the treatment of the first, partial month. The code currently knows a monthly invoice for the calendar month that the operator issues manually; automatic monthly invoicing is a later package.]

6.2. Invoice. The invoice is issued electronically via Számlázz.hu in the Operator's name (D5). [FOR THE LAWYER: regulating the acceptance of e-invoices; invoicing is currently manual with the platform's own numbering; issuing through Számlázz.hu is a later package.] The Subscriber is responsible for the accuracy of its billing data (company name, tax number, address, invoice e-mail); registration does not ask for these today, later development will.

6.3. Payment term. The Subscriber pays the invoice within the term stated on the invoice, [8] days from issue. [The platform default is 8 days; the owner finalises.]

6.4. Payment method. Bank transfer. Recurring card payment will be available through Stripe (D4); when introduced the Operator will inform the Subscriber separately and ask for separate consent to card payment. The Operator neither sees nor stores card data. [FOR THE LAWYER: Stripe as an independent controller and the separate terms of recurring card charges; there is no card collection today, the Stripe integration is not part of the current wave.]

6.5. Late payment. In case of late payment the Operator may charge statutory default interest and a cost lump sum and may proceed under clause 7. [FOR THE LAWYER: the exact rules on default interest and recovery cost lump sum between businesses.]

6.6. Refunds. The Operator does not refund the fee of a monthly period already begun, unless the law or a breach by the Operator requires it. [FOR THE LAWYER: pro-rata refund on cancellation and mid-month change, if at all; validity of a "no refund" clause.]

7. Arrears, suspension, reinstatement

7.1. Arrears. If the Subscriber's invoice remains unpaid [30] days after its due date, the account enters the "past due" state. The Operator warns of the past-due state and its consequences by e-mail. [FOR THE LAWYER: the owner decides; the 30-day threshold is the system default (the owner's decision of 2026-08-26); payment reminders are not sent yet, the Platform emails package (W1-B) builds them.]

7.2. Suspension. If the arrears continue for a further [14] days after the past-due state began, the Operator may suspend the account. Under the system defaults suspension occurs 30 + 14 days after the due date. [FOR THE LAWYER: the owner decides; finalising the two thresholds; the system currently treats the default of the automatic-suspension switch inconsistently in two places (known defect, W1-F).]

7.3. The suspended account. A suspended account is read-only: the Subscriber can sign in, view and export its data, but no new booking or modification can be recorded; the Booking page shows a "temporarily unavailable" message; marketing and customer-care automations stop. Transactional reminders for bookings already recorded continue regardless, because the Guest is not at fault for the Subscriber's arrears. [FOR THE LAWYER: the owner decides; central write protection is not yet extended to all writes (currently only new bookings are blocked); package W1-A builds it. The Terms describe the decided behaviour.]

7.4. Reinstatement. After the arrears are settled the Operator lifts the suspension. The system never reverts automatically: the Operator lifts it manually, within [FOR THE LAWYER: a reasonable period, e.g. 1 business day] of receiving payment.

7.5. Immediate suspension. The Operator may suspend the account with immediate effect, with notice, if its use endangers the security of the system or other Subscribers' data, or a serious breach of clause 10 is evident. [FOR THE LAWYER: procedure and remedy.]

8. Termination and the fate of data

8.1. Cancellation. The Subscriber may terminate the contract at any time, in the interface or in writing. Termination of a paid Plan takes effect [FOR THE LAWYER: the owner decides; at the end of the paid period begun / immediately]. [Salon-side cancellation is available in the interface (app/api/admin/subscription/cancellation).] Use of the Free plan may be ended at any time.

8.2. Termination by the Operator. The Operator may terminate the contract for serious breach (in particular a breach of clause 10 or persistent arrears) [FOR THE LAWYER: the length of arrears that justifies termination], and also [FOR THE LAWYER: the possibility and notice period of ordinary termination, discontinuation of the Free plan] with notice.

8.3. 90-day export window. For 90 days from termination (from the account entering the "cancelled" state) the account is read-only: the Subscriber can sign in, view its data and export its complete data set (guests, bookings, treatment cards, declarations). The Booking page is unavailable during this time and no new booking can be recorded. [FOR THE LAWYER: the owner decides; the complete salon export is available (POST /api/admin/export/salon, ZIP); the 90 days is the decision in the specification and D9.]

8.4. Anonymisation. When the 90 days have passed the Operator anonymises or deletes the personal data processed in the account (Guests, Users, contact messages, message log). Booking history may remain without personal data for statistical purposes. The Operator retains invoices issued by it, accounting documents and the related records, and the necessary part of security and audit logs, for the period required by law. [FOR THE LAWYER: the data scope to be retained, its legal basis and retention period (code comments assume 8 years for accounting documents; this is not a legal opinion); the choice between deletion and anonymisation by data type; which data can be irreversibly anonymised; automatic anonymisation is written (lib/tenant-exit/anonymise.ts, anonymiseTenant(), runTenantAnonymisation()), setting deletedAt at the end (anonymise.ts:208).]

8.5. Backups. Terminated or anonymised data drops out of backups gradually within the backup retention period (the backup script's default is 14 days; retention of off-site copies depends on the Operator's configuration). Details are in the Data Processing Agreement.

8.6. Reactivation within the window. [FOR THE LAWYER: the owner decides; whether the Subscriber may reactivate the account within the 90-day window (by choosing a paid Plan), and in what state it gets its data back.]

9. Data protection

9.1. Roles. For Guest and User data processed on the Booking page and in the Service the Subscriber is the controller and the Operator is the processor; the Data Processing Agreement applies. For the data of the Subscriber and its representatives related to using the Service (account, billing, security logs) the Operator is the controller; the Privacy Notice covers this. [FOR THE LAWYER: the division of roles, especially for Users' (staff) account data and sole-trader Subscribers.]

9.2. The Subscriber's obligations. The Subscriber is responsible for: (a) having a proper legal basis to process Guests' data; (b) informing Guests with its own privacy notice (the Booking page settings allow entering the notice's web address and the Guest confirms having read it with a mandatory checkbox when booking; the Operator does not supply the notice text) [FOR THE LAWYER: whether the Operator supplies a model notice to Subscribers]; (c) collecting and managing proper consent for marketing contact and respecting unsubscribes; (d) obtaining the necessary consent when recording health-related and other special data; (e) fulfilling requests to exercise Guests' rights, using the system's tools (per-guest export, erasure/anonymisation, consent log, retention setting).

9.3. Special data. The Subscriber decides whether it records data indicating health status (for example contraindications, allergy tests, signed declarations, treatment cards, answers to custom questions). The Subscriber should record only what the treatment requires. The Service also records the Guest's separate "processing of health data" consent.

9.4. Retention. The Subscriber may switch on automatic anonymisation of Guest data in the settings (default: off; when on, by default after 5 years of inactivity). The Operator deletes the log of outgoing messages after 365 days by default.

10. Acceptable use

10.1. The Subscriber and its Users must not use the Service: (a) for unlawful purposes or to store or publish unlawful content; (b) to send unsolicited commercial messages (spam) or marketing contact without consent; (c) in a way that circumvents or attempts to circumvent the protection of the Service or other Subscribers' data (bypassing access controls, querying another salon's data, security testing without the Operator's permission); (d) to place undue load on the Service (automated mass queries, denial-of-service attacks); (e) to circumvent Plan limits (for example by creating several free accounts for the same salon); (f) to use the Booking page in a misleading way or in a way that infringes third-party rights (unauthorised use of another salon's name or brand). [FOR THE LAWYER: the content and enforceability of item (e), additions to the prohibited list.]

10.2. The Subscriber is solely responsible for content it publishes on the Booking page and in notifications (texts, images, prices, declarations).

10.3. In case of a breach the Operator may act under clauses 7.5 and 8.2.

11. Availability, support, backups

11.1. Availability. The Operator runs the Service continuously with due care but does not commit to a specific availability ratio (SLA). Maintenance and updates may cause brief interruptions. [FOR THE LAWYER: the owner decides; whether the Operator commits to an availability ratio for the paid Plans; the code does not measure availability today and sends no active alerts.]

11.2. Backups. The Operator makes database backups for its own disaster recovery; this is not an archiving service for the Subscriber. The Subscriber is responsible for exporting in time the data it needs.

11.3. Support. The Operator's support channel: [FOR THE LAWYER: contact, hours, response time. The product has no support channel, contact link or help today; package 1.12 builds it.] No response time applies to the Free plan; for Standard the Operator aims at an e-mail reply within 2 business days, for Pro within 1 business day (docs/14 proposal, awaiting approval).

11.4. Delivery of notifications. Delivery of e-mail and SMS notifications also depends on providers' and recipients' systems; the Operator attempts delivery with due care but is not liable for non-delivery unless it results from the Operator's wilful or grossly negligent conduct. Without SMS credit no SMS is sent.

12. Liability

12.1. The Operator is liable for providing the Service under the Civil Code. [FOR THE LAWYER: limiting liability in a business contract: excluding indirect damage and loss of profit; a cap on damages (proposal: the fees paid by the Subscriber in the last 12 months); excluding from the limitation breaches that are wilful or grossly negligent or that harm life, bodily integrity or health.]

12.2. The Operator is not liable for: (a) damage arising from the legal relationship between the Subscriber and the Guest; (b) the accuracy and lawfulness of data recorded or content published by the Subscriber; (c) outages or operation of third-party providers (payment, invoicing, e-mail, SMS, calendar or measurement providers); (d) unauthorised access resulting from the loss or leak of the Subscriber's credentials; (e) force majeure.

13. Intellectual property, the Subscriber's content

13.1. The software and documentation of the Service belong to the Operator; during the contract the Subscriber receives a non-exclusive, non-transferable right of use.

13.2. The Subscriber remains the rightholder of the data it records and of its content. The Subscriber grants the Operator the right to store, process and display the content to the extent necessary to provide the Service.

13.3. [FOR THE LAWYER: the owner decides; displaying the Operator's brand ("operated by [PRODUCT NAME]" footer) on the Free plan's Booking page. It is planned (docs/14, 7.5) but the code has no such feature today; if it is built, it has to be stated here.]

14. Confidentiality

The Operator treats the Subscriber's data and business information confidentially, does not use it except to perform the contract and does not disclose it to third parties, except the sub-processors named in the Data Processing Agreement and cases required by law. [FOR THE LAWYER: whether mutual confidentiality is needed.]

15. Amending the Terms

15.1. The Operator may amend these Terms. The Subscriber is notified at its registered e-mail address and in the interface at least [30] days before the amendment takes effect.

15.2. Until the amendment takes effect the Subscriber may terminate the contract free of charge; after it takes effect, continued use of the Service counts as acceptance of the amended terms. [FOR THE LAWYER: validity of this construction in a business contract; separate acceptance of material changes.]

15.3. Earlier versions of the Terms are available to the Subscriber on request.

16. Governing law and disputes

16.1. The contract is governed by Hungarian law. [FOR THE LAWYER: designating the court with exclusive jurisdiction; jurisdiction and governing law and mandatory local rules for foreign Subscribers.]

16.2. The parties settle disputes primarily by consultation. If the Hungarian and English texts differ, the Hungarian text prevails. [FOR THE LAWYER: whether the English version is an information-only translation.]

17. Miscellaneous

17.1. The Operator sends contract-related notices to the Subscriber's registered e-mail address; the Subscriber reports an address change without delay. 17.2. The Operator needs no consent to assign the contract on succession; assignment by the Subscriber requires the Operator's consent. [FOR THE LAWYER: to be completed] 17.3. Partial invalidity does not affect the validity of the other provisions.

18. Contact and complaints

[FOR THE LAWYER: the Operator's contact details (e-mail, postal address, telephone), complaint-handling procedure and deadlines, data protection contact. The product has no support or complaint channel today.]

Annex 1: Plans and fees

The table records the owner's decision of 2026-10-02 (D2). The feature content is the starting state per the proposal in chapter 3 of docs/14-arazas-es-csomagok.md, awaiting approval; the final annex must follow the plan description that is actually live. Prices are net, in forints, monthly fees.

[FOR THE LAWYER: the owner decides; finalising feature content; the place of the cash register module, inventory and commission in the plans (they currently have no separate feature key and are available in every plan); the price of SMS credit; the EUR and RON price lists before launching abroad.]