← Privacy policy

Elevate platform subprocessor register

Version 1 · effective 2026-07-28

Service providers Dynaminds engages to process data on your behalf, each under its own data-processing agreement. [email protected]

Binding version: the Polish text. This English translation is informational. In case of divergence the Polish version prevails.

Elevate platform subprocessor register

Version 1. Effective 28 July 2026.

Publication approval reference: B2BNET-SUBPROC-V1-APPROVAL-2026-07-28-OWNER-NO-EXTERNAL-COUNSEL.

This register is an annex to the Data Processing Agreement (DPA) and lists the processors the Provider uses in delivering the Elevate platform.

§1. General principles

  1. The Provider engages subprocessors only to the extent necessary to deliver the services, under contracts imposing obligations no less strict than those in the DPA.
  2. The Provider gives at least 30 days' notice before adding or changing a subprocessor, by publishing an updated register and notifying Organisation administrators.
  3. The Customer may raise a reasoned objection to a new subprocessor within 30 days. Absent agreement, the Customer may terminate the part of the contract covering the affected services without termination charges.
  4. Transfers outside the European Economic Area rely on the European Commission's standard contractual clauses or an adequacy decision.

§2. Subprocessor register

SubprocessorRoleData categoriesProcessing location
Supabase (Supabase Inc.)Database, authentication, file storageAll Customer data held in the Platform: accounts, tickets, comments, attachments, billing recordsEU — Frankfurt (eu-central-1)
Hetzner Online GmbHApplication hostingData processed transiently in application memory; request logsEU — Germany
Microsoft Ireland Operations Ltd.Inbound and outbound mail (Microsoft Graph), staff SSO (Entra ID)E-mail addresses, ticket correspondence content, e-mailed attachmentsEU
Stripe Payments Europe Ltd.Payments and invoicingOrganisation billing data, purchaser e-mail address, tax data. The Provider does not store card dataEU / USA (standard contractual clauses)
Anthropic PBCAI classification and assistance: routing tickets to the right competency, knowledge-base generation, RAG answers, reportsTicket title and body sent to the model at processing time. Data is not used to train modelsUSA (standard contractual clauses)
Voyage AIContent vectorisation for semantic searchTicket and knowledge-base titles and bodiesUSA (standard contractual clauses)
Functional Software, Inc. (Sentry)Application error monitoringTechnical identifiers, exception traces. Personal data is redacted before transmission (beforeSend)EU — Frankfurt
Grafana LabsOperational logs and metricsApplication logs without ticket contentEU — Frankfurt / Ireland
Cloudflare, Inc.Attack protection (WAF), CDNIP addresses, request headersGlobal edge network
Slack TechnologiesProvider team notifications (optional)Ticket number and title, Organisation nameUSA (standard contractual clauses)

§3. Customer control over AI processing

  1. Sending ticket content to Anthropic PBC for routing requires the Organisation's separate, explicit opt-in. This setting is off by default.
  2. Other AI features (knowledge base, RAG answers, reports) are governed by a separate Organisation-level switch.
  3. Disabling AI features does not restrict raising or delivering tickets; it affects only how tickets are routed and which assistive features are available.