Legal
DM Triage Additional Terms
Last updated: 16 November 2026
Version 1.0 · Effective date: 2026-11-17
DM Triage is offered by productivity-boost.com Betriebs UG (haftungsbeschränkt) & Co. KG, Reichenberger Str. 2, 94036 Passau, Germany, Amtsgericht Passau HRA 12725 ("we"). These Additional Terms supplement our Terms of Service ("Terms"). The German version prevails if the language versions differ.
TT1. Scope and precedence
TT1.1 These Additional Terms apply to DM Triage for the Customer's Zendesk account, including the report, shadow mode, backfill dry run and paid classification. They do not change contracts for other Decision Models services.
TT1.2 The contract comprises these Additional Terms, the Terms, the Acceptable Use Policy and the Data Processing Agreement ("DPA") with Annex T. Under Terms 15.5, individual written agreements rank first, the DPA including Annex T takes precedence for personal-data processing, then these Additional Terms, then the Terms, the Acceptable Use Policy and the general price list.
TT1.3 For DM Triage, TT3 replaces Terms section 5 (API prepaid credit and token prices). API credit cannot pay for DM Triage and its fees create no API credit. Terms 3.3 (tier selection) and 4.2 (customer API keys) do not apply: DM Triage uses only our EU tier and connects to Zendesk by OAuth. TT2 replaces the general account/contract acceptance rules for this product; TT9 governs product cancellation and disconnect.
TT2. Business customers and contract conclusion
TT2.1 DM Triage is offered only to businesses acting in the exercise of their trade, business or profession (§ 14 BGB), legal entities under public law and special funds under public law. It is not offered to consumers (§ 13 BGB); Terms 1.1 is restricted accordingly. You confirm that you may bind the business you represent.
TT2.2 Before Zendesk is connected or any of your ticket data are retrieved, you must separately confirm your business status by an unticked checkbox and, through a second unticked checkbox, click-accept these Additional Terms, the Terms and the DPA with Annex T. Only these four contract documents require acceptance. The Privacy Policy, privacy addendum and sub-processor list are shown for information and their versions are recorded, without acceptance; sub-processor changes follow DPA 6.2. The documents are linked next to the checkboxes. Both confirmations are checked server-side. We record the declaration, company name, accepting administrator/email, bound Zendesk account, document versions and SHA-256 hashes, UTC time and IP hash. At the OAuth callback, an account mismatch is rejected. For changes to the four contract documents we notify administrators by email at the start of the notice period and in the app, describing the change and acceptance deadline. Existing accepted connections continue under the previously accepted contract for six weeks (42 days) after notice, consistent with Terms 14.1. New connections require the current contract. After the deadline processing pauses until renewed acceptance, with no excess charges accruing while paused. You may object and cancel with effect from the pause; we refund the pro-rata prepaid base fee for the paused period, including any prepaid unused period after cancellation. The Plan page provides this cancellation and refund. A pause alone does not cancel a subscription. The free-service contract is concluded on this acceptance. This product acceptance replaces DPA acceptance in the API dashboard (Terms 6.2); accepting the API documents elsewhere alone does not activate DM Triage.
TT2.3 Paid orders use Stripe Checkout. Before ordering, you see the recurring price, included volume, excess-ticket price, trial end, first charge and cancellation terms. Clicking the clearly labelled order button submits a binding order; we accept it by confirming and activating the subscription after Stripe confirms successful Checkout completion. Where a trial is ordered, payment is first due at its disclosed end, unless you cancel before then. At paid checkout you repeat the business-status declaration and provide the required company name; VAT ID is optional. We provide the contract documents and confirmation in a durable form.
TT2.4 If a buyer is a consumer despite the declaration, mandatory consumer rights remain unaffected. On request, we end the contract and refund fees paid. A declaration alone does not remove statutory consumer protections.
TT3. Trial, prices, metering and limits
TT3.1 The paid plan costs EUR 49 per month per Zendesk account, includes 10,000 classified tickets per billing month, and costs EUR 0.003 for each additional classified ticket. Prices are net, plus applicable VAT, shown before ordering. Billing months follow the Stripe subscription period. Unused included tickets do not carry over. The base fee is charged in advance; excess use is billed after the applicable billing month.
TT3.2 A classified ticket is one successfully completed classification operation for a ticket, including all fields classified together in that operation. A technical retry of the same operation is not charged again. A separately requested classification of the same ticket after a change or a new run is a new operation. Failed operations without a classification result and undo operations are not billable classifications. The app shows counted usage, remaining included volume and accrued excess charges. Free operations under TT3.4 do not generate excess fees.
TT3.3 A 14-day trial is available once per Zendesk account. The trial includes the full Pro volume of 10,000 classified tickets. Its start, end and included volume are displayed before activation. The free tier alone does not create a paid subscription. A trial converts into the paid plan only where you expressly ordered that subscription under TT2.3; otherwise it ends without a charge. No excess fee is incurred during a free trial without an express paid order covering it.
TT3.4 The free tier provides a report covering up to 1,000 past tickets per 24 hours, shadow mode for 14 days or 2,000 shadow classifications, whichever is reached first, and a backfill dry run of up to 500 tickets. Shadow mode and a dry run do not write classification changes to Zendesk. At the relevant limit, the free operation stops; it does not silently purchase a plan or extra volume. Paid live classification, including paid backfills, requires the paid order and write enablement. The report's scope is shown before it starts.
TT3.5 Above 10,000 classifications, excess charges continue under the paid plan at the stated rate. There is no unlimited-use entitlement. Any customer-selected volume or spend cap is shown in the app and must be applied before new work exceeds it; reaching a cap pauses new classification until the Customer raises it or the allowance renews. No cap is represented as active unless the app confirms it. Pausing processing does not itself cancel the subscription.
TT3.6 Stripe handles payment, invoices and the subscription portal linked in the app. We receive payment status and identifiers, not full card numbers or ticket content through Stripe. Price increases require at least 30 days' email notice before the billing period affected and allow cancellation before they take effect; material contractual changes otherwise follow Terms 14.
TT4. Processing, results and Customer responsibility
TT4.1 Using the Customer's OAuth permission, DM Triage retrieves ticket subject, description and channel and the relevant field definitions, values and group names. Requester, assignee and organisation IDs are retrieved only for the sidebar access check and are not sent to inference. It requests classification and probabilities through the Decision Models EU tier and, when enabled, writes the selected fields or routing result back to Zendesk. No Peer-to-Peer, worldwide or independent network processing is used.
TT4.2 Results are AI-generated statistical estimates; probabilities are not guarantees of correctness, calibration or suitability. The Customer chooses allowed fields, routing rules, thresholds and whether to enable writing, and remains responsible for ticket-handling decisions, their legal basis and appropriate human review. Review results before relying on them, particularly where errors could materially affect a person. Undo uses recorded before/after values; it is not a promise to reverse every downstream action in Zendesk.
TT4.3 The Customer must have authority to connect Zendesk and a lawful basis for the processing and required notices to affected people. Special-category and criminal-conviction data require the assessment and legal basis in DPA 3.2. Do not use DM Triage for solely automated decisions with legal or similarly significant effects without the applicable safeguards. Do not use ticket classifications or agent identifiers to score, rank or monitor individual employees or applicants, or for recruitment, performance or disciplinary decisions. Use as part of a high-risk AI system requires prior written agreement; the Acceptable Use Policy continues to apply.
TT5. Content, access and retention
TT5.1 Ticket text is processed transiently and is not stored by the app, except for accuracy-report snapshots. Snapshots let the Customer inspect the original ticket inputs used in an accuracy report. Snapshots are encrypted in the database at application level (Fernet) and deleted from the live database after seven days or on demand. The app stores ticket IDs, predictions, probabilities, field values, an undo change log with before/after values and usage counters. These records may themselves contain personal data. The gateway's content-retention limits and the replica/backup arrangements are in Annex T; this is not a promise that no content ever reaches any disk.
TT5.2 Customer Content is not used to train or fine-tune models. No human reads ticket content except a named person responding to the Customer's support request; no automated agents or third-party AI tools read Customer Content. The app's requested inference through the EU tier is the processing described in TT4, not an additional support or development tool.
TT5.3 Disconnect and deletion follow TT9 and Annex T. Account, acceptance, billing, login and notify-list data are described in the DM Triage privacy addendum.
TT6. Availability and beta features
DM Triage is a beta service without a contractual availability target; the general API Service Level Targets do not apply. Zendesk and inference availability can affect processing. Features may change subject to Terms 14 and mandatory law. We announce discontinuation at least 30 days in advance where possible, allow export of retained results, and refund the unused prepaid base-fee portion if we discontinue the paid service or terminate it without good cause attributable to the Customer. Accrued valid excess charges remain due.
TT7. Support, warranty and liability
Support: info@productivity-boost.com on German business days. Terms sections 9 (warranty), 10 (liability), 11 (indemnity) and 12 (confidentiality) apply. These Additional Terms introduce no separate liability exclusion. Mandatory law, including Art. 82 GDPR, remains unaffected.
TT8. Notices and changes
Terms 14 applies to amendments; TT3.6 applies to prices. Sub-processor changes follow DPA 6.2 and Annex T. New terms do not silently authorise additional data uses. The accepted version remains available with its date in the app and in the archive.
TT9. Cancellation, disconnect and deletion
TT9.1 The paid subscription renews monthly until cancelled. Cancel at any time in the linked Stripe portal or by email to info@productivity-boost.com, effective at the current billing period's end. Paid processing remains available until then unless you disconnect. Cancellation alone does not revoke Zendesk credentials immediately.
TT9.2 Disconnecting in the app stops processing and deletes our stored Zendesk credentials immediately; it also sets an existing Stripe subscription to cancel at the current period's end. It does not create another monthly renewal. Unused time after a voluntary disconnect is not refunded, subject to TT2.4, TT6 and mandatory rights. Charges already validly incurred remain payable. Revoke any remaining authorisation in Zendesk as needed.
TT9.3 You may end the free service at any time by disconnecting or by email. Following disconnect, we purge all Customer Content and ordinary customer-account data from the live database within 30 days; historical database copies follow Annex T. Minimal statutory billing records, contract evidence and the repeat-trial marker follow the privacy addendum. Export retained results before disconnect or request their return before deletion. Ticket content and changes already in the Customer's Zendesk remain under the Customer's control. Terms 13.2 (termination for good cause) remains applicable.
TT10. Final provisions
Terms section 15 applies. The German version of these Additional Terms prevails. Previous versions.