Choose group messaging privacy settings by matching each space to its job. Use stronger privacy for sensitive direct messages, small trusted groups, and conversations where server-side search or automation is not worth the risk. Use server-readable spaces when the group needs discovery, moderation, bots, previews, exports, or shared community content. A good privacy model is not one global switch. It is a set of clear choices for different kinds of communication.
What should be private first?
Put private-first protection around conversations that would be harmful if exposed as readable server archives:
- Personal plans, health, finance, family, or location details.
- Sensitive team or creator coordination.
- Small trusted group conversations.
- Attachments that should not be stored as plaintext on a server.
- Conversations where losing search or automation is acceptable.
In Arcana, current direct messages and group DMs use alpha/simple P-256 device-envelope encryption. Encrypted attachments stay ciphertext-only on the server side, and push notifications avoid plaintext message content.
When should a space stay server-readable?
Some collaboration features require content the server can read. That does not make them bad spaces. It means they have a different trust model.
| Use server-readable spaces when you need | Why |
|---|---|
| Search | The server can index content for fast lookup. |
| Moderation and safety review | Moderators and support flows can inspect reported content. |
| Apps, bots, and previews | Automation can transform, summarize, or enrich content. |
| Exports and compliance workflows | The service can package readable records when required. |
| Public or semi-public discovery | Members can find posts, channels, pages, and resources. |
Arcana communities can mix public, permissioned, and stronger private spaces. That makes it possible to put announcements, docs, and shared resources in server-readable spaces while keeping sensitive conversations elsewhere.
What does encryption not solve?
Encryption is a boundary, not a spell. It limits what the service can silently read or store as plaintext, but it does not protect every risk.
Encryption does not stop:
- A recipient from copying, forwarding, screenshotting, or describing content.
- A compromised device from exposing plaintext after decryption.
- A malicious browser extension from reading what appears on screen.
- Metadata needs such as account, device, membership, routing, delivery, and abuse-prevention records.
- Feature tradeoffs in encrypted spaces.
That is why Arcana explains the privacy boundary directly instead of claiming every surface has the same protection.
How should a group decide?
Use this simple decision path:
- If the conversation is sensitive, start in a protected DM or group DM.
- If the content needs to be discovered, searched, moderated, or reused, use a server-readable community space.
- If the information should outlive chat but does not need DM-style encryption, use a shared Workspace note or community page.
- If the space needs both privacy and community structure, accept that some features may be reduced.
- Revisit the decision when the group grows or the content changes.
What is a practical Arcana setup?
For most groups:
- Use DMs and group DMs for sensitive or fast-moving conversation.
- Use community posts for announcements, media, and longer updates.
- Use Workspace notes for guides, links, and decisions.
- Use calendars for busy/free planning without exposing every external event.
- Use roles and permissions to control who can see or manage shared spaces.
That setup keeps privacy where it matters and keeps collaboration features where they are useful. See the product overview or join launch updates for availability.