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.
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 not yet reportable.Published Reporting Data
| Reporting Period | Total Legal Requests | Complied Requests | Rejected Requests | Requests Where No Data Existed | Technically Unavailable Requests | Encrypted Content Requests | Emergency Requests | Account Preservation Requests | User Notifications |
|---|---|---|---|---|---|---|---|---|---|
| 2024 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2026 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
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.
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.
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 where applicable.
- Account lifecycle restrictions where applicable.
- 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
Transparency reporting has limits:- Some requests can be subject to legal restrictions.
- Some categories may be unavailable in early reporting periods.
- Aggregated reporting cannot describe every individual case.
- Publication timing can depend on legal review.
- Statistics do not replace the technical limitations described in the Legal Process Guidelines.