Legal
Privacy addendum — DM Triage
Version 1.0 · Effective date: 2026-11-17
P1. Controller and scope
This supplements the Privacy Policy for DM Triage. Controller: productivity-boost.com Betriebs UG (haftungsbeschränkt) & Co. KG, Reichenberger Str. 2, 94036 Passau, Germany, represented by productivity-boost.com UG (haftungsbeschränkt), represented by managing director Florian Standhartinger. Contact: info@productivity-boost.com, +49 178 1981631; Imprint. The German version of this addendum prevails.
We act as controller for the data and purposes below. The Customer controls its Zendesk ticket content, classifications, field values and undo records; we process those on its instructions under the DPA and Annex T. Their retention is described there. Customer-directed audit identifiers may also fall within Annex T; operational use does not make all ticket metadata our controller data.
P2. Data, purposes and legal bases
| Data | Purpose | Legal basis |
|---|---|---|
| Connecting administrator's agent ID/email, Zendesk subdomain/account identifier, company details, connection status and settings | Establish and administer the business account, connect the service and communicate about it | Art. 6(1)(b) GDPR where the contact is the contracting person; otherwise Art. 6(1)(f), legitimate interest: administering the business contract through its authorised representatives |
| § 14 BGB business declaration, company name, optional VAT ID, accepting administrator/account, UTC time, document versions and SHA-256 hashes, IP hash and order confirmation | Document authority, contract and B2B eligibility | Art. 6(1)(f), legitimate interest: proof and defence of the contract; Art. 6(1)(c) where a legal recordkeeping duty applies |
| Stripe customer/subscription identifiers, plan, billing details and status, invoices and usage totals needed for charging | Manage subscription, charge EUR 49/month and excess use, account for payments | Art. 6(1)(b), or Art. 6(1)(f) for representatives as above; Art. 6(1)(c) for statutory accounting/tax duties |
| Aggregate classification counters, billing-period totals, timestamps and technical status, without ticket text | Apply allowances, show usage, prevent duplicate billing, keep the service stable | Art. 6(1)(b), or Art. 6(1)(f) for business administration and reliable billing |
| Hosted-login email, hashed magic-link token, issue/expiry | Authenticate the administrator; tokens expire after 15 minutes | Art. 6(1)(b), or Art. 6(1)(f) for secure access by representatives |
| Secret-key HMAC of the IP-address/email rate-limit key and request counter | Prevent login and connection abuse; 15-minute windows, deletion within 30 minutes | Art. 6(1)(f), legitimate interest in secure access and abuse prevention |
| Marketplace notify-list email, locale, campaign labels, consent version, consent/confirmation time and status | Double-opt-in confirmation and the Marketplace availability notification requested by you | Art. 6(1)(a), consent, withdrawable at any time by unsubscribe or email; no ticket content |
| Secret-key HMAC of the normalised Zendesk subdomain as repeat-trial marker | Enforce one trial per Zendesk account, prevent repeated-trial abuse | Art. 6(1)(f), legitimate interest: preventing abuse of the free trial; we treat a marker as personal data where linkable to a person, rather than assuming hashing makes it anonymous |
Stripe Checkout collects payment details directly; we do not receive the full card number. Stripe's controller/processor roles are described in the main policy. Providing required account, authority and billing information is necessary to use/order the service; the notify list, optional VAT ID and analytics participation are not conditions of purchase. This account/billing processing makes no automated decision producing legal or similarly significant effects about an individual; Customer-directed ticket decisions remain the Customer's responsibility.
P3. Retention
The three strictly necessary cookies dmt_session, dmt_connect and dmt_login_csrf are used under § 25(2) no. 2 TDDDG; no consent is required for this strictly necessary access/storage.
Deleting a ticket in Zendesk does not automatically delete an existing report snapshot; it remains until the seven-day expiry or earlier on-demand snapshot deletion.
- Disconnect: stored Zendesk credentials are deleted immediately. Ordinary administrator/account data and operational usage data are purged from the live database within 30 days, except records below. Customer Content follows Annex T; snapshot text has its separate seven-day live-database limit.
- Login: magic-link tokens are stored only as hashes and expire after 15 minutes. Strictly necessary cookies are dmt_session (one hour, authenticated session), dmt_connect (15 minutes, connection-form protection) and dmt_login_csrf (15 minutes, login-form protection). For abuse prevention we store a secret-key HMAC of the IP-address/email rate-limit key and a counter in 15-minute windows, deleted within 30 minutes. These mechanisms serve secure access under Art. 6(1)(f) GDPR, our legitimate interest in protecting accounts and preventing abuse.
- Notify list: unconfirmed entries are deleted after seven days; confirmed entries are kept until unsubscribe, then deleted from the active list. No account or subscription is required. Withdrawal does not affect processing already lawful before withdrawal.
- Contract evidence: the B2B declaration and acceptance records are kept, with restricted access, until the end of the third calendar year after account deletion to prove/defend the contract (Art. 6(1)(f), Art. 17(3)(e) GDPR), unless a specific longer statutory duty or legal dispute requires longer retention.
- Billing: minimal records needed to identify and evidence a transaction may include Stripe identifiers, administrator email and Zendesk subdomain. These identifiers are retained only within the required invoice/accounting-voucher record, generally for eight years from the end of the relevant calendar year, not in a separate ten-year identifier table. Main policy section 5 applies: generally eight years for accounting vouchers/invoices, ten years for books and annual accounts, six years for commercial correspondence, calculated under the applicable rules; a specific statutory extension may apply. Ordinary account identifiers are not automatically all subject to ten-year retention.
- Repeat-trial marker: to prevent repeat trials, we store a secret-key HMAC of the normalised Zendesk subdomain in a separate table used only for the trial check. We delete it 24 months after the trial started. The secret key is stored separately from the database like the snapshot key. Where the marker is linkable to a person, we treat it as personal data; you may object under Art. 21 GDPR, and we erase it where required.
- Copies: live database and local dumps at Hetzner HEL1-DC6, Finland (dumps approximately two days); streaming replica HEL1-DC7, Finland. Deleted data are removed from the local dumps on rotation, at the latest 180 days after deletion from the live database. Restores must reapply deletion, unsubscribe, credential revocation and snapshot expiry before reuse. The replica follows live deletions; no claim of an exact zero-lag copy is made.
P4. Recipients and locations
Hetzner hosts the app, live database and local dumps at HEL1-DC6 and the replica at HEL1-DC7, Finland. Snapshot text is encrypted at application level before entering database copies; its key is held only in the app environment. Other fields are not asserted to be encrypted at application level. See the product-specific provider list.
Resend (Plus Five Five, Inc., USA) delivers sign-in, double-opt-in/notify and service emails without ticket content. Its sending region is Ireland; message/delivery records may be stored in the USA; safeguards and processor role are as in the main policy. Stripe Payments Europe, Ltd., Ireland, processes checkout, subscriptions and invoices, without ticket content; transfers to Stripe, Inc. (USA) may occur under the safeguards in the main policy. Do not send ticket content to a support mailbox: mail providers would receive it. Arrange any necessary support access inside the app with a named person.
Zendesk receives the Customer's authorised updates and supplies the connection data from its Customer-managed account. The Customer's own Zendesk contract governs its hosting and retention. EU inference providers process ticket content under Annex T, not the notify list or payment details.
P5. Website analytics and technical logs
If analytics is enabled on /start, self-hosted Umami follows main policy section 2.2: no cookies/browser storage, no stored IP address, no account linkage, only allowed non-personal campaign data, and no sending when Do Not Track or Global Privacy Control is set. Sign-in tokens, OAuth codes, email addresses, Zendesk subdomains/account IDs and ticket information are stripped from URLs, referrers and event data. Analytics is not loaded on authenticated app, OAuth, login, report or checkout-return pages. Legal basis: Art. 6(1)(f), legitimate interest in improving the entry page; retention: up to 24 months, as in section 2.2. Server logs follow main policy section 2.1 (normally at most 14 days, with its incident exception). The strictly necessary authentication and form-protection cookies and the rate-limit records are described in P3.
P6. Your rights
Main policy sections 7–8 apply: access, correction, erasure, restriction, portability where applicable, objection under Art. 21 and withdrawal of consent. You may complain to a supervisory authority, including BayLDA (www.lda.bayern.de). For our controller processing contact info@productivity-boost.com. Requests about ticket processing go to the business using Zendesk; we assist it under the DPA.
P7. Integration with the main policy
For DM Triage this addendum supplements sections 1–6; it does not alter other products. Previous versions.