License & use
Who may use EPTT, on which devices and in which customer environment.
Licensing, deployment, support, data responsibility and commercial terms should reflect the concrete EPTT scope and operating model.

Who may use EPTT, on which devices and in which customer environment.
Billing, hardware, project deliveries and any commitment period.
Responsibility, maintenance, incident handling and customer obligations.
Reference to privacy/DPA and relevant security conditions.
Access, data, hardware and possible export when the agreement ends.
Must be drafted legally for the final company and sales structure.
Use the contact flow for concrete questions about deployment, responsibility, data and security.
Final terms should cover licensing, payment, hardware, deployment, support, data responsibility, termination and liability in a way that matches the actual company and product model.
License and usage must match the concrete EPTT delivery.
Support and deployment responsibility must reflect the selected model.
Liability, governing law and company details require final legal validation.
What is purchased, when is it billed and which parts are one-time/subscription?
What service level is agreed and what sits outside it?
Privacy/DPA references and relevant roles must remain consistent.
Access, data, hardware and possible export should be described at end of service.