Skip to main content
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.

​
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.

​
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.

​
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.

​
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. See Platform Limitations.