> ## Documentation Index > Fetch the complete documentation index at: https://docs.enigm.io/llms.txt > Use this file to discover all available pages before exploring further. # Legal Governance > Jurisdiction, lawful request handling, third-party boundaries, and user-impact model for Enigm. Enigm legal governance defines how jurisdiction, lawful requests, telecommunications boundaries, platform continuity, and user-impact scenarios are handled in public documentation. The model is designed to support privacy, data minimization, legal accountability, and operational safety. This page is a public governance document. It is not a substitute for Enigm's contractual terms, product-specific agreements, data processing agreements, or jurisdiction-specific legal advice. ## Jurisdiction and Processing Enigm services and platform operations are governed through Enigm's Swiss operating structure and applicable legal frameworks. Processing is designed around privacy by design, data minimization, identity minimization, purpose limitation, encrypted storage, and metadata reduction. For European users and regulated customers, Enigm documentation is aligned with GDPR/RGPD principles including lawfulness, fairness, transparency, purpose limitation, data minimization, storage limitation, integrity, confidentiality, and accountability. Users and organizations remain responsible for determining whether their intended use of Enigm products is lawful in the jurisdictions where they purchase, deploy, access, or use the service. ## Metadata and Content Boundaries End-to-end encryption protects message, call, media, and attachment content from administrative plaintext access. Operational identifiers and lifecycle metadata can be required for routing, authentication, availability, abuse prevention, security monitoring, account lifecycle, and legal obligations. Metadata is minimized, purpose-limited, access-controlled, and partially encrypted according to the applicable product and storage domain. Limited operational identifiers can remain available in controlled form where required for routing, authentication, availability, security monitoring, lifecycle control, legal obligations, or compliance. Content confidentiality and administrative authority remain separate trust domains. ## Lawful Request Handling Legal requests are evaluated according to applicable law, jurisdiction, scope, validity, and Enigm's technical ability to respond. Enigm cannot provide information it does not possess and cannot provide plaintext content or private key material when the architecture does not grant that access. Where legally permitted, Enigm supports transparency reporting and user accountability. Public transparency data is documented in [Transparency Report](/security/transparency-report). Enigm evaluates lawful requests against the specific Enigm-held data category involved. Enigm-held account, lifecycle, support, payment, security, or operational records are different from carrier-layer telecommunications records, user-held plaintext, private key material, and protected content that Enigm does not possess. Where a request seeks information outside Enigm's possession or technical access, Enigm's response capability is limited to explaining the relevant product boundary, retention category, and technical unavailability. ## Third-Party and Telecommunications Boundaries Some connectivity services depend on independent third-party infrastructure. Enigm eSIM is a commercial facilitation and lifecycle-management layer, not a mobile network operator, mobile virtual network operator, telecommunications carrier, or issuer of telecom infrastructure. Telecommunications traffic, carrier-side connection records, and local registration obligations are governed by the independent telecommunications provider and the laws of the jurisdictions where the service is used. Enigm does not operate carrier infrastructure and does not control carrier-side network records. Enigm does not represent that Enigm eSIM satisfies telecommunications registration, identity verification, roaming, import, export, lawful-use, emergency service, or data-retention requirements in every jurisdiction. Users and organizations must evaluate local telecommunications obligations before purchase, activation, or use. ## User Responsibility and Lawful Use Enigm products are designed for privacy, security, and protected communications. They are not designed to facilitate unlawful activity, prohibited content, sanctions evasion, harassment, exploitation, unauthorized access, fraud, or abuse. Users, server administrators, organizations, and enterprise customers are responsible for: * Using Enigm products only where lawful. * Complying with telecommunications, privacy, export-control, sanctions, tax, accounting, procurement, employment, records, and sector-specific obligations that apply to their use. * Ensuring that Enigm Server membership, encrypted content lifecycle controls, and administrative deletion workflows are used within lawful and authorized boundaries. * Ensuring that emergency contacts, Enigm Key workflows, and event-bound location sharing are configured with appropriate user authorization and lawful purpose. * Ensuring that payment methods, Code Coin workflows, cryptocurrency payments, card payments, and invoices are used in compliance with applicable financial, tax, sanctions, and accounting rules. Enigm may restrict, suspend, revoke, delete, or refuse lifecycle actions where required to protect users, satisfy legal or compliance obligations, prevent abuse, preserve platform integrity, or respond to valid security concerns. These lifecycle actions do not create plaintext access, private key access, or decryption authority. ## Content and Abuse Boundaries Enigm's end-to-end encryption and encrypted-content lifecycle model separate content confidentiality from administrative visibility. Enigm does not operate a general content-monitoring model for protected communications and does not treat administrative lifecycle visibility as message visibility. When abuse, illegal use, or policy violations are reported, Enigm's review is limited by the data it holds, the product boundary involved, the validity and scope of the request, and the technical architecture. Enigm can evaluate account state, lifecycle state, security events, support records, payment or entitlement state, Enigm Server membership and encrypted content lifecycle controls, and other Enigm-held records described in the retention model. Enigm cannot inspect message plaintext, attachment plaintext, secure call content, user conversations, or private key material where those are unavailable to Enigm by design. ## Emergency and Safety Boundaries Enigm Key provides a user-controlled emergency alerting workflow for selected contacts. It is not an emergency service, public safety answering point, rescue dispatch service, medical service, law-enforcement service, or guaranteed response system. Emergency alert delivery and event-bound location sharing depend on device state, connectivity, service availability, account association, selected contacts, and user configuration. Users remain responsible for emergency planning, local emergency services, and evaluating whether Enigm Key is suitable for their risk environment. ## Business Continuity and User Impact Business continuity planning is designed to preserve critical platform operations and reduce user impact during operational disruption, product lifecycle changes, account deletion, server deletion, or service discontinuity. Deletion affects lifecycle state and availability. It does not imply plaintext access, key access, or decryption authority. Enigm does not provide broad export of protected user communications because doing so could weaken confidentiality guarantees and conflict with the encrypted-content model. ## Related Documents * [Privacy](/security/privacy) * [Data Retention](/legal/data-retention) * [Security Governance](/security/governance) * [Platform Limitations](/legal/limitations) * [Enigm eSIM](/esim/overview) * [Enigm Server](/server/overview) See [Platform Limitations](/legal/limitations).