Ascrotech BV · Eyzen
The third parties involved in supporting an Eyzen deployment, and those we use to run our own business. Two separate lists, because they carry different rights.
Why this list is short. Eyzen is not delivered as a hosted service. Our customers install and run it in their own environment, so the operational data stays with them and there is no Ascrotech-side platform, and therefore no chain of hosting, storage and analytics providers behind one. See our Privacy Policy for the full picture.
What remains is the support channel, and the ordinary tooling any company needs to run itself. Both are set out below.
Table 1 lists the sub-processors we engage when we process personal data on a customer's behalf, which happens only during support and implementation work. These are the parties your data processing agreement with us covers, including the notice period before any change and your right to object.
Table 2 lists the service providers we use in our own business, where we act as controller. They are published for transparency. They are not sub-processors of your data, and the objection right under your data processing agreement does not extend to them.
We process personal data as a processor only when a customer gives us access in the course of support or implementation work: remote access for diagnosis, read access to the customer's own telemetry, a diagnostic export the customer chooses to send, a non-production environment the customer makes available, and whatever is submitted through the support channel. The following third parties are involved in that processing.
| Sub-processor | Purpose | Location | Transfer mechanism | In use since |
|---|---|---|---|---|
| Atlassian Jira Service Management (cloud) |
Hosting of the support channel: support requests, ticket correspondence and material submitted with them | European Union. EU regional data residency is configured before the channel carries any customer data, as the data processing agreement requires | Atlassian's data processing addendum, incorporating the European Commission's Standard Contractual Clauses, for any processing outside the EEA | Not yet in use. The support channel goes live with the first customer deployment |
Support is otherwise carried out by our own personnel, working wherever possible on redacted diagnostic material from which personal data has been removed. We do not take copies of a customer's production database into our own environment.
None engaged. We do not submit personal data, or unredacted diagnostic material, to any third-party artificial-intelligence or machine-learning service. Where a customer gives prior written approval for such a service, it is added to Table 1 with the same detail as any other sub-processor, engaged on terms that prohibit training on the submitted data and require its prompt deletion. We do not use customer data to train, fine-tune or improve any model, whether our own or a third party's.
These providers support our own operations, where we act as controller. They have no access to any customer's Eyzen installation, and the objection right under a data processing agreement does not extend to them.
| Provider | Purpose | Location | Personal data involved |
|---|---|---|---|
| Microsoft Microsoft 365 | Email, calendar, documents and collaboration | European Union | Business correspondence with our contacts, and the documents in which their details appear |
| Yuki | Accounting and invoicing | European Union | Billing contact details and transaction records |
Where any of these providers processes personal data outside the EEA, that transfer is covered by the provider's data processing terms incorporating the European Commission's Standard Contractual Clauses.
What is deliberately absent. We use no customer relationship management or marketing automation platform, and no website analytics: prospect and customer contacts live in our correspondence, and our site sets only strictly necessary cookies. We engage no external IT or security provider with access to our systems. We do not yet operate a public website; the hosting provider will be added here when we do. If any of that changes, this table changes with it.
Before we add or replace a sub-processor in Table 1, we notify each affected customer in writing, to the contact nominated for that purpose, and we update this page at the same time. The notice period, and the right to object on reasonable data protection grounds, are those in the data processing agreement between us and that customer.
You can also ask to be added to our change notification list at privacy@ascrotech.com. Subscribing is a convenience and does not replace the notice we give under your agreement.
This page is a record of fact: who our sub-processors and providers are, for what, and where. Your rights are governed by the data processing agreement between us, and by the annex to that agreement stating the position as at its effective date. Where this page and that agreement differ, the agreement prevails. Nothing on this page varies any agreement, and we do not change any agreement by updating this page.
| Version | Date | Change |
|---|---|---|
| 1.0 | 17 August 2026 | Initial publication. |
Earlier versions of this page are retained so that the position at any past date can be established. Ask us at the address below if you need one.
Questions about this page, about a specific sub-processor, or about the measures we impose on them: privacy@ascrotech.com.
Ascrotech BV, Schuttershof 10, 2070 Zwijndrecht, Belgium, enterprise number 0694.557.315.