Current version — effective 5 June 2026. This is a living document that we may update from time to time as our service and applicable law evolve; the latest version is always available on this page.

FyraSoft Platform — Terms of Service

Provider: Fyra Software Korlátolt Felelősségű Társaság (FyraSoft Kft.), a Hungarian limited liability company; company registration number (cégjegyzékszám) 13-09-241696; tax number (adószám) 32857090-2-13; EU VAT number HU32857090; registered seat: 2724 Újlengyel, Petőfi Sándor utca 48., Hungary ("FyraSoft") Effective date: 2026-06-05 Version / last updated: v1.0 (2026-06-05) Contact: privacy@fyrasoft.com (general account contact: admin@fyrasoft.com)

These Terms of Service ("Terms") form a binding agreement between FyraSoft ("FyraSoft", "we", "us", "our") and the business entity that registers for or uses the FyraSoft platform ("Customer", "you", "your"). By creating an account, purchasing a subscription or credits, or otherwise using the Service, you agree to these Terms on behalf of your organisation and confirm you are authorised to bind it.

If you do not agree, do not register for or use the Service.

These Terms incorporate by reference the FyraSoft Privacy Policy, the FyraSoft Data Processing Agreement (DPA), the FyraSoft Sub-processor list (Section 8.8), the Acceptable Use Policy (Section 4, whether stated here or maintained separately), and Paddle's buyer terms (Section 6).

1. Definitions

• Platform — the FyraSoft hosted software-as-a-service environment through which the Modules are made available, including the web application, APIs, dashboards, account/wallet management, and supporting infrastructure.
• Module — a distinct AI-powered functional component of the Platform (for example, but not limited to: FyrAura (AI voice), FyrAgents (AI agents), FyrAero (GEO/visibility), FyrAction (workflows/automation), FyrAcademy (training), and fyradmin (tax tooling)). Modules may be offered as part of the Platform and/or marketed standalone; in all cases use is governed by these Terms.
• Service — collectively, the Platform and all Modules, features, APIs, documentation, and related support made available to you under these Terms.
• Credits — the euro-pegged unit of account used to meter and pay for consumption of the Service. Credits are not money, not a stored-value or e-money instrument, not a deposit, and not redeemable for cash. See Section 5.
• Subscription — a recurring (e.g. monthly) plan that grants a monthly allotment of Credits and access to the Service, billed through Paddle.
• Subscription Credits — Credits granted as part of a Subscription that reset each billing cycle (use-it-or-lose-it). See Section 5.
• Purchased Credits — Credits bought separately as a one-time add-on, which do not expire while your account is active and in good standing. See Section 5.
• Org Wallet — the organisation-level Credit balance held against your account, against which consumption is drawn.
• Customer Data — data, content, files, prompts, spreadsheets, and other materials that you, your Users, or your own end users submit to or process through the Service.
• Output — content generated by the Service in response to Customer Data or instructions.
• User — an individual (such as an employee, contractor, or agent of the Customer) authorised by you to access the Service under your account.
• Paddle — Paddle.com Market Ltd and its affiliates, our Merchant of Record. See Section 6.
• Sub-processor — a third party engaged by FyraSoft to process personal data on the Customer's behalf in the course of providing the Service, as described in the Sub-processor list (Section 8.8) and the DPA.
• Data Protection Law — the EU General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR"), the Hungarian Act CXII of 2011 on Informational Self-Determination and Freedom of Information ("Infotv."), and any other applicable data-protection or privacy law.
• EU AI Act — Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence.

2. The Agreement, the Platform, and the Module Model

2.1 One agreement covers everything. These Terms govern your use of the Platform and every Module, whether you subscribe to the full Platform, a bundle, or a single standalone Module. You do not enter into a separate contract per Module. Where you purchase a "standalone" Module, you still receive scoped access to the Platform necessary to use that Module.

2.2 Modules and scoped access. Your entitlement to specific Modules and features depends on your chosen plan and any add-ons. We may add, change, rename, or retire Modules and features over time (see Section 15).

2.3 Automatic technical dependencies. Some Modules rely on other Modules or platform components to function (for example, a voice Module such as FyrAura may depend on an agent Module such as FyrAgents under the hood). Where this is the case, we provision and operate those dependencies automatically as part of delivering the Module you selected. This does not grant you a separate, independent licence to use the dependency Module on its own, and any Credit consumption arising from such operation is metered as part of using the Module you selected. Such dependencies, and any Sub-processors they entail, are covered by the same data-protection terms in Section 8 and the DPA.

2.4 Beta and pre-release features. Features marked beta, preview, or experimental are provided "as is", may change or be withdrawn, and may be excluded from any availability commitments.

3. Account Registration and Eligibility

3.1 Business use only (B2B). The Service is offered solely for business and professional use by organisations. It is not intended for consumers, and consumer-protection rules applicable to consumer contracts are not intended to apply. By registering you confirm you are acting in the course of a business, trade, or profession. (For the avoidance of doubt, nothing in these Terms limits the statutory data-protection rights of any natural person whose personal data is processed through the Service; those rights are addressed in Sections 8–9 and the Privacy Policy.)

3.2 Eligibility. You must be a legal entity (or an individual acting for business purposes) capable of forming a binding contract, and the individual registering must be authorised to bind the organisation. You must not use the Service if you are barred under applicable law or sanctions (including EU and Hungarian sanctions regimes).

3.3 Paid-only public signup. At launch, public self-serve registration is paid-only: there is no free tier. Access requires an active Subscription and/or Purchased Credits. Free trials, if any, are granted manually by FyraSoft to selected partners and are subject to any additional terms communicated at the time.

3.4 Account information. You agree to provide accurate, current, and complete registration and billing information and to keep it up to date. Billing and tax details are collected and verified by Paddle as Merchant of Record (Section 6).

3.5 Account security. You are responsible for safeguarding credentials, for all activity under your account, and for your Users' compliance with these Terms. Notify us promptly at security@fyrasoft.com of any suspected unauthorised access.

3.6 Users. You may authorise Users within the limits of your plan. You are responsible for your Users' acts and omissions as if they were your own, and for ensuring your Users are informed of and comply with these Terms.

4. License and Acceptable Use

4.1 License to you. Subject to these Terms and payment of applicable fees, FyraSoft grants you a non-exclusive, non-transferable, non-sublicensable, revocable right to access and use the Service for your internal business purposes during your subscription term.

4.2 Acceptable Use. You agree not to, and not to permit any User or third party to:

(a) use the Service for any unlawful, fraudulent, infringing, deceptive, or abusive purpose, or to create or distribute illegal content; (b) upload or process content you do not have the right to use, or that infringes intellectual-property, privacy, or other rights, or for which you lack a valid lawful basis under Data Protection Law; (c) attempt to breach, circumvent, or test the Platform's security or tenant isolation, or attempt to access another customer's data, account, or tenant; (d) upload, run, or cause the execution of untrusted, malicious, or unauthorised code in order to reach, read, or affect other customers' data or the underlying infrastructure; (e) reverse engineer, decompile, or attempt to derive source code, except to the extent this restriction is prohibited by applicable law; (f) resell, sublicense, or provide the Service to third parties except as expressly permitted, or use it to build a competing service; (g) interfere with or disrupt the integrity or performance of the Service, including via excessive automated requests, scraping, or denial-of-service activity; (h) circumvent Credit metering, usage limits, or access controls; (i) submit special categories of personal data (GDPR Art. 9), criminal-offence data (GDPR Art. 10), or other particularly sensitive data through the Service except where expressly supported by your plan, agreed in the DPA, and lawful for you to process.

4.3 Forbidden high-risk and prohibited uses. You must not use the Service to make, or to materially support, automated decisions in the following high-risk domains, including (without limitation) any use that would constitute a high-risk AI system under Annex III of the EU AI Act, or any practice prohibited under Article 5 of the EU AI Act:

(a) creditworthiness evaluation or credit scoring of natural persons; (b) employment decisions, including recruitment, selection, promotion, or termination, and worker management/monitoring decisions; (c) law-enforcement, migration, asylum, border-control, or administration-of-justice decisions; (d) any practice prohibited under Article 5 of the EU AI Act (for example, certain social scoring, untargeted facial-image scraping, or manipulative or exploitative techniques); (e) any other use that would make the Service a high-risk or prohibited AI system under applicable law.

The Service is not designed, validated, or intended for such uses, and you are solely responsible if you attempt them.

4.4 Enforcement. We may investigate suspected violations and may remove content or suspend access as described in Section 14. We may use automated and manual means to monitor for abuse and to protect the Service and other customers, in each case consistent with the DPA and applicable Data Protection Law.

5. Credits and Billing

5.1 Credits as the unit of consumption. Use of the Service is metered in Credits. Credits are euro-pegged units of account used solely to access and consume the Service. Credits have no cash value, are not a deposit, not e-money, and not a stored-value instrument, cannot be transferred outside your organisation, and are non-refundable except as required by law or as expressly stated (see Section 6 for refunds handled by Paddle).

5.2 Subscription Credits (monthly reset). A Subscription grants a monthly allotment of Subscription Credits. Unless stated otherwise for your plan, Subscription Credits reset at the start of each billing cycle and do not roll over — unused Subscription Credits expire at the end of the cycle (use-it-or-lose-it).

5.3 Purchased Credits (non-expiring). Purchased Credits are bought separately as one-time add-ons. Purchased Credits do not expire while your account remains active and in good standing, and they are not reset by the monthly cycle. On full account closure or termination, a wind-down window applies as set out in Section 7.4(b).

5.4 Consumption order. Where both types are available, Credits are drawn in the following order unless we indicate otherwise in the Service: Subscription Credits first (so the use-it-or-lose-it allotment is consumed before non-expiring Purchased Credits), then Purchased Credits.

5.5 Org Wallet and spend limits. Credits are held in an organisation-level Org Wallet. You may optionally configure spend limits at the team and/or User level. Spend limits are a control you set; you remain responsible for all consumption against your account, including consumption that occurs before a limit takes effect or due to misconfiguration.

5.6 Pricing and changes. Plan prices, Credit pricing, and the Credit-to-Euro peg are as published at the point of sale via Paddle. We may change pricing prospectively; changes apply from your next renewal (see Section 15). Credit consumption rates per Module/feature may vary and may be adjusted with reasonable advance notice.

5.7 Insufficient Credits. If your Org Wallet is depleted, metered features may be paused or rate-limited until you replenish Credits or your next cycle begins. We are not liable for consequences of depletion.

5.8 Taxes. All fees and Credit purchases are handled through Paddle as Merchant of Record. Applicable VAT and other taxes are assessed, collected, and remitted by Paddle at checkout (see Section 6). Prices are exclusive of taxes unless Paddle's checkout states otherwise.

6. Paddle as Merchant of Record

6.1 Paddle is the seller/reseller of record. Our order process, checkout, and payment processing for Subscriptions and Credits are conducted by Paddle.com Market Ltd (a company registered in England and Wales under company number 08172165, registered office Judd House, 18-29 Mora Street, London, EC1V 8BT, United Kingdom) ("Paddle"), which acts as the Merchant of Record (reseller / seller of record) for these transactions. When you purchase, your contract for the payment transaction is with Paddle, and Paddle — not FyraSoft — is responsible for the checkout, payment processing, billing, invoicing, and the assessment, collection, and remittance of VAT and other sales taxes. FyraSoft does not itself process card or payment-instrument data; that data is handled by Paddle and its payment processors.

6.2 Paddle's terms apply to the transaction. Your purchase is also subject to Paddle's buyer terms and policies, which govern the payment transaction: Paddle Checkout Buyer Terms; Paddle Privacy Notice; Paddle Refund Policy.

6.3 Refunds. Refunds, chargebacks, and payment disputes are processed by Paddle in accordance with Paddle's refund policy together with these Terms. Because the public service is paid-only and Credits are consumable, fees and Credits are generally non-refundable except (a) where required by applicable law, (b) where expressly stated in your plan, or (c) at Paddle's or FyraSoft's discretion. Refund requests should be directed as instructed at checkout / on your Paddle receipt (Paddle buyer support), or to the contact in Section 17.

6.4 Data protection re Paddle. Paddle acts as an independent controller (and, for the payment transaction, as the contracting seller) in respect of the payment, billing, and tax data it processes; that processing is governed by Paddle's own privacy terms. Where Paddle processes personal data on FyraSoft's behalf, the Paddle Data Processing Addendum applies. Where FyraSoft receives billing/usage data from Paddle to operate your account, FyraSoft processes it as controller per Section 8.6 and the Privacy Policy.

6.5 Payment failure. If Paddle is unable to collect payment (e.g. expired card, failed renewal), we may suspend or downgrade your access and Credit allotment until payment is resolved (see Section 14).

7. Subscriptions, Renewals, Cancellation, and Credits on Termination

7.1 Term and auto-renewal. Subscriptions run for the stated billing period (e.g. monthly) and automatically renew for successive periods unless cancelled before the renewal date, billed through Paddle.

7.2 Cancellation. You may cancel auto-renewal at any time through the account/billing interface or via Paddle. Cancellation stops future renewals; it takes effect at the end of the current paid period unless stated otherwise.

7.3 Effect on access. Upon cancellation, you retain access to your paid Subscription features until the end of the current paid period. After that, the Subscription (and its monthly Subscription Credit allotment) ends.

7.4 What happens to Credits. (a) Subscription Credits are tied to the Subscription and expire when the Subscription period ends or the Subscription is cancelled/lapses — they are not carried over or refunded. (b) Purchased Credits remain available while your account is active and in good standing. On full account closure or termination, unused Purchased Credits remain usable during a wind-down period of 30 days after the effective date of termination, after which any remaining unused Purchased Credits are forfeited, unless a refund is required by law or expressly agreed.

7.5 Reactivation. If you re-subscribe after lapse, prior expired Subscription Credits are not restored. Recovery of any previously Purchased Credits after account closure is at our discretion and subject to data-retention limits.

7.6 No refunds for partial periods. Except as stated in Section 6 or required by law, fees for the current period are non-refundable on cancellation.

8. Customer Data, Data Protection, and Intellectual Property

8.1 You own your data and Outputs. As between the parties, you retain all right, title, and interest in your Customer Data and, to the extent permitted by applicable law and any underlying model/provider terms, in the Outputs generated for you. You are responsible for your Customer Data and for having the rights and lawful basis to submit and process it.

8.2 License to operate. You grant FyraSoft a limited, worldwide, non-exclusive license to host, process, transmit, display, and otherwise use Customer Data and Outputs solely to provide, secure, maintain, and support the Service, including via Sub-processors and as instructed by you. We do not sell your Customer Data.

8.3 We own the Platform. As between the parties, FyraSoft (and its licensors) owns all right, title, and interest in and to the Platform, Modules, software, models, configurations, documentation, and all related intellectual property, including any improvements. No rights are granted except as expressly stated.

8.4 Feedback. If you provide suggestions or feedback, you grant FyraSoft a perpetual, irrevocable, royalty-free license to use it without restriction or obligation.

8.5 Aggregated / de-identified data. We may generate and use aggregated and de-identified data (which does not identify you, your Users, or your end users, and is not reasonably re-identifiable) to operate, secure, analyse, and improve the Service. We do not use your Customer Data to train foundation models beyond what is necessary to serve your request, except with your separate documented consent. Sub-processor model providers are contractually directed not to train their models on Customer Data, as described in the DPA and Sub-processor list.

8.6 Controller / processor roles. (a) For tenant and end-user personal data processed through the Modules on your behalf, FyraSoft acts as processor and you act as controller. This processing is governed by the FyraSoft Data Processing Agreement (DPA), which forms part of these Terms and addresses the matters required by GDPR Article 28 (subject-matter, duration, nature and purpose of processing, types of personal data and categories of data subjects; processing only on documented instructions; confidentiality of personnel; security measures under Art. 32; Sub-processor terms and authorisation; assistance with data-subject rights and with Arts. 32–36; return or deletion of data at the end of processing; and information for / contribution to audits). Under the DPA, FyraSoft will notify you of intended additions or replacements of Sub-processors at least 30 days in advance, giving you an opportunity to object; and you (or a third-party auditor on your behalf) may audit FyraSoft's compliance once per twelve (12) months (or more frequently following a personal-data breach affecting your data or where a supervisory authority so requires), with FyraSoft entitled to satisfy audit requests through third-party audit reports and certifications where available. (b) For account, billing, and usage data that FyraSoft collects to provide and operate the Service (e.g. account identifiers, plan and wallet data, login and audit logs, support communications), FyraSoft acts as controller, as described in the Privacy Policy. (c) Paddle acts as the seller of record and, for payment/billing/tax data, as an independent controller (Section 6.4).

8.7 EU data residency. Customer tenant data is processed on EU infrastructure (at launch: Hostinger EU; dedicated Hetzner-DE available for sovereignty-tier customers). Certain Sub-processors may route or process limited data outside the EU/EEA; such transfers are made under appropriate safeguards, in particular the EU Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914 of 4 June 2021, applying Module Two (Controller-to-Processor) for transfers from FyraSoft (as exporter/processor on your behalf) to a Sub-processor in a third country, together with any necessary supplementary measures, as detailed in the DPA and Sub-processor list.

8.8 Sub-processors. FyraSoft uses Sub-processors to provide the Service. The current Sub-processor list (also maintained at the FyraSoft Sub-processor page referenced in the Privacy Policy / DPA) includes the following. For transfers outside the EU/EEA, the EU Standard Contractual Clauses (Module Two, Controller-to-Processor) under Commission Implementing Decision (EU) 2021/914 apply, together with the Sub-processor's published data-processing terms:

Planned / at-trigger Sub-processors (added at adoption, with notice and an opportunity to object per the DPA): ElevenLabs and Telnyx (voice) and Hetzner (EU dedicated infrastructure) — DPA/processing terms. We will give notice of new or replacement Sub-processors and an opportunity to object as set out in the DPA (at least 30 days' notice per Section 8.6(a)).

8.9 Code / spreadsheet analysis and the non-EU compute restriction. When the Service analyses Customer Data such as uploaded files, code, or spreadsheets, Customer Data containing personal data stays on EU infrastructure and is not sent to a non-EU code-execution sandbox. The E2B sandbox (US) is used only for non-personal-data compute unless and until an EU region and a signed Article-28 DPA with E2B (FOUNDRYLABS, INC.) are in place.

8.10 Data-subject rights. Data subjects may exercise their rights under GDPR — access, rectification, erasure (implemented via crypto-shredding), restriction, portability, and objection — as described in the Privacy Policy. Where FyraSoft acts as processor, we will assist you (the controller) in responding to data-subject requests as required by the DPA. Requests reaching FyraSoft directly that relate to data we process for you will be referred to you. Contact: privacy@fyrasoft.com.

8.11 Data after termination. Return, export, and deletion / crypto-shredding of Customer Data on termination are addressed in Section 14.5 and the DPA, subject to mandatory legal retention (e.g. financial records retained under Hungarian law for approximately 8 years).

9. AI-Specific Terms

9.1 Nature of AI Outputs. The Service uses artificial intelligence and large language models. Outputs are generated probabilistically and may be inaccurate, incomplete, outdated, biased, or otherwise unsuitable for your purpose. Outputs are not professional advice (legal, financial, medical, tax, or otherwise). You must independently evaluate Outputs before relying on them.

9.2 Human oversight is your responsibility. You are responsible for meaningful human oversight of, and final decisions based on, any Output. You must not use Outputs as the sole basis for decisions that have legal or similarly significant effects on individuals, and you must comply with the forbidden-use restrictions in Section 4.3.

9.3 AI transparency (EU AI Act Article 50). Consistent with our transparency obligations under Article 50 of the EU AI Act (applicable from 2 August 2026), users are informed when they are interacting with an AI system, and AI-generated or AI-manipulated media may be marked and/or carry machine-readable provenance information. Where you make Outputs available to your own end users, or deploy the Service in your own products, you are responsible for any disclosures, labelling, transparency, or other AI-Act / Data-Protection obligations applicable to your deployment, including any role you take on as a deployer of an AI system.

9.4 No high-risk automated decision-making by the Platform. The Platform is not designed to make Annex-III high-risk automated decisions (e.g. creditworthiness, employment, law-enforcement), and such uses, together with practices prohibited under Article 5 of the EU AI Act, are forbidden under Section 4.3.

9.5 Third-party models and providers. Outputs may be produced using third-party model and infrastructure providers (Sub-processors, see Section 8.8). Their availability, behaviour, and terms may affect the Service.

10. Service Availability and Support

10.1 Reasonable efforts. We will use commercially reasonable efforts to keep the Service available and to provide support consistent with your plan. The Service is otherwise provided on an "as available" basis.

10.2 No SLA at launch (unless agreed). Availability is provided on a commercially-reasonable-efforts basis. Unless a written service-level agreement is expressly agreed, no uptime guarantee, service credit, or guaranteed response time applies. A formal SLA (target uptime %, support response times, and service credits) may be introduced for enterprise customers and, where offered, will be set out in a separate written agreement.

10.3 Maintenance and changes. We may perform maintenance, modify, or temporarily suspend parts of the Service. We will make reasonable efforts to limit disruption and, where practicable, to give notice of planned maintenance that is likely to be materially disruptive.

10.4 Dependencies. Availability may be affected by third-party Sub-processors and by your own systems and connectivity, which are outside our control.

11. Confidentiality

11.1 Confidential Information. Each party may receive non-public information of the other that is marked or reasonably understood to be confidential ("Confidential Information"), including the Service's non-public features, pricing, and security details, and the other party's business information. Customer Data is your Confidential Information.

11.2 Obligations. The receiving party will use Confidential Information only to perform under these Terms, protect it with at least reasonable care, and not disclose it except to personnel and Sub-processors who need it and are bound by confidentiality obligations.

11.3 Exclusions. Confidential Information does not include information that is or becomes public without breach, was lawfully known before disclosure, is independently developed, or is rightfully received from a third party without restriction.

11.4 Compelled disclosure. A party may disclose Confidential Information if legally required, giving reasonable prior notice where lawful.

11.5 Relationship to data protection. To the extent Confidential Information includes personal data, the DPA and Data Protection Law govern, and prevail over this Section in case of conflict.

12. Warranties and Disclaimer

12.1 Mutual. Each party warrants it has the authority to enter into these Terms.

12.2 Your warranties. You warrant that you have all rights and the lawful basis necessary for your Customer Data, that your use complies with applicable law (including Data Protection Law and the EU AI Act) and these Terms, and that you will not engage in any forbidden or unacceptable use.

12.3 DISCLAIMER. EXCEPT AS EXPRESSLY STATED IN THESE TERMS, THE SERVICE, MODULES, AND OUTPUTS ARE PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY. TO THE MAXIMUM EXTENT PERMITTED BY LAW, FYRASOFT DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ACCURACY, AND ANY WARRANTY THAT THE SERVICE OR OUTPUTS WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR THAT OUTPUTS WILL BE ACCURATE OR RELIABLE. NOTHING IN THESE TERMS EXCLUDES LIABILITY THAT CANNOT BE EXCLUDED UNDER APPLICABLE LAW.

13. Limitation of Liability

13.1 Exclusion of indirect damages. To the maximum extent permitted by law, neither party is liable for any indirect, incidental, special, consequential, or punitive damages, or for lost profits, lost revenue, lost data, or loss of goodwill, arising out of or relating to these Terms or the Service, even if advised of the possibility.

13.2 Liability cap. To the maximum extent permitted by law, FyraSoft's total aggregate liability arising out of or relating to these Terms or the Service will not exceed the total fees the Customer actually paid for the Service (via Paddle) in the twelve (12) months immediately preceding the event giving rise to the claim.

13.3 Exceptions. The exclusions and cap do not apply to liability that cannot be limited or excluded under applicable law (for example, liability for death or personal injury caused by negligence, fraud, or intentional misconduct, and any liability that cannot be limited under mandatory Data Protection Law, including GDPR Art. 82), or to your payment obligations.

13.4 Allocation of risk. You acknowledge that the pricing reflects this allocation of risk and that, given the probabilistic nature of AI Outputs, you assume responsibility for verifying Outputs and for decisions made using them.

14. Suspension and Termination

14.1 Termination for convenience. You may stop using the Service and cancel renewal at any time per Section 7. Either party may terminate these Terms when you have no active Subscription and no remaining Credits.

14.2 Suspension. We may suspend or limit your access (in whole or part) with or, where necessary, without prior notice if: (a) payment fails or is overdue; (b) we reasonably believe you have violated Section 4 (acceptable use), including security, tenant-isolation, or forbidden-use violations; (c) your use poses a security, legal, or operational risk to the Service or others; or (d) required by law. We will aim to limit suspension to what is reasonably necessary and to restore access promptly once the cause is resolved.

14.3 Termination for cause. Either party may terminate for the other's material breach not cured within 30 days of written notice (or immediately for serious breach, illegality, or insolvency).

14.4 Effect of termination. On termination: your right to use the Service ends; outstanding fees become due; Subscription Credits expire and, on full account closure, unused Purchased Credits are subject to the 30-day wind-down and then forfeited per Section 7.4(b).

14.5 Data after termination. We will make Customer Data available for export for 30 days after termination where feasible, after which we may delete or crypto-shred it in accordance with the DPA, subject to mandatory legal retention obligations (e.g. financial records retained per Hungarian law for approximately 8 years). Personal data is retained per the retention periods stated in the Privacy Policy / DPA and then deleted or crypto-shredded.

14.6 Survival. Sections that by their nature should survive (including Definitions, IP, confidentiality, data-protection effects, disclaimers, limitation of liability, indemnity, governing law, and these effects) survive termination.

15. Changes to the Service and to These Terms

15.1 Changes to the Service. We may evolve the Service, including adding, modifying, or discontinuing Modules and features. We will not materially degrade the core Service you are paying for during a paid period without reasonable cause; material discontinuation will be handled with reasonable notice.

15.2 Changes to these Terms. We may update these Terms. For material changes, we will provide reasonable advance notice (e.g. by email or in-Service notice). Changes take effect on the stated date or on your next renewal. Continued use after the effective date constitutes acceptance. If you do not accept a material change, your remedy is to stop using the Service and cancel before the change takes effect. Changes to the DPA or Sub-processors are handled per the DPA.

16. Indemnification

16.1 Your indemnity. You will defend, indemnify, and hold harmless FyraSoft and its affiliates, officers, and personnel from and against third-party claims, damages, liabilities, costs, and reasonable legal fees arising from: (a) your Customer Data; (b) your use of the Service in violation of these Terms or applicable law; (c) your forbidden or unacceptable use (Section 4); or (d) your breach of your warranties.

16.2 Our indemnity (limited). FyraSoft does not provide an intellectual-property indemnity under these v1.0 Terms. A limited IP indemnity (e.g. defence against third-party claims that the unmodified Platform, used as permitted, directly infringes a third party's intellectual-property rights, subject to the limitation of liability and standard carve-outs) may be offered in a separate written agreement for enterprise customers.

16.3 Procedure. The indemnified party will promptly notify the indemnifying party, allow it to control the defence (without settling in a way that admits liability or imposes obligations on the indemnified party without consent), and provide reasonable cooperation.

17. Governing Law, Disputes, and Contact

17.1 Governing law. These Terms are governed by the laws of Hungary and applicable European Union law, without regard to conflict-of-laws rules. The UN Convention on Contracts for the International Sale of Goods does not apply.

17.2 Jurisdiction. The competent courts of Hungary, sitting in Budapest, have exclusive jurisdiction over disputes arising out of or relating to these Terms, subject to any mandatory law.

17.3 Informal resolution. Before commencing proceedings, the parties will attempt in good faith to resolve any dispute by negotiation, contacting the other party at the addresses below.

17.4 Supervisory authority. Nothing in these Terms limits any data subject's right to lodge a complaint with a supervisory authority, including the Hungarian National Authority for Data Protection and Freedom of Information (Nemzeti Adatvédelmi és Információszabadság Hatóság, NAIH), or another competent EU supervisory authority. NAIH contact details: postal address H-1363 Budapest, Pf. 9 (registered seat: H-1055 Budapest, Falk Miksa utca 9-11); telephone +36 1 391 1400; fax +36 1 391 1410; email ugyfelszolgalat@naih.hu; website naih.hu.

17.5 Notices. Legal notices to FyraSoft should be sent to admin@fyrasoft.com, addressed to Fyra Software Kft., 2724 Újlengyel, Petőfi Sándor utca 48., Hungary. We may give notice to you via the email associated with your account or via in-Service notification.

17.6 Contact. General and privacy contact: privacy@fyrasoft.com (account contact: admin@fyrasoft.com). Data-subject rights requests (access, rectification, erasure via crypto-shredding, portability, restriction, objection) may be exercised via the privacy contact as described in the Privacy Policy. Data Protection Officer: no Data Protection Officer is appointed; a DPO is not required under GDPR Article 37 (FyraSoft's core activities do not consist of large-scale regular and systematic monitoring of data subjects, nor large-scale processing of special-category data). The responsible point of contact for data-protection matters is privacy@fyrasoft.com.

18. General

18.1 Entire agreement. These Terms, together with any referenced policies (Privacy Policy, DPA, Sub-processor list, plan/order details, and Paddle's buyer terms for the payment transaction), constitute the entire agreement and supersede prior understandings on the subject.

18.2 Order of precedence. If there is a conflict, a signed order form or written agreement (if any) prevails over these Terms, which prevail over linked policies, except that the DPA and mandatory Data-Protection terms govern in respect of personal data, and Paddle's buyer terms govern the payment transaction.

18.3 Assignment. You may not assign these Terms without our consent; we may assign to an affiliate or in connection with a merger, acquisition, or sale of assets. The Terms bind permitted successors and assigns.

18.4 Subcontracting. We may use Sub-processors and subcontractors to provide the Service, remaining responsible for their performance as required by the DPA and applicable law.

18.5 Force majeure. Neither party is liable for delay or failure due to events beyond its reasonable control. This does not excuse payment obligations or data-protection obligations that survive a force-majeure event.

18.6 Severability. If any provision is unenforceable, the rest remain in effect and the provision is modified to the minimum extent necessary.

18.7 No waiver. Failure to enforce a provision is not a waiver.

18.8 Independent parties. The parties are independent contractors; nothing creates a partnership, agency, or joint venture.

18.9 No third-party beneficiaries. Except for FyraSoft's affiliates and indemnified parties where stated, these Terms create no third-party rights.

18.10 Language. These Terms are provided in English and the English version controls. If a Hungarian translation is published, it is provided for convenience only and the English version prevails in case of conflict, except where Hungarian mandatory law requires otherwise.

End of Terms of Service. Current version, effective 5 June 2026 — subject to periodic updates.