Privacy Policy & Terms of Service

1. Scope, Governing Law, and Jurisdiction

Entropix is a security infrastructure provider operating under the laws of the Federal Republic of Germany. All services are operated from Frankfurt, Germany. This document governs the collection, processing, storage, use, and deletion of data generated through any interaction with Entropix infrastructure, directly or indirectly, including through third-party software that integrates Entropix components, automated systems, scripts, bots, or any other means.

This document applies without exception to all users, clients, customers, end-users, trial users, API consumers, integration partners, resellers, and any other party that interacts with Entropix infrastructure. It applies regardless of whether the interaction is initiated by a human user or an automated system.

The following laws and regulations apply to all users of Entropix services and must be complied with at all times. Violation of any of these constitutes grounds for immediate termination and legal action.

General Data Protection Regulation (GDPR / EU 2016/679) in its currently applicable version. Federal Data Protection Act (Bundesdatenschutzgesetz, BDSG) as amended May 25, 2018 and all subsequent amendments. Telecommunications Telemedia Data Protection Act (TTDSG) and the Telemedia Act (TMG). Telecommunications Act (Telekommunikationsgesetz, TKG) in its current version. German Criminal Code (Strafgesetzbuch, StGB), specifically §202a Unauthorized access to data, §202b Interception of data, §202c Preparation of unauthorized access and interception, §303a Data tampering, §303b Computer sabotage, §263a Computer fraud, §269 Forgery of legally relevant data, §274 Suppression of documents, §238 Stalking, §123 Trespass as applied to digital systems, and §241 Threat as applied to digital communications. Act Against Unfair Competition (Gesetz gegen den unlauteren Wettbewerb, UWG) where applicable. Copyright Act (Urheberrechtsgesetz, UrhG) in its current version. Network and Information Systems Directive (NIS2, EU 2022/2555) and its national implementation. IT Security Act 2.0 (IT-Sicherheitsgesetz 2.0, ITSiG 2.0) in its current version. German Civil Code (Bürgerliches Gesetzbuch, BGB), specifically §§ 823 and 1004 governing civil liability and injunctive relief. Code of Civil Procedure (Zivilprozessordnung, ZPO) governing enforcement proceedings. Code of Criminal Procedure (Strafprozessordnung, StPO) governing criminal investigations. German Commercial Code (Handelsgesetzbuch, HGB) §§ 238 and 257 regarding record retention. German Tax Code (Abgabenordnung, AO) § 147 regarding retention of tax-relevant records. Product Liability Act (Produkthaftungsgesetz, ProdHaftG) where applicable. Act on Civil Law Aspects of Information Society Services (e-Commerce Directive implementation). Regulation (EU) 2022/2554 on Digital Operational Resilience (DORA) where applicable. EU Cybersecurity Act (Regulation EU 2019/881) and associated certification frameworks.

All disputes arising from or in connection with the use of Entropix services shall be subject exclusively to the jurisdiction of the courts of Frankfurt am Main, Germany. Users located outside of Germany submit irrevocably to the exclusive jurisdiction of German courts by using this service. The substantive law of the Federal Republic of Germany shall apply exclusively, with the exception of its conflict of law rules. The United Nations Convention on Contracts for the International Sale of Goods (CISG) is expressly excluded.

2. Data Controller and Contact

The data controller responsible for all processing of personal and technical data under GDPR and BDSG is Entropix. All data protection inquiries, subject access requests, deletion requests, objections, and legal correspondence must be submitted in writing to [email protected]. Entropix will appoint a Data Protection Officer as required under GDPR Article 37 and publish their contact details at entropix.dev/privacy upon appointment. Entropix will respond to all valid data subject requests within 30 calendar days of receipt of a verifiable request.

3. Network and Connection Data

Upon any connection attempt to Entropix infrastructure, the following data is collected automatically, immediately, and without exception. Collection begins at the moment a connection attempt reaches any Entropix-controlled network boundary, regardless of whether authentication succeeds or the connection is subsequently terminated by protective systems.

IPv4 and IPv6 source addresses of all connecting clients, including intermediate addresses visible through proxy, relay, or NAT traversal chains. Geolocation data derived from IP address at country, region, and city level where technically resolvable. Autonomous System Number and Internet Service Provider identification for each connecting address, including hosting provider identification. Connection type classification covering residential broadband, datacenter hosting, cloud provider egress, corporate network, mobile carrier network, commercial VPN service, open anonymization proxy, and Tor exit node. All port numbers used for inbound and outbound connections across the full port range. Layer 4 protocol identification covering TCP, UDP, QUIC, and any encapsulation thereof. Packet timing measurements including inter-arrival timing, jitter measurements, and latency profiles between client and server. Round-trip time measurements. Bandwidth consumption in both directions per session. Packet loss rates and retransmission patterns. DNS query metadata including queried domain names, query types, response codes, TTL values of responses, and resolver identification. Routing path metadata including visible hop counts, TTL values, and ICMP response characteristics. Connection state information including handshake completion status, abnormal reset events, and connection teardown reasons. Flow metadata including session start time, end time, duration, and total bytes exchanged. Any headers or metadata present at the network boundary before application-layer parsing.

4. Device and Hardware Identification

Entropix collects device-level identifying information to establish client identity, detect unauthorized or spoofed clients, prevent credential sharing, and maintain session integrity. This collection is performed on the legal basis of Article 6(1)(f) GDPR.

Hardware fingerprint derived from available system identifiers including CPU model and microarchitecture, CPU core and thread count, CPU instruction set extension flags, GPU model and vendor, total installed RAM, storage device model identifiers and capacity, and motherboard or platform identifier hash where accessible. MAC address hash of the primary network interface, stored only as a cryptographic hash and never in plaintext. Operating system type, distribution, version number, build number, and installed patch level. System architecture including x86, x86-64, ARM, ARM64, and any emulation layer. Installed system locale, keyboard layout, and language pack configuration. System timezone and UTC offset at the time of connection. Device uptime since last boot and approximate last boot timestamp derived from uptime. Virtual machine hypervisor detection including VMware, VirtualBox, Hyper-V, KVM, QEMU, Xen, Parallels, and others. Container runtime detection including Docker, Podman, LXC, containerd, and similar environments. Sandbox and analysis environment detection including automated malware analysis environments, fuzz testing frameworks, and security research tooling signatures. Emulation layer detection including Wine, Rosetta 2, and other binary translation systems. Hardware capability flags and instruction set extensions visible through protocol behavior. Display configuration where exposed through connection metadata. Network interface count and configuration where visible at the application layer. System call behavior patterns where observable through timing.

5. Cryptographic and Protocol Fingerprinting

Entropix employs comprehensive protocol inspection and cryptographic fingerprinting to verify client authenticity, detect replayed or injected connections, and identify clients whose behavior deviates from their established profile. All fingerprinting is performed on the legal basis of Article 6(1)(b) and (f) GDPR.

Full TLS ClientHello fingerprint collected and hashed via JA3, JA3S, and JA4 methodologies. Complete list of cipher suites presented in the ClientHello and their exact ordering. TLS version presented and negotiated, and the full set of versions advertised by the client. All TLS extensions present in the ClientHello, their ordering, and their values where relevant to identification. Supported elliptic curves and their ordering. Supported point formats. Certificate chain metadata for all mutual TLS connections including issuer common name, validity period, signature algorithm, and subject alternative names. Server Name Indication values presented during handshake and any discrepancies from expected values. Session ticket and session resumption behavior. TCP stack fingerprint including initial window size, window scaling factor, maximum segment size, TCP options present and their ordering, initial TTL value, IP don't-fragment flag behavior, and IPID randomization behavior. HTTP/2 settings frame parameter values and their ordering. HTTP/2 stream priority weighting and dependency structure. HTTP/3 QUIC transport parameter values. HTTP header ordering and exact casing across all request headers. Accept-Language header value and quality weighting. Accept-Encoding header value and ordering. User-Agent string in its raw presented form, a normalized canonical form, and consistency check against other fingerprint elements. Content-Type values and encoding specifications. Any custom or non-standard headers present.

Cryptographic primitives currently in active use across Entropix infrastructure are as follows. All client implementations must support these algorithms. Connections presenting unsupported cipher suites or algorithms will be terminated and flagged.

Asymmetric signing: ECDSA-P521 as primary, Ed448 as secondary. Symmetric encryption: AES-256-GCM as primary, ChaCha20-Poly1305 as secondary for environments without AES hardware acceleration. Stream obfuscation: AES-256-CBC within DHK protocol layers. Key agreement: X25519 for ephemeral Diffie-Hellman key exchange. General hashing: SHA-512 for primary operations, SHA-3-512 for secondary operations, BLAKE3 for high-throughput operations. Password and key derivation: PBKDF2-SHA512 for legacy compatibility, Argon2id as primary memory-hard function, scrypt for storage encryption contexts, HKDF-SHA512 for session key expansion. MAC computation: HMAC-SHA512, Poly1305. Random generation: system CSPRNG with minimum 32 bytes per nonce, 256 bits per session key, 512 bits per long-term key. Certificate formats: X.509v3 for public key infrastructure, raw public keys for protocol-level authentication.

6. Authentication and Session Data

All authentication events and the complete session lifecycle are logged in full. This logging is performed on the legal basis of Article 6(1)(b) and (f) GDPR and is necessary for the performance of the security contract.

Session tokens generated at authentication, stored exclusively as SHA-512 hashes and never in any recoverable form. Precise timestamps for all authentication lifecycle events including initial connection, challenge issuance, challenge delivery, challenge response receipt, authentication completion or failure, session renewal, token rotation, and logout. The multi-factor authentication method used per session where applicable. Public key identifiers presented during asymmetric handshake, stored as hashes. All nonce values presented during authentication to enable replay detection for the full nonce lifetime. Challenge port values used during DHK protocol handshake. Session UUID values assigned at authentication. Total number of authentication attempts per session including successes and failures. Specific failure reason codes for all failed authentication events. Complete session duration from establishment to termination. All idle period lengths within a session. Every IP address change detected within a single authenticated session, which triggers automatic session invalidation and mandatory re-authentication. All session invalidation events including the precise reason, timestamp, and triggering condition. Token rotation events and timestamps. User-Agent consistency checks between authentication and subsequent requests. Geographic consistency checks between authentication location and subsequent request origins.

7. Behavioral Analysis and Anomaly Detection

Entropix operates a continuous real-time behavioral analysis system that monitors all client interactions to detect, classify, and respond to anomalous, abusive, or malicious behavior.

Request rate measured at one-second, one-minute, and one-hour intervals per client. Total request volume per session and per authentication period. Distribution of requests across all available endpoints and services. Time-of-day usage patterns and deviations from established patterns. Inter-request timing distributions and deviations. Sequential access patterns and their deviation from established profiles. Deviation magnitude from the established baseline behavioral profile for each authenticated client. Anomaly scores calculated by the intrusion detection system at each request, including score components and their weights. Rate of anomaly score change over time. Circuit breaker state transitions and their triggering conditions. All rate limit breach events including which specific limit was exceeded, excess magnitude, and duration. All leaky bucket overflow events including overflow volume. All token bucket exhaustion events and associated burst measurements. Port scan detection including source address, scanned port range, scan rate, and technique classification. SYN flood detection including packet rate, source address distribution, and spoofing assessment. UDP flood and amplification detection. HTTP flood and application-layer attack detection. Slowloris and slow-read attack detection. Protocol confusion and malformed request patterns. Geofencing violation attempts from addresses originating in non-whitelisted regions. Replay attack detection through duplicate nonce identification and timestamp drift measurement. Session fixation attempt detection. Credential stuffing pattern detection. Distributed attack pattern recognition across multiple source addresses. Behavioral clustering to identify coordinated multi-source attacks.

8. Security Event Logs

Entropix maintains comprehensive security event logs for incident response, forensic analysis, legal proceedings, regulatory compliance, and continuous improvement of protective systems. Retention of these logs is required under the IT Security Act 2.0 and constitutes a legal obligation under Article 6(1)(c) GDPR.

All IP address ban events including banned address or CIDR range, triggering condition, ban duration, and issuing system component. All entries added to and removed from temporary and permanent blocklists with full audit trail. All intrusion detection system alerts including severity classification, triggering signature or anomaly threshold, affected system component, and response action taken. All firewall rule match events including rule identifier, matched traffic characteristics, and action applied. All challenge issuance events and their outcomes. All payload inspection events where suspicious or malicious content signatures were identified. All matches against threat intelligence feeds, known malicious IP lists, and ASN blocklists. Tor exit node detection events and response actions. Commercial VPN provider detection events. Open proxy detection events. Datacenter and cloud hosting provider IP identification events. Bot signature detection events with technique classification. Crawler and scraper detection events. All brute force detection events including targeted endpoint, source address, attempt frequency, lockout duration, and response action. All incidents where protective systems entered a degraded operational mode or emergency state. All manual administrative interventions in protective systems including reason, timestamp, operator identifier, and action taken. All changes to security policy, firewall rules, or IDS signatures including who made the change and when. All failed administrative authentication attempts. All privilege escalation events on Entropix infrastructure.

9. File Encryption Service

When Entropix file encryption services are engaged, the following metadata is collected and processed. File contents are at no point accessible to Entropix systems, personnel, or infrastructure beyond the client-controlled encryption boundary established by the client's own key material.

File metadata including file size in bytes, MIME type, upload timestamp, and client-provided filename stored as a hash. Client-generated content hash for integrity verification, stored only in hashed form. Encryption key identifiers assigned to each object, stored as opaque identifiers without any association to key material. Key derivation parameters used for each encryption operation including algorithm selection, iteration count, salt hash, and memory and parallelism parameters. Full access event logs per encrypted object including authenticated client identifier, timestamp, source address, and operation type for every read, write, modify, delete, and permission change operation. All failed decryption attempt events including source address, timestamp, and failure reason code. Key rotation events with old identifier, new identifier, and rotation timestamp. Object creation, modification, and deletion events. All access control modification events for encrypted objects. Integrity verification check results at each access.

Entropix does not hold, escrow, have access to, or retain any encryption key material under any circumstances whatsoever. Key derivation and management is performed exclusively client-side. Loss of key material by the client results in permanent and irrecoverable loss of access to encrypted data. Entropix bears no responsibility or liability for such loss under any circumstances. This limitation applies even if Entropix is notified of the loss.

10. Infrastructure Monitoring

For all Entropix-managed server deployments, the following operational monitoring data is collected continuously at one-second resolution unless otherwise noted.

CPU utilization at core, socket, and system level. CPU temperature and throttling events where sensor data is available. RAM utilization including used, free, cached, buffered, and swap memory. Memory error counts from ECC reporting where available. Disk utilization including used and available capacity per partition. Disk I/O throughput and IOPS per device. Disk error counts and SMART health indicators. Network interface throughput in both directions, packets per second, error counts, and drop counts per interface. Running process inventory including name, PID, resource consumption, and uptime. Process crash and restart events with exit code and restart action. Kernel log events at warning severity and above. System call error rates. API endpoint response times at 50th, 95th, and 99th percentile. API error rates by endpoint and error code. Service dependency health check results and latency. Database query response times and error rates. Cache hit rates and eviction counts. SSL certificate validity status and days until expiry. Automated backup execution status, data volume, completion time, and integrity hash. Configuration file modification events with file path, timestamp, and operator identifier. All SSH login and logout events with source address and key fingerprint. All web administration panel access events. All package installation, update, and removal events. Service restart and deployment events. Scheduled task execution results. Anomalous resource consumption events triggering threshold alerts.

11. Purpose and Legal Basis for All Processing

Every processing activity conducted by Entropix operates on one or more defined legal bases under GDPR Article 6. Processing without a valid legal basis does not occur.

Legitimate interest under Article 6(1)(f): detection and prevention of unauthorized access, DDoS attacks, abuse, fraud, credential stuffing, reverse engineering, and all other security threats. This legitimate interest overrides the interests of parties conducting such activities. Performance of contract under Article 6(1)(b): all processing necessary to deliver the services agreed to by the client in their service agreement. Legal obligation under Article 6(1)(c): retention of records required by German commercial law, tax law, IT Security Act 2.0, and other applicable regulations. Consent under Article 6(1)(a): where documented consent has been obtained from end-users by the client and documented accordingly.

Entropix does not engage in automated individual decision-making producing legal effects under Article 22 GDPR beyond security access decisions, which are subject to human review on request. Entropix does not process data for advertising, marketing, profiling for commercial purposes, or any purpose beyond those stated. Entropix does not sell, rent, license, or transfer personal data to third parties for their independent purposes.

12. Data Retention

Session tokens: cryptographically erased 1 hour after session expiry. Authentication event logs: 30 days at full resolution, then aggregated. Anomaly scores and IDS alert detail: 90 days. Behavioral baseline profiles: duration of client relationship plus 90 days. IP ban records: 180 days. Firewall and security event logs: 1 year. Security audit logs including all administrative access: 1 year. Incident response case files: 3 years. Billing records, invoices, and contract documentation: 10 years under §147 AO and §257 HGB. Encrypted file object metadata: contract duration plus 30 days after termination. Infrastructure performance metrics at full resolution: 90 days. Infrastructure performance metrics in aggregated form: 1 year. Legal correspondence and regulatory submissions: 10 years. Court orders, law enforcement requests, and responses thereto: 10 years.

Upon expiry of the applicable retention period, data is permanently deleted using cryptographic erasure where technically feasible, followed by physical overwrite for storage media that cannot be cryptographically erased. Deletion operations are themselves logged. Deletion logs are retained for audit purposes for 3 years.

13. Data Security Measures

All data at rest is encrypted using AES-256-GCM with keys managed in a dedicated hardware security module or equivalent isolated key management system. All data in transit uses TLS 1.3 minimum, with TLS 1.2 accepted only for documented legacy compatibility and scheduled for deprecation. All internal service-to-service communication uses mutual TLS with certificates from a private Entropix certificate authority. All storage is located exclusively on Entropix-controlled hardware in Frankfurt, Germany. No data is stored in shared cloud environments, third-party object storage, or any infrastructure not under direct Entropix operational control. Access to production systems uses role-based access control with multi-factor authentication mandatory for all administrative sessions. All administrative sessions are recorded in full and subject to periodic audit. Key material is never stored or logged in any recoverable form. Security controls are reviewed and tested on a regular basis.

14. Prohibited Conduct

The following actions are expressly prohibited when using Entropix services and may constitute criminal offenses under German law as cited.

Unauthorized access to Entropix systems or third-party systems using Entropix infrastructure, constituting an offense under §202a StGB. Interception of data not intended for the accessing party, constituting an offense under §202b StGB. Preparation of unauthorized access or interception through acquisition, production, or distribution of tools, constituting an offense under §202c StGB. Unauthorized modification, deletion, or suppression of data, constituting an offense under §303a StGB. Sabotage of computer systems through disruption of data processing, constituting an offense under §303b StGB. Computer fraud through manipulation of data processing for unlawful gain, constituting an offense under §263a StGB. Forgery or falsification of authentication data or digital signatures, constituting an offense under §269 StGB. Launching denial-of-service attacks against Entropix infrastructure or third parties. Conducting port scans, network reconnaissance, or vulnerability scans outside expressly authorized testing environments. Using the service to distribute malware, exploit code, command-and-control traffic, or any malicious payload. Circumventing, disabling, reverse-engineering, or interfering with any Entropix security or protective system. Sharing, reselling, or sublicensing service access without prior written authorization. Impersonating another client, user, or system. Using the service in violation of any applicable law or regulation. Attempting to extract, infer, or reconstruct information about other clients or their data. Conducting timing attacks, side-channel attacks, or any other cryptanalytic attacks against Entropix infrastructure. Introducing false or manipulated data into Entropix systems. Using the service to process data obtained through illegal means. Using the service to facilitate human trafficking, terrorist financing, money laundering, or any other serious criminal activity. Attempting to identify Entropix personnel, infrastructure locations, or internal network topology through any means. Conducting social engineering attacks targeting Entropix personnel.

15. Enforcement, Termination, and Legal Action

Entropix reserves the full and unrestricted right to take any of the following measures upon detection of a violation of these terms, applicable law, or any misuse of the service. Measures may be applied individually or in combination, immediately and without prior notice, at Entropix's sole discretion, without liability to the violating party.

Immediate and permanent suspension of all service access for the violating party without refund of any payments made. Deletion of all data, resources, credentials, and configurations associated with the violating party's account. Permanent addition of the violating party's IP addresses, client identifiers, hardware fingerprints, and all associated technical identifiers to blocklists. Disclosure of connection logs, IP addresses, timestamps, behavioral data, and all other relevant records to competent German law enforcement authorities in accordance with §§ 161 and 163 StPO. Filing of criminal complaints with the competent public prosecutor's office for suspected offenses under §§ 202a, 202b, 202c, 303a, 303b, 263a, or 269 StGB. Pursuit of civil damages under §§ 823 and 826 BGB and injunctive relief under § 1004 BGB. Emergency applications to the competent Landgericht for interim injunctions to immediately halt ongoing harmful conduct, including applications outside normal business hours where permitted by §§ 935 et seq. ZPO. Enforcement of contractual penalties where agreed. Referral to Interpol, Europol, or other international law enforcement bodies for cross-border offenses. Publication of technical indicators of compromise derived from the attack without disclosure of the attacker's identity, for the protection of the broader security community. Notification of the violating party's own internet service provider or hosting provider. Cooperation with the victim's representatives in civil proceedings against the violating party.

The violating party is liable for all costs and damages incurred by Entropix as a result of the violation, including without limitation legal fees, forensic investigation costs, remediation costs, third-party claims arising from the violation, and all costs associated with enforcement proceedings. Entropix documents all violations and enforcement actions comprehensively. This documentation may be used as evidence in civil or criminal proceedings without restriction.

16. Cooperation with Authorities and Mandatory Reporting

Entropix complies fully with all mandatory reporting obligations under applicable German and European law. Significant security incidents are reported to the Bundesamt für Sicherheit in der Informationstechnik (BSI) within 24 hours of detection as required by the IT Security Act 2.0. Personal data breaches that may result in risk to affected individuals are reported to the competent supervisory authority within 72 hours under GDPR Article 33. Entropix cooperates fully and without delay with German courts, public prosecutors, police authorities, the BSI, the BfDI, and other competent authorities upon receipt of lawful process. Entropix responds to court orders, search warrants, and lawful production orders in accordance with the StPO and applicable EU law. Users are informed of law enforcement requests for their data where legally permissible and where no authority order for confidentiality is in force. Entropix does not comply with requests from foreign governments or foreign law enforcement that are not routed through applicable mutual legal assistance treaty (MLAT) procedures or do not comply with German law.

17. Your Rights under GDPR

All data subjects located in the European Union or European Economic Area hold the following rights with respect to personal data processed by Entropix. These rights are enforceable and Entropix will not obstruct their exercise.

Right of access under Article 15 GDPR: obtain a copy of all personal data held and information about its processing. Right to rectification under Article 16 GDPR: correction of inaccurate personal data without undue delay. Right to erasure under Article 17 GDPR: deletion of personal data where the legal basis no longer applies, subject to overriding statutory retention obligations. Right to restriction of processing under Article 18 GDPR: limitation of processing in defined circumstances. Right to data portability under Article 20 GDPR: personal data provided in a structured, commonly used, machine-readable format. Right to object under Article 21 GDPR: objection to processing based on legitimate interests with effect unless compelling grounds override. Right not to be subject to solely automated decisions with legal effect under Article 22 GDPR. Right to lodge a complaint with the competent supervisory authority under Article 77 GDPR. The supervisory authority for Germany is the Bundesbeauftragte für den Datenschutz und die Informationsfreiheit (BfDI), Husarenstraße 30, 53117 Bonn, [email protected].

All rights requests must be submitted to [email protected] with sufficient identity verification information. Entropix responds within 30 calendar days. Where a request is refused, Entropix will state the reason and inform the requester of their right to complain to the supervisory authority.

18. Liability

Entropix is liable for intentional and grossly negligent breaches without limitation. For minor negligence, Entropix is liable only for breach of material contractual obligations and only up to the amount of the monthly service fee paid in the month of the breach. Liability for indirect damages, lost profit, and consequential losses is excluded for minor negligence. Liability for data loss is limited to the cost of recovery that would have been incurred with proper and regular backup by the client. These limitations do not apply to liability for death, bodily injury, or harm to health, or to liability under the German Product Liability Act.

19. Changes to This Document

Entropix reserves the right to update, expand, and amend this document at any time, including upon introduction of new services, changes in applicable law, or changes in technical procedures. Material changes are communicated to active clients by email and through the service dashboard no less than 14 days before taking effect. The current version is always available at entropix.dev/privacy. Continued use of any Entropix service after the effective date of changes constitutes acceptance of the updated terms.

20. Imprint (Impressum)

Information provided in accordance with § 5 TMG and § 55 RStV.

Service: Entropix
Contact: [email protected]
Website: entropix.dev

Responsible for content under § 55 Abs. 2 RStV: Entropix

Dispute resolution: The European Commission provides an online dispute resolution platform at https://ec.europa.eu/consumers/odr. Entropix is not obligated to participate in dispute resolution proceedings before a consumer arbitration board and does not do so voluntarily for business-to-business contracts. For consumer contracts, participation is evaluated on a case-by-case basis.

Liability for content: The content of this website has been created with the utmost care. However, Entropix cannot guarantee the accuracy, completeness, or timeliness of the content. Entropix is responsible for its own content on this website under general laws. Entropix is not obligated to monitor transmitted or stored third-party information or to investigate circumstances that indicate illegal activity.

Liability for links: This website may contain links to external third-party websites over whose content Entropix has no influence. Entropix assumes no liability for external content. The respective provider or operator of the linked pages is always responsible for their content.

Copyright: The content and works created by Entropix on this website are subject to German copyright law. Reproduction, processing, distribution, or any form of commercialization of such material beyond the scope of copyright law requires the prior written consent of Entropix.