Intelligence
Database.

Yes. The public feed is a read-only surface accessible without authentication. It remains strictly chronological to preserve the integrity of the release sequence.

No. Once a post satisfies its trigger conditions and is released, it becomes an immutable part of the cryptographic ledger. Deletion is only possible via a court-ordered administrative workflow involving a sysadmin and a sealed audit event.

The publishing engine requires a consensus (or a user-defined threshold) from approved data nodes. If sources conflict or provide contradictory data, the release is held in a 'STALLED' state until the conflict is resolved or the threshold is met.

In 'User-Managed' mode, the platform holds no recovery material. If the primary key factor is lost, the account and its associated encrypted records become permanently unrecoverable by design.

Yes, for legacy compatibility, but the UI/UX is engineered to prioritize and enforce hardware security keys (WebAuthn) and TOTP as the primary secure factors.

No. Application-level IP retention is strictly disabled. IP data is processed ephemerally at the edge for WAF and rate-limiting purposes but is never persisted in application logs or databases.

No. The protocol is designed to be decentralized at the node level. No single administrative entity has the power to silence a verified user once their release triggers are cryptographically established.