Privacy

What Fold keeps, and where.

Effective 29 October 2026 · founding beta

Fold is designed to minimize what a service operator can learn. This notice describes the shipped default service at fold.bruket.co; a self-hosted relay has its own operator and policy.

On your devices

Fold stores account keys, device keys, contacts, conversations, message bodies, attachments, voice messages, profile photos, drafts, settings, receipts, and on-device memory in an encrypted application store. Your device and filesystem can still expose access patterns, backups, crash data, or plaintext while Fold is unlocked. Fold does not send message contents to an analytics service.

On the relay

The relay stores opaque mailbox capabilities, sealed envelopes, encrypted bundles and recovery vaults, temporary encrypted file chunks, public handle cards, signed Pages and posts, public images, key-transparency entries, short-lived call-routing state, and—only where you or a store build turned them on—phone push targets and reports. Private-message bodies, contact names, profile photos, and conversation identifiers are not fields in the relay envelope table; a profile photo travels only inside the encrypted conversations you share it with.

A file larger than 1 MiB is uploaded once as encrypted chunks that the relay keeps for at most 30 days, or until the sender withdraws the message. The relay can see how many chunks there are, their sizes, and when they are stored and fetched, never what they contain.

When Bruket removes public material that is illegal to host from its relay, it keeps a log of each removal: the address of the Page, post or comment, the public note shown in its place, the time, and the addresses of any pictures removed with it and of the other public records that showed them. The log holds none of the removed content and is kept without a set expiry. The notice left in place of what was removed stays until Bruket lifts it, also if the owner deletes everything they published; a Page's notice also goes when the Page is published again with changed content. While a Page's removal stands, the relay also keeps a fingerprint of the removed Page's name, introduction, links and portrait, not the content itself, so that a Page with the same content can be refused whatever else about it changed, and one whose content changed can replace the notice; the fingerprint goes with the notice.

The service and its infrastructure providers can observe IP addresses, request time, route category, byte size, response status, and opaque capability identifiers. Those facts can reveal communication timing even when content stays sealed. Application logging is designed to use route templates rather than capability-bearing URLs.

Public material

A handle, Page, public post, public comment, link, and public image are deliberately public once published. Anyone can read a public Page and its posts on the web at fold.bruket.co/@handle without Fold; that page sets no cookies and runs no scripts, and its visits are seen by the relay and Cloudflare like any other request. Public material can be copied by other people and caches. Withdrawing authorization or deleting at the current relay cannot recall copies held elsewhere.

Phone notifications

If you turn on notifications in Fold on a phone, the relay stores a push target beside your mailbox: an Apple push token, or the address of the UnifiedPush distributor you chose on Android. When something arrives, the relay sends that target a wake-up that says only whether it is a message or a call, and the phone then fetches and decrypts it itself. Apple or your distributor learns that your device was woken and when, never who wrote or what was said. Turning notifications off or deleting the mailbox removes the target. Fold does not use Google's Firebase Cloud Messaging.

Reports

Fold installed from the App Store or Google Play can report a public Page, post, or comment, or a person. A report sends the operator exactly what you chose: what or whom you reported, a reason, an optional note, any messages you copied into it, and which store build sent it. The operator can read everything in a report, cannot read your private conversations, and cannot verify that copied messages are genuine. A report is deleted 90 days after the operator resolves it, and in any case 180 days after it arrived. Store builds also download the operator's list of public items hidden after reports. Fold downloaded from this site has no reporting path.

Optional discovery

If you bind an email address or phone number, Supabase Auth and the configured delivery provider process that identifier and a short-lived verification code. The binding service stores a keyed digest used for discovery and the Fold account key it maps to; it is not a Fold login or recovery credential. Requests are rate-limited and replay-protected. A validated delivery job may retain the address and one-time code in Cloudflare Durable Object storage for up to one hour while it makes at most five bounded delivery attempts, then deletes it; that storage's 30-day recovery history, described below, still holds the deleted job until it ages out.

Recovery and linking

Encrypted recovery vaults and device-link staging bundles are stored under high-entropy capabilities. A capability holder may fetch the encrypted bytes; cryptographic keys remain necessary to open them. Abandoned staging resources expire. Fold cannot recover an account without the recovery material you chose.

Retention and deletion

Sealed message envelopes and epoch claims expire under the relay policy shown inside Fold. Encrypted file chunks expire within 30 days. Acknowledged envelopes are removed. Public content and encrypted vaults remain until their authorized deletion path is used. “Delete everywhere” asks the configured providers to delete what the account controls and then reports any failure; it cannot delete recipient copies, screenshots, exports, or external backups. Cloudflare keeps a 30-day change history of the relay's storage. For up to 30 days after something is deleted there, the operator could return that storage to an earlier moment and so bring the deleted record back. Fold uses that history only to recover from a failure.

Infrastructure and transfers

The default relay and download service use Cloudflare infrastructure; optional identity binding uses Supabase Auth and configured email or SMS providers; phone wake-ups pass through Apple's push service or your chosen UnifiedPush distributor. Their processing locations can differ from yours. Fold does not sell personal data, run advertising, or include a third-party tracking SDK.

Your choices

You can use Fold without a phone number or email, choose a storage posture, disable optional discovery, turn phone notifications off, self-host a compatible relay, export recovery material, inspect a custody receipt, withdraw public material, or delete an account through the app. Diagnostic export previews exactly what will be included.

Questions

Email support@bruket.co with a privacy question, after reading Fold support; report a vulnerability as the security page describes. Material changes to this notice will appear in the changelog before a new release relies on them.