Skip to main content
Enigm publishes aggregated transparency reporting where legally permitted.

​
Overview

Transparency reporting supports accountability while preserving user privacy, legal compliance, and operational security. This page includes currently published reporting data for 2024, 2025, and 2026.

​
Reporting Principles

Enigm transparency reporting is guided by:
  • Accuracy.
  • Aggregation.
  • User privacy.
  • Legal compliance.
  • Data minimization.
  • Content confidentiality.
  • Operational safety.
Reports should avoid exposing individuals, sensitive legal details, internal processes, or operational security information.

​
Reporting Period

Enigm’s transparency report model is annual. Each reporting period should identify the calendar period covered and explain whether any category is unavailable, legally restricted, or excluded from public reporting.

​
Published Reporting Data

No legal requests are reported for 2024, 2025, or 2026. No user notifications were issued during these reporting periods because no legal requests were received. Enigm does not currently provide a user-notification mechanism for legal requests. Annual reports may include aggregated statistics for:
  • Total legal requests received.
  • Requests complied with.
  • Requests rejected.
  • Requests where no data existed.
  • Requests technically impossible to satisfy.
  • Requests involving encrypted content.
  • Requests involving account or lifecycle metadata.
Published reporting data is included in the aggregated table above.

​
User Data Requests

Reports may include categories for requests involving account, device, lifecycle, security, or operational data. Availability depends on whether the requested data exists, is retained, is legally available, and is technically accessible.

​
Content Requests

Content request categories should distinguish encrypted content from plaintext availability. Enigm cannot provide plaintext message content, attachment plaintext, secure call content, or user conversation plaintext when Enigm does not possess plaintext. Requests involving encrypted content should be reported in an aggregated category where legally permitted.

​
Technically Impossible Requests

Some requests are technically impossible to satisfy because the requested data is:
  • Not collected.
  • Not retained.
  • Deleted according to policy.
  • Not accessible in plaintext.
  • Protected by end-to-end encryption.
  • Held only on authorized endpoint devices.
Reports may include aggregated counts for technically impossible requests where legally permitted.

​
Rejected Requests

Rejected request categories may include requests rejected because of insufficient legal basis, overbreadth, jurisdictional issues, invalid scope, unavailable data, or technical impossibility. Public reporting should avoid disclosing sensitive legal detail about individual requests.

​
Emergency Requests

Emergency request categories may include time-sensitive requests where legally permitted to report. Emergency reporting should remain aggregated and should avoid exposing individual users or sensitive operational detail.

​
Account Actions

Reports may include aggregated account-related actions where legally permitted. Categories may include:
  • Account preservation requests when legally permitted.
  • Account lifecycle restrictions when legally permitted.
  • User notification statistics where legally permitted.
  • Requests affecting account or device lifecycle state.

​
Government And Law Enforcement Requests

Reports may include aggregated government and law enforcement request statistics where legally permitted. Categories may include:
  • Total requests.
  • Jurisdictional categories where legally safe.
  • Complied requests.
  • Rejected requests.
  • Requests involving no available data.
  • Requests involving technically unavailable plaintext.

​
Limitations

See Platform Limitations.

​
Report Updates

Transparency reports are updated as reporting periods complete and legal review permits publication. Category detail remains limited to aggregated, documentation-safe information that does not expose individual users, sensitive legal details, or operational procedures.