Ciphera Transparency Report — H1 2026 (January – June 2026)
Published: 17-07-2026 Company: Ciphera, Belgium Reporting period: 01-01-2026 to 30-06-2026 (period closed 30-06-2026 — final H1 2026 report expected by 31-07-2026) Interim snapshot as of: 17-07-2026
Note: The final H1 2026 report is still in preparation. This interim snapshot has been refreshed to confirm the numbers below are unchanged; the final report with closed-period figures is expected by 31-07-2026.
Requests received
| Category | Count | Users affected | Data disclosed |
|---|---|---|---|
| Law enforcement requests (Belgian) | 0 | 0 | none |
| Law enforcement requests (EU member states) | 0 | 0 | none |
| Law enforcement requests (non-EU) | 0 | 0 | none |
| National Security / gag-ordered requests | see warrant canary | — | — |
| Subpoenas (civil) | 0 | 0 | none |
| Data Protection Authority inquiries | 0 | 0 | none |
| Emergency disclosure requests | 0 | 0 | none |
Summary
During H1 2026 to the date of this interim report, Ciphera received zero legal process requiring disclosure of user data. This is the baseline report preceding Pulse's public launch.
Methodology
- All requests, including those ultimately not complied with, are counted.
- "Users affected" counts distinct user accounts named in a request, whether or not data was ultimately disclosed.
- Gag-ordered requests are counted only to the extent lawful; the warrant canary is the mechanism for signaling undisclosable compulsion. See
/trust/canary.
Next report
Final H1 2026 report expected by 31-07-2026. It is currently in preparation.