FAQs

A secure, encrypted communication platform for private, temporary collaboration. You create rooms or send one-time secrets. Messages are end-to-end encrypted — our servers never see or store your messages. We do not store room keys. Users are responsible for lawful and appropriate use.

The system is designed so we do not retain message content or room keys. We have minimal records. Participants are responsible for their own use of the service.

No. We store encrypted envelopes for delivery, but we do not have keys to decrypt them. We do not store room keys, one-time secrets, or user identities.

No. If you lose a room key or secret link, the content is permanently unrecoverable. We are designed not to have access.

No. We have no visibility into room participants or message content.

We do not store IP addresses or device identifiers for user traffic. We may log minimal server metrics (e.g., request counts) without identifiers.

Rooms have a configurable expiry (typically 24 hours by default, up to a maximum). When empty for a grace period or past expiry, they are tombstoned.

We cannot prevent or detect screenshots. Deniability protects against us, not against other participants. Only share keys with people you trust.

The room key is the invite link or credentials needed to join a room. Whoever has it can access the room. If you share it with the wrong person, revoke access by destroying the room and creating a new one.

You can create new invite links. There is no server-side "rotation" — you effectively get new invite URLs. Old links may still work until you destroy the room.

Destroy the room and create a new one. We cannot revoke access for specific participants because we do not know who they are.

No. Our design prevents us from attesting that a room or message existed. That is intentional.

Tokens fund the service. They are prepaid room keys for creating rooms and burn-after-read secrets.

A payment record in Stripe and a bundle code. We do not link the purchase to any room or session. The bundle code is shown once; we do not store it in a way that links it to you.

We have no way to verify your purchase or identity without a transaction identifier. If you provide a Stripe payment/charge ID, we may be able to investigate billing issues.

Token purchases are generally non-refundable. Exceptions may apply where required by law. Contact support with your Stripe transaction ID if you believe a refund is owed.

Contact support with your Stripe transaction ID. We can verify the payment and issue replacement bundle codes. Without a transaction ID, we cannot investigate.

Billing and token issues that can be verified via a transaction ID. We may help with payment success but missing tokens if you provide the Stripe payment/charge ID.

Room content, message recovery, identity verification, or anything requiring visibility we do not have. We cannot recover lost room keys or one-time secrets.

Use the Support form and optionally provide an email or other contact method. We do not have your details by default. If you want a response, you must voluntarily provide contact information.

We do not monitor, inspect, or log communications. We have no visibility into room participants or message content.

Abuse reporting is limited by design. We cannot verify or investigate reports about room or message content. If you experience harm, consider local resources (e.g., law enforcement, trusted contacts).

Leave the room and do not share more information. Consider local authorities or support resources. We cannot intervene in specific rooms because we cannot see them.

A command-line tool for offline room creation, encrypted messaging, file transfer, and burn-after-read secrets. It runs entirely on your device with no server dependency for ceremony operations. Download it from our Download page.

An iOS app is in development. It uses the same Rust cryptographic core as the CLI, compiled as a native library. Android support is planned.

Yes. Monero payments create no identity linkage between payment and token issuance. A fresh one-time address is generated for each payment, and payment records are deleted after tokens are delivered.