Privacy
The privacy policy is dated September 2026. The data controller named at the bottom is Rift Communications LLC, a Wyoming limited liability company. That form keeps the members off the public record, in line with the FAQ's reason for a pseudonymous team. The filing is on the company page. This page follows the policy.
IP addresses
The about page and the policy both say Rift stores no IP addresses. All traffic is proxied through Cloudflare, which receives IP addresses and request headers under Cloudflare's own policy. Rift says its backend does not persist IP addresses and keeps no IP-to-account map.
Abuse control uses a one-way HMAC of the connecting address. The salt rotates daily and is destroyed within 48 hours. The policy says:
While a day's salt still exists, we could check whether a fingerprint matches an IP address someone supplies. Once that salt is destroyed, no fingerprint computed under it can be tied to any IP by anyone, including us.
They say that after the salt is gone, Rift cannot tie a fingerprint to an IP. While the salt exists, they can test an address someone supplies.
Other network facts in the same policy:
- Signup puzzles, when enabled, are counted against that fingerprint. The puzzle runs on Rift's servers, not a third-party captcha. Nothing from the check is stored on the account.
- Several brand-new accounts from the same connection deleting themselves in a day pauses new signups from that connection for the rest of the day.
- Voice operations collect country-level call usage, region, aggregate connection quality, and media traffic totals. Country hints come from the network edge and may be a VPN exit. Lookups tied to a live call expire within ten minutes of the last refresh. Pseudonymous caller keys last up to two UTC days. Aggregate stats last 90 days. They say audio and video are not retained in this feature, and the reports go to Rift, not a third-party analytics product.
- Tor is not blocked or degraded, by their policy.
On 3 October 2026 the marketing homepage's content security policy allowed scripts from the site itself, including unsafe-inline, and connections to therift.chat, api.therift.chat, and releases.therift.chat. That response had no third-party ad host. The observation is that one response from the marketing site.
Deletion and retention
Since 15:47 UTC on 3 October 2026 the homepage says the row leaves the database, and that limited moderation exceptions apply. The policy says: "When you delete a message, it is permanently purged from the database. It is not soft deleted or hidden." The same policy then says the database keeps rolling point-in-time backups of the previous seven days, so a deleted row can remain in a backup until that backup ages out. They say seven days is the whole window, and that they do not keep long-term archival backups.
More retention, all from the same policy:
- Account deletion diagnostics: a rolling five-minute trail, capped at 64 API actions, of route names, methods, status codes, and times. Not message bodies, passwords, or IPs. A completed self-service deletion saves an encrypted copy that administrators can read for 24 hours. Daily cleanup removes it, "normally within 48 hours."
- A separate receipt keeps account ID, deletion source and time, client platform, and account age for seven days.
- If the account is less than a day old, that receipt also keeps an encrypted copy of the username, the Shards joined and when, and up to 20 of the most recent Shard messages, first 300 characters each. Direct messages are excluded. Administrators can see it. It is deleted with the receipt after seven days. This exists, they say, to investigate abuse of brand-new accounts.
- Reports and the evidence captured with them are kept after the reported account, or the reporter's account, is deleted. A deleted reporter is unlinked from their reports. Messages a moderator removed stay in that Shard's mod log for up to 14 days.
- Lobby rooms are deleted when the room dissolves, "typically after 30 minutes."
- The terms, separately, say CSAM is preserved and reported where the law requires it.
The encryption page says deleting a DM removes the row, with no moderation retention copy of encrypted DM text, because the server could not read it. Attachments are removed from storage once nothing references them. The features page says mods keep an encrypted review window for deleted messages: hours for self-deletes, two weeks for mod removals. The command center on that page says 12 hours and 14 days. u/TheRiftChat wrote that shard owners had reported deletions before a review. The privacy policy states the seven-day backups and the 14-day log for messages a moderator removed. The 12-hour self-delete window is on the features page.
What an account contains
The policy lists: username, the public key derived from the Rift Key, the age-attestation timestamp, profile fields you fill in, Shard content (encrypted at rest, with keys Rift holds), DM ciphertext plus routing metadata, and attachments as described on the encryption page.
Optional connections, also in the policy:
- YouTube, if you connect an account: OAuth tokens, stored encrypted, and the channel name. Read-only access to subscriptions, liked videos, and channel name. Feeds are fetched when opened and not stored. Disconnect revokes the token. Searching YouTube without connecting uses Rift's own key.
- Apple Music and Twitch, if connected: tokens and the provider display name. Apple Music may include a music user token.
- Push tokens (APNs or FCM) plus platform, app version, and an optional device label and locale. Removed on logout, revoke, or when notifications are denied. Push for encrypted DMs cannot include the text.
- Two-factor secrets, if you turn 2FA on, encrypted at rest. No phone number required.
- Stripe, if you pay: checkout happens on Stripe. Rift says it stores an opaque customer token and subscription state (active, past due, cancelled, period dates), and that it does not receive the card, the billing address, or financial identity. Stripe receives what Stripe Checkout collects.
Crash reports
The FAQ says the app carries no analytics SDK, and that the mobile app can send crash reports you can switch off. The policy says the mobile app sends crash and error reports to Sentry: the error, the stack, device model, OS version, app version, and a short trail of recent activity (log lines, screens opened, and network requests) from just before the failure. The policy says those reports are not tied to the account and are not supposed to include messages. Crash reporting and the activity trail are on by default, each with a switch under Settings, Privacy, Diagnostics. Web and desktop send Sentry nothing.
Age
FAQ:
Being adults-only also unlocks the privacy features regulators don't permit on platforms that allow minors: no email, no phone number, no government ID, and deleted messages actually leave the database.
The signup control is a confirmation. The policy stores the date and time you confirmed you are 18, uses it as evidence of that representation, and deletes it with the account. There is no government ID check. The about page calls the product a lounge: "Sorry, kids. This one isn't for you."
Until the afternoon of 3 October 2026 the children's section also named the Children's Online Privacy Protection Act and children under 13. On the 15:47 UTC copy that statute is gone. The section says Rift is for 18 and older, does not knowingly collect personal information from anyone under 18, does not aim the product at children, and will terminate an under-18 account and delete the data, subject to obligations such as CSAM reporting. u/TheRiftChat wrote that counsel had suggested the older wording was not required, and that they removed it because it could confuse people.
That sentence is on the FAQ. The terms say a false age is a material misrepresentation and a permanent bar. Google Play lists the app as PEGI 18. The age check described in the policy is the signup confirmation.
Law enforcement, in their words
They say they will comply with valid process, review it, and push back when they believe it is overbroad. What they say they can provide: account creation date, username, Shard metadata, and DM routing metadata (participants, timestamps, delivery state). What they say they cannot provide: plaintext of end-to-end DM text, and an IP-to-account answer from Rift's own systems once the salt is gone. Emergency disclosure is allowed for an imminent threat of death or serious physical injury. Notice to the user when the law allows it.
The warrant canary and the transparency report are on the company page. As of the August 2026 canary and the July 2026 report, every counter they publish is zero. They call that a baseline.