Security, by design.

All traffic to Community Archives runs over HTTPS, encrypted in transit. Your archived content and files are encrypted at rest by our infrastructure providers.

• Members verify with their source identity — a WhatsApp phone number or Slack workspace identity — before they can read an archive.
• Admin-only settings control visibility and which groups are archived.
• Private source identity details are never exposed to other members.

Community Archives runs on Vercel for application hosting and Supabase for database and file storage. We rely on their platform security for the underlying systems.

Found a security issue? Email support@community-archives.com with the details and we'll respond as quickly as we can. Please give us a reasonable chance to fix an issue before disclosing it publicly.

This describes the security controls in place today. We'll expand this page as the product matures — we'd rather tell you what we actually do than list badges.