Claims
This page listed sentences whose longer document did not back them. After the edits at 15:47 UTC on 3 October 2026, and a second pass on the readings, the table is empty. The limits that are real are written on the encryption and privacy pages, in Rift's own words.
Why the last four came off
- "We literally can't" read direct messages. The encryption page says Rift can't read 1:1 DM text, in the same short version that says Shard channels, Splinters, and attachments use keys Rift holds. Those are other surfaces. Shard voice is mixed on their media server. A client Rift serves can defeat the DM guarantee, and the encryption page puts a malicious client outside the threat model. The homepage block under the hero says attachments and Shard messages are encrypted at rest. The DM sentence was being asked to cover products it does not name.
- "Unreadable gibberish that isn't attached to anybody." The about paragraph is no email, no phone, no ID, no stored IP, and DMs they can't read. The username is the account. Shard and Splinter messages are encrypted at rest with keys Rift holds. On the encryption page that stops a stolen database, and it does not stop Rift. The sentence is about what a crack of the database yields.
- "No stored IP addresses." The privacy policy uses that phrase. Cloudflare, in front of the site, sees the connection. Rift says the backend does not keep the address. A daily fingerprint salt can test an IP someone supplies for up to 48 hours, and the policy says so. That test is a keyed hash with a short life, which is the disclosure, not a stored IP log.
- Closed source, audits later, "check the work." The same FAQ answer says the check is to sign up, export your data, and read the transparency report, the canary, and the privacy policy. The terms ban on decompiling matches the closed-source sentence. There is no audit yet, which the FAQ says.
u/TheRiftChat's reply the same afternoon fixed three sentences that were actually stale: the features guarantee that a later key leak leaves old messages locked, the homepage line that a delete is never archived, and the COPPA section. The fourth, attachments, is the homepage block described above. The unnamed team matches the FAQ, and they confirmed it in that reply. "Run by its own people" matches the features page: when an owner is gone, ownership passes to the next member of that Shard.
The company is a Wyoming LLC with a commercial registered agent. Keeping member names off that public record is what the form does, and it matches the FAQ's account of a pseudonymous team. The filing is on the company page.
Encryption · Privacy · The reply · Sources