Terms of Service

1. Parties and acceptance

1.1 These terms are a contract between Polygonface s.r.o., Sládkovičova 60, 974 05 Banská Bystrica, Slovakia, registered in the Commercial Register of the District Court Banská Bystrica, Section Sro, Insert No. 29301/S, company ID (IČO) 50187210, tax ID (DIČ) 2120203151, VAT ID (IČ DPH) SK2120203151 (“Polygonface”, “we”, “us”), and the person or business named at sign-up (the “Customer”, “you”). Tealbrick is a brand of Polygonface.

1.2 How you accept. You accept these terms by ticking the acceptance box when you create an Account and again at checkout. We record the version of these terms and the time of acceptance. A person who downloads or runs Tealbrick Software without an Account may use it only under the Tealbrick Software Licence shipped with it (section 8.3).

1.3 Who may buy. We sell to businesses and professionals acting for their trade, business, craft or profession (“Business Customers”) and to natural persons acting for purposes outside their trade, business, craft or profession (“Consumers”). At checkout you tell us whether you buy for a business. A business name and a VAT ID or company registration number are optional; if you give a VAT ID, you buy as a Business Customer. You must be at least 18 years old.

1.4 Consumers. Where a provision of these terms says that it applies only to Business Customers, it does not apply to Consumers. Nothing in these terms limits the rights that mandatory consumer protection law gives a Consumer. Consumer-specific rules are in sections 9A (withdrawal), 16A (conformity) and 17.8 (liability), and in Annex A (withdrawal information and model form).

1.5 Concluding the contract online. You create an Account, choose a Licence in Portal, review the order (Mini App, Major Version, price and taxes) at checkout, can correct your entries before you pay, and conclude the contract by paying. We record the version of these terms that you accepted; you can view and save the current version at tealbrick.com/terms and we send you a confirmation by email after each purchase. The contract language is English. We have not signed up to any code of conduct. For Business Customers, the parties agree that the information duties in Articles 10(1)–(2) and 11(1) of Directive 2000/31/EC (E-Commerce Directive), as implemented in Slovak law, do not apply, as the law permits between parties who are not consumers.

2. Definitions

2.1 Account: the customer account in Portal that belongs to the Customer.

2.2 Account Owner: the one natural person who signs in for the Account (section 4.6).

2.3 Portal: the hosted control plane at portal.tealbrick.com and its API, which we operate.

2.4 Tealbrick Software: our proprietary software that we make available for download or deployment: the workspace bridge (container image), the tealbrick command-line tool (CLI) with its relay and harness adapters, and the installer, including updates. The Tealbrick desktop app is not Tealbrick Software under these terms; it has its own terms.

2.5 SDK Packages: miniapp-sdk, manifest, spec, conformance, create-tealbrick-miniapp and ui (the design-system kit), under any package scope we publish them, and their successors.

2.6 Tealbrick Software Licence: the licence published at tealbrick.com/software-licence and shipped with the Tealbrick Software and the SDK Packages. Part B of it is the Tealbrick SDK Licence.

2.7 Mini Apps: the Tealbrick mini apps published in our public repositories. Their own code is licensed under the Apache License 2.0. Their images also contain third-party components under other licences (section 8.6).

2.8 Licence: an entitlement, paid or complimentary, recorded in Portal, that lets Portal deploy, manage and update one Mini App in one Workspace within one Major Version (section 9).

2.9 Major Version: all releases with the same first version number, for example 1.0.0 up to but not including 2.0.0.

2.10 Workspace: one configured set of Mini Apps, bridge and agent connections, managed in Portal.

2.11 Customer Infrastructure: every hosting account, server, network, volume, database and device on which your bridge, your Mini Apps, your agents or your data run. By default this is a project in your own Railway account. It is never our infrastructure.

2.12 Customer-Supplied Components: everything you choose, configure, run or pay for yourself and connect to the Service, including: (a) AI agents, agent harnesses and agent runtimes (for example Claude Code, Codex, the Claude Agent SDK or other MCP clients); (b) AI models and model providers (for example Anthropic, OpenAI, Google, OpenRouter), and your API keys and accounts with them; (c) third-party accounts and services connected through Connect (the Tealbrick Mini App for connecting outside services) or otherwise, for example Composio, chat channels, MCP connectors, email and social accounts; (d) your hosting provider and your Customer Infrastructure; (e) your own code, forks and modifications.

2.13 Customer Data: all data that is created, stored, sent or received in Customer Infrastructure or by Customer-Supplied Components, including app content, documents, memories, agent inputs and outputs, tool calls and their results, messages, credentials, and API keys entered in the bridge page (the page served by your bridge where you enter keys).

2.14 Workspace Data: all data that Portal stores for an Account or a Workspace, including: canvas configuration and drafts; agent cards; grants, scopes and policies; skill texts you change (instructions your agents receive); Mini App setting values you enter in Portal; hook settings; deployment records, including the names of your hosting projects and services; status reports from your bridge (app states and versions, connection identifiers and client names, key names without values, scope labels and short status texts that apps write); and the Workspace audit log.

2.15 Account Data: identity, sign-in, contact, billing, Licence and order data about you and the Account Owner.

2.16 Controls: the configurable functions that limit or record what agents do, such as grants, scopes, holds, approvals, pause, revoke, rules and the audit log. The grant interface is the part of Portal where you set grants.

2.17 Standalone mode: a bridge mode in which the bridge stops taking configuration from Portal, keeps the last signed configuration and issues its own grants.

2.18 Service: Portal, the Tealbrick Software, the SDK Packages, the Mini Apps as delivered by us, the documentation and support.

2.19 Brand Assets: the names TEALBRICK, TEAL BRICK and POLYGONFACE, our logos and app icons, our product names when used with “Tealbrick”, the look and feel of our websites, Portal and apps, and our domain names and handles.

2.20 Security Update: an update whose main purpose is to fix a vulnerability in the Tealbrick Software, the SDK Packages or the Mini Apps.

2.21 Support Period: the period during which we provide Security Updates for a product and Major Version, as published at tealbrick.com/security (section 13).

2.22 Order: a separate written order form signed by both parties, for example under the partner terms.

2.23 Partner: a business with a signed partner agreement with us.

2.24 Term: the period from acceptance until these terms end under section 15.

2.25 Policies: the Acceptable Use Policy, the Data Processing Addendum, the Subprocessors list, the Brand Use Policy and, for information, the Privacy Policy.

2.26 Consumer and Business Customer: as defined in section 1.3.

3. What the Service is

3.1 Deterministic software. Tealbrick is deterministic software. Portal, the bridge, the CLI and the SDK Packages register, configure, deploy, route, check, execute and record instructions that you or your agents give. We do not provide, train or host AI models, and we do not pay for, proxy or resell model use. Features that call a model call the provider you picked, with your key, under your contract with that provider.

3.2 Features that call a model. In the current releases these are: (a) Knowledge Mini App (research and embeddings). You pick the model provider in the Knowledge settings and enter your own key in the bridge page. Knowledge ships default model names for each provider (a chat model and an embedding model); where the settings let you change them, the names you set apply. The choice of provider is yours. Because Anthropic offers no embedding model, the Anthropic option also needs your OpenAI key, and Knowledge then sends content to OpenAI to create embeddings. (b) CLI agent runs. The CLI can start an agent run in the agent runtime you choose, with your key and on your schedule. For its optional claude-sdk runner, Anthropic’s Claude Agent SDK is installed from npm under Anthropic’s terms.

3.3 AI Act position. Regulation (EU) 2024/1689 (AI Act) is separate from the cybersecurity rules in section 13. (a) For any AI system that you assemble from Customer-Supplied Components and the Service, you are the deployer (Art. 3(4)), and the provider (Art. 3(3)) where you put it into service under your own name. You are responsible for the duties that follow for your use, including prohibited practices (Art. 5) and any transparency or high-risk duties. (b) The model-calling features in section 3.2 are minimal-risk features. They are not intended for any use listed in Annex III of the AI Act. If you use them for such a purpose, you are responsible for the duties that follow. (c) Where a duty under the AI Act applies to us for a feature we ship, we meet it.

3.4 Who operates what.

3.5 What Portal receives and stores. Portal stores Workspace Data and Account Data. Portal does not store Customer Data. Your agents reach your Mini Apps through the bridge in Customer Infrastructure; Portal does not receive their tool calls or the results. Two exceptions are part of the Service: (a) Deploy logs. While a deployment or update that you started runs (at most about 15 minutes), Portal reads the build and start-up log lines of that service from your hosting provider and shows them to you. Portal removes recognisable secrets from each line and does not store the lines. (b) Values you enter in Portal. Mini App setting values and skill texts that you enter in Portal are stored as Workspace Data and passed to your hosting account or bridge. Do not enter secrets or personal data in them unless the setting asks for it. API keys for model providers and other services belong in the bridge page, not in Portal.

3.6 Railway is your vendor. Your Railway account and projects are governed by your own agreement with Railway. Railway is your provider and, where you act as controller of personal data in your projects, your processor. Railway is not our sub-processor for Customer Infrastructure. Railway’s availability, security, prices, data practices, backups and deletion are outside the Service. The same applies to any other hosting provider you use. We also use Railway, under our own contract, to host Portal; that is separate.

3.7 Portal’s access to your hosting account. (a) When you link Railway through Railway’s authorisation flow, Railway gives Portal administrative rights in the Railway workspace you choose (scope workspace:admin). If you paste a token instead, Portal accepts the scope of that token, which may be wider. Use a token limited to one workspace. (b) You instruct Portal to use this access only to: list your projects; create projects you ask for; deploy, update, configure, restart and remove the bridge and Mini Apps; set the variables they need; read their status; and read deploy logs under section 3.5(a). Portal uses it only for actions you start and the follow-up steps those actions need. We do not use it for support or debugging unless you ask in writing. (c) Portal stores the token encrypted with AES-256-GCM under a key held outside the database. Portal deletes the token when you unlink Railway or delete your Account. Deletion in Portal does not revoke the token at Railway; to end access fully, also revoke it in your Railway account settings.

3.8 Destructive actions you start. Some actions you start change or delete resources in Customer Infrastructure, for example removing a Mini App together with its data volume. Portal asks you to confirm them. Loss that follows from carrying out such an action as you instructed it is outside our responsibility. Loss caused by Portal carrying out an action differently from your instruction is not covered by this sentence.

3.9 Grants, revoke and Portal outages. (a) An online bridge checks Portal for new configuration continuously. A revoke, pause or grant change made in Portal normally reaches it within seconds. A call that is already running is not stopped. (b) Agent access tokens last 15 minutes. Signed configuration and grants last at most 12 hours. (c) If a bridge cannot reach Portal, it keeps serving under its last configuration until that configuration expires (at most 12 hours). After that it refuses all agent calls until Portal is reachable again or until you switch it to standalone mode. (d) Switching to standalone mode needs Portal to be available at the time you switch. (e) A revoke does not reach a bridge that cannot contact Portal until it reconnects or its configuration expires.

4. Account

4.1 Sign-in is provided by our identity provider (Clerk). You must give accurate details and keep them current.

4.2 The Account Owner must use multi-factor authentication.

4.3 You are responsible for every action taken under your Account and in your Workspaces, by the Account Owner, by your agents and by anyone who uses your credentials, unless the action results from our breach of these terms.

4.4 Do not share sign-in credentials, devices or pairing codes. Keep keys and tokens secure.

4.5 Tell us without undue delay at security@tealbrick.com if you suspect unauthorised use of your Account.

4.6 Account ownership. The Account belongs to the person or business named at sign-up. One natural person signs in for it as Account Owner. If the Account belongs to a business and the Account Owner leaves it, we move the Account to another person that the business names, after proof of authority that satisfies us. Until then we may suspend sign-in to protect the Account.

5. Your responsibilities

5.1 Customer Infrastructure. You are responsible for Customer Infrastructure: its account, contract, costs, capacity, configuration, network, access control, secrets, monitoring, logs, backups and restores, retention and deletion, and its security. Our templates may set defaults (for example a daily volume backup kept for 7 days). Defaults are a convenience, not a backup service. You must check that they meet your needs.

5.2 Customer Data. You are responsible for Customer Data: its lawfulness, accuracy, legal basis, rights clearance, retention, security and backup. If you are a Business Customer, you are the controller of personal data in Customer Data. We do not store it and are not your processor for it, except for the transient deploy-log display in section 3.5(a), which the DPA covers.

5.3 Agents and models. You are responsible for every agent and model you connect, for their configuration, prompts, instructions and tools, and for every output, decision, message and action they produce or take, including actions taken through the Service (section 7).

5.4 Credentials and keys. You are responsible for API keys, tokens, passwords and signing material that you create or enter, in the bridge page, in Connect or in your hosting account. Do not give an agent a person’s sign-in credentials.

5.5 Third-party accounts. When you connect a third-party account, you confirm that you may do so and may let agents act in it. You must follow that provider’s terms.

5.6 Compliance with law. You are responsible for your compliance with all law that applies to your use of the Service, including data protection, electronic communications and anti-spam rules, consumer protection, employment and workplace monitoring, sector rules, export control and sanctions, and the AI Act.

5.7 Outbound messages. If you or your agents send emails, posts, chat messages or other communications with the Service, you are the sender (Acceptable Use Policy, section 2).

5.8 Updates. You decide when to install updates in Customer Infrastructure. You must install Security Updates without undue delay after we publish them.

5.9 Your own modifications. If you change, fork or extend Mini Apps or other software, you are responsible for the result. Portal deploys only releases recorded in our signed release registry.

5.10 Workspaces for your clients (Business Customers only). If you run a Workspace in a client’s infrastructure or for a client (for example as a consultant or agency without a partner agreement): (a) you confirm that the client authorised you to connect its hosting account and to act for it; (b) before the client or its people use the Workspace, you bind the client to rules at least as protective of us as the Acceptable Use Policy and sections 5, 7 and 8; (c) you remain responsible to us for the client and its people as for yourself; (d) you forward our security notices to the client without undue delay; (e) the client has no rights against us under these terms. If you want to run client Workspaces under a separate commercial arrangement, our partner terms apply.

5.11 Records for claims (Business Customers only). You keep the logs of your bridge and Mini Apps for at least 12 months, and give us the relevant parts when a third party or an authority makes a claim against us about your use of the Service.

6. Acceptable use and content moderation

6.1 You must follow the Acceptable Use Policy, which forms part of these terms.

6.2 You may test the security of Portal or our infrastructure only under our coordinated vulnerability disclosure policy at tealbrick.com/security, or with our prior written permission.

6.3 You must not use the Service, our code, designs or Brand Assets to build or operate a product that competes with Portal or the bridge, except as the Tealbrick Software Licence allows.

6.4 Content moderation. We may restrict Workspace Data, agent cards, Workspaces or Accounts under the Acceptable Use Policy. We act on notices and on our own checks. We use no automated content moderation. We give you a statement of reasons when the restriction starts, unless the law forbids it. You may contest the decision under section 8.4 of the Acceptable Use Policy.

7. Customer-Supplied Agents and Models

7.1 Your agents, your decisions. All decisions, outputs and actions of agents and models are yours: content they create, messages they send, data they change or delete, payments or orders they start, and calls they make through the Service. The Service carries out and records instructions. It does not judge whether an instruction is wise, lawful, accurate or safe.

7.2 Controls are tools, not guarantees. Grants, scopes, holds, approvals, rules, pause, revoke and audit logs are configurable software functions that you operate. They work only as you configure them and within the limits in section 3.9. They are not a safety system, a compliance system or a promise that an agent will not cause harm. You choose suitable Controls, review held actions with care and keep the human oversight your use requires.

7.3 No professional advice. Nothing in the Service or its outputs is legal, financial, medical, tax or other professional advice.

7.4 Model providers. Your use of a model is governed by your contract with its provider. A model’s availability, behaviour, output, data use, price and changes are outside the Service.

8. Intellectual property

8.1 Our property. Polygonface and its licensors own all rights in Portal, the Tealbrick Software, the SDK Packages, the designs, user interfaces and look and feel, the documentation, the research, the release registry and its signatures, the Brand Assets and all improvements to them. Nothing in these terms transfers ownership to you.

8.2 Portal. During the Term you may use Portal for your own purposes and, if you are a Business Customer, under section 5.10, for your clients. You get no copy of Portal and no right to its code.

8.3 Tealbrick Software. You may install and use the Tealbrick Software under the Tealbrick Software Licence. That licence ends only under its own termination clause or under section 15. It survives the end of the Term for a bridge in standalone mode, unless we terminated these terms for your breach.

8.4 SDK Packages. Versions of the SDK Packages that ship the Tealbrick Software Licence are licensed under the Tealbrick SDK Licence (Part B of that licence). Earlier versions were published with an MIT licence declaration. Those versions stay available under the MIT licence; we do not withdraw it.

8.5 Restrictions. Except where these terms, the Tealbrick Software Licence or mandatory law allow it, you must not: (a) copy, modify, translate or create derived works of Portal or the Tealbrick Software; (b) decompile, disassemble or reverse engineer them, except as Articles 5(3) and 6 of Directive 2009/24/EC, as implemented in Slovak law, allow; (c) remove or change copyright, licence or trademark notices; (d) rent, lease, sell, sublicense, resell or host them for third parties; (e) bypass licence checks, signatures or technical protection; (f) use the Tealbrick bridge or CLI with a control plane, signing service or configuration source other than Portal, except in standalone mode; (g) publish benchmark or performance comparisons of Portal or the Tealbrick Software without first giving us the method and results and 30 days to comment; (h) publish a vulnerability before the end of the coordinated disclosure period in our security policy (normally 90 days). This does not limit any right to report to an authority or under whistleblower protection law.

8.6 Mini Apps. The Mini Apps’ own code is licensed under the Apache License 2.0. These terms do not restrict the rights that licence gives you. A Licence is not a licence to the source code. The Apache License 2.0 grants no right to our trade names, trademarks or product names (its section 6). Mini App images also contain third-party components under their own licences, listed in each repository’s THIRD_PARTY_NOTICES file.

8.7 Brand Assets. You get no right to use the Brand Assets except as the Brand Use Policy allows. You must not use them, or a confusingly similar name, logo or look and feel, for a fork, a reseller offer, a hosted service, a domain name, an app store listing, a package name or a social account.

8.8 Your property. You keep all rights in Customer Data and in code you write yourself.

8.9 Workspace Data. We use Workspace Data only to provide, secure and support the Service, to meet legal duties and to enforce these terms, as set out in the DPA. Under the DPA you instruct us to produce anonymous statistics from it.

8.10 Feedback. If you give us ideas, suggestions or feedback, you grant us a non-exclusive, perpetual, irrevocable, worldwide, royalty-free, transferable and sublicensable licence to use them in any manner and to the extent of all uses known at the time, without duty to you.

8.11 Contributions to our public repositories follow the contribution policy in the Brand and contribution policy and in each repository (Apache License 2.0 inbound and outbound, with a Developer Certificate of Origin sign-off).

9. Licences, prices and payment

9.1 What a Licence covers. A Licence lets Portal deploy, manage and update one Mini App in one Workspace, including the grant interface, for every release in the Major Version it covers. A paid Licence is a one-time purchase with no expiry (“lifetime for the Major Version”). A complimentary Licence is marked as such in Portal and ends at the expiry date shown there, or earlier if we withdraw it with 30 days’ notice.

9.2 Scope. A Licence sits on the Account that received it. You may assign it to one Workspace of that Account at a time and move it between your Workspaces. A Licence that served a Workspace switched to standalone mode stays with that Workspace and cannot be moved. You may not resell, rent, sublicense or transfer a Licence without our written consent.

9.3 Later Major Versions. A new Major Version needs a new Licence, except as section 13.3 provides for Security Updates.

9.4 No release promise. We do not promise new features, a release schedule or a minimum number of releases in a Major Version. We may stop selling a Mini App. Section 13 still applies.

9.5 Prices. Prices are in US dollars. Prices shown to Consumers include VAT. Prices shown to Business Customers exclude VAT and other taxes, which are added where they apply; with a valid VAT ID the reverse charge may apply. Checkout shows the total price including all taxes before you pay, and the price at checkout applies. Your bank may charge currency-conversion fees.

9.6 Payment. Stripe processes payments. A purchase is concluded when Stripe confirms payment. Card data never reaches us.

9.7 Refunds. Fees are not refundable, except under section 9A (withdrawal), section 16.2, section 16A (Consumers), section 15.5, mandatory law, or as we agree in writing.

9.8 Chargebacks and holds. (a) If a payment is refunded, reversed or disputed, we put the Licences bought with it on hold while we review it. (b) A hold stops new grants for the Mini Apps under that Licence. Your agents lose access to those Mini Apps within minutes. (c) We lift a hold without undue delay when the dispute is resolved in your favour. We otherwise revoke the Licence; a revoked Licence is final. (d) A chargeback that is not upheld is a breach of these terms. You then owe the price and, if you are a Business Customer, also the dispute fee charged to us and the recovery costs under section 9.10. (e) A chargeback on a Licence used in standalone mode does not end your duty to pay.

9.9 Referral. If you do not yet have a Railway account, Portal may show a sign-up link with our referral code. Railway may pay us a commission. It does not change your price and does not make us a party to your Railway contract.

9.10 Late payment (Business Customers only). For amounts we invoice outside Stripe checkout, late-payment interest and compensation for recovery costs apply as the Slovak Commercial Code provides.

9A. Right of withdrawal (Consumers only)

9A.1 Your right. If you are a Consumer, you may withdraw from a contract for a paid Licence within 14 days from the day the contract is concluded, without giving any reason (Directive 2011/83/EU on consumer rights, as amended, and the Slovak law implementing it).

9A.2 How to withdraw. Send us a clear statement of your decision before the 14 days end, by email to support@tealbrick.com or by post to our registered office. You may use the model withdrawal form in Annex A, but you do not have to. It is enough that you send your statement before the period ends.

9A.3 Immediate supply and loss of the right. A Licence is digital content that is not supplied on a tangible medium: when it is issued, Portal can at once deploy and update the licensed Mini App release in your infrastructure. At checkout we ask you whether you want us to start supplying the Licence immediately. If you expressly ask us to start supply before the withdrawal period ends and acknowledge that you thereby lose your right of withdrawal, you lose the right once supply has started. We confirm your request and acknowledgement in the purchase confirmation email. If you do not make this request, we issue the Licence only after the withdrawal period has ended.

9A.4 Refund. If you withdraw validly, we refund all payments received from you without undue delay and at the latest within 14 days from the day we receive your withdrawal, using the same means of payment you used, unless you agree otherwise. You pay no fee for the refund. The Licence ends when you withdraw, and you must stop using what you received under it, except the Mini Apps’ own code, which you may keep using under the Apache License 2.0.

9A.5 If a court treats a Licence as a service rather than as digital content, and you asked us to start before the withdrawal period ended, you may still withdraw within 14 days, and you pay an amount proportionate to what we supplied until you told us of your withdrawal, compared with the full contract.

10. What happens when a Licence ends, lapses or is on hold

10.1 This table states what keeps working.

10.2 The Apache-licensed code of a Mini App keeps working without a Licence. Connecting it to agents is then your own work. You may build your own bridge as the Tealbrick SDK Licence allows, but you may not use our Brand Assets for it.

10.3 When a Licence stops, Portal stops issuing grants for that Mini App and our bridge stops serving it to agents within minutes. Data in Customer Infrastructure stays there.

11. Data protection

11.1 Account Data. We process Account Data as controller under our Privacy Policy.

11.2 Workspace Data. If you are a Business Customer, we process personal data in Workspace Data for you, as your processor, under the Data Processing Addendum (DPA), which forms part of these terms. If you are a Consumer, the DPA does not apply; we process your Workspace Data as controller under our Privacy Policy, only to provide the Service to you.

11.3 Customer Data. We do not store Customer Data. Apart from the transient deploy-log display (section 3.5(a)), the DPA does not apply to it. You choose your own providers for it, for example Railway.

11.4 Requests about your data. If an authority or a data subject contacts us about Customer Data or Workspace Data, we forward the request to you where the law allows, and we do not answer it for you.

11.5 Third-party and data-subject claims (Business Customers only). Between the parties, you bear claims of data subjects and other third parties that arise from Customer Data, from Customer-Supplied Components or from your instructions. This allocation applies between the parties under Article 82(5) GDPR and does not affect the rights of data subjects.

11.6 Fines (Business Customers only). Each party bears administrative fines imposed on it. To the extent the law allows, you compensate us for a fine imposed on us because of your instructions or your breach of data protection law.

12. Confidentiality

12.1 Each party keeps the other’s non-public information confidential, uses it only for these terms and protects it with at least reasonable care. Our non-public information includes non-public code, security information, roadmaps and privately offered prices.

12.2 This does not cover information that is or becomes public without breach, was known before without duty, was independently developed or was lawfully received from a third party. Disclosure required by law is allowed, with prior notice where lawful.

12.3 This duty lasts during the Term and 5 years after it. Trade secrets stay protected while they remain trade secrets under the Slovak Commercial Code. Software we ship in public images or packages is not a trade secret.

13. Security, Support Periods and Security Updates

13.1 Support Periods. We publish at tealbrick.com/security, for each product and Major Version, the end date of its Support Period, and we show it before you buy a Licence. Each Support Period is at least 5 years from the first release of the Major Version.

13.2 Free Security Updates. During the Support Period we make Security Updates available free of charge, whether or not you hold a Licence, through our public release channels (signed release index, container registry, installer). With an active Licence, Portal also offers them as a deploy action. Without one, you deploy them yourself from the public channels.

13.3 Fix in a later version. We may provide a Security Update only as a later version, including a later Major Version, if you can get that version free of charge and without other cost to adjust your environment beyond what that version’s documentation requires. In that case your Licence for the earlier Major Version also covers Portal deployment of the later version until the end of the earlier version’s Support Period.

13.4 Feature updates are not included. Features, improvements and new Major Versions are not Security Updates and may need a new Licence.

13.5 Automatic security updates. Where the Service offers automatic Security Updates, they are on by default and you may switch them off or postpone them. The current releases do not offer them.

13.6 Vulnerability reports and notices. Report vulnerabilities as set out at tealbrick.com/security. We report actively exploited vulnerabilities and severe incidents as Article 14 of Regulation (EU) 2024/2847 (Cyber Resilience Act) requires, and we inform affected users. We contact the Account Owner by email and show notices in Portal for this purpose.

13.7 Our duties stay. Nothing in these terms limits our duties as manufacturer under the Cyber Resilience Act.

13.8 Our security measures for Portal are described in the DPA. We rely on our vendors (Railway, Clerk, Stripe) for the security of their services. No system is free of vulnerabilities.

14. Availability and support

14.1 No availability duty (Business Customers). For Business Customers, Portal availability is not a contractual duty. Unavailability of Portal, whatever its cause, including maintenance, updates, security measures and outages of our hosting, identity, payment, DNS or code-hosting vendors, is not a breach of these terms. For Consumers, this section does not limit the conformity rights in section 16A; planned maintenance is announced in Portal in advance where possible. Section 3.9 explains the effect of an outage on your bridge.

14.2 An Order may add a service level for a fee.

14.3 Support is by email on a reasonable-effort basis, in English, at support@tealbrick.com.

15. Term, suspension, termination, export and deletion

15.1 Term. These terms apply from acceptance until the Account is closed and section 15.7 is complete.

15.2 By you. You may stop using the Service and close the Account at any time. Fees paid are not refunded, except where section 16.2 or mandatory law provides otherwise. Before closing, switch any bridge that should keep serving agents to standalone mode (section 3.9(d)).

15.3 Suspension. We may suspend all or part of the Service for you, at once, if: (a) you breach the Acceptable Use Policy or section 8; (b) your use creates a security risk or may harm the Service, other customers or third parties; (c) the law, a court or an authority requires it; (d) a payment is disputed (section 9.8); or (e) we reasonably suspect fraud or misuse of the Account. A suspension under this section is not a breach of these terms. Where reasonable, we tell you first and give you a chance to fix the problem; otherwise we tell you when it starts and why. We lift the suspension when the reason ends.

15.4 Termination by us for cause. We may terminate these terms: (a) for a material breach that you do not cure within 30 days after notice (15 days for non-payment), or at once if the breach cannot be cured; (b) at once if you become insolvent, enter liquidation or a similar procedure, as far as the applicable insolvency law allows.

15.5 Discontinuation of Portal. We may discontinue Portal for all customers with at least 90 days’ notice. During the notice period we switch every Workspace that asks to standalone mode, and we provide the export in section 15.6. We do not terminate an individual customer’s paid Licences for convenience. If you are a Consumer and Portal is discontinued within 5 years after you bought a paid Licence, we refund the part of the Licence fee that corresponds to the remaining part of those 5 years.

15.6 Export. During the Term and for 30 days after the Account closes or these terms end, you may ask for a copy of your Workspace Data. We provide it in a structured, machine-readable format (JSON) within 30 days of the request.

15.7 Deletion. After the export period we delete Workspace Data and Account Data within 30 days, except: data we must keep by law (for example accounting records, for up to 10 years); audit-log entries, which are deleted when their 365-day retention ends; and backups, which expire within 27 days. If a bridge of a deleted Workspace is still connected to Portal, it stops serving agents when its configuration expires (section 3.9).

15.8 Effect of termination. Portal features stop as in section 10. Software already in Customer Infrastructure stays there. Section 8.3 states when the Tealbrick Software Licence survives.

15.9 Survival. Sections 5, 7, 8.1, 8.3 (as stated there), 8.4 (for copies already distributed inside mini apps), 8.5–8.11, 9.8, 9.10, 10, 11, 12, 13.2–13.3, 15.6–15.9, 16, 17, 18, 19 and 20 survive the end of these terms.

16. Quality of the Service

16.1 Each party confirms that it may enter into these terms.

16.2 What we promise. During the Support Period, the Tealbrick Software and each licensed Mini App, as delivered by us, materially perform the functions described in their documentation for the Major Version. If they do not, and you tell us in writing, we provide a fix or a workaround within a reasonable time. If we cannot, you may end the affected Licence and we refund the fee paid for it. This is the complete remedy for this promise, without prejudice to section 17.1.

16.3 What we do not promise. Beyond section 16.2 and section 13, we do not promise that the Service is fit for a particular purpose, accurate, uninterrupted, error-free or free of vulnerabilities, that it meets your requirements, that it keeps or protects Customer Data, or that it stops an agent.

16.4 Open-source software, including the Mini Apps’ own code, is provided under the warranty and liability terms of its own licence; the Apache License 2.0 provides it without warranty (its sections 7 and 8).

16.5 Customer-Supplied Components, Customer Infrastructure, Railway and other hosting providers, model providers and other third-party services are outside the Service.

16A. Conformity rights (Consumers only)

16A.1 If you are a Consumer, you have the statutory rights under Directive (EU) 2019/770 on contracts for the supply of digital content and digital services, as implemented in Slovak law. These rights cannot be excluded or limited by these terms, and sections 14.1, 16.2 and 16.3 do not limit them.

16A.2 What we must supply. The Licence, Portal and the Tealbrick Software must match the description, functionality, compatibility and other features stated in these terms and in the documentation, be fit for the purposes for which such software is normally used, and come with the updates, including Security Updates, needed to keep them in conformity for the period the law requires.

16A.3 Your remedies. If something is not in conformity, you may ask us to bring it into conformity free of charge within a reasonable time. If we refuse, cannot do so, fail to do so within a reasonable time, or the lack of conformity is serious, you may ask for a proportionate price reduction or, unless the lack of conformity is minor, end the contract and get a refund.

16A.4 How long. For one-time supply (such as the Licence entitlement and released software) we are liable for a lack of conformity that becomes apparent within at least 2 years of supply; for Portal’s continuous service, during the period of supply. A longer period applies where the law provides it.

16A.5 Your environment. We are not liable for a lack of conformity caused by your own hosting account or other Customer-Supplied Components that do not meet the technical requirements we told you about before the contract (a Railway account or other supported host, and an agent runtime of your choice), as Article 9 of Directive (EU) 2019/770 allows. You must cooperate reasonably to find out whether the cause is in your environment.

16A.6 To make a claim, use the complaints procedure in section 20.14.

17. Liability

Each paragraph of this section is independent. If one is invalid, the others still apply.

17.1 Mandatory liability. Nothing in these terms limits or excludes liability: (a) for damage caused intentionally; (b) for damage caused by gross negligence; (c) for harm to life, body or health; (d) under product liability law that cannot be excluded; or (e) any other liability that mandatory Slovak or EU law does not allow to limit. Sections 17.3 to 17.6 do not apply to these cases.

17.2 Scope. Our duties are those stated in these terms and the DPA. In particular: (a) We do not store, back up or protect Customer Data; it is in Customer Infrastructure (section 5.1). (b) For Workspace Data our duties are those in the DPA. The loss the parties foresee from its loss is the cost of restoring it from our latest backup. (c) Portal availability is not a duty (section 14.1). (d) Agent and model decisions, outputs and actions are yours (section 7). (e) Actions carried out as you instructed them are yours (section 3.8).

17.3 Foreseeable loss. Taking into account the scope of the Service in sections 3, 7, 13, 14 and 16, and the price, the parties agree that the highest loss we could foresee at the conclusion of this contract as a possible result of a breach of our duties (Slovak Commercial Code, § 379) is the greater of: (a) the fees you paid us in the 12 months before the event that caused the loss; and (b) EUR 1,000. The parties do not foresee loss of profit, revenue or goodwill as a likely result of a breach, because the Service does not run your business processes and you keep Controls and human review (section 7). You confirm that you have told us of no circumstance that would make a higher loss foreseeable.

17.4 Cap. Separately and in addition to section 17.3, our total liability arising out of or in connection with the Service and these terms is limited to the amount in section 17.3.

17.5 Higher limit for credentials and keys held by Portal. If an unauthorised person obtains the hosting-account token that Portal holds for you, or our configuration signing keys, because we breached our security duties, the amounts in sections 17.3 and 17.4 are replaced, for the loss that follows, by the greater of: (a) three times the fees you paid us in the 12 months before the event; and (b) EUR 10,000.

17.6 Your contribution. We are not liable for the part of a loss that you caused or contributed to, or could have avoided, including by not installing a Security Update within a reasonable time, not keeping backups of Customer Infrastructure, not using suitable Controls, or not keeping your credentials secure.

17.7 Notice of claims (Business Customers only). You must tell us in writing of a claim within 6 months after you learn of the loss. Late notice does not bar the claim, but we are not liable for the part of the loss that earlier notice would have avoided.

17.8 Consumers. If you are a Consumer, sections 17.3, 17.4, 17.5 and 17.7 do not apply. We are liable to you as mandatory law provides, and section 17.6 applies only as far as that law allows a reduction for your own contribution.

18. Force majeure

18.1 Neither party is liable for a failure to perform a duty other than payment, to the extent it is caused by an obstacle beyond its control that it could not reasonably foresee or overcome (Slovak Commercial Code, § 374), such as war, terrorism, civil unrest, epidemic, natural disaster, acts of authorities, or large-scale failures of the internet or power networks. Section 14.1, not this section, covers Portal availability.

18.2 The affected party tells the other within a reasonable time and takes reasonable steps to limit the effect.

19. Compensation by you (Business Customers only)

19.1 You compensate us for amounts we must pay to third parties, and for reasonable costs of defence, where a claim or a proceeding against us arises from: (a) Customer Data, including its collection, content and processing; (b) your agents, models and other Customer-Supplied Components, and their outputs and actions; (c) your use of third-party accounts and services, including messages sent through them; (d) your breach of these terms, the Acceptable Use Policy or the law; (e) your Customer Infrastructure and its operation; (f) your clients under section 5.10; (g) your forks, modifications or use of the Brand Assets.

19.2 Section 11.6 governs administrative fines.

19.3 We tell you promptly about the claim and give you the chance to take part in the defence. You give us the records under section 5.11. We do not settle a claim at your cost without consulting you.

20. General

20.1 Changes to these terms. We may change these terms. We give at least 30 days’ notice of material changes by email or in Portal and ask you to accept the new version. If you do not accept, you may close the Account before the change takes effect, and the export in section 15.6 applies. Changes required by law or for security may take effect sooner. Changes do not reduce what a Licence you already have covers in its Major Version, except where the law or security requires it. If you are a Consumer, we change these terms only for a valid reason: a change in law or regulatory guidance, a security need, a change in the Service or our providers, or to make the terms clearer. If a change of the Service negatively affects your access to or use of a paid Licence more than in a minor way, you may end the contract free of charge within 30 days of the notice or of the change, whichever is later, and we refund the part of the Licence fee that corresponds to the remaining part of 5 years from purchase.

20.2 Assignment. You may not assign or transfer these terms or a Licence without our written consent. You consent in advance to our assigning these terms to an affiliate or to a successor to the Tealbrick business; we tell you when we do. If you are a Consumer, an assignment must not reduce your rights.

20.3 Subcontractors. We may use subcontractors and vendors. We remain responsible for our own duties.

20.4 Notices. We send notices to the Account Owner’s email address or in Portal. You send formal notices to legal@tealbrick.com and a copy by post to our registered office. An email notice is received on the next business day.

20.5 Entire agreement. These terms, the Policies, the Tealbrick Software Licence and any Order are the entire agreement on their subject. Your purchase orders or general terms do not apply. For Business Customers, statements on our websites and in our marketing are descriptions, not promises, unless these terms repeat them. For Consumers, such public statements count where the law makes them part of the conformity requirements.

20.6 Precedence. If documents conflict, this order applies: Order; DPA (for personal data); these terms; Tealbrick Software Licence (for the Tealbrick Software and SDK Packages); Acceptable Use Policy; Brand Use Policy; other Policies.

20.7 Severability. If a provision is invalid or unenforceable, the rest stays in force. The parties will replace it with a valid provision that comes closest to its purpose.

20.8 No waiver. A failure to enforce a right is not a waiver.

20.9 Independent parties. Nothing creates a partnership, agency, employment or joint venture.

20.10 Export and sanctions. You must not use the Service in breach of EU or other applicable export control or sanctions law, or in a sanctioned country or for a sanctioned person.

20.11 Language. These terms are in English. A translation is for information only.

20.12 Governing law. Slovak law governs these terms and all disputes arising from them, excluding its conflict-of-law rules and the UN Convention on Contracts for the International Sale of Goods. If you are a Consumer, this choice does not deprive you of the protection of the mandatory provisions of the law of the country where you have your habitual residence (Article 6 of Regulation (EC) No 593/2008).

20.13 Courts. For Business Customers, the competent court of the Slovak Republic determined by the registered office of Polygonface has exclusive jurisdiction (Article 25 of Regulation (EU) No 1215/2012), and we may also bring a claim in the courts of the EU Member State or Lugano Convention state where you have your seat. If you are a Consumer, you may bring proceedings against us in the courts of the Slovak Republic or of the country where you are domiciled, and we may bring proceedings against you only in the courts of the country where you are domiciled (Articles 17 and 18 of Regulation (EU) No 1215/2012).

20.14 Complaints and conformity claims. Send complaints and conformity claims to support@tealbrick.com with your Account email, the Licence or order concerned and a description of the problem. We confirm receipt without undue delay and decide within 30 days.

20.15 Alternative dispute resolution (Consumers). If you are a Consumer and you are not satisfied with how we handled your complaint, or we did not reply within 30 days, you may ask us to remedy it, and you may then submit the dispute to an alternative dispute resolution body under the Slovak Act No. 391/2015 Coll. on alternative resolution of consumer disputes. The competent body for our sector is the Slovak Trade Inspection (Slovenská obchodná inšpekcia, www.soi.sk), unless another authorised body listed by the Slovak Ministry of Economy is competent. A Consumer resident in another EU country may also contact the ADR body or the European Consumer Centre of that country. The European Commission’s online dispute resolution (ODR) platform was discontinued in July 2025 and is no longer available.

Annex A — Withdrawal information and model withdrawal form (Consumers only)

Withdrawal information. You have the right to withdraw from a contract for a paid Licence within 14 days without giving any reason. The withdrawal period ends 14 days after the day the contract is concluded. To exercise the right, inform us — Polygonface s.r.o., Sládkovičova 60, 974 05 Banská Bystrica, Slovakia, support@tealbrick.com — of your decision by a clear statement (for example a letter or an email). You may use the model form below, but it is not obligatory. To meet the deadline, it is enough that you send your statement before the period ends.

Effects of withdrawal. If you withdraw, we refund all payments received from you without undue delay and at the latest within 14 days from the day we are informed of your decision, using the same means of payment as you used, unless you expressly agreed otherwise; you will not incur any fees for the refund.

Loss of the right. If you expressly asked us to start supplying the Licence before the withdrawal period ends and acknowledged that you thereby lose your right of withdrawal, the right ends once supply has started (section 9A.3).

Model withdrawal form (complete and return this form only if you wish to withdraw from the contract)

• To: Polygonface s.r.o., Sládkovičova 60, 974 05 Banská Bystrica, Slovakia, support@tealbrick.com
• I/We () hereby give notice that I/We () withdraw from my/our () contract for the supply of the following digital content () / for the provision of the following service (*):
• Ordered on () / received on ():
• Name of consumer(s):
• Address of consumer(s):
• Email address used for the Tealbrick Account:
• Signature of consumer(s) (only if this form is sent on paper):
• Date:

(*) Delete as appropriate.

Contact

Polygonface s.r.o., Sládkovičova 60, 974 05 Banská Bystrica, Slovakia, registered in the Commercial Register of the District Court Banská Bystrica, Section Sro, Insert No. 29301/S; company ID (IČO) 50187210, tax ID (DIČ) 2120203151, VAT ID (IČ DPH) SK2120203151.

Support: support@tealbrick.com. Security: security@tealbrick.com. Legal notices: legal@tealbrick.com. Tealbrick is a brand of Polygonface s.r.o.