Hosting and operations
T-NEX plans hosting and support for web applications and AI solutions, with defined accounts, operating tasks, ongoing costs and a practical handover plan.
Explore serviceTransparency for companies
Plan data protection and software operations together.
We clarify with you which data your application processes, who may access it and how operations are organised. This creates a shared basis for introduction and ongoing support. Information about this website's operations is provided in a separate section.
Business applicationsYour workflowsInterfaces
Shared data modelData · Roles · Permissions
AI FoundationAI functions within the application
Platform principle; the specific scope is agreed for each project.
In daily work
For your project: identify the company, tasks and access
For business owners, IT teams and data protection leads who need to understand a planned application’s data flows.
Project planning begins with the contracted company and each party’s tasks. The proposal should clearly identify the contracting entity, your contact and the specific scope. Operations, development and business approvals each need an assigned responsibility.
We then examine your application’s data flow: which data comes from your company, who should be able to view or edit it, and what access does T-NEX need for setup and support? Development and support access are part of this overview, including the countries from which access is actually planned.
Data protection roles and the agreements required are assessed against that specific process. Identifying T-NEX GmbH as responsible for the website does not by itself establish which company performs each task in your project.
| Area | What needs to be recorded |
|---|---|
| Contract and responsibility | Contracted company, scope, business approvals and contacts |
| Accounts and permissions | Account owners, required roles, granting and removing access |
| Access | People or organisations involved, their tasks and actual access countries |
| Agreements | Contract documents that fit the data flow and decisions still needed |
Overview
Examine every service involved in the data flow
The overview covers the application, database and file storage, plus email delivery, AI models and other interfaces where used. Each selected service is reviewed for its purpose, data processed, contracting party and configured location. Backups, logs and administrative access are included.
For an AI feature, we clarify which content reaches the model, whether personal data is needed for the task and what settings the selected service offers for that use. The data permitted in testing is established beforehand.
A provider name or server location alone does not describe all this processing. Project documentation should also make subprocessors, relevant access and the required data protection documents understandable. The specific services and countries depend on the chosen application and its actual configuration.
Overview
Decide on operations with a concrete overview
For the operating decision, we bring together the information needed: the system and its services, data flows, responsibilities, access, retention and deletion, and incident handling. The overview records which evidence is available and which decisions remain at the relevant point.
Maintenance, backups, recovery and a future handover are agreed to suit your application. An initial discussion needs a description of the workflow and the types of data involved. Actual customer records or confidential documents are not needed at that stage.
Overview
This website: the company and technical delivery
T-NEX GmbH, Freiligrathstraße 2, 32805 Horn-Bad Meinberg, Germany, is responsible for this website. You can contact us at info@t-nex.de. The version currently provided uses OpenAI’s ChatGPT Sites, with Cloudflare involved in technical delivery.
Website requests produce technical information such as the IP address, requested address and browser details. The infrastructure providers process this information to deliver and operate the service. Where access is protected, the platform provider also processes sign-in. The website privacy policy and the providers’ notices explain this processing in more detail.
This website has its own operating setup. The providers for your future application, data locations and support access are established for the specific project. The website’s setup therefore does not determine where your application data will be stored.
Overview
Your enquiry: from the form to an email you send
The contact form currently prepares a message in your browser. You enter your name, email address and message; the company field is optional. If you arrive from an offering page, its topic may be included in the prepared message.
Preparing the message does not send these entries from the website code to a form server or an AI service. You then open your email application or copy the message. T-NEX receives your enquiry when you send the email yourself. Opening the email application alone does not send it.
When the form loads, the website checks whether direct delivery is available. That technical request contains no completed form fields. Direct delivery is not enabled in the setup described here. The website code also does not write your entries into the page address or store them in persistent local message storage.
| Action | Information processed | What happens next |
|---|---|---|
| Prepare email | Form entries and, where applicable, the selected offering topic in the browser | You see the prepared message. |
| Copy message | Clicking the button writes the prepared message to the clipboard. | You paste the text into your chosen application. |
| Open email application | The recipient, subject and message are passed to your email application. | You review the draft and send it there. |
| Send email | The contact details and content you send reach T-NEX through the email services involved. | T-NEX handles your enquiry and replies. |
Overview
Local preferences, content and technical logs
The website stores your animation pause preference locally. It remains until you change it or clear the website’s data in your browser. The homepage also uses the browser tab’s session storage to remember whether the introduction animation has already played.
Fonts, images and product views are delivered with the website. The website code does not include analytics or advertising trackers or automatically load external videos or maps. External links open the relevant service when you click them.
Infrastructure providers may process technical request information in operational and security logs. The description of local preferences therefore does not mean that no data is stored during a website visit. Log contents, access permissions and retention for your future application are established separately.
What needs to be agreed before use
The website data flows described apply to the version currently provided. Contracting parties, access countries, services and operating commitments for a client application are established and documented for the specific project.
FAQ
Frequently asked questions
Does T-NEX receive my message while I am completing the form?
In the contact process described here, entries remain in the browser while you complete the form and prepare the message. T-NEX receives the message when you send it from your email application. The copy button writes the draft to the clipboard when you request it.
Who can I contact about this website?
T-NEX GmbH in Horn-Bad Meinberg is responsible for this website. For questions about the website and the processing described, contact info@t-nex.de. The company details and privacy policy are available through the corresponding links.
Will our application use the same providers as this website?
Your application’s technical environment is selected for the project. Its database, storage, AI service, delivery and support depend on the task and the agreed requirements. This website’s providers do not automatically become providers for your application.
Where can we find out which countries our data will be accessed from?
The project overview should identify the data locations and access countries actually planned. This includes development, support and administration access. The information and documents needed are reviewed against the specific operating model.
What information helps with an initial enquiry?
Describe the workflow, systems, types of data and your access and operating requirements. For example, a customer portal needs to store requests, provide documents and send notifications. That allows us to discuss the relevant data flows before actual customer records are needed.
Related options
You may also be interested in these.
Custom software development for companies
T-NEX develops business applications and extends existing systems, from clickable prototypes and integrations to agreed handover and support.
Explore serviceStandard contractual clauses and DPAs
SCCs for processing in third countries: choosing modules, understanding the DPA relationship and completing the details for software development.
First version: Updated:
Read articleTransfer Impact Assessment template
Assess development and support transfers: data flows, SCCs, third-country law and safeguards. Includes editable TIA working templates in German and English.
First version: Updated:
Read articleWhich task would you like to solve next?
Bring a concrete task. Together, we will define what the application needs to do.
Discuss your application’s data flows