Privacy, plainly.

Imported source content

The messages, files, and reactions from the WhatsApp groups or Slack channels you choose to archive, with their thread structure intact.

Member identity

The phone number (WhatsApp) or workspace identity (Slack) a member uses to verify access. We use it only to confirm who may read the archive.

Admin account

The email address of the admin who creates and manages the archive, used for account access and billing.

We collect this only to build and run your archive: importing history, letting verified members read it, and keeping it available to your community. We do not use your community's content to train models, and we do not sell it.

Community Archives links to your source to read history. It never posts messages back into your community, and it never reads your one-to-one (1:1) WhatsApp chats — only the groups and channels you select.

Members see archived content according to the archive's access level, which the admin controls. Private source identity details — like a member's raw phone number — are never shown to other members.

Your archive stays available while your plan is active. When you cancel, the archive is deleted on request. To request deletion or a copy of your data, email support@community-archives.com.

We rely on a small set of subprocessors to run the service. We share only what each needs to do its job:

Vercel

Application hosting and content delivery.

Supabase

Database and file storage for your archive.

Stripe

Subscription billing and payment processing.

Slack and WhatsApp

Connectivity to import from the source you link.

No. Not to advertisers, not as training data, not aggregated, not anonymized. Community Archives is funded by subscriptions.

Questions about privacy? Email support@community-archives.com.