Awazira.PDFLicense Terms

Awazira.PDF License Terms

Date
Binding
English text
Applicable terms
Worldwide, one version

All versions: LT-2026-11-12 · LT-2026-11-10

Source:

Only the English contract text is binding, so this page shows it in English in every language version.

Editions and prices

Contents

Version LT-2026-11-12, dated 12 November 2026. This version applies to Orders placed from that date. Earlier and later versions stay available under their version ID.

These terms consist of Parts 1 to 10. The Core Licence for the free features consists of Parts 1, 2, 5, 7, 9.1 and 10. One set of terms applies worldwide, including the USA and Canada. The English text is binding. Prices are not part of these terms; they follow from the Price List or the Order. Only the OEM fees in 4.5 are stated here, as they stand at the date of these terms; they change only under 8.5.

Part 1. Parties and definitions

#1.1 Parties. These terms are an agreement between torck GmbH, Friedhofstraße 11, 93142 Maxhütte-Haidhof, Germany, registered at the Amtsgericht Amberg under HRB 7272 ("torck"), and the person or organisation that uses the Software under them (the "Licensee"). Whoever accepts these terms for an organisation confirms that they may bind it.

#1.2 Licences for businesses. torck issues Licence Files only to businesses, public bodies, research institutions and open-source projects, not to consumers. Private individuals may use the Core under Part 2.

#1.3 Definitions.

  • Software: the Awazira.PDF engine as published by torck, in every package and form (NuGet, npm, native libraries, command line tool, container images), with its documentation and any update or patch. Wrappers and samples that torck publishes under an open-source licence are governed by that licence, not by these terms.
  • Core: the features of the Software that work without a Licence File. The Core includes signing a document at the PAdES levels B-B and B-T with a certificate and verifying signatures at every level.
  • Licensed Features: the features that need a Licence File: e-invoicing (creating, reading and validating ZUGFeRD, Factur-X, XRechnung and Peppol invoices), validation against PDF/A, signature workflows (signing at the PAdES levels B-LT and B-LTA, document time-stamps, certification, field locks, an order of signers, batch signing, and signing through an HSM, a cloud or a remote signing service, as described in the Documentation), redaction, and further features that the Documentation marks as licensed when they are first published. torck never moves a feature from the Core to the Licensed Features within a Release Line that is already published.
  • Licence File: the signed licence text that torck issues. It names the Licensee, the kind of licence, the Edition, the Licensed Features, the Updates Until date and, for OEM, the App-ID.
  • Edition: Essentials, Professional, Enterprise, OEM or OEM Start, as described in Parts 3 and 4.
  • Release Line: a minor version of the Software, such as 2.0. A Release Line starts on the day its x.y.0 release is first published. Each patch release keeps that day.
  • Updates Until: the date in a Licence File. The licence covers every Release Line that started before that date, without time limit.
  • Affiliate: an entity that controls, is controlled by or is under common control with the Licensee, where control means more than 50 % of the votes or the power to direct its management.
  • Own Use: use of the Software by the Licensee in its own applications and services, including services it provides in its own name to its own customers, such as invoices it issues or a customer portal it runs. Own Use does not include making Licensed Features available to third parties through a Product.
  • Product: software or a service that the Licensee distributes to third parties or makes available to them.
  • Hosted Service: a Product that the Licensee or a provider on its behalf operates and through which third parties use Licensed Features, for example a SaaS application, an API or a multi-tenant platform.
  • App-ID: the identifier of a Product family named in an OEM Licence File. One App-ID covers all customers, variants, rebrandings and releases of that family.
  • End Customer: each legal entity that uses Licensed Features through a Product of the Licensee. A tenant of a Hosted Service counts like an installation. Several installations, accounts or tenants of one legal entity count once, and a group of companies (entities that control, are controlled by or are under common control with each other, as for Affiliates) counts once as a whole. Test and demo tenants, and the Licensee’s own test, demo and training systems, do not count.
  • End Customer Declaration: the declaration of the number of End Customers under 4.6.
  • OEM Tier: the fee level of an OEM licence under 4.5, set by the number of End Customers.
  • Rule Package: an update of the validation artefacts of an e-invoicing standard within the same version of that standard, such as validation rules and code lists, as published by the issuer of the standard (for example KoSIT, OpenPeppol or FeRD). Its Rule Package Date is the day the issuer published it.
  • LTS Line: a Release Line that torck designates under 3.4 to receive Rule Packages for three years.
  • Order: a purchase through torck’s online shop, an order form signed by both sides or an offer by torck accepted by the Licensee. Orders through the online shop (Essentials, Professional and Enterprise) are self-service Orders, and the licences they create are self-service licences. OEM and OEM Start are available only by order form or offer.
  • Price List: torck’s published prices in force when an Order is placed or renewed, subject to the price lock in 3.5 and to 8.5.
  • Documentation: the documentation that torck publishes for the Software, including the licensing page.

Part 2. Free use

#2.1 Core Licence. torck grants everyone a free, non-exclusive, worldwide right to use the Core of every stable release for private, business and institutional purposes, on any number of devices, servers and containers. This use needs no Licence File, no account and no separate acceptance. Parts 1, 2, 5, 7, 9.1 and 10 of these terms apply to it as the Core Licence, which torck ships with every release. Using the Core means agreeing to them. The right cannot be transferred, except together with a Product under 2.2.

#2.2 Shipping the engine in a Product. Whoever distributes the engine as part of a Product, also with free features only, either accepts these terms once through torck’s web form or holds an OEM licence. torck confirms the acceptance by email with its date. Serving the unmodified browser module from a web application needs no acceptance, if the application makes the Core Licence and the third-party notices readily available. In every case the distributor:

  1. keeps all copyright, licence and third-party notices of the Software;
  2. distributes the engine only as part of its Product, not on its own and not as a development library for others;
  3. binds its own customers to terms that forbid reverse engineering and separate redistribution of the engine at least as far as Part 5 does;
  4. does not ship any Licence File other than an OEM Licence File (Part 4).

#2.3 Free licences with a Licence File. torck issues these licences on request. Each enables the Licensed Features named in its Licence File.

Kind For whom Conditions Term
Small Company a company whose group (with all Affiliates) had a revenue under EUR 1,000,000 in its last completed financial year written declaration; Own Use only; not for public bodies (except education and research), not for listed companies, not for Products or Hosted Services one year; renewal with a new declaration; 90 days to buy a paid licence after the threshold is passed
Research universities and research institutions non-commercial research and teaching only; productive administration needs a paid licence one year; renewal with a new declaration
Open Source a named open-source project with a public repository under a licence approved by the Open Source Initiative for the project’s builds, tests and CI; the Licence File stays out of the public repository and out of distributed applications; a commercially hosted service of the project for third parties needs OEM one year; free renewal while the project is maintained
Developer a development team development, tests and CI only; no production use; never shipped with an application one year; renewal on request
Trial anyone who wants to test the Licensed Features evaluation only; no production use 30 days from its start date, once extendable by 30 days on request; 60 days for a Licensee that declares it is switching from ZUGFeRD-csharp and names the package it uses

#2.4 Declarations. Declarations for a free licence must be true and complete. torck may ask for reasonable evidence. If a declaration was false, torck may end the free licence with immediate effect and claim the fee that the matching paid Edition would have cost for the period of use.

#2.5 Prereleases. Alpha, beta and release-candidate builds are for testing only. They are provided without any commitment to support, updates or fitness for production.

#2.6 No fees, limited duties. Free use carries no right to support or availability. Liability for free use follows 7.4.

Part 3. Paid editions for Own Use

#3.1 Grant. After an Order and payment, torck grants the Licensee a non-exclusive, worldwide right to use the Licensed Features of its Edition for Own Use. The right covers every Release Line that started before the Updates Until date. There is no limit on developers, projects, servers, containers or build agents. The licence unit is one legal entity. Enterprise also covers the Licensee’s Affiliates.

#3.2 Editions.

Edition Licensed Features Who may use it
Essentials e-invoicing, including the validation against PDF/A-3 of a received ZUGFeRD, Factur-X or XRechnung file with an embedded CII or UBL invoice; other validation against PDF/A is not included the Licensee
Professional e-invoicing, validation against PDF/A, signature workflows, redaction; OCR and conversion of e-mails (EML, MSG) to PDF once published the Licensee
Enterprise everything in Professional; HSM and remote signing adapters and the designer for internal use once published; priority support the Licensee and its Affiliates

E-invoicing in every Edition includes the PDF/A-3 viewing copy of a received invoice with the original XML and the validation report, once published; the HTML view and the plain PDF view of a received invoice are part of the Core. Signature workflows include signing at the PAdES levels B-LT and B-LTA. Add-ons such as the accessibility retrofit are licensed by a separate Order once published. The Documentation states which Edition a new Licensed Feature belongs to when it is first published.

#3.3 What the fee buys. The fee buys the right under 3.1 and new Release Lines until the Updates Until date, normally one year after the Order (two or three years for multi-year Orders). The right to use the covered Release Lines does not end when the Updates Until date passes or the licence is not renewed. The Software never stops working on a date. Only a trial licence ends on a date. After it, the Licensed Features stop and the Core keeps working.

#3.4 Security updates and Rule Packages.

  1. Security updates. torck handles vulnerabilities in the Software as Regulation (EU) 2024/2847 (Cyber Resilience Act) requires of manufacturers, in particular Article 13(8) and Annex I, Part II: without delay, by security updates, free of charge. torck provides security updates for every Release Line for five years from the day it started, as patch releases of that line. They also reach Licensees whose Updates Until date has passed. For a vulnerability with a CVSS base score of 7.0 or higher, torck’s target is a security update at the latest 30 days after it has confirmed the reported vulnerability. A security update for any other vulnerability follows with the next regular release of each affected Release Line. These times put the duties of the Cyber Resilience Act into practice. They are targets, not a guarantee (6.1).
  2. Rule Packages. torck ships Rule Packages as patch releases of the two newest Release Lines. In addition, torck designates one Release Line per calendar year as an LTS Line and ships Rule Packages into it for three years from the day it started. torck commits to the LTS Line towards Enterprise and OEM Licensees.
  3. Coverage. A licence covers a Rule Package whose Rule Package Date is before its Updates Until date. A Rule Package with a later Rule Package Date is not covered, even if it ships in a covered Release Line. A late delivery by torck does not change the Rule Package Date.
  4. New versions of a standard. A new version of an e-invoicing standard, such as XRechnung 4.0, ships in a new Release Line, not in a patch.
  5. Target times. torck publishes these target times on its page "Rule updates and deadlines":
    • a Rule Package for a mandatory date: at the latest four weeks before that date, if the issuer published the final artefacts at least ten weeks before it; otherwise at the latest six weeks after their publication;
    • a correction that applies from its publication: at the latest 30 days after its publication;
    • a fix for a wrong rejection of valid invoices: at the latest ten business days after torck confirmed the error.

    For Essentials, Professional and OEM Start, and for Enterprise and OEM until 30 June 2027, these are targets, not commitments.

  6. Commitment for Enterprise and OEM. From 1 July 2027 the target times of 5 are binding for Enterprise and OEM. For each target time that torck misses, the Updates Until date of the affected licence moves three months later. If torck misses target times twice within 12 months, the Licensee may terminate the licence with immediate effect and receives a pro-rata refund of the fees paid for the remaining term.

#3.5 Renewal and price lock. Self-service licences, Enterprise from the online shop included, renew automatically for the term of the current period (one, two or three years, as ordered) unless the Licensee cancels before the renewal date. The Licensee cancels through the payment partner’s account management linked in the purchase confirmation. torck sends a reminder at least 30 days before. Enterprise and OEM by order form or offer renew under 8.5. A renewal extends the Updates Until date from the previous date. A Licensee who renews without a gap of more than 30 days keeps the price of the year of its first purchase. That price is the Price List price of that year. One-time discounts, such as a discount on the first year, do not lower it. After a longer gap the current Price List applies, without back payment.

#3.6 Upgrades. The Licensee may move from Essentials to Professional or Enterprise, and from Professional to Enterprise, at any time. torck credits the unused part of the current period. The Updates Until date stays the same.

#3.7 Support. Every paid Edition includes support by email to support.awazira.pdf@torck.io with a target first response within three business days, until the Updates Until date. Enterprise and OEM include priority support with a target first response on the next business day. Support Priority and Support Premium can be added by Order. Response times are targets, not guarantees. Support covers the use of the Software as documented, not the Licensee’s own code.

#3.8 Delivery. torck delivers the Licence File by email after payment. The Licensee keeps it confidential and stores it in a secret store or protected file, not in a public repository.

Part 4. OEM and hosted services

#4.1 When OEM is needed. A Licensee that makes Licensed Features available to third parties through a Product needs OEM or OEM Start. This covers shipping a Licence File with an installed Product and running a Hosted Service. OEM Start is for vendors whose group revenue was under EUR 1,000,000 in the last completed financial year. A vendor that passes the threshold moves to OEM at the next renewal. A Small Company licence never covers a Product.

#4.2 Grant. torck grants the Licensee a non-exclusive, worldwide right, for as long as the OEM agreement runs, to:

  1. integrate the Software into the Product family named by the App-ID;
  2. distribute the engine and the OEM Licence File with the Product, or operate the Product as a Hosted Service;
  3. let End Customers use the Licensed Features only through the Product.

OEM includes the Licensed Features of Enterprise. OEM Start includes the same Licensed Features as OEM, the HSM and remote signing adapters included, without Affiliates and without priority support.

#4.3 App-ID. torck issues one App-ID per Product family. Each further App-ID of the same Licensee costs the fee in 4.5. Locked features work only in a process that states the App-ID of the Licence File. On request torck issues a separate Licence File per distribution channel, so each can be withdrawn on its own.

#4.4 End Customers. The Licensee binds its End Customers to terms that forbid using the engine or the Licence File outside the Product, extracting them, and reverse engineering, at least as far as Part 5 does. The Licensee gives first-level support to its End Customers. torck supports the Licensee, not the End Customers. End Customers have no claims against torck under these terms. The Licensee holds torck harmless from claims of End Customers that arise from the Product or from the Licensee’s terms with them, unless torck is liable for the cause under Parts 6 and 7.

#4.5 Fees. The Licensee pays per contract year the fee of its OEM Tier and EUR 1,990 for each App-ID beyond the first. The OEM Tier follows from the number of End Customers of all App-IDs of the Licensee together, as stated in the latest End Customer Declaration. There is no fee and no report per End Customer.

OEM Tier End Customers EUR per contract year
OEM 25 up to 25 3,990
OEM 50 26 to 50 4,890
OEM 100 51 to 100 5,390
OEM 200 101 to 200 6,090
OEM 400 201 to 400 7,590
OEM 800 401 to 800 9,690
OEM 1,600 801 to 1,600 13,490
OEM 3,200 1,601 to 3,200 17,890
OEM Unlimited more than 3,200 24,990

OEM Start (4.1) costs EUR 1,290 per contract year for up to 100 End Customers. The tolerance of 4.6 (3) applies to this limit too, so the higher fee applies only if the declared number exceeds 110. Then OEM Start costs the fee of the matching OEM Tier less EUR 3,500. All fees are net amounts.

#4.6 End Customer Declaration.

  1. When. The Licensee declares the number of its End Customers when the OEM agreement is concluded and at least 30 days before each renewal. This also applies to OEM Unlimited.
  2. Content. The declaration states one number, rounded to the nearest ten, without names or tenant identifiers. A person authorised to represent the Licensee signs it.
  3. Tolerance. The OEM Tier is the lowest tier whose upper limit, increased by 10 %, the declared number does not exceed. A higher OEM Tier therefore applies only if the number exceeds the upper limit of the current tier by more than 10 %. If the number fits a lower OEM Tier, the lower tier applies from the renewal. The same tolerance applies to the limit of 100 End Customers of OEM Start in 4.5.
  4. No adjustment within the year. The OEM Tier is set at conclusion and at each renewal. A change in the number of End Customers during a contract year does not change the fee for that year. torck neither invoices nor credits a difference within the year.
  5. Records. The Licensee keeps the records on which a declaration is based for two years.
  6. False declaration. If a declaration was false through the Licensee’s fault, the Licensee pays the difference between the fee paid and the fee of the correct OEM Tier for the current contract year and at most the previous one.

#4.7 Audit. torck may have the number of End Customers checked only if there are concrete indications that an End Customer Declaration is false, or if the Licensee did not submit one. A check takes place at most once in 36 months, with 30 days‘ notice and during business hours. An auditor bound by professional secrecy, such as a certified public accountant or a tax adviser, carries it out. The auditor tells torck only the number of End Customers, no names. torck bears the cost of the check, unless it shows that the declared number was more than 10 % below the actual number. Then the Licensee bears the cost and pays under 4.6 (6).

#4.8 End Customers after the end. If the OEM agreement ends for a reason other than the Licensee’s material breach, End Customers keep the right to use the Product releases delivered to them before the end, within the Release Lines covered by the OEM Licence File.

#4.9 Security updates for End Customers. The Licensee names a security contact to torck and passes security updates of the Software on to its End Customers without undue delay.

#4.10 Hosted Services. A Hosted Service must add substantial functionality of its own. A service whose main purpose is to offer the functions of the Software to developers, such as a general PDF API or SDK service, needs a separate written agreement with torck.

#4.11 Source code escrow.

  1. Who is covered. The OEM Tiers from OEM 1,600 include escrow under this clause. Enterprise Licensees and OEM Licensees up to OEM 800 can add it by a separate Order. Essentials, Professional and OEM Start cannot.
  2. Deposit. torck deposits the source code of the Software for each Release Line with an escrow agent under a collective escrow agreement, which covered Licensees join as beneficiaries. torck names the escrow agent once the collective agreement is concluded.
  3. Release events. The escrow agent releases the source code to a covered Licensee if:
    1. insolvency proceedings are opened over torck’s assets, or an application to open them is rejected for lack of assets;
    2. torck is liquidated or deleted from the commercial register;
    3. torck discontinues Awazira.PDF without a successor;
    4. torck transfers its rights to the Software and the acquirer does not take over torck’s obligations under these terms within 90 days;
    5. torck has stopped maintaining the Software, which means either of the following, in each case despite a reminder in text form and a further period of 30 days:
      • for a vulnerability with a CVSS base score of 9.0 or higher, or one that torck must report as actively exploited under Article 14 of the Cyber Resilience Act, in a Release Line within its security support under 3.4 (1), torck has delivered neither a security update nor a documented workaround within 90 days after it confirmed the vulnerability;
      • torck has not delivered a Rule Package needed for a mandatory date within 90 days after that date.

      A delay caused by a third-party component for which no fix is available does not count.

    The escrow agreement gives torck an objection procedure before the escrow agent. A change of control of torck alone is not a release event.

  4. Use after a release. torck grants each covered Licensee, when its escrow cover starts, the right to use released source code only to maintain and build the Software for its own App-IDs, or for Enterprise for its Own Use. This right is subject to the condition precedent of a release event.

Part 5. Licence Files, restrictions and withdrawal

#5.1 Licence Files. A Licence File is for the Licensee named in it. The Licensee does not change, forge or pass it on, except an OEM Licence File within its Product under Part 4. It does not use a Licence File issued to someone else.

#5.2 Restrictions. Unless mandatory law allows it, the Licensee does not:

  1. decompile, disassemble or otherwise reverse engineer the Software, except as permitted by Sections 69d(3) and 69e of the German Copyright Act or comparable mandatory law;
  2. remove or bypass the licence checks or the App-ID check;
  3. remove copyright, licence or third-party notices;
  4. rent, sublicense or distribute the Software, except under 2.2 or Part 4;
  5. use the Software to build a product that offers developers substantially the same functions as the Software.

#5.3 Third-party components. The Software contains third-party components under their own licences. They are listed in the notices shipped with each release. For those components, their licences apply in addition to these terms.

#5.4 Offline checks, no telemetry. The Software checks Licence Files offline. It does not contact torck and sends no usage data. Licensed Features never run in a web browser, under any licence.

#5.5 Withdrawal of Licence Files. torck may withdraw a Licence File if:

  1. the Licence File was published or passed to third parties outside Part 4;
  2. torck issued it in error;
  3. the Licensee commits a material breach and does not cure it within 30 days of written notice;
  4. fees are unpaid 30 days after a written reminder.

A withdrawal takes effect through the withdrawal list in releases published after it and through replacement Licence Files. Where the Licensee is not at fault (cases 1 by a third party, and 2), torck replaces the Licence File free of charge. In case 3 torck withdraws only after terminating under 8.6. If a renewal fee stays unpaid, torck does not withdraw the Licence File but replaces it with one that keeps the previous Updates Until date.

#5.6 Confirmation of use. Once a year torck may ask a Licensee of Part 3 to confirm in writing that its use stays within its Edition. Checks of End Customer Declarations follow 4.7.

#5.7 Licensed, not sold. The Software is licensed, not sold. torck and its licensors keep all rights not expressly granted in these terms.

Part 6. Quality, defects and third-party rights

#6.1 Agreed quality. The Software has the functions described in the Documentation of the release in question. Descriptions in the Documentation, on the website or in samples describe the Software. They are not guarantees. torck gives a guarantee only if it calls it a guarantee in a signed document.

#6.2 Defects in paid licences. The Licensee reports a defect with a description that allows torck to reproduce it. torck remedies it within a reasonable time, at its choice by a patch release, a workaround or a new Release Line. If two attempts fail, the Licensee may reduce the fee for the affected period or end the affected licence. Damages follow Part 7. Claims for defects become time-barred one year after delivery of the release, except in the cases of 7.1. Strict liability for defects that already existed when the contract was concluded is excluded.

#6.3 Third-party rights: remedy for all paid licences. If a third party claims that the Software as delivered by torck infringes its rights, torck at its own cost and choice will:

  1. obtain the right for the Licensee to keep using the Software;
  2. change or replace the affected part so that it no longer infringes, without a material loss of function; or
  3. if neither is possible at reasonable cost, end the licence for the affected part and refund the fees paid for the affected licence, less one thirty-sixth for each full month since the affected release was delivered.

#6.4 Defence and indemnity: Enterprise and OEM only. torck defends an Enterprise or OEM Licensee against claims by third parties that the Software as delivered by torck infringes a copyright, a trademark or a patent granted outside the United States of America. torck pays the damages and costs finally awarded against the Licensee, or a settlement torck has approved in writing.

  1. Nature. This clause sets out torck’s liability for defects in title and breach of duty under this agreement. It is not a guarantee and not an independent promise to indemnify.
  2. Conditions. The Licensee informs torck in writing within ten business days after it learns of the claim, does not acknowledge the claim, leaves the defence and any settlement to torck and its insurer, and gives the information and help needed, at torck’s cost.
  3. Exclusions. No defence or payment is owed for: patents granted in the USA or patent claims brought before US courts; changes not made by torck; combinations with software, data or hardware not supplied by torck where the claim would not exist without the combination; use against the Documentation, or after torck offered a non-infringing update; content, fonts and templates supplied by the Licensee or its End Customers; third-party components under open-source licences; contractual penalties and punitive or exemplary damages.
  4. Cap. torck’s payments under 6.4 are limited per contract year to the higher of three times the fees paid by the Licensee in the 12 months before the claim and EUR 50,000. The limits of Part 7 do not reduce this amount further, and the cases of 7.1 remain unlimited.

#6.5 Self-service, free use and US patents. Essentials, Professional and OEM Start receive the remedy of 6.3, not the defence and indemnity of 6.4. Free use (Part 2) receives neither. No Edition receives a defence or indemnity for patents granted in the USA or for patent claims brought before US courts.

#6.6 Damages. 6.3 to 6.5 state torck’s remedies for infringement of third-party rights. Claims for damages follow Part 7.

Part 7. Liability

#7.1 Unlimited liability. torck is liable without limit for intent and gross negligence, for injury to life, body or health, under the German Product Liability Act, for defects it fraudulently concealed and under a guarantee it gave in writing.

#7.2 Slight negligence. For slight negligence torck is liable only if it breaches an essential obligation, that is an obligation whose fulfilment makes the proper performance of the contract possible and on which the Licensee may regularly rely. This liability is limited to the damage typical for the contract and foreseeable when it was concluded.

#7.3 Amount for paid licences. In the cases of 7.2 the parties assume that the typical foreseeable damage per contract year does not exceed the higher of the fees paid by the Licensee in the 12 months before the damaging event and EUR 25,000. torck’s liability under 7.2 is limited to that amount.

#7.4 Free use. For free use under Part 2, torck is liable only in the cases of 7.1.

#7.5 Loss of data. Except in the cases of 7.1, torck is liable for loss of data only for the effort needed to restore the data from backups that the Licensee should have made according to good practice.

#7.6 Persons. The limits in this Part also apply to torck’s employees, representatives and agents. They do not change the burden of proof.

#7.7 Duties of the Licensee. The Licensee tests the Software in its own setting before productive use. It remains responsible for the content of its documents and for meeting the legal requirements that apply to them, in particular for e-invoices, archiving and signatures. torck provides validators for this purpose, but their results do not replace the Licensee’s own checks.

#7.8 Implied warranties. Where the law of another country applies despite Part 10: TO THE EXTENT PERMITTED BY LAW, ALL IMPLIED WARRANTIES AND CONDITIONS, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, ARE EXCLUDED. THE REMEDIES IN PARTS 6 AND 7 ARE THE LICENSEE’S ONLY REMEDIES. NOTHING IN THIS SECTION LIMITS 7.1.

Part 8. Contract, fees and term

#8.1 Conclusion. In the online shop the contract is concluded when the Licensee completes the checkout and accepts these terms. An order form is concluded when both sides have signed it, an offer when the Licensee accepts it in text form.

#8.2 Payment partner. Self-service purchases run through torck’s payment partner named at checkout (at present Stripe). Where the payment partner acts as merchant of record, it sells the licence to the Licensee, collects the fee and issues the invoice. The right to use the Software is still granted by torck under these terms, and support is still provided by torck.

#8.3 Fees. Fees follow the Price List or the Order. They are net amounts and due in advance. Invoices from torck are payable within 14 days. The payment partner charges self-service fees at checkout and at each renewal.

#8.4 Taxes. The Licensee pays value added tax, sales tax and similar taxes on top. Where the payment partner is merchant of record, it calculates and collects them. If the Licensee must withhold tax from a payment to torck, it pays the amount needed for torck to receive the full fee, unless a tax treaty reduces the withholding and the Licensee provides the documents for it.

#8.5 Term, notice and price changes. Self-service licences run for the term ordered and renew under 3.5; this clause does not apply to them. Enterprise and OEM by order form or offer run for the term in the Order, at least one year, and renew by one year at a time. For them the following applies:

  1. Notice by the Licensee. The Licensee may give notice at least three months before the end of a contract year.
  2. Notice by torck. torck may give ordinary notice at the earliest to the end of the third contract year, and only with at least 12 months‘ notice to the end of a contract year.
  3. Price changes. The fees of Enterprise and OEM stay fixed for the first three contract years. After that torck may change them for a renewal by at most the change of the German consumer price index (VPI, published by Destatis) over the last 12 months for which it is published, and by at most 5 % per contract year. If the index falls, torck lowers the fees by the same rule. torck announces a change in text form at least four months before the renewal. A move to another OEM Tier under 4.6 is not a price change.
  4. Termination after a price increase. If torck raises the fees, the Licensee may terminate the agreement to the date on which the increase takes effect.

#8.6 Termination for good cause. Either side may terminate for good cause. Good cause exists in particular if the other side commits a material breach and does not cure it within 30 days after written notice.

#8.7 After the end. When a licence ends, the rights under 3.3 to the covered Release Lines continue, unless torck terminated for good cause because of the Licensee’s breach. In that case all rights end and the Licensee deletes its Licence Files. When an OEM agreement ends for another reason:

  1. the Licensee may go on installing and patching the Release Lines delivered before the end for the End Customers it had at the end, without time limit, and may go on operating a Hosted Service for them;
  2. for 12 months after the end, the Licensee may also supply the Product to new End Customers;
  3. after the end, Rule Packages are covered only through Continued Maintenance, which the Licensee can order for 50 % of the fee of its last OEM Tier per year;
  4. if torck ended the agreement by ordinary notice, the period in 2 is 24 months, and Rule Packages with a Rule Package Date in that period are covered without Continued Maintenance.

End Customers keep their rights under 4.8. The Licensee pays the fees up to the end.

Part 9. Export control, data protection and confidentiality

#9.1 Export control and sanctions. The Software contains cryptographic functions for encryption and digital signatures. The Licensee complies with the export control and sanctions laws of the European Union and Germany and, where they apply, of the USA when it exports or passes on the Software or a Product. It does not supply the Software to persons or countries under sanctions. torck may refuse or cancel an Order where sanctions law requires it.

#9.2 Data protection. The Software runs on the Licensee’s systems and sends no data to torck. torck does not process the content of the Licensee’s documents. For purchase and account data torck’s privacy notice applies. In support cases the Licensee sends only the data needed, if possible anonymised samples. Where torck must process personal data on the Licensee’s behalf, the parties first conclude a data processing agreement.

#9.3 Confidentiality. Each side keeps confidential the non-public information it receives from the other, in particular Licence Files, non-public prices and the terms of Orders. This duty lasts for three years after the contract ends, for Licence Files without time limit. It does not apply to information that is public without breach, was already known, or must be disclosed by law.

#9.4 Reference. torck names the Licensee as a customer, with its name or logo, only if the Licensee has agreed in text form. The Licensee may withdraw its agreement at any time with effect for the future.

#9.5 Feedback. torck may use suggestions and feedback on the Software freely and without payment.

#9.6 US Government end users. The Software and its Documentation are commercial computer software and commercial computer software documentation (FAR 12.212, DFARS 227.7202). US Government end users receive only the rights granted in these terms.

Part 10. Law, disputes and final provisions

#10.1 Governing law. German law applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG) and the conflict-of-laws rules.

#10.2 Courts for Europe. For Licensees with their seat in the European Union, the European Economic Area, Switzerland or the United Kingdom, the courts competent for torck’s registered office have exclusive jurisdiction. torck may also sue at the Licensee’s seat.

#10.3 Arbitration for all other Licensees. For Licensees with their seat elsewhere, including the USA and Canada, all disputes are finally decided under the Arbitration Rules of the German Arbitration Institute (DIS), without recourse to the ordinary courts. The tribunal has one arbitrator. The seat is Munich, the language English. Interim relief from state courts remains available.

#10.4 Language. The English text is binding. Translations are for information. For Licensees in Québec torck provides a French version before the contract is concluded.

#10.5 Changes to these terms. For Enterprise and OEM, these terms change only by agreement of both sides in text form. For self-service licences, torck may change these terms for renewals only where a change in law, case law, technology or the Software requires it, or to add new features, and only if the change does not shift the balance of the contract to the Licensee’s disadvantage. torck announces changes in text form at least 60 days before the renewal and points out the right to object. A Licensee that objects does not renew; until the renewal date the previous terms apply. Rights to Release Lines already covered stay unaffected.

#10.6 Assignment. The Licensee may assign the contract to the acquirer of its business without torck’s consent, unless the acquirer is a competitor of Awazira.PDF. Any other assignment by the Licensee needs torck’s consent, which torck does not refuse without good reason. torck may assign the contract to an Affiliate or to the acquirer of the Awazira.PDF business.

#10.7 Order of precedence. The contract consists of the Order, these terms and the Price List, in this order. Terms of the Licensee do not apply, even if torck does not object to them.

#10.8 Form. Notices and declarations may be given in text form, such as email. Where these terms say "in writing", text form suffices, except where they require a signed document.

#10.9 Severability. If a provision is invalid, the rest stays valid. The statutory rules replace the invalid provision.

#10.10 Force majeure. Neither side is liable for delays or failures caused by events beyond its reasonable control, such as natural disasters, war, epidemics, strikes not aimed at it alone or failures of public networks. The affected side informs the other without undue delay.

Questions about the license terms?

Write to us through the contact form. We aim to reply within one business day.

Ask a questionBack to top