Terms and Conditions
These terms govern access to and use of all LogiHash platform touchpoints, including Home, Try platform, scanner experiences, API demo, documentation resources, reporting/contact channels, and planned Flutter-based mobile apps (iOS/Android).
Effective date: 2026-04-07
1. Scope
- •These terms apply to contracts with business customers and consumers unless otherwise agreed.
- •Conflicting customer terms apply only if expressly accepted in writing by Trustec Valley.
- •Some functions may be restricted to business customers based on service model and compliance requirements.
2. Subject matter
- •LogiHash provides generation, management, and verification of cryptographically protected T-Codes for physical and digital documents.
- •Services may include web interfaces, mobile-supported verification, API access, and associated operations/support.
- •Specific service characteristics follow the applicable offer, service description, and where relevant SLA.
3. Contract formation
- •Offers are non-binding unless explicitly marked as binding.
- •A contract is formed by signed offer acceptance, written order confirmation, or service activation (e.g., account enablement).
4. Usage prerequisites and customer duties
- •Customer must ensure only authorized users access the services.
- •Credentials, API keys, and tokens must be kept confidential.
- •Customer remains responsible for legality of uploaded/processed content and metadata.
5. Fees and payment
- •Pricing, billing periods, and payment terms follow the applicable offer/order.
- •Unless agreed otherwise, prices are net plus statutory VAT/taxes where applicable.
- •Statutory late-payment rules apply in case of payment default.
6. Availability and maintenance
- •Trustec Valley aims for high service availability.
- •Planned maintenance is announced in advance where reasonably possible.
- •Events outside reasonable control (force majeure, third-party outages) do not constitute a breach.
7. Security and cryptography
- •LogiHash uses cryptographic methods to support integrity, authenticity, and traceability.
- •Absolute security against every possible attack cannot be guaranteed.
- •Customer is responsible for securing endpoint devices, networks, and internal processes.
8. Data processing and hosting locations
- •Processing follows applicable data-protection law and, where applicable, a separate DPA.
- •Solution architecture may include Telekom Open Cloud components (e.g., API Gateway, KMS) and Hetzner infrastructure (hosting/object storage).
- •Concrete technical setup depends on the agreed operating model.
9. Software and content rights
- •All rights in the platform, software, and documentation remain with Trustec Valley and/or licensors.
- •Customer receives a non-exclusive, non-transferable usage right for contract duration.
- •Reverse engineering, unauthorized modifications, and bypassing technical controls are prohibited.
10. Liability
- •Unlimited liability applies in cases of intent, gross negligence, injury to life/body/health, and mandatory product-liability scenarios.
- •For ordinary negligence, liability is limited to breach of essential contractual duties and foreseeable typical damage.
- •Further liability is excluded to the extent legally permissible.
11. Indemnification
Customer indemnifies Trustec Valley against third-party claims arising from unlawful use, unlawful content, or unlawful data processing attributable to the customer.
12. Term and termination
- •Term and notice periods follow the agreed commercial offer, service description, or ordering process.
- •Unless otherwise agreed, contract term starts upon contract conclusion.
- •The right to extraordinary termination for cause remains unaffected.
13. Confidentiality
Both parties must treat non-public information as confidential.
14. Final provisions
- •German law applies, excluding CISG, unless mandatory law states otherwise.
- •Venue is the registered seat of Trustec Valley where legally permissible.
- •If a clause is invalid, remaining clauses stay effective.
15. AI-assisted security analysis and anomaly detection
- •Trustec Valley may use AI-assisted models to detect unusual behavior patterns, potential attacks, fraud indicators, and misuse scenarios.
- •These models support system security, quality assurance, and protection of legitimate users.
- •Automated classifications may reflect probability assessments and can be supplemented by human review.
16. Reporting channel (including plausibility checks)
- •LogiHash may provide a reporting function for suspicious documents, T-Codes, identity data, or processes.
- •Incoming reports may be checked by intelligent/automated systems for plausibility, consistency, and abuse indicators.
- •Trustec Valley may temporarily restrict suspicious processes pending clarification.
17. Evaluation, feedback, and product improvement
- •Evaluation and feedback features may be provided in apps and interfaces.
- •Feedback may be processed for quality improvement, error analysis, and product development, including aggregated/anonymized analytics.
- •Personal feedback data is processed only within the legally permissible scope.
18. Consequences of abusive feature use
- •Any abuse of platform features (e.g., generation, verification, reporting, API, feedback channels) is prohibited.
- •Depending on severity, Trustec Valley may issue warnings, apply rate limits, suspend temporarily/permanently, terminate for cause, claim damages, and pursue legal action.
19. False identity or legitimacy documents
- •Submitting or using forged, falsified, or misleading identity evidence is strictly prohibited.
- •Trustec Valley may immediately stop related processes, suspend accounts/features, and notify competent authorities where legally required or permitted.
- •Any resulting legal and financial consequences remain with the responsible party under applicable law.
20. AdES (advanced electronic signatures)
- •LogiHash may provide AdES-related signing and verification features for digital documents.
- •Identity proofing within the signing flow is performed by LogiHash itself; Trustec Valley obtains certificates from an appropriate certificate-chain provider.
- •Signature creation, signature validation, and integrity evidence are handled within LogiHash systems as described in the service scope.
- •AdES does not automatically replace qualified electronic signatures (QES); customers remain responsible for selecting the legally required signature level.
- •Actual evidentiary value depends on applicable law, procedural context, and the integrity of the evidence chain.
- •Suspected compromise of signing means, keys, or credentials must be reported immediately and handled through blocking and/or key rotation.
