1. Messages are redacted after 12 hours, and server side metadata associated with the social graph is purged after approximately 1 day. The 1 day retention window is intentionally short and aligned with the redaction schedule, once the 12hr window has passed, the message is no longer recoverable, and any related data is removed by 24hrs.
We also enforce automatic weekly device logouts to reduce client side session persistence and limit residual local metadata. In addition, we maintain a live Technical Verification panel on our website that provides real time status of the redaction process. It can be manually verified by any user and is continuously monitored. If the server becomes unavailable or redaction processing fails, this will be detectable through stale receipts.
2. Most Matrix servers operate in a federated model, where data is shared across servers according to federation rules and local retention policies. Tor onion service deployments are niche. Ephemere is a NON-federated Hardened Tor and clearweb server (two options - both highly secure) and is explicitly designed as an ephemeral messaging environment, which is the basis of its name, which essentially means temporary state.
Matrix does not natively provide automatic redaction across the system, so we use a purpose built script to enforce redaction in a deterministic and automated way. We do not rely on bots, which can introduce reliability, latency, and client side intrusion concerns. To our knowledge, this approach is not widely deployed across servers.
The result is a materially different operational model, built for users who need communication without persistent record retention. This includes disabled backups and non recoverable message data.
Contact Support to Learn more