Home / Licence Terms and General Terms and Conditions (GTC) for TAOM.AI

Licence Terms and General Terms and Conditions (GTC) for TAOM.AI

Version 1.10 · in force from publication. Every change receives a new version number; earlier versions are archived in the customer account under What’s new. The version in force at the time the contract is concluded is decisive for a contract.

Preamble

These General Terms and Conditions (“GTC”) govern the use of the platform TAOM.AI (taom.ai) and the services offered on it, in particular TAOM Process Studio (“Platform”, “Service”).

The Platform is operated by:

Traniva AG
Zimbergstrasse 11
8335 Hittnau, Switzerland
(“Traniva”, “we”, “us”).

The Platform may be used by companies, organisations and private individuals worldwide, insofar as this is permitted under the law of the respective country of residence or registered office.

Where these GTC distinguish between businesses and consumers, the following applies:

  • Consumer: any natural person who uses the Service predominantly for purposes that can be attributed neither to their commercial nor to their independent professional activity.
  • Business: a natural or legal person or a partnership with legal capacity who, when using the Platform, acts in the exercise of their commercial or independent professional activity.

The GTC are expressly incorporated as part of the respective registration, ordering or contracting process. The version relevant to the contractual relationship and the time of consent are documented.


1. Scope and contracting party

1.1 These GTC apply to all contracts and legal relationships between Traniva and customers/users in connection with the use of taom.ai, TAOM Process Studio, the licences, trainings, project packages offered and any other related services.

1.2 Deviating, conflicting or supplementary general terms and conditions of the customer/user only become part of the contract if Traniva expressly agrees to their validity in writing.

1.3 Where individual agreements (e.g. Enterprise contracts, framework agreements, service level agreements – SLA) are concluded with a customer, these take precedence over these GTC in case of doubt. For support, the Support Terms (SLA) apply in addition; they form part of these GTC.

1.4 The contracting party is always Traniva AG, unless expressly provided otherwise.


2. Definitions

For the purposes of these GTC:

  • Platform: the website taom.ai and the web applications accessible through it.
  • TAOM Process Studio: the cloud-based SaaS solution for creating, analysing and managing processes, models and documentation, including AI-supported functions.
  • Customer: any natural or legal person who acquires a licence or obtains paid services.
  • User: any natural person who accesses the Platform within a customer account (including the customer themselves if they are a natural person).
  • Licence: the right of use in TAOM Process Studio granted to the customer (e.g. Demo, Webuser, Webuser Pro, Project user, Enterprise).
  • AI agents: the AI-supported functions and agents integrated in TAOM Process Studio.
  • Evaluation use: free test/demo version without productive use.
  • Productive use: use in the course of business, governmental or other organisational activity or for real, permanent processes and documentation.

The licence tiers are, in ascending order: Demo, Webuser Basic (marketed as “Process Studio Modeller”), Webuser, Webuser Pro and the separately agreed models Project user and Enterprise. The Team add-on licence is already included in Process Studio Modeller.

Team add-on licence: a self-contained, separately purchasable licence that allows several users to edit the same model at the same time. It is managed with its own licence key and its own term.

Add-on licences: the Team add-on licence, the Testing and verification add-on licence, the Process Mining add-on licence, the Reporting add-on licence and the TAOM Process Recorder add-on licence. Each is managed with its own licence key and its own term, they end independently of one another and do not affect the licence tier acquired.

Licence key: the character string allocated to the customer with which a licence is assigned to an account.


3. Conclusion of contract, registration and Marketplace

3.1 The presentation of services, licences and packages on taom.ai does not constitute a binding offer but a non-binding invitation to submit an offer.

3.2 By ordering in the Marketplace, by submitting a form or by any other ordering action, the customer submits a binding offer. A contract is concluded by:

  • express order confirmation by Traniva (e.g. by e-mail), or
  • activation of the ordered licence(s) or commencement of performance.

3.3 Registration is required for certain content (e.g. demo access). The customer/user ensures that the information provided is correct and complete and is updated without delay in the event of changes.

3.4 Traniva may reject registrations or orders in individual cases without giving reasons (e.g. in the event of obvious misuse or legal risks in certain countries or sectors).

3.5 Minors may only use TAOM.AI if and to the extent that this is legally permitted in the respective country and, where applicable, with the consent of their legal representatives.

3.6 Licences, add-on licences and support licences are only activated once payment has been received and all documents required for the order (e.g. GTC, data processing agreement, Support Terms, extended SLA) have been confirmed, digitally signed or signed. Until then there is no entitlement to use. Clause 18.6 (interim licence) remains reserved.


4. Subject matter – TAOM.AI / TAOM Process Studio

4.1 TAOM Process Studio is a cloud-based software-as-a-service (SaaS) solution for modelling, analysing and documenting business processes and organisational structures (including BPMN processes, organisation charts, process maps, RACI matrices, system landscapes).

4.2 The specific scope of services results from:

  • the licence chosen (e.g. Demo, Webuser, Webuser Pro, Project user, Enterprise),
  • the service description in the Marketplace or on taom.ai valid at the time the contract is concluded,
  • and any supplementary individual agreements (e.g. Enterprise contracts, statements of work).

4.3 Traniva is entitled to adapt, extend or replace functions, supported AI models, integrations and interfaces in the course of further development, provided the typical benefit for the customer/user is preserved.

4.4 There is no entitlement to the provision or continued use of a particular AI model (e.g. a particular large language model).

4.5 AI models and model changes
TAOM Process Studio may use AI models operated or configured by Traniva (“TAOM models”) as well as AI services and models of external providers. Traniva is entitled to change, update or replace the AI models used, their versions, parameters and configurations at any time or to use other models, provided the typical purpose of use of TAOM Process Studio (in particular support for documentation and modelling) is preserved. The customer/user has no entitlement to the use of a particular AI model, a particular version or a particular performance level of the AI functions.


5. Licence models, term and termination

5.1 The use of TAOM Process Studio requires a valid licence. Licence models differ, among other things, in the number of users, available functions, integrations, usage volume and remuneration.

5.2 The term of a paid licence is based on the duration chosen at purchase (e.g. 1, 3, 6, 12, 24 or 36 months). It begins with activation and ends when the chosen duration expires, without notice of termination being required. There is no automatic renewal. The customer may purchase a new term at any time; if this is done before expiry, the remaining duration is added to the new term. Different terms and renewal rules may be agreed in individual contracts (e.g. Enterprise).

5.3 The free Demo licence is provided free of charge and without obligation. Traniva may change, restrict or terminate Demo accounts at any time. Productive use is generally not permitted (see clause 12).

5.4 The right to extraordinary termination for good cause remains unaffected.

5.5 Upon termination of the contract, the rights of use in TAOM Process Studio end. Traniva may block access. Where technically possible and legally permissible, the customer may be granted a reasonable period for data export before termination.

5.6 AI use as part of certain licences
In the licence models Demo, Webuser and Webuser Pro, access to the AI functions and AI resources provided by Traniva (e.g. TAOM agents, language models, AI quotas) is already included in the licence price, unless expressly stated otherwise in the Marketplace or contract. For these licence models, no additional usage fees are payable to Traniva for the use of the AI models used by TAOM. However, the restrictions on fair use and availability set out in these GTC apply.

5.7 Licence tier Webuser Basic (Process Studio Modeller). The licence tier Webuser Basic exclusively covers the use of the editor (in particular modelling, import and export) without AI functions. This tier includes no AI licences, no AI quotas and no use of the TAOM agents. There is no entitlement to the provision of AI functions in this tier; accordingly, no AI-related usage fees are charged for it.

5.8 Team add-on licence 

5.8.1 The Team add-on licence is purchased independently of the licence tier and is managed with its own licence key, its own term and its own number of users. It may be included in a package offer.

5.8.2 A valid Team add-on licence remains effective until the end of its term, even if the customer changes the licence tier during this term.

5.8.3 The Team add-on licence is included in Process Studio Modeller. It can be purchased and renewed separately for Webuser and Webuser Pro. The licence tiers in which a renewal is possible result from the service description in the Marketplace valid at the time.

5.8.4 When the Team add-on licence expires, the associated functions cease. The
other functions of the licence tier remain unaffected.

5.8.5 Channels and target systems. The Team add-on licence includes the connection to channels (Microsoft Teams, Slack) and the maintenance of the customer’s own target systems (e.g. Jira, Confluence, SAP Cloud ALM) in the customer account. They can be set up by the person who manages the licence; a valid licence tier from Webuser Basic is also required. Notifications from processes are sent exclusively to channels of the same customer. If the Team add-on licence or the licence tier ends, nothing is delivered any more; the set-up is retained and takes effect again after a renewal. Writing from the editor to a target system additionally requires clause 5.10.1. The transmission is governed by clause 16.25.

5.8.6 Working together and guest access. The Team add-on licence includes working together on the same model and the team chat. The customer may share individual models with persons of another customer (guest access); they require their own valid licence with a Team add-on licence. The sharing and its scope are the responsibility of the sharing customer; it can end the sharing at any time. The shared content remains data of the sharing customer.

5.9 Change of licence tier (upgrade)

5.9.1 A change is only possible to a higher licence tier (upgrade). A change to a lower tier during the current contract term (downgrade) is not provided for.

5.9.2 In the event of an upgrade, the residual value of the current licence is credited against the price of the new licence. The remaining term at the time of the upgrade is decisive; at most the price of the new licence is credited. The customer pays the remaining difference.

5.9.3 The residual value is not paid out, refunded or credited, not even pro rata and not even in the event of early termination.

5.9.4 When the upgrade takes effect, the previous licence key loses its validity. The new licence begins with activation; the term is based on the duration chosen at the upgrade.

5.9.5 Only the customer (purchaser of the licence) is entitled to upgrade, not the individual users managed under the licence.

5.9.6 Clause 5.9 does not apply to the licence models Project user and Enterprise; changes there are made in accordance with the respective individual agreements.

5.9.7 In the event of an upgrade, all users managed under the previous licence are transferred to the new licence. The new licence must therefore comprise at least as many user seats as are occupied at the time of the upgrade; a lower number of seats is not possible, a higher one is possible at any time. If seats are to be reduced, this must be done in the customer account before the upgrade. If the customer orders fewer user seats with the upgrade than the previous licence comprises, the difference lapses when the new licence is activated. No credit, refund or credit note is given for the seats that lapse (cf. clause 5.9.3). The future number of seats and a corresponding notice are displayed before the order is submitted.


5.10 Testing and verification add-on licence

5.10.1 The Testing and verification add-on licence applies per person. It may be included in a package offer. At the process step it unlocks in particular: verification obligation, risks and controls; equipment and infrastructure with the qualification status (IQ, OQ, PQ); test cases with test steps and process tests (E2E); test plans and cycles; guided test runs with results, test data and screenshots; the transfer of defects to connected target systems (e.g. Jira); approval and versions under the four-eyes principle; the test record as PDF; the user manual and the reconciliation with connected target systems.

5.10.2 Anyone who only performs verification does not need a higher licence tier: the add-on licence applies independently of the tier of the respective account. Without a higher tier, the other functions of that tier are not available, in particular no AI-supported functions.

5.10.3 The Testing and verification add-on licence is not included in any licence tier. The customer can purchase and renew it for a licence of the tiers Webuser, Webuser Pro or Enterprise and assign it to persons of its company, irrespective of their own tier (clause 5.10.2). It cannot be purchased for Process Studio Modeller or Demo.

5.10.4 A valid add-on licence remains effective until the end of its term, even if the licence tier changes in the meantime. After expiry, the associated functions cease; information already recorded is retained in the model and continues to be displayed, but can no longer be edited. The other functions of the licence tier remain unaffected.

5.10.5 Processing associated with use. The functions require that a permanent identifier is assigned to each account and stored with the content created with it. Without this assignment, origin and approval cannot be told apart and the functions cannot be used. Anyone using the add-on licence thereby accepts this processing; it cannot be deselected. Details are governed by clause 16.15 and the privacy policy.

5.10.6 Likewise, identifiers for process steps, risks and test cases are assigned automatically and cannot be changed once assigned (clause 16.16). This too is a prerequisite for use and cannot be deselected.

5.10.7 Deviations from test runs. If testers record a deviation from the model, TAOM shows it as a proposal to adapt the model. A changed version only applies once it has been approved in accordance with the customer’s rules; until then, the approved version remains decisive. Clause 16.13 applies accordingly.

5.10.8 Signature and seal. Signatures and approvals in TAOM (e.g. on the test record or user manual) are confirmations within the Platform: they record which person (identifier) confirmed what and when, and are secured against subsequent alteration with a document seal. They apply only within TAOM and are not a qualified electronic signature (ZertES/eIDAS); documents are not signed externally but sealed.

5.11 Process Mining add-on licence

5.11.1 The Process Mining add-on licence unlocks at the process step the recording and evaluation of times by time type (e.g. processing, waiting and idle time, lead time), key figures and case numbers per period as well as the comparison with planned values.

5.11.2 It is not included in any licence tier and can be purchased with its own term for Webuser, Webuser Pro and Enterprise. Clause 5.10.4 applies accordingly to the end of the term.

5.11.3 Interfaces to external systems (e.g. the automatic transfer of times or event logs from ERP, workflow or target systems) are not part of the add-on licence; Traniva offers them on request as an integration service under clause 22.

5.11.4 Project times (planned and actual per activity and role) do not belong to the add-on licence; they are included in the licence tier from Process Studio Modeller.

5.12 Reporting add-on licence

5.12.1 The Reporting add-on licence unlocks evaluations across all models under a node of the enterprise model (e.g. overview, Process Mining, project times, tests and risks). It can be purchased with its own term from Webuser Pro; clause 5.10.4 applies accordingly.

5.12.2 Only the information that the customer has recorded in its models is evaluated. The customer is responsible for its correctness and completeness.

5.13 TAOM Process Recorder add-on licence (applies from availability of the product)

5.13.1 The TAOM Process Recorder is an extension for web browsers. It records sequences in web applications (screenshots and clicked positions) and proposes process models and test cases for TAOM Process Studio from them. The proposals are not an approval (clause 16.13).

5.13.2 The full version is licensed per person and requires a valid Testing and verification add-on licence; without it, it can neither be purchased nor used. Its term ends at the latest with the Testing and verification add-on licence. The licence key and the associated secret key are issued in the customer account and must be treated confidentially in accordance with clause 6.6.1; Traniva may block keys that are misused.

5.13.3 The demo version is free of charge, limited in time and scope (term and number of recording steps according to the service description) and serves exclusively for evaluation (clause 12). It is provided after contact details have been given; after expiry a new demo key can be obtained. There is no entitlement to provision.

5.13.4 The Recorder only works together with the Platform; authorisation is checked there. Without a connection to the Platform or without a valid key, no recording is possible. Passing on, modifying or using the Recorder outside the Platform is not permitted (clause 13.4).

5.13.5 Technical limitations. Only what is displayed in the browser tab in which the Recorder is active is recorded. In particular, desktop applications, remote access and virtualised sessions as well as protected areas of the browser are not supported. With graphically drawn interfaces, embedded third-party content or unusual rendering, the recognition of fields may be limited. Supported browsers and distribution channels result from the service description. There is no entitlement to every web application being captured completely.

5.13.6 The customer ensures that it may use and record the recorded applications in this form (in particular under the licence terms of their manufacturers) and that recordings do not contain personal or confidential data that is not required. Clauses 16.26 and 16.29 apply accordingly. For recordings, the TAOM Screen Engine (marking and masking before saving) and – with automated data protection activated – the automatic redaction under clause 16.26 are available. They support the customer but do not release it from its own review.

5.13.7 Pilot customers. Customers who agree a pilot participation with Traniva AG make their learning recordings and the models, test cases and feedback resulting from them available. Traniva AG may review the insights gained from them and incorporate them into beta and later versions of TAOM; for this it receives a free, non-exclusive right of use. The pilot customer removes personal and confidential information before handover; content of the pilot customer is not shown to other customers. Clause 12 applies to pilot and beta functions; participation can be ended at any time.

6. Requirements for use and obligations of the customer/user

6.1 To use the Platform, the customer/user needs a suitable internet connection, current browsers and a customary workstation or end-device environment. The customer is itself responsible for providing and configuring its own IT infrastructure (e.g. networks, firewalls, end devices, identity and access systems).

6.2 Where the customer integrates TAOM Process Studio with its own systems or third-party systems (e.g. Jira, Confluence, SAP, Microsoft 365, Make.com, n8n, GitHub, Power BI, other cloud or on-premise systems), it is itself responsible for their procurement, licensing and technical operational readiness, unless expressly agreed otherwise in an individual contract or statement of work (SOW).

6.3 The customer ensures that Traniva is provided in good time with all access, test and production environments, interface information and contact persons necessary for integration and consulting services. Delays or additional effort due to missing or late cooperation are borne by the customer.

6.4 The customer is responsible for ensuring that integrations with its systems are only configured and operated in a manner compatible with the applicable legal requirements (in particular data protection, information security, sector rules) and its internal policies. Traniva provides advisory support on request but assumes no legal responsibility.

6.5 Access data must be treated confidentially and protected against unauthorised access.

6.5.1 Traniva may require a second factor for sign-in and for confirmations (multi-factor authentication, MFA for short). Users can set up MFA themselves in their user account, e.g. with a common authenticator app; the customer’s administrator can make it mandatory for all users of its company. Users do not pass on their second factor. Sign-ins and confirmations with a second factor are deemed to be acts of the signed-in person until a loss or misuse is reported to Traniva.

6.6 Licence keys and user seats

6.6.1 The licence key must be treated confidentially. It may not be passed on, published or made available for retrieval to third parties outside the licensed organisation.

6.6.2 The number of user seats acquired determines how many natural persons may use the licence. User seats are personal; simultaneous use of one seat by several persons is not permitted. A seat may be transferred to another person if the previous person permanently no longer uses it.

6.6.3 Traniva is entitled to check compliance with the number of seats technically and, if it is exceeded, to restrict use or to charge for the additional seats retrospectively.

6.6.4 A sign-in applies to one device. Simultaneous use of the same user account on several devices is deemed an indication of impermissible multiple use under 6.6.2. Traniva may point this out to the users and end the sign-in on the further device if the other sign-in is not ended. In the event of repeated multiple use, 6.6.3 applies.

6.7 Classification, approvals and permissions

6.7.1 Through its administrator – the person who acquires and manages the licence for the customer – the customer determines how models and content are classified and which approval levels and rights users, guests and AI agents receive, in particular for outputs, guest invitations and the use of AI agents, and whether changes are logged and assessed. Traniva provides functions and default settings for this. Default settings are proposals, not a recommendation for the individual case.

6.7.2 The customer alone is responsible for defining, maintaining and reviewing these settings. This also applies to the permissibility of the processing, disclosure and AI use thereby approved. Traniva implements the settings technically but does not check their content.

6.7.3 Guests from other organisations only receive access within the scope of the customer’s settings and the invitation. The customer is responsible for selecting the guests and for their obligation to confidentiality.

6.7.4 Documents and storage locations. For documents stored in the Platform, Traniva technically implements the approvals and rights for viewing and downloading defined by the customer. If the customer only stores a reference to its own system or a target system (e.g. SharePoint, DMS, Jira, Confluence) or transfers content there, that system alone governs access, retention and security; the customer is responsible for this. Traniva only guarantees protection for content within the Platform. Downloaded or exported files are the customer’s responsibility from the moment of download.

6.8 Assessment of changes

6.8.1 Impact score, effort and costs are non-binding estimates. They are based on the links in the model and on the assessment rules, efforts and rates defined by the customer. Preset rates are placeholders. The estimates do not replace a professional review, approval or calculation by the customer.

6.8.2 Whether rates are recorded per role or per person and who may see amounts is determined by the customer through its administrator (clause 6.7). If the customer records rates per person, it is responsible for the permissibility of this processing.


7. Use of AI, EU AI Act and “human in the loop”

7.1 TAOM Process Studio uses AI agents to support the creation, analysis and optimisation of processes, documentation and other work results. The AI agents can generate texts, models or other proposals.

7.2 All AI outputs are proposals, not a binding expert opinion or legal advice. Responsibility for all decisions, processes and documentation remains with the people and organisation using the Service (“human in the loop”).

7.3 Where technically possible, TAOM Process Studio labels the involvement of AI in work results (e.g. fully / partly / not AI-generated) as well as their origin and version (origin seal). This labelling may also be contained visibly or in machine-readable form in exports.

7.4 Users/customers who pass on or publish work results undertake not to remove or misleadingly alter AI labels and origin seals where content appears AI-supported or statutory transparency obligations exist (in particular under Regulation (EU) 2024/1689 – EU AI Act).

7.5 The Platform is primarily designed as a documentation and productivity tool. It is not intended to make automated individual decisions with legal or similarly significant effect without human control.

7.6 Users/customers from the EU/EEA undertake to use the Platform only in scenarios in which the Service is typically classified as a minimal-risk or limited-risk system under the EU AI Act. Use as a stand-alone high-risk system requires a separate written agreement with Traniva.

7.7 Traniva does not provide legal advice on classification under the EU AI Act. Users/customers are themselves responsible for assessing their specific use scenarios in the light of the applicable legal system.

7.8 No guarantee of result quality or response behaviour
There is no entitlement to a particular quality of content, accuracy, completeness, style, response speed or availability of the AI functions. AI outputs may be incorrect, incomplete, outdated or unsuitable and must always be reviewed and assessed by the customer or its users. To the extent permitted by law, neither a quality of AI results perceived as insufficient nor a temporary restriction or unavailability of individual AI functions alone gives rise to a claim for reduction, refund, credit or damages.

7.9 Language of the interface and the agents. The editor, the viewer and the TAOM agents are available in several languages. Interface labels and texts generated by agents may differ by language; there is no entitlement to identical wording in all languages. In the event of discrepancies between language versions of a text provided by Traniva AG, the German version prevails. Clause 13.3 applies to content created by the customer; clauses 7.1 to 7.4 apply to responsibility for AI-generated texts.

7.10 AI agents and classified content. Whether and up to which classification content is passed to AI agents is determined by the customer through its administrator (clause 6.7). An AI agent never receives more content than the triggering person may view themselves. Classification alone does not rule out the use of AI agents.


8. Prices, payment, international customers

8.1 Prices for licences, trainings and packages are displayed in the Marketplace or offered individually. They may be stated in CHF or – for orientation – in other currencies (e.g. EUR).

8.2 Unless stated otherwise, prices include any local taxes and duties in accordance with the information given in the Marketplace. Additional taxes/customs duties in the recipient country are borne by the customer.

8.3 Payments are made using the payment methods offered in the Marketplace (e.g. credit card, online payment service, invoice). Fees of external payment service providers may apply.

8.4 Unless otherwise agreed, invoices must be paid without deduction within 30 days of the invoice date. Different periods may apply to consumers depending on the payment method.

8.5 In the event of late payment, Traniva is entitled to demand default interest at the legally permissible rate, to charge reminder costs and to temporarily block licences/accounts.

8.6 Processing fee in the event of default (businesses). If a business remains in default after a second reminder has expired without result, Traniva may charge a processing fee of 15% of the outstanding gross amount in addition to the default interest. The business remains free to prove lower damage; Traniva remains free to prove higher damage.

8.7 Consumers. No processing fee is charged to consumers. Default interest at the legally permissible rate and the reminder costs actually incurred remain applicable.

8.8 Consumption-based components. The services are currently offered as licences with a fixed price per service tier; there is currently no separate billing based on consumption. TRANIVA AG reserves the right to introduce consumption-based components in the future – in particular the purchase of additional computing units (tokens) beyond the quota referred to in clause 10.4. Such components are shown in the service description and price list before their introduction; they do not apply retroactively nor to billing periods already running. The recording of consumption under clause 10.3 takes place independently of this and remains unaffected.


9. Availability, maintenance and support

9.1 TAOM Process Studio is provided as a standard cloud service. Unless expressly provided otherwise in a separate service level agreement (SLA), there is no entitlement to particular availability figures (e.g. 24/7, 99.9%) or firmly defined response times.

9.2 Maintenance work, updates and changes may lead to temporary interruptions. Traniva endeavours to carry out planned maintenance at times of lower use where possible and – where reasonable – to announce it.

9.3 Partial AI outages
Temporary outages, disruptions or restrictions of individual AI functions or of the AI models or AI services used by TAOM (e.g. maintenance, model changes, capacity bottlenecks at third-party services) do not constitute complete unavailability of the Platform within the meaning of any availability information, provided the other core functions of TAOM Process Studio (e.g. display, editing and export of existing models) remain generally usable.

9.4 Support. Traniva provides support via the support portal in accordance with the support tier booked. Details, in particular support tiers, business hours, live support, support access as well as recording and billing of support services, are governed by the Support Terms (SLA); they form part of these GTC and can be viewed in the customer account. The standard SLA applies to the licence tiers Webuser and Webuser Pro. Traniva offers extended agreements (extended SLA) only for Enterprise; unless these provide otherwise, the standard SLA applies. In the event of contradictions, the Support Terms take precedence over these GTC; individual agreements take precedence over both (clause 1.3).

10. Fair use, impermissible content and blocking

10.1 Users/customers undertake to use the Platform fairly and appropriately. The following are impermissible in particular:

  • automated mass use without a meaningful use case,
  • circumvention of technical restrictions,
  • attacks on the Platform or infrastructure (e.g. hacking, DDoS),
  • dissemination of unlawful, discriminatory or harmful content,
  • use for the development or operation of AI systems that are prohibited under applicable law.

10.2 In the event of violations, Traniva is entitled to:

  • remove or block content,
  • block accounts temporarily or permanently,
  • take legal action.

10.3 Measurement of consumption. The use of the AI-supported functions is recorded per access. In particular, the number and time of processing runs, the language model used and the volume of data processed in computing units (tokens) are recorded. The recording serves billing, capacity planning, detection of misuse and traceability towards the customer. The customer can view its consumption in the customer account at any time.

10.4 Reasonable consumption and quotas. Each service tier includes a consumption quota appropriate for the intended use. The amount of the respective quota results from the service description of the tier booked. TRANIVA AG is entitled to adjust quotas for future billing periods; periods already running remain unaffected.

10.5 Procedure in the event of exceptional consumption. If the consumption of an access considerably exceeds the quota of its service tier or is permanently well above the consumption of comparable accesses, TRANIVA AG informs the customer by e-mail. The customer is given the opportunity to purchase additional computing units or to change to a higher service tier. If there is no response within a reasonable period, TRANIVA AG is entitled to switch the access concerned to a more resource-efficient language model or to limit the processing speed. Use of the Platform remains possible in both cases; content already created remains accessible unchanged. Blocking under clause 10.2 remains reserved in the event of misuse.


11. API access and integrations

11.1 API keys and access tokens may only be used by the authorised customer/user and may not be passed on to third parties.

11.2 Integrations with third-party systems (e.g. Jira, Confluence, SAP, Microsoft 365, Make.com, n8n, GitHub, Power BI) require appropriate licences/contracts with the respective providers. These providers are not contracting parties of Traniva customers. Where the service description names third-party services as included (e.g. agents on an automation platform operated by Traniva AG), these are included to the extent stated; clauses 10.3 to 10.5 apply accordingly.

11.3 Traniva may change, suspend or discontinue integrations, in particular if third-party providers change or discontinue their interfaces or if legal or technical reasons speak against them.

11.4 Third-party licences and additional costs
11.4.1 Separate licences are generally required for the operation and integration of third-party systems. These are not part of the TAOM licences but must be procured and paid for separately by the customer, unless expressly agreed otherwise.
11.4.2 Where Traniva procures third-party licences (e.g. rental or test licences) in the name or on behalf of the customer under Enterprise or project contracts, this is done on the basis of the manufacturer’s terms. The corresponding costs are invoiced to the customer in addition to the TAOM licences.
11.4.3 In the context of Enterprise implementations, the third-party licences, environments and interfaces required for the desired digital twin use case can be determined together with the customer during an evaluation phase. The results are documented in the SOW or architecture concept.


12. Evaluation use and productive use

12.1 Demo and test accesses serve exclusively for the evaluation of the Platform, not for permanent productive use. Use for creating services for third parties or in critical business processes is not intended within the scope of the demo.

12.2 Use is deemed productive as soon as generated content flows into operational processes, is used vis-à-vis customers, suppliers, authorities or other third parties, or forms part of paid services/products.

12.3 An appropriate paid licence is always required for productive use.


13. Rights to the Platform and to content

13.1 All rights to TAOM.AI, TAOM Process Studio, the software components, designs, methods, trademarks and signs belong exclusively to Traniva or its licensors.

13.2 Users/customers receive – within the scope of the respective licence – a simple, non-transferable, non-sublicensable right to use the Platform for their own purposes.

13.3 The content created by the user/customer (models, texts, documents) generally belongs to the customer, unless third-party rights stand in the way. Traniva receives a right to use this content insofar as this is necessary for providing the services, for support, security, backups and statutory obligations.

13.4 Algorithms, models and internal configurations as trade secrets
The internal algorithms, AI models, training data concepts, prompt structures, system and model configurations, architecture designs, evaluation and optimisation procedures and other technical know-how of TAOM/Traniva are confidential business and trade secrets of Traniva or its licensors.
The customer/user has no entitlement to disclosure, inspection, examination or release of source code, model weights, training data, prompts, configurations or comparable technical details.
Reverse engineering, decompilation, systematic analysis or replication of the Platform, the models or their configurations are only permitted to the extent mandatorily allowed by law. Any further technical analysis for the purpose of replication, competitive monitoring (“benchmark scraping”) or disclosure to third parties is prohibited without the express written consent of Traniva.

13.5 In-house development. The TAOM Process Studio editor, including the display, editing and evaluation of BPMN models, is entirely developed in-house by Traniva AG. No third-party modelling libraries are incorporated whose licence terms would require attribution, disclosure of source code or redistribution under the same terms. Where open-source components are used in the operation of the Platform, this is done under licences that do not prevent commercial use; the corresponding notices are stored in the application. All rights to the in-house development remain with Traniva AG. Which open-source components are used in detail is published under What TAOM is built on and is updated continuously. This overview serves as an explanation; the provisions of this clause remain decisive. Information on the service providers involved in data processing can be found separately under Sub-processors.

13.6 Prohibition of reverse engineering. It is prohibited to reverse engineer, decompile, disassemble or replicate TAOM.AI, TAOM Process Studio and all other solutions of Traniva, including downloadable components such as browser extensions, plugins and viewers, in whole or in part, to create derived or competing products from them or to circumvent licence and protection mechanisms. Mandatory statutory rights (e.g. to establish interoperability) remain reserved. In the event of violations, Traniva may block access and terminate the contract without notice; further claims remain reserved.


14. Warranty

14.1 Traniva warrants that the Service essentially corresponds to the functions described. Permanent freedom from errors or interruptions cannot be guaranteed.

14.2 Defects must – where reasonable – be reported and documented without delay. Traniva endeavours to remedy them or provide a workaround.

14.3 Third-party components and services (e.g. cloud providers, AI models, integrations) are subject to their own warranties; Traniva is liable for these only to the extent permitted by law.


15. Liability

15.1 Traniva is liable without limitation for damage resulting from:

  • intentional or grossly negligent breach of duty,
  • injury to life, body or health.

15.2 In the event of slight negligence, Traniva is only liable for breach of essential contractual obligations (cardinal obligations); in these cases liability is limited to the typically foreseeable damage.

15.3 To the extent permitted by law, Traniva’s liability – except in the cases under clause 15.1 – is limited for paying customers to the remuneration paid for TAOM Process Studio in the respective contract year, but no more than twice this annual remuneration.

15.4 To the extent permitted by law, Traniva is not liable for indirect damage, consequential damage, lost profit or loss of data. Users/customers are obliged to back up their data on their own responsibility.

15.5 To the extent permitted by law, liability for damage resulting from use of the Platform contrary to these GTC or to the applicable legal system (e.g. use as a high-risk system within the meaning of the EU AI Act without a suitable agreement) is excluded.

15.6 External AI services
Where TAOM Process Studio builds on AI services or infrastructures of third parties (e.g. cloud models of external providers), Traniva is not liable for their availability, functionality or changes insofar as the cause lies outside Traniva’s sphere of influence. In such cases Traniva will use reasonable discretion to seek technical alternatives or workarounds, without this giving rise to an entitlement to a particular solution.


16. Data protection

16.1 Traniva processes personal data in accordance with the applicable data protection laws (in particular the Swiss FADP and the EU GDPR) and the privacy policy published on taom.ai.

16.2 The roles (controller/processor) may vary depending on the usage constellation. The Data Processing Agreement (DPA) is decisive; it is agreed to with every order and takes precedence over these terms in the area of data processing.

16.3 Users/customers are themselves responsible for the lawfulness of the data they enter or import and for informing the data subjects.

16.4 Place of operation. The Platform is operated in Switzerland. Application, database, file storage, backups and e-mail dispatch are hosted by a Swiss provider whose data centre is located in Central Switzerland. Traniva may change the provider; the place of operation remains Switzerland or a state of the EEA, unless otherwise agreed with the customer.

16.5 Adequacy. The European Commission recognises an adequate level of data protection for Switzerland. A transfer of personal data from the EEA to Switzerland therefore requires no additional safeguards such as standard contractual clauses.

16.6 Access under foreign law. Traniva and the operating partner used are subject to Swiss law. A disclosure claim under foreign law, such as that provided for by the US CLOUD Act against companies based there, does not exist vis-à-vis Traniva. Official requests for information are only processed on the basis of the applicable Swiss law and after examination in the individual case.

16.7 AI processing. Clause 16.4 does not automatically apply to requests to language models: these are processed by the respective model provider, whose processing locations and terms are decisive. The provider used, the purpose, the types of data processed and the place of processing are shown in the publicly available list of sub-processors (clause 16.23); no separate request is necessary for this. From the Enterprise tier, provider, model, hosting, processing region and special data retention or data protection configurations can be contractually defined, including zero data retention, insofar as these are available and agreed for the technical configuration concerned, as well as operation in the customer’s environment; in this case the individually agreed arrangement takes precedence. Details are governed by clause 11 of the Data Processing Agreement.

16.8 Sub-processors. Traniva maintains and publishes a continuously updated list of the sub-processors used, with purpose, data types and place of processing. The current list is publicly available on taom.ai. The addition or replacement of a sub-processor is communicated in advance to customers with an existing data processing agreement in accordance with the conditions set out there.

16.9 Input in AI requests. The user or customer alone determines which content is included in an AI request. Traniva does not inspect this content and does not check it for personal data, secrets or third-party rights. The customer is responsible for ensuring that there is a legal basis for transmitting such content to the respective model provider, that the principle of data minimisation is observed and that data subjects are informed where necessary.

16.10 Standard configuration outside Enterprise. Below the Enterprise tier, model provider, model and processing region are specified by the standard configuration and cannot be agreed individually. For content that the customer discloses via a request, the terms of the respective provider also apply in this respect. Traniva recommends not to enter special categories of personal data, trade secrets or content subject to special supervision in requests outside the Enterprise tier. If such content is nevertheless entered, the customer bears the resulting data protection and regulatory consequences; Traniva’s liability is governed by clause 15 and remains unaffected for its own breaches of duty.

16.11 Processing at the model provider. What a language model derives from an input, how it processes it internally and whether it retains it lies with the respective model provider. Traniva has no influence on the internal functioning of the respective model and gives no assurance in this regard that goes beyond the published terms of the provider. Traniva undertakes which provider is used and which data is transmitted. Traniva’s data protection obligations regarding the selection, engagement and monitoring of sub-processors used remain unaffected.

16.12 Testing and verification. The functions for verification obligation, risks, controls, test cases and test results require a separate, paid add-on licence. It applies per person, has its own term and exists independently of the tier acquired; its lapse does not affect the tier.

16.13 Proposals are not approvals. Test cases, process tests, verification details, user manuals, model adjustments and documents generated by an agent or proposed from the model are proposals. They only take effect once a human approves them. Traniva does not warrant professional correctness, completeness or suitability for a particular purpose; the customer bears responsibility for selection, scope of verification and approval.

16.14 Regulated environments. TAOM is not a validated system within the meaning of regulatory requirements and does not replace a validation to be carried out by the customer. Whether a process step must be verified and whether a record is sufficient is decided by the customer in accordance with the requirements applicable to it.

16.15 Identifier per person. For traceability, each account receives a permanent, non-meaningful identifier. It is stored with the content generated by the account and serves to distinguish origin and approval – for instance for a four-eyes principle. The identifier contains neither name nor address. Its assignment to the account is stored exclusively within the Platform; it is resolved by Traniva in the course of operation or at the customer’s request. Anyone reading a file outside the Platform sees only the identifier in the origin seal and on the elements; the editing note of a model names the display name of the person who last saved it. Persons without their own account whom the customer records as process owners or in the project organisation also receive a non-meaningful identifier per customer. In the model files, only this identifier appears instead of their e-mail address; the address remains stored within the Platform and is only used where a function needs it, for instance for transfer to connected target systems or for notifications. Names appear in models only insofar as the presentation requires them, for instance as process owner or in the organisation chart. Details are governed by the privacy policy.

16.16 Immutable identifiers. Once assigned, identifiers for process steps, risks and test cases cannot be changed or removed. Without this fixing, an assignment between model, operation and record would not be reliable.

16.17 Operating log. Technical events are logged for operation and troubleshooting; persons appear in it only with their identifier, e-mail addresses are redacted. It is cleaned up automatically after a period set in the system; the default is no more than 30 days. The customer can adjust the period in its environment; if it is set to zero, deletion is the customer’s responsibility.

16.18 Retention after deletion of an account. If a user account is deleted, the identifiers stored with approved records are retained. Without them it would no longer be possible to determine who created a verification record and who approved it; the customer’s chain of evidence would be broken. Retention is based on the fulfilment of the customer’s legal retention and evidence obligations and on the legitimate interest in the evidential value of approvals given; it falls under the exception to the right to erasure under Art. 17(3)(b) and (e) GDPR. The name and address of the data subject are not retained, only the non-meaningful identifier. The customer determines the duration in accordance with the retention requirements applicable to it.

16.19 Processing for customers in the EEA. Where a customer uses TAOM within the scope of the GDPR and Traniva processes personal data exclusively on its behalf, the customer is the controller and Traniva the processor. The controller’s obligations, in particular informing data subjects and handling data subject requests, remain with the customer. Traniva supports the customer within the framework of the Data Processing Agreement (DPA).

16.20 Retention of enquiries. Enquiries via the contact form and the related correspondence are retained for twelve months after completion and then deleted. The basis is the legitimate interest in still knowing the history in the event of a follow-up question. Business letters within the meaning of commercial law provisions and documents relating to concluded contracts are not covered; the statutory retention periods apply to them.

16.21 Retention of user accounts. When the contract ends, the user account is deleted 90 days later. The period gives an opportunity to save content or to continue the contract without starting from scratch. The customer may request deletion earlier at any time. Documents subject to statutory retention periods (in particular invoices) and the identifiers on approved records under clause 16.18 remain unaffected. Workspaces are additionally subject to the tier-dependent retention under clause 4.

16.22 Usage and consumption data. To provide the service, TRANIVA AG processes information on when which access used which function: time and number of processing runs, the language model used, the volume of data processed in computing units (tokens), the duration and the result of the run. This information is assigned to a user account and is therefore personal. It is processed for the purposes set out in clause 10.3 – billing, capacity planning, detection of misuse and traceability towards the customer. The legal basis is the performance of the contract and the legitimate interest in secure and economical operation. No evaluation for assessing individual persons or their work performance takes place. The data is not sold to third parties and does not leave the infrastructure referred to in clause 16; it is deleted as soon as it is no longer required for the stated purposes, at the latest when the commercial retention periods expire. The customer can view its consumption in the customer account at any time.

16.23 Authoritative list of sub-processors. A complete and continuously maintained overview of all service providers used – with purpose, types of data processed, place of processing and legal basis – is published under Sub-processors. This list is authoritative; information in these terms and in other documents serves as explanation and is subordinate to it.

16.24 Customer number and customer identifier. Each customer receives a permanent customer number. It links the accounts of a company licence, remains in place for upgrades and new licence keys and appears on the invoice, licence confirmation and contract documents as well as in the customer account. It determines which workspaces, projects and organisational data are assigned to a customer; accounts of other customers have no access to them. If an account is removed from a licence or moves to another customer, its assignment lapses; the content created with it remains with the previous customer (clause 13.3). In files – for instance in the origin seal of an exported model – a non-meaningful customer identifier appears instead of the customer number; its assignment is stored exclusively within the Platform.

16.25 Transmission to channels and target systems of the customer. If the customer sets up a channel or a target system, Traniva transmits the information intended for this to the stored address on its instructions – for channels in particular the type of event, the company, number, name and path of the process, the activity concerned, the status, a note, depending on the customer’s setting the name or the person identifier of the triggering person or no information about them, as well as references to the process and the activity; in the detailed form that the customer chooses per channel, additionally information on the verification of the process step (verification obligation, risks, test coverage, open defects, required roles) and references to the connected target systems and test management, in each case according to the classification of the process step. The customer is responsible for the receiving system and the processing there; its provider is the customer’s contracting party and not a sub-processor of Traniva. Access keys to target systems are stored encrypted and are not displayed again after entry. Deliveries are logged with time and result.

16.26 Automated data protection. With the “Testing and verification” add-on licence, the customer can activate automated data protection. It can be activated by an administrator of the customer; in doing so, they confirm the supplementary terms “Automated data protection” in the version in force at the time. The confirmation is stored with a seal in the customer account and sent to the confirming person. The supplementary terms form part of these terms; a new version must be confirmed again. Switching off and on again does not require renewed confirmation.

16.26.1 The function redacts personal information – such as e-mail addresses, names, user names and identifiers, telephone numbers and company names – in the outputs chosen by the customer (test record, user manual, HTML export, display of images, e-mails, transfer to target systems such as Jira or Confluence) and can replace it with placeholders before transmission to language models. The data in the system remains unchanged.

16.26.2 Automatic recognition is an aid, not a guarantee; it does not find every instance, in particular not in third-party screenshots, with small fonts or unusual rendering.

16.26.3 Third-party screenshots and images – uploaded or captured from other applications – must be reviewed by a person of the customer’s organisation, marked where necessary and expressly confirmed as reviewed (human in the loop). Until then, TAOM only outputs them redacted or with the note “Review pending”. Review, approval and disclosure are the responsibility of the customer as controller within the meaning of data protection law (GDPR, revFADP); the customer is responsible for information that appears in outputs as a result of omitted or incomplete review.

16.26.4 Original images remain stored unchanged. They can only be viewed by the person who uploaded the image and by an administrator with the right “View originals”; every retrieval is logged.

16.26.5 The customer determines what is redacted in which output; every change is logged. Documents already generated are not changed silently – the re-check reports findings, regeneration takes place at the customer’s instigation. Addresses and names of employees of TRANIVA AG appear redacted in outputs to the customer irrespective of its setting.

16.27 Data protection content & logs. For each log type, the customer determines whether persons are recorded in the logs of its company in plain text, as placeholders or not at all, how long entries are retained and what is transferred to target systems and interfaces. Without a setting, the previous recording remains in place; proposals by TAOM are non-binding.

16.27.1 Placeholders are assigned when writing; the assignment is stored encrypted. The customer determines per person who may view logs and reveal persons.

16.27.2 Signatures and document seals remain in plain text as evidence.

16.27.3 TRANIVA processes the logs as a processor in accordance with the customer’s instructions. Information deleted after the period has expired cannot be restored.

16.28 Process Studio Viewer. The Viewer is read access for the customer’s employees to its process models, sequences and manuals and, depending on licence and role, to test management, risks, reporting, Process Mining and project times.

16.28.1 Licence and seats: The Viewer is licensed per named person and for the term purchased. A seat is occupied with the first sign-in. The customer releases it by blocking the account. Accounts without a sign-in for 365 days release their seat automatically.

16.28.2 Access: The customer determines the e-mail domains of its employees and only specifies its own domains. What a person sees depends on their role and approval level; the same protection rules apply as in the editor. The Viewer shows areas without a licence without content.

16.28.3 View only: Manuals and screenshots are displayed in the Viewer, not provided for download.

16.28.4 BPMN demo in the Viewer: The processes shown in the “BPMN-DEMO” area are sample models of TAOM and are marked with a red notice. They do not necessarily correspond to real business processes. All associated content – in particular key figures, risks, incidents, test cases, test runs, test records, Process Mining data and project times – is fictitious and serves exclusively to illustrate the functions of the TAOM Process Studio Viewer and the Process Studio Editor. It constitutes neither advice nor an assurance and does not relate to real companies or persons. TAOM does not accept reports on these models. The customer can hide the area in the customer account.

16.28.5 Public examples: TAOM may show sample models classified as “Public” without sign-in.

16.28.6 Responsibility: The customer is responsible for whom it gives access to and which content it makes visible.

16.28.7 Withdrawal: In the event of cancellation or refund, TAOM takes back the seats; occupied accounts remain until the customer blocks them.

16.28.8 Viewer on its own address: If TAOM operates the Viewer for the customer under its own address, sign-in continues to take place via the Platform; passwords are not transferred there. Model data is only cached there briefly.

16.29 Screenshots. Screenshots are only created when a person starts the capture themselves (in a test run or with the TAOM Process Recorder). The customer ensures that no personal or confidential data is captured that is not required for the purpose. The images are stored access-protected with the model, are not publicly accessible and can be transferred to the user manual. The customer’s administrator can switch off screenshots and their transfer to the manual for its company. Images from outdated test runs that have not been accepted are deleted after a period set in the system; images from accepted test runs remain with the record.

16.29.1 TAOM Screen Engine. Before saving, the capturing person can mark and mask areas. If automated data protection is activated (clause 16.26), recognised information is redacted in the chosen outputs; until the review of an image is completed, TAOM only outputs it redacted. Without activation, images appear as they were captured. The review by a person of the customer remains decisive (clauses 16.26.3 and 16.34).

16.30 Attachments, test records and manuals. Files in the formats and sizes stated in the service description can be stored at the process step and at the test run. They are only accessible to authorised users of the customer and are only delivered via the Platform. Test records and approved user manuals are stored unalterably with an identifier and checksum (SHA-256). Storage currently takes place at Traniva (clause 16.4); connection to a storage system of the customer (e.g. SharePoint, Confluence) is possible as an integration service under clause 22. Attachments are deleted with the workspace; clause 16.18 remains unaffected. If the customer connects its own storage or other external system, storage, access protection, retention and deletion of the content transferred there are the responsibility of the customer or the provider; Traniva AG is not responsible for this (clause 11.2).

16.31 Versions and backups. When saving, TAOM creates automatic backups of a model and keeps a limited number of them. Versions created or approved by the customer are retained until the model is deleted. Backups and versions do not replace the customer’s own filing to fulfil statutory or regulatory retention obligations; the retention of verification records remains the customer’s obligation.

16.32 Test cases from Excel. If the customer imports test cases from an Excel file, the file is stored as a reference with a checksum with its company. It is deleted together with the associated test cases or the workspace.

16.33 Design Protection. With TAOM Data Protection Design Protection, the customer defines protection patterns and blocked applications. Attempts to capture protected content or to work in blocked applications are recorded in the log of its company in accordance with the settings under clause 16.27. The customer informs its employees about this.

16.34 Approval of manuals, test records and exports. What is transferred to a user manual, a test record, a PDF or an export is reviewed and approved by a person of the customer (human in the loop). Screen Engine and automated data protection are aids. The approval is the customer’s decision; it ensures that approved documents do not contain impermissible personal or confidential information. Traniva AG assumes no responsibility for the content of approved documents (clauses 7.2, 16.13 and 15).


17. Confidentiality

17.1 Both parties treat information that is not publicly known and that becomes known to them in the course of using the Platform as confidential.

17.2 This obligation continues for at least five (5) years after the end of the contractual relationship, unless mandatory statutory retention or disclosure obligations stand in the way.

17.3 Classifications and approvals in the Platform support confidentiality. They do not replace confidentiality agreements between the customer and its guests or third parties.


18. Right of withdrawal for consumers (EU/EEA/UK)

18.1 Consumers resident in an EU/EEA state or in the United Kingdom generally have a statutory right of withdrawal for distance contracts for digital content/services.

18.2 The withdrawal period is 14 days from conclusion of the contract. To exercise the right of withdrawal, the consumer must inform Traniva of the withdrawal by means of a clear statement (e.g. letter, e-mail). The model withdrawal form is reproduced in clause 18.9; its use is optional.

18.3 The right of withdrawal expires prematurely if:

  • the contract is directed at the supply of digital content or services,
  • the provision has already begun,
  • and the consumer has previously expressly agreed that Traniva begins performing the contract before the withdrawal period expires and has confirmed their knowledge that they lose their right of withdrawal when performance begins.

18.4 For contracts with businesses or consumers outside the EU/EEA/UK area, the statutory consumer protection rights of the respective country apply; mandatory protective provisions remain unaffected.

18.5 If a consumer orders an upgrade and agrees to the immediate start of performance, clause 18.3 applies accordingly: the right of withdrawal expires prematurely when the new licence is activated.

18.6 Immediate provision, waiver of withdrawal and interim licence
When ordering, the consumer can separately confirm that Traniva should begin performance immediately and that they thereby lose their right of withdrawal (clause 18.3). This confirmation is voluntary; the order is also possible without it.


With confirmation: The licence tier purchased is provided in full immediately after receipt of payment. The right of withdrawal expires when performance begins; withdrawal is excluded thereafter.


Without confirmation: Immediately after receipt of payment, the consumer receives an interim licence of the tier Webuser Basic (“Process Studio Modeller”). It covers the use of the editor without AI functions, with the number of users ordered and the term ordered. The licence tier purchased is activated automatically after the 14-day withdrawal period has expired. The consumer can bring the activation forward at any time by expressly waiving their right of withdrawal in the customer account; with this waiver the right of withdrawal expires.
If the consumer withdraws within the period, they receive the amount paid back in full; no deduction or compensation for value is charged. Access is blocked upon withdrawal. Whether and when the confirmation was given is recorded with a time stamp and shown on the invoice and licence document. In the event of subsequent activation, the customer receives an updated licence document; the previous key loses its validity.

18.7 Binding nature, businesses, refunds
Businesses have no right of withdrawal. Orders by businesses are binding; cancellation or return is not provided for. The scope of the order must be checked carefully before submission.
Consumers who have waived their right of withdrawal under clause 18.6 are bound by the order.
Refunds are always made in Swiss francs and in the amount actually paid. Exchange rate changes between payment and refund as well as fees of the payment service provider or the customer’s bank are not compensated.


18.8 Withdrawal address, meeting the deadline and consequences of withdrawal
Withdrawal is possible without giving reasons and must be addressed to Traniva AG, Zimbergstrasse 11, 8335 Hittnau, Switzerland, e-mail info@traniva.com, telephone +41 79 730 06 60, or via the contact form on taom.ai. Timely dispatch of the declaration is sufficient to meet the deadline. If the right of withdrawal has not expired prematurely under clause 18.3 or 18.6, Traniva refunds the payments made without delay, at the latest within fourteen days of receipt of the declaration of withdrawal. The same means of payment as for the original payment is used for the refund, unless expressly agreed otherwise; the consumer is not charged any fees for this. The refund is made in accordance with clause 18.7 in Swiss francs in the amount actually paid.

18.9 Model withdrawal form
If you wish to withdraw from the contract, you can fill in this form and send it back to us; its use is optional.
To: Traniva AG, Zimbergstrasse 11, 8335 Hittnau, Switzerland, info@traniva.com
I/We hereby withdraw from the contract concluded by me/us for the purchase of the following licence/service:
Ordered on / order number:
Name and address of the consumer:
Date and signature (only if notified on paper):

19. Export control, sanctions law and international use

19.1 Users/customers are obliged to comply with all applicable export, sanctions and embargo regulations when using the Platform.

19.2 Traniva may restrict or refuse use from certain countries, regions or sectors if, in Traniva’s view, this is necessary to comply with sanctions, export or security regulations.


20. Changes to the GTC and to the services

20.1 Traniva is entitled to amend these GTC insofar as this is necessary to reflect legal changes, new technical circumstances or the further development of the offering and does not unreasonably disadvantage the user.

20.2 Traniva will provide information about material changes in a suitable form, usually by e-mail and in the customer account under “What’s new”. Each version bears a version number and a date from which it applies; earlier versions remain available there. Non-material changes may take effect after prior notification. Changes that materially alter existing rights or obligations of the customer or require consent under applicable law only take effect after the customer’s express consent.

20.3 If a change requires express consent, Traniva asks the customer for it by e-mail. Consent and its time are recorded on the account. Until consent is given, the version last confirmed by the customer applies to that customer. The wording applicable at the conclusion of the contract is additionally recorded as contract documentation and can be retrieved in the customer account.


21. Choice of law, place of jurisdiction and language version

21.1 Swiss law applies in principle, excluding the UN Convention on Contracts for the International Sale of Goods (CISG) and the conflict-of-law rules.

21.2 For legal disputes with businesses, the exclusive place of jurisdiction – where permissible – is the registered office of Traniva AG (Canton of Zurich, Switzerland).

21.3 Consumers are subject to the mandatory consumer protection and jurisdiction rules of their state of residence. These GTC may not restrict such mandatory rights.

21.4 These GTC are available in German. Translations are for information purposes only; in case of doubt, the German version prevails.


22. Consulting, training and integration services

22.1 Types of service
In addition to providing the TAOM.AI platform, Traniva offers, among other things, the following additional services:

  • consulting services (e.g. process and organisational consulting, digital twin design),
  • trainings and courses (online or on site),
  • integration and engineering services (e.g. connection to SAP, Jira, Confluence, Microsoft 365, automation platforms),
  • project-related project management and professional services.

The specific scope results from the service description in the offer, the order confirmation and/or a separate statement of work (SOW).

22.2 Remuneration and billing
Unless a fixed price is expressly agreed, consulting, training and integration services are billed on a time & material basis according to the daily/hourly rates in force at the time, plus expenses and incidental costs.

22.3 Use of AI in consulting and training services
In consulting, training and integration services, Traniva may use AI-supported tools and models (including but not limited to TAOM’s own agents and approved third-party models), e.g. to support analyses, documentation, modelling, test cases or textual proposals.
In this context too, all AI-supported results are proposals and replace neither the customer’s professional decisions nor legal or regulatory assessments. Responsibility for the use of such results in the customer’s organisation remains with the customer.

22.4 Customer’s obligations to cooperate
The customer undertakes to provide Traniva in good time and in full with all information, documents, access, test data, test environments and decision-makers required for the proper performance of the agreed services.
If the customer does not fulfil its obligations to cooperate or does so late, Traniva is entitled to adjust deadlines appropriately and to invoice the resulting additional effort separately.

22.5 Project documents and work results
Concepts, architectures, process models, templates, scripts and other work results created in the course of consulting, training and integration services may be used by the customer to the extent contractually agreed. Unless otherwise agreed, the customer receives a simple, non-transferable right to use these results for its own purposes.
Methods, generic know-how, frameworks, standard training content, the TAOM method, the TAOM framework and the underlying tools remain the intellectual property of Traniva or its licensors.

22.6 Course and training materials. In addition to clause 22.5, the following applies to materials that are not created as a work result for the customer but are provided by Traniva AG: materials provided in the course of trainings and courses – presentations, manuals, exercise files, model solutions and recordings – are provided exclusively electronically and are protected by copyright. The customer receives a simple, non-transferable right to use them within its own company and for the persons trained. Passing them on to third parties, publishing them and using them for own or third-party trainings is not permitted without prior written consent. Recordings of the training by participants are only permitted with prior consent. No physical materials are sent.

22.7 Language of the training materials. Trainings are held in German or English; the associated materials are provided in one of these two languages. There is no entitlement to further language versions. The customer may translate the materials into other languages for its own internal use with common translation tools; the resulting versions are machine translations and are not checked by Traniva AG. No warranty is given for their correctness and completeness; the original German or English version remains decisive. Passing translated versions on to third parties is governed by clause 22.6.

22.8 Training platform. Traniva provides trainings, e-learning and certifications via the training platform (training.taom.ai); sign-in takes place with the TAOM account. Participation may require an active licence or further prerequisites, which are stated for the respective course. Training materials are provided for viewing on the platform; downloading and passing them on are not permitted (cf. clause 22.6). Dates, certifications and prices result from the offer in the Marketplace.

22.8.1 Learning videos are only displayed on the training platform; downloading is not provided for. Trainings and videos on content that is not classified as public are only shown to authorised, signed-in participants. The Process Studio Viewer may refer to suitable public courses.

22.9 Trainings with third-party platforms. In trainings in which agents or connections are built on third-party platforms (e.g. n8n, make.com, Langdock, Microsoft Copilot, ChatGPT, Claude), licences and accounts for these platforms are only included where the offer expressly states this; otherwise the customer provides them. A TAOM licence is only included if the offer expressly states it. Interfaces to external systems are not included in any licence tier or any add-on licence; they are agreed as an integration service under clause 22.1. If services of a third-party platform are included (e.g. agents on an automation platform operated by Traniva AG), their consumption is recorded under clause 10.3; clauses 10.4 and 10.5 apply accordingly.

Licence Terms and General Terms and Conditions (GTC) for TAOM.AI


Related documents