Terms of Use for Online Communication

1. Provider and scope

The provider is Jürgen Eishold Einzelunternehmen, Hauptplatz 26, 3340 Waidhofen an der Ybbs, Austria, operating under the EISHOLD brand. General contact: [email protected]. Technical contact: [email protected]. Full provider information is available in the legal notice.

The environment supports enquiries, existing assignments, project documents, support and collaboration with invited customers and partners. Mattermost is the software used; the contracting party for EISHOLD services is the provider identified in the relevant assignment.

2. Access and account responsibility

Access is granted to a specific person for the authorised project scope. Credentials must not be shared. Users should use available multi-factor authentication and promptly report suspected misuse to the technical contact.

Users acting for a business must have the necessary authority. Access to a channel does not grant authority to agree new services, prices or contracts.

3. Project channels and customer communication

Subject to agreement, Mattermost is intended to be the central operational communication channel for an assignment. Mandatory notices, legal form requirements and obligations to contracting marketplaces remain unaffected. Messages must be placed in the channels intended for the relevant customer and assignment.

The Head of Business Administration, identified as an AI assistant, is intended to be the central operational contact. Internal execution agents should not independently communicate with customers. Human review or escalation may be requested in the project channel or through [email protected].

4. Upwork and other contracting marketplaces

For assignments initiated through Upwork, communication generally remains on Upwork before the contract starts. Moving to this environment occurs only after the contract starts or under an expressly applicable exception in the marketplace rules.

Payments, milestone approvals, acceptance and dispute procedures remain where the customer agreement or marketplace rules require them. This environment must not be used to circumvent marketplace fees or other obligations. Corresponding rules of other marketplaces also apply.

5. AI assistance and internal systems

Where identified in the project and configured for an authorised purpose, AI assistants may structure messages, make preliminary assessments of assignments, prepare questions and delegate internal tasks. They may make mistakes. Material business outputs should be checked before use.

EISHOLD remains responsible for its own services. New contracts, binding changes to prices or services, and other legal commitments require approval by an authorised human unless explicit documented authority exists. An automated acknowledgement of receipt is not acceptance of an assignment.

An internal connection to EISHOLD Nexus is envisaged for assignment management. This does not confer blanket access to all messages or permit disclosure to arbitrary AI providers. New recipients, purposes or data transfers must be addressed in privacy information and any required agreements before activation.

6. AI concierge and service

The central customer contact's concierge function is intended to provide friendly, professional and courteous assistance while maintaining appropriate personal boundaries. It should identify needs from the conversation, confirm assumptions where necessary, clarify requirements and suggest suitable next steps. AI involvement is identified, and human review remains available on request.

If a request cannot be fulfilled, the concierge should explain why and proactively offer a realistic alternative or a proposed remedy. Binding credits, discounts, additional services and other commitments may only be made within expressly authorised powers. This does not replace or restrict statutory remedies.

This service approach is an intended quality standard, not a promise of unlimited availability, guaranteed fulfilment of every request or comprehensive advice in every area of life. Communication hours and scope follow the assignment. Where a task falls outside the agreed or professionally permissible scope, appropriate referral should be proposed.

7. Confidentiality and permitted content

Project information may only be used within the authorised scope and disclosed to authorised persons. Existing non-disclosure agreements remain effective. Users may upload only content for which they have the necessary rights and authority.

Unlawful content, malware, unauthorised access, harassment and disclosure of others' confidential data are prohibited. Passwords, API keys, payment data, identity document copies and particularly sensitive personal data must not be placed in ordinary chat channels; a suitable transfer method must first be agreed with EISHOLD when necessary.

8. Privacy and technical access

Use may require processing contact and account details, messages, files, and access and security logs. Purposes include assignment-related communication, collaboration and secure operation. The applicable legal bases and further information are provided separately under the GDPR.

A private channel does not promise end-to-end encryption. Authorised administrators and technically necessary service providers may have access to the extent required. Specific recipients, AI providers, storage locations, third-country transfers, retention periods and data subject rights must be described in the accompanying privacy information.

Acceptance of these terms is not blanket consent to advertising, model training or other unrelated processing. Where EISHOLD processes personal data on a customer's behalf, any required data processing agreement must be concluded separately.

9. Content and rights

Rights in submitted content remain with the respective rights holders. Only the permissions needed to store, technically display and process content within the agreed project scope are granted. Publication as a reference or further use requires separate authority.

Rights in project results, software, licences and deliverables are governed by the customer agreement. Uploading or making them available in chat does not automatically transfer those rights.

10. Availability, deadlines and outages

Without a specific agreement, there is no commitment to continuous availability, a particular response time or round-the-clock staffed support. Maintenance or outages may restrict use.

Urgent or deadline-sensitive notices must use the channel agreed in the customer contract. During an outage, [email protected] may be used as a contact. Users should retain important original documents themselves; the communication environment does not replace their own archive.

11. Backups, retention and termination

Retention and deletion follow the relevant purpose, privacy information, legal duties and documented agreements. A backup supports recovery; it is not a permanent customer archive. Restores must account for deletion obligations that have already taken effect.

EISHOLD may proportionately restrict affected access in response to security risks or significant misuse. Where possible and legally permissible, the reason will be communicated. Closing an account does not automatically terminate the customer agreement or remove statutory privacy rights.

12. Contract priority, changes and statutory rights

Mandatory law prevails. Individually agreed customer contracts and applicable marketplace rules remain authoritative; these terms supplement use of the communication environment. They do not restrict mandatory consumer rights and contain no blanket exclusion of liability.

Material changes will be communicated with a version identifier and, where necessary, a request for renewed acceptance. Silence does not automatically constitute acceptance of a contractual change. The available language versions are intended to convey the same rules; mandatory language-related protections remain unaffected.

13. Contact and human escalation

General enquiries, complaints, privacy requests and requests for human review: [email protected]. Technical security reports: [email protected]. Do not include passwords or secret keys in a security report.